A comprehensive collection of insights, methodologies, and findings from my extensive engagements in Agile hardware and software development.
Hardware development is not “software development with longer lead times.” This executive briefing explores Agile approaches adapted specifically for complex hardware-development environments.
Hardware product development is subject to recurring problems that increase cost, schedule risk, and difficulty adapting as development progresses. This paper examines these pathologies and shows how an appropriately adapted Agile development system can help address them.
A practical guide to applying Agile across the enterprise, from individual teams to programs and portfolios. The book provides frameworks and techniques for Agile Project, Program, and Portfolio Management, with particular attention to the challenges of developing complex hardware, software, and integrated hardware-software products. It covers Scrum, Kanban, Agile Program Management, Agile Portfolio Management, governance, planning, estimation, team organization, dependencies, requirements, and decision-making.
This is the foundational publication on how to develop hardware products using an Agile process. It reflects 18 months of my original research into the relevant issues and has been the basis for my subsequent work in the field.
Thermo Fisher Scientific makes biotechnology equipment and supplies. This case study of an Agile transformation for the company shows lessons learned from my first Agile hardware engagement. The lessons aligned surprisingly well with the predictions of my white paper, Agile Processes for Hardware Development.
Gartner is a highly respected research and advisory company focusing on business and technology topics. This briefing that I delivered to Gartner expresses the basic drivers and challenges of implementing hardware products with Agile processes.
This presentation lays out the findings from my original research into the nature of Agile hardware development. It provided the foundation for all subsequent work I have done in this area.
This case study of Accela shows the fine details of their first Release Planning experience. It makes a good reference for any team or company that is about to have their first such experience.
The development of medical products is regulated by the US Food and Drug Administration, whose regulations permeate all aspects of development. In spite of some beliefs to the contrary, FDA rules and Agile development can coexist without any difficulty. This paper addresses common issues with FDA regulation, especially around requirements management and traceability of test cases.
This paper examines some misconceptions around the inability to hit dates in product development with Scrum and clarifies that Scrum is actually a very date-oriented process.
This paper conducts an analysis of two projects, both intended to produce the same Business Intelligence and Reporting system. One uses the classic Waterfall method, while the other uses an Agile process. The two projects are stress-tested with unforeseen challenges and delays, and the results are analyzed to show the differences in outcomes for the two projects. The Agile project emerges as the clear winner when uncertainty is high.
Plantronics has a lengthy pedigree in making audio headsets of all kinds. The Plantronics case study highlights the issues and successes of an Agile hardware process applied to a Research and Development organization.
This was a large Agile transformation, involving 14 teams spread across three continents. The case study documents the before and after states and describes basic elements of the transformation.
Bird Technologies makes radio-frequency communications products and test equipment. I developed this case study because the Agile Alliance wanted me to deliver a presentation about the transformation work I did for Bird at an Agile Alliance conference. It highlights the challenges and successes of Bird’s Agile hardware transformation.
This case study of the Thermo Fisher transformation was written up by and appeared in AgileVox magazine, a Scrum Alliance publication. It overlaps with the above case study but provides more perspectives from the participants in the transformation.
The Scrum4HW conference was held under the auspices of the Scrum Alliance, to explore the possibility of using Scrum for hardware development. I was contacted and asked to deliver a keynote presentation due to the article in AgileVox magazine about my introduction of Scrum for hardware development at Thermo Fisher Scientific. This presentation is the one that I delivered to the conference.
Project, Program, and Project-Portfolio Management Organizations need to evolve from their classic roots in order to accommodate Agile processes. This paper analyzes the impacts of Agile processes on PMOs, PgMOs, and PPMOs. It reveals a surprising discovery, namely that the impact decreases as one moves from the PMO, through the PgMO, to the PPMO, because the PPMO is found to have a substantial “Agile flavor” from the beginning.
The purpose of this lengthy white paper was to develop scaling concepts for the Agile world. It pioneered Agile versions of Program and Portfolio management. The basis for the entire paper is a definition for governance that I devised for it, namely, “Governance is the formalization and exercise of repeatable decision-making practices.” Much of the content for this paper was folded into the Sage book.