Articles for category: Delivery

When Digging Holes

The only way to go is down when digging a hole. When you hit a rock, you switch from the big awesome tool to the small tiny tool that is slower progress but gets the job done. When one obstacle is cleared, you keep digging further and further until you hit the next one. Until you finally hit the bottom, and then you’re there and you’re done. You never know how far you are to your goal because you can see past the rock and sand, all you can see is what is in front of you, and what is

Return of the Bugs

The best thing about writing code is the immediate feedback. It works or it doesn’t. Your code pumps out oodles of value or it returns bugs. Bugs are great, they never go out of style and you get the same level of response to what you are doing – immediate feedback as to whether you’re on the right path or the wrong one. Never fear the bug, fear the program that has no bugs.

The Wheel doesn’t Need to be Reinvented

Doing everything differently for every project isn’t going to help you move faster. Redefining your methodology during a project is never going to work, that’s an outside-of-project task when no project will be affected. Tweaks are good, but changes are not good. Tweaks – “Let’s log these types of issues as bugs instead of tasks” Changes – “Let’s stop using sub-tasks and stories and go to epics and tasks” Your methodology might not do one thing, it doesn’t mean you need to throw it out.

Commitment to the Idea

The first thing everyone wants to do when the idea goes sideways is to change. Do something different. Throw it all out. Start over. Give up. The moment those thoughts enter your mind, that is the first test of the idea’s strength, can it stand the test of being kicked, can it get knocked down and stand back up again, can it rise up. Don’t stop at the first sign of distress, this is the proving moment your idea has been begging for – put me to the test, break me, make me stronger.