Michael K. Levine

A Tale of Two Systems (eBook, PDF)

Lean and Agile Software Development for Business Leaders

• Format: PDF

Produktbeschreibung

A Tale of Two Systems: Lean and Agile Software Development for Business Leaders reviews two fictional systems development projects. One project proves to be an abject and expensive failure, while the other succeeds in creating a major new revenue stream and solving important customer needs. Contrasting the methods employed in a traditional, process-centric 'waterfall' approach, with a lean and agile-inspired approach, this book provides business leaders with a tangible understanding of why lean thinking is so well-suited to contemporary environments requiring flexibility, speed, and the input of specialized knowledge.

---

Dieser Download kann aus rechtlichen Gründen nur mit Rechnungsadresse in A, B, BG, CY, CZ, D, DK, EW, E, FIN, F, GR, HR, H, IRL, I, LT, L, LR, M, NL, PL, P, R, S, SLO, SK ausgeliefert werden.

Produktdetails

• Verlag: Taylor & Francis
• Seitenzahl: 344
• Erscheinungstermin: 24. Juni 2009
• Englisch
• ISBN-13: 9781439803912
• Artikelnr.: 57160414

Autorenporträt

Michael K. Levine

Inhaltsangabe

The First 6 Months: September 2005-February 2006. Kicking off Project #1-TRIM: The "Troubled Real Estate Information Management" Project. Kicking off Project #2: The Cremins United Project. Two Different Approaches to the Two Different Projects. Understanding Lean & Agile Development. The CU Project Team Will Follow "The Process". The CU Project Imposes Technology Architecture from the Top. Setting Expectations for the CU Project: How Iron Is the Triangle? Don't Shoot the Messenger: The CU Project Team Meets with Management. Cutting CU Project Development Time-by a Year. Planning the TRIM Project. Planning and Managing TRIM's One-Month Sprints. Status Update for Both Projects. The CU Project's Buy vs. Build Decision. Drawing Boundaries and Tailoring Methods. The TRIM Project's 1^st Sprint Demo: A Bit behind Schedule, but Catching up. The CU Project Requirements Handoff: An Uneasy Transition. The 2^nd 6 Months: March 2006-August 2006. The CU Project Leaders Visit the TRIM Team. Checking in on the CU Project's Development: Green for Go, or Screaming Red? A Status Check: TRIM's OK, but CU May Be in Trouble. Year 2: September 2006-February 2007. A Dismal Reality Check for the CU Team. The TRIM System Goes Live; Managing Problems & Growth. The CU Project Is Finally Officially Code Complete. The CU Project Retrospective: Slipcharts and Some Towering Expertise (Too Late). The Beginning of the End: The Last 6 Months of 2 Years of Work. 18 Months In: Status Updates for Both Projects. The Decision to Go Live with the CU System. Final Lessons for Leaders. Epilogue: What We Learned from the TRIM and CU Projects.

Rezensionen

A Tale of Two Systems takes us on an intriguing and very realistic journey through the development of two systems - one a spectacular success, and the other an equally spectacular failure. It exposes in detail why one system succeeds and the other fails. In the epilogue, Levine summarizes the lessons leaders should take away from this wonderful tale. This chapter alone is worth the price of the book; following the story brings a deep appreciation of its wisdom.
--Mary Poppendieck, author of Implementing Lean Software Development: From Concept to Cash

A Tale of Two Systems takes us on an intriguing and very realistic journey through the development of two systems - one a spectacular success, and the other an equally spectacular failure. It exposes in detail why one system succeeds and the other fails. In the epilogue, Levine summarizes the lessons leaders should take away from this wonderful tale. This chapter alone is worth the price of the book; following the story brings a deep appreciation of its wisdom.
--Mary Poppendieck, author of Implementing Lean Software Development: From Concept to Cash