If a software development organization needs to be changed, what is the best way to go about it?
The organizations that need to undergo change are quite different from each other. One organization's (MCCA) operation and product development were chaotic and depended entirely on the heroics of a few dedicated individuals. It didn't have a product strategy and road map in place. Sales team basically sold contracts with strong penalties for non-delivery, without considering implementation in mind. Sales team bonus was linked to the sales contracts closed and hence contract closure (even at a loss to the organization) was an usual practice. Since there was no product road map in place and what a client wanted determined the product strategy, the operations and development team were at the receiving end of this practice of sales team.
MCCA's challenge was to standardize and improve the operations and make reliable the product development (with the help of a long term strategy and a road map).
Urgency of Change
Moderate; possible to stumble along
High; failure assured if not successful
Technical Expertise of Leader
Low to moderate
Style of Leader
Individuals Critical to Mission
Some key leaders and technicians
Few if any
Ability of Organization to Reform Itself, Given Support and Chance
Possible; not set in any particular way; see need to change
Support from Senior Executives
Supportive, but wary
Supportive and trusting
|Approaches to Lean/Agile Transformation|
To Summarize, most books introduce theory by providing abstract details. This book approaches the problem differently, takes the reader through the specific details of implementation in two totally different organizations with the people and political aspects. And where ever needed, theoretical aspects of Agile and Lean are also discussed and key decisions are explained in detail. This has the advantage of making the transformation realistic and story stick. Recommended reading.