How can the scrum framework accelerate progress and improve quality in hardware development, despite the challenges unique to tangible products?
Many similarities exist between implementing scrum in software and hardware products. You may hear that the differences between the two products are so great that scrum canβt work with both. Thatβs not true. Anytime you can encapsulate the work to be done and prioritize it against other work, you can use scrum to your immense benefit.
Anytime you can encapsulate the work to be done and prioritize it against other work, you can use scrum to your immense benefit.
Focus on Feedback Early and Often
A key element of hardware products done with scrum is to focus on feedback early and often. You may not have much to work with in the beginning, but keep producing workable increments during each sprint, and what you have to show customers and stakeholders will grow β with their feedback incorporated.
Unlike traditional hardware development, scrum encourages frequent testing and feedback, even when only partial prototypes are available. This accelerates innovation and reduces costly late-stage errors.
Early Identification of High-Risk Requirements
You save time, money, and hassle if you discover defects and problems early. In waterfall, testing was left until the end. But why test only at the end when you can test all along the way and find (and resolve) defects early?
Scrum forces timely integration between firmware and software. Scrum breaks down functional silos and gets engineers working together to solve problems rather than coming together later to fix problems.
In the daily scrum (which is no more than 15 minutes), you can coordinate whatβs been done with whatβs going to be done and list what impediments are in the way.
Open-source hardware is a gift to scrum and engineering as a whole. As open-source submissions increase, organizations can quickly and creatively implement existing designs, frameworks, and architectures that get their products to market faster.
How might early feedback and rapid iteration change the way hardware teams handle defects compared to traditional approaches?
Want to go deeper? The science behind early defect detection
Early testing and integration, as promoted by scrum, lowers the cost of fixing defects by catching them before they propagate into later stages. Research in engineering management shows that defects found during early prototyping are typically faster and cheaper to resolve compared to those found during final assembly or after launch.
Live Hardware Development: Real-World Applications
In the following sections, we discuss four examples of the scrum framework successfully used for hardware development. Each situation is unique, but the essence of scrum is consistent. For the most part, whatever the product, you can use scrum to develop it faster and with higher quality and ease.
Scrum is now being used in high-stakes hardware projects, from satellites to jet fighters, demonstrating its versatility beyond software.
Johns Hopkins CubeSat
The Johns Hopkins University Applied Physics Lab used scrum in its Multi-Mission Bus Demonstrator (MMBD) product development effort for building two CubeSat satellites. NASA sponsored the program itself.
Three key elements were identified as being critical to the success of the product:
- Scrum teams: These teams were made up of subsystem leads. All team members were co-located and given direct access to the NASA representative (the onsite product owner) for quick decision-making.
- Emphasis on a working system: Only one design review was funded, and computer-aided design (CAD) models were used to simulate and manipulate designs. Informal peer reviews were conducted throughout the product, and documentation was minimal.
- Culture of innovation: Change was welcomed and incorporated. Daily scrums were held to coordinate and identify the best ways of addressing the highest-priority requirements. Long-term planning was eschewed in favor of responding to reality.
As in manufacturing, change is inevitable in hardware products. Fortunately, change in hardware product design and development is workable and practical.
What are the benefits and challenges of co-locating hardware scrum teams with decision-makers like product owners?
Wikispeed Modular Car
Wikispeed is an all-volunteer, green prototype car designer. The company built a functional prototype car that gets 100 miles per gallon by forming self-organizing teams and using the scrum framework. The teams win races because their car is completely modular. They can swap out components based on how theyβre running that day, on that track, in that weather. Their competition doesnβt have the same ability.
Wikispeed garnered four key takeaways from its scrum experience:
- Customer feedback: Teams went to users for regular feedback and tested what they could every week.
- Sprints and reviews: Regular sprint cycles were conducted, with meetings at the end of each stating what went right and wrong.
- Transparency: All team members knew the goals, and anyone could make a suggestion.
- Peer-to-peer communication: No one person was the boss; everyone was equal and contributed to achieving the sprint goal daily.
A design approach in hardware (and software) where components can be swapped or reconfigured independently, allowing rapid adaptation and innovation.
Telefonica Digital
Telefonica Digital began as a hardware manufacturing firm that used waterfall project management. As technology changed, it began to develop more software. As the focus shifted from hardware to software, the company adapted fully to agile and scrum.
When technology and the firmβs direction changed, it returned to producing hardware. Because of its experience with scrum over the years, the company had no desire to go back to traditional project management, so it used the scrum framework for its hardware products.
The first issue was relocating the facility so employees could be co-located because the company understood the value of working in proximity. Telefonica also created a system in which it could easily procure equipment and materials on the day it needed them.
The company used scrum teams and fostered cross-functionality. It tested early and often, even using 3D printing and prototyping technologies to hasten the testing. It used lots of open hardware, which it could use for testing. At times, this process accelerated the hardware teamβs progress to the point of waiting on the software teams.
Co-locating teams and rapid procurement can dramatically speed up hardware development cycles, highlighting scrum’s flexibility in adapting to operational needs.
Saab Jet Fighter
Saab Defense uses scrum to develop the JAS 39E Saab Gripen jet fighter. Building this highly complex jet requires more than 1,000 engineers and more than 100 teams. Scrum provides team-level priorities and the transparency needed to expose, inspect, and adapt to changing variables regularly and quickly. Saab scaled scrum across multiple teams and departments.
Why building a complex fighter worked:
- Enhanced autonomy: Teams are given degrees of freedom within a clearly defined framework. The focus on autonomous teams encourages decision-making at the lowest level and reduces bureaucracy.
- Modular architecture: Saab used modular architecture to reduce monolithic dependencies and focus on flexibility for future changes.
- Continuous improvement: Retrospectives after each sprint and short feedback loops from outside the team enable product and process improvements.
How does enhanced team autonomy help in managing the complexity of large-scale hardware projects?
The practice of empowering scrum teams to make decisions within a clear framework, enabling faster responses and reducing bureaucracy.
- Scrum can be applied to hardware development as effectively as software.
- Early testing, feedback, and modularity are essential for hardware teams using scrum.
Scrum is only suitable for software development, and can’t handle the complexity or rigidity of hardware projects.
Scrum’s principles of iterative work, early feedback, and team autonomy make it highly effective in hardware development, even for complex and regulated projects.
Continuous Improvement in Scrum
Tap to revealRetrospectives and short feedback loops allow teams to regularly adapt and enhance both product and process in hardware development.
Open-Source Hardware
Tap to revealHardware designs and frameworks publicly shared, allowing teams to rapidly build on existing solutions and accelerate development.
Co-located Scrum Teams
Tap to revealTeams working in the same physical location to enhance communication, speed up decision-making, and facilitate rapid response to issues.
Which key element helped Saab successfully scale scrum across more than 100 hardware development teams?
Practice breaking down a hardware project into sprints, focusing on early identification of high-risk requirements.
- List three potential high-risk requirements for a hardware product (e.g., a prototype drone).
- Describe how you would use scrum to test and address these risks in early sprints.
Reflect on a time when change emerged during a hardware project you worked on or studied. How could a scrum approach have helped respond to those changes more effectively?
Scrum enables hardware teams to rapidly iterate, detect and resolve defects early, and incorporate innovation, leading to faster and higher-quality product development.
Team autonomy, modularity, and open feedback loops are critical for scaling scrum across complex hardware projects.
How confident are you that you can explain how scrum is applied to hardware development projects?
The Shift
- Scrum is not limited to softwareβits iterative, feedback-driven approach accelerates hardware development and quality.
- Early risk identification, modularity, and autonomy are essential for complex hardware projects using scrum.
- Open-source hardware, co-located teams, and continuous improvement are powerful enablers for scrum in tangible goods production.