Managing software projects is complex. How long would you need to make a cup of coffee? Did you consider whether you’d need to grow the beans? Unlike physical constructions, software can be replicated at no cost. If it’s been done before, there’s little point. You are rarely in well-charted territory.

There are several well-known methodologies for software project management. Instead of detailing these, I'll direct you to external resources and focus on selecting the right approach based on the following variables:

Product Clarity: Is your product vision well-defined and precedented?

Flexibility: Do circumstances necessitate its launch by a specific date? Can you scale back your plans if necessary?

The following table suggests some methodologies accordingly:

Below, we briefly overview each scenario.

🎢 Shaping

Suited for experienced teams, this method promotes flexibility, assuming a coarse product specification can be “shaped.” It balances autonomy and structure and eschews traditional estimates for a concept known as "appetite.” Other approaches may also be suitable in this quadrant.

Shape Up: Stop Running in Circles and Ship Work that Matters

Outline of the Shape-Up methodology

👔 Agile / Scrum

Favors cohesive teams that have worked together building similar products before. Its structured approach can produce accurate estimates over time, but the number of cycles needed will vary. Short-term projects may see less benefit.

One of the tenets of Agile is "responding to change over following a plan,” so flexibility and adaptability are required even here. However, this approach offers increased predictability once a reliable velocity has been established.

ThoughtWorks and Friends on Agile Estimation

ThoughtWorks and Friends on Agile Estimation

🧑‍🔬 R&D Mode

Ideal for unprecedented projects that aim to foster innovation through exploration, this approach substitutes a rigid project management framework with a focus on learning by building, high-bandwidth communication, and serendipity.

Place Your Bets | Shape Up

R&D Approach in Shape-Up

🚨 Danger Zone

Sometimes, you are playing Mission Impossible. When in the danger zone, the lack of flexibility introduces serious risk. The best approach is to raise funds or adjust expectations to convert to another quadrant. If you must play this game, invest in prior design exploration and a team experienced in related projects. Agile/Scrum may be a good fit. Keep an eye on the accuracy of your estimates: there’s a risk they won’t be worth much. Patience and adaptability are key here: things will almost certainly not go according to plan.

Building unknown products on a tight schedule can feel like Mission Impossible