In recent years, the agile methodology, specifically Scrum, has gained a lot of traction in software development. However, this approach can also be applied to physical product development.

The traditional Waterfall method, which is a linear and sequential approach, has been the go-to method for developing physical products for many years. However, there is a growing consensus that using a hybrid approach of both Scrum and Waterfall can lead to a more efficient and effective product development process.

Scrum is a flexible and iterative approach to project management that emphasizes collaboration, communication, and continuous improvement. It involves breaking down a project into smaller, manageable parts called sprints, which are typically 1-4 weeks long. During each sprint, the development team focuses on delivering a specific set of product features, which are prioritized based on the customer’s needs.

Katherine Radeka, in her book “The Mastery of Innovation: A Field Guide to Lean Product Development“, states that

“When agile gets physical, Scrum is ideal in the early stage of development, where there are many unknowns and experimentation is necessary.”

In the early stages of physical product development, there are typically a lot of unknowns and uncertainties that need to be addressed. Scrum’s iterative approach allows for quick experimentation and testing of new ideas, which can help to reduce risks and identify issues early on. This approach can also help to keep the development team motivated and focused on delivering a tangible product within a short period of time.

However, in the later stages of physical product development, Waterfall may be a more appropriate approach. This is because at this stage, most of the features and specifications of the product have been defined, and the focus is on executing the plan to deliver the final product. Waterfall’s linear approach can provide a clear roadmap for development, with specific milestones and deliverables that need to be met. This can help to ensure that the product is developed according to the specifications and within the given timeline.

The choice between Scrum and Waterfall depends on the specific needs and requirements of a project. Here are some general guidelines on when each framework might work better:

Scrum:

• When the project requires a more iterative and flexible approach with frequent feedback loops. This typically happens at the early stage of product development, when concepts have being developing
• When there are no or limited dependencies between activities
• When the team is cross-functional and self-organizing and can collaborate closely
• When the project is complex or large-scale and requires a more adaptive approach

Waterfall:

• When the project requirements and scope are well-defined and fixed. This normally happens in the later stages of product development, when concepts have been defined and CAD models have been issued
• When changes involve CAPEX and investment, typically in the industrialization phase
• When the project has a clear and linear sequence of activities and dependencies
• When the project has low to medium complexity and doesn’t require a lot of adaptation or flexibility

While both Scrum and Waterfall have their advantages, using a hybrid approach can provide the best of both worlds. This can involve using Scrum in the early stages of development to identify key requirements, test new ideas and reduce risks. As the development progresses, Waterfall can be used to provide a structured approach to execution and delivery.

In conclusion, when it comes to physical product development, using a hybrid approach of both Scrum and Waterfall can lead to a more efficient and effective product development process. As Katherine Radeka suggests, Scrum is ideal in the early stage of development, where there are many unknowns and experimentation is necessary. While Waterfall can be more appropriate in the later stages of development, where a structured approach is necessary for executing the plan and delivering the final product.