Wrapping up a project or software release can be a real challenge. For almost fifteen years now my business partner and I have referred to the process as “snapping chalk lines.” If you are carpenter or home improvement buff you’ll know we are referring to the chalk lines you “snap” to mark where walls will go. At some point or another you have to convert the blueprint into a finished basement. That process begins when you start snapping the chalk lines. Designing is done and building has begun.
Stop scope creep now.
Decide on the final features for a software release. Then, that’s it – no more saying, “let’s squeeze one more feature in.” One sure way to introduce bugs into a project is with the unintended consequences of last minute (typically not well thought out) feature additions.
Settling on a feature set results in finite number of tasks to complete before the project is shippable. This process starts when you snap the chalk line. There is always room for incremental releases between significant versions. Save that list of features for you next incremental release.
Deciding on your chalk lines
If you are listening, your customers will decide on the chalk lines for you. Here’s a few of the projects I’m snapping chalk lines on right now. Well, the ones I can talk about at least.
- Upgraded ProofPass.com client and server application.
- Turning over day-to-day ColorMetrix marketing to a new team member.
- Planning a ColorMetrix user group meeting for April.
What chalk lines will you be snapping in 2011?
When I’m around snapped chalked lines I know that the real work is about to begin, and I typically can’t contain my excitement. But it also provides a road-marker to pause and appreciate how much work in research, planning, and design has come before that moment. Funny how different our industries are, but how important those chalk lines can be in the process.
Joe,
yes?
Sorry about that we had a Disqus comments email reply #fail. I have edited the above reply to reflect what I intended it to say from the beginning. 😉