I don’t have to tell you, developing software is risky business. You need a method to help you protect and guide your investment in the team and product.
Implementation may not turn out as well as hoped: unforeseen bugs arise; edge conditions crop up that no one anticipated—and are really hard to fix now. Software that worked fine in development suddenly can’t scale as needed. Usability is questioned as the real needs of users drifted during development. The list goes on…
Our solution to all these problems, and more, is to use Tracer Bullet Development.
A Tracer is a thin, full-range slice of functionality that always works. It’s code that goes all the way from user input to backend, with all the plumbing in the middle: end-to-end. A Tracer is skeletal-thin, with stubbed-out, canned data at first.
Tracer code is easy to write, easy to change, easy to work with.
From there, the team GROWS the code bit by bit, evolving it in accordance with other GROWS principles, so that problems are identified early and often, and fixed easily and cheaply, while they are still small.
Protect your investment by using Tracer Bullets to get meaningful results early.
Next> Make Accurate Decisions with The “Continuous Paradigm”
"I especially like the GROWS fixed-rate understanding of team velocity. I've used that idea on a project where I was able to show that given our task list and our current velocity (reported daily on a wall calendar), we needed help. We got it, and I was then able to show we were on track."
—Mike Bonar, Victoria, BC
"The themes that hit closest to home for me were aligning my work with Executive Vision/Initiatives, permitting Experimentation and tracking my growth through a Learning Journal. I recommend learning how the GROWS™ Method can help your team grow through the application of Agile and Lean methodologies and beyond."
—Harold M, RTP, NC
"Spread this information to masses—this is what the real world needs"
—Zemira L, GROWS Tutorial