After a year of development and much learning, the JavaBrew team has completed their agile project for a new smart coffee maker. In this chapter, we review the results of their effort and conduct a post-mortem of their Modified Agile
It’s been ten weeks since the JavaBrew agile team started development on their new smart coffee maker and they are now competing sprint five. The team is nearing their product launch! Unfortunately, they have have a major design problem. It
It’s been ten weeks since the JavaBrew agile team started development on their new smart coffee maker and they are now competing sprint five. This also marks the completion of their first iteration — a major milestone. But the team only completed
After completing their MAHD On-ramp planning, in Step 6, the JavaBrew team has spent the last two weeks working on their first sprint. All is good, but the reality of execution has started to highlight some flaws in their agile
In steps one through four, the JavaBrew team is worked through the MAHD On-ramp to write user stories, identify major product attributes, develop an iteration plan and create the backlog. The team is now ready to begin execution with their
In step four, the team is now ready to develop their backlog — the prioritized list of work items that need to be done. Since the team is still engaged in On-ramp planning (and haven’t even started their first sprint),
Agile for Hardware Is Different By now you are probably thinking about Agile, but not sure if Scrum or typical agile for SW methods work. And you’d be right to be skeptical since directly applying agile methods can lead to
The JavaBrew team has gathered to execute the next step toward developing their cutting edge Smart Coffee Maker. In the previous step, Lynda, the Product Owner and Jordan, the Agile Project Manager, kicked off their smart coffee maker agile project.
As with any process, you need people with clear roles and responsibilities. To effectively lead and manage the application of the Modified Agile for Hardware Development Framework, we describe two key roles below in the form of job descriptions. These
Traditional development projects typically get kicked off by writing a lengthy Product Requirements Document (PRD) and then passing it to R&D for review and scoping. The expectation is that the product is fully defined based on extensive customer and market
Register for the MAHD Community to get access to member resources and new tools and tips directly to your email.
© 2023 MAHD Framework, LLC
