How to Implement Shape Up for Product Development

TL;DR

Shape Up is a product development approach that focuses on setting fixed timeboxes and varying the scope to avoid dragging projects. It emphasizes shaping sessions where engineers, product, and design collaboratively define projects before committing resources. This method is particularly useful for teams experiencing slow progress and unclear project goals. By adopting Shape Up, teams can achieve more predictable shipping and reduce the cycle of endless sprints.

Transcript

I often use this analogy of if you're doing  a home renovation, you can have the most   beautiful rendering of the new bedroom and we're  going to have these lamps on the side of the bed that are coming out from the wall. But if you  haven't checked if there's electricity in that   wall there or not, it's going to drastically  change the cost and t... Read More

Key Insights

• Shape Up utilizes an 'appetite-driven' approach where teams set a fixed timebox, usually six weeks, and vary the scope instead of expanding timelines.
• Shaping sessions are crucial for collaboratively defining projects, involving engineers, product, and design to ensure clarity before committing resources.
• Most teams struggle with too little detail in planning rather than too much, leading to unclear project goals and dragging timelines.
• The 30-to-50-person team size is a critical point where growing startups need to adopt more structured processes like Shape Up.
• Shape Up bridges the engineering-design divide by bringing technical and product perspectives together earlier in the process.
• Breadboarding and fat marker sketching are techniques that help teams align on solutions without getting lost in high-fidelity details.
• Clear warning signs that a development process is failing include dragging projects, unclear goals, and a lack of predictable shipping.
• Shape Up shifts the PM role upstream, focusing more on problem definition and less on project management.

Questions & Answers

Q: How does Shape Up differ from traditional Agile and Scrum?

Shape Up differs by focusing on fixed timeboxes and varying the scope instead of expanding timelines. It emphasizes shaping sessions where engineers, product, and design collaboratively define projects before committing resources, reducing the cycle of endless sprints and unclear project goals common in traditional Agile and Scrum.

Q: What is the role of shaping sessions in Shape Up?

Shaping sessions are crucial in Shape Up as they bring engineers, product, and design together to collaboratively define projects. These sessions aim to achieve clarity on project goals and scope before committing resources, ensuring that teams have a clear understanding of what to build and reducing the risk of dragging timelines.

Q: Why do most teams struggle with project planning?

Most teams struggle with project planning due to too little detail, leading to unclear project goals and dragging timelines. Shape Up addresses this by ensuring that projects are well-defined during shaping sessions, with clear goals and scope before resources are committed, reducing the risk of project delays and inefficiencies.

Q: What is the critical team size for adopting Shape Up?

The critical team size for adopting Shape Up is typically 30-to-50 people. At this point, growing startups often experience the need for more structured processes to manage project complexity and ensure predictable shipping, making Shape Up a suitable methodology to adopt.

Q: How does Shape Up bridge the engineering-design divide?

Shape Up bridges the engineering-design divide by involving technical and product perspectives earlier in the process through shaping sessions. This collaborative approach ensures that both design and engineering are aligned on project goals and solutions, reducing misunderstandings and enhancing project efficiency.

Q: What techniques does Shape Up use to align teams on solutions?

Shape Up uses techniques like breadboarding and fat marker sketching to help teams align on solutions. These methods allow teams to visualize solutions without getting lost in high-fidelity details, ensuring clarity and alignment on project goals and reducing the risk of project delays.

Q: What are the warning signs that a development process is failing?

Warning signs of a failing development process include dragging projects, unclear project goals, and a lack of predictable shipping. These issues often stem from inadequate planning and unclear scope, which Shape Up addresses through structured shaping sessions and a focus on clear project definition.

Q: How does Shape Up affect the role of the PM?

In Shape Up, the PM role shifts upstream to focus more on problem definition rather than project management. This shift involves negotiating the problem space, understanding business context, and ensuring that projects are well-defined before resources are committed, leading to more efficient and predictable project outcomes.

Summary & Key Takeaways

• Shape Up is a product development method that sets fixed timeboxes and varies project scope to avoid endless sprints and missed deadlines. It emphasizes shaping sessions where engineers, product, and design collaboratively define projects before starting.

• The method is especially beneficial for teams experiencing slow progress and unclear project goals, providing a structured process that enhances predictability and efficiency. Shape Up is adaptable to various company contexts, even those unlike Basecamp.

• Key techniques include breadboarding and fat marker sketching, which help align teams on solutions without getting bogged down in details. The PM role shifts to focus more on defining problems than managing projects.