"You cannot change how a team builds software without changing how it thinks about time."— S+3 Agile Field Record
The Challenge
Harley-Davidson's software-development organization operated with a heavy waterfall tradition — a legacy of the manufacturing mindset that built the rest of the company. Waterfall in a manufacturing context makes sense: physical production lines do not iterate. Software does, and a team that cannot iterate cannot compete. The Connected Enterprise initiative demanded faster delivery cycles, more responsiveness to changing requirements, and a development model that did not require multi-month planning gates for every change.
The challenge was not purely technical. Changing a delivery methodology in an organization with a deep manufacturing identity is a cultural intervention, not just a process change. Engineers who have spent their careers in waterfall are not resistant to Agile because they are wrong — they are resistant because Agile requires them to accept uncertainty as the default state, and waterfall gave them the illusion of certainty they had been trained to require.
The Intervention
Introducing Agile in a waterfall culture
Himanshu introduced the Agile framework incrementally — starting with the teams most willing to experiment and using their results as the proof point for broader adoption. This is the Shu stage of MuShuHaRi applied to organizational change: establish the practice with discipline before allowing variation. The early-adopter teams produced measurable productivity improvements and faster release cadence, which created internal pull for the methodology rather than top-down mandate.
Connected Enterprise delivery modernization
The Connected Enterprise initiative required coordinating software delivery across multiple teams with different legacy rhythms. Agile provided the common operating language: sprint cadences, retrospectives, shared definition of done. Within the manufacturing context, this was a significant cultural shift — treating software as a living product rather than a manufactured artifact with fixed specifications.
Key Results
| Metric | Outcome |
|---|---|
| Delivery methodology | Waterfall → Agile across multiple engineering teams |
| Productivity | Measurably increased (sprint-velocity tracking introduced) |
| Release cadence | Accelerated from multi-month cycles to sprint-based delivery |
| Cultural impact | Agile mindset established in manufacturing-heritage engineering org |
| Foundation for | Blueprint for all subsequent S+3 Agile framework development |
Methodology change is culture change. Start with the willing, let their results create the pull, and adoption becomes a movement instead of a mandate.