You might not know it, but for a while, I was (Writer)Blocked. Couldn’t think of anything new to write. Was tired with what was out there that I was reading. Thought everything that had been said had already been said. Couldn’t get started. It made me think of how many times I sat down to start a new project and stared at the screen as it asked me what I wanted to name my class…
The beginning of a Sprint and/or Release are exciting times, everyone wants to jump on every feature and story and get them done. Mid-way through either though, we start to realize that we are not going to be able to deliver it all and now we are left with a bunch of half-completed work items. It’s not a great feeling and it’s one Agile/Scrum is supposed to eliminate but still, there’s that pesky feeling we…
Because if you’re not, someone else will and when they do, they will no longer be your team, they will now be on this other person’s team. Org charts do not define who belongs to what team, they only define who you report to. We all know whose team everyone belongs to.
They aren’t going to kill you. Or the early mornings. Or everything in between. None of that is going to stop your idea from seeing the light of day. From getting your code out there into the wild for people to use. The only thing that’s going to stop it, that might kill it, is if you stop working on it because you’re worried about the Late Nights, the early mornings and everything in between.
Everyone struggles with what is actually good enough. Not because we all have different levels of what we feel is “actually” good enough but rather because we are at our most critical when trying to decide if our work is at the stage of being good enough to show others. “It doesn’t do these seven things” “I need to make one last edit” “I think it should be red, not orange.” Your good enough, my…