iterative development
“It’s not the pants, it’s the people in the pants”: Learnings from The Gap Agile Transformation
Tue, 2008-02-19 01:13 — Michael ElbazAfter 7 years of traditional IT delivery, Gap Inc. Direct decided to adopt Agile. This experience report discusses three key factors that contributed to our successful (and ongoing) Agile transformation: 1. Ambitious Pilot Project 2. Massive Investment in Continuous Integration 3. Rethinking our Assets
Successful Customer Collaboration Resulting in the Right Product for the End User
Mon, 2008-02-18 16:27 — Sean CohanIn May 2007, our DISA customer asked Pragmatics to support the requirements definition and development of a new web application for the Joint Forces Command (JFCOM) Joint Staff (JS). JFCOM needed to have the application built, delivered and fielded in a tight, six-week time frame.
Embrace Uncertainty, why in Agile development knowing what you want may be an impediment to getting it
Sat, 2008-02-02 18:36 — Jeff Patton
When Kent Beck first published Extreme Programming Explained in 2000 he invited us to embrace change. Certainly XP’s and Agile Software Development’s value system and practices support that. However, succeeding in Agile processes now requires more. We’ve come to value the successful delivery of the outcome of our work. It’s the value our “user stories” bring to business and end users that use the software that matter most. If user stories are a means to an end, then it’s the end that matters most.
