Too often, tech projects rush the planning so they can get started quickly, build, configure, shovels in the ground 🏗️
This makes everyone happy and we see ‘progress’. But inevitably the project crashes into problems. The team is then firefighting, fixing things but then more things break and more fixing.
So what do successful Tech projects do differently?
It’s not more ‘planning’ in the traditional sense. Planning is not bureaucratic, isolated, 1 dimensional thinking and Gantt charts.
Good tech project planning is iterative. It’s asking questions and validating ideas. We collaborate, explore, test, imagine, design, analyze, be creative.
As a consequence, Iterative Planning takes time. We’re spotting implications, proving ideas, and scheduling the work 🗓️.
The result is a detailed, proven, and tested build plan. This means build is quick and smooth (black swans excepted :))
🐌Slow in itself is not good.
⌛Iterative planning requires time.
👟Iterative planning makes the build go faster.
Plan Slow, Build Fast.
