1. 4/23/ :45 PM
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. A Perspective on Agile Development
Colin Bird
Founder
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Mission
RippleRock formed in 2009 to dedicate itself to the task of assisting customers drive dramatic improvements in their software development capability.

4. Agile is Mainstream!

5. Reasons For Adopting Agile

6. Benefits of Agile

7. So... Why do we see: Flaccid Scrum ??? Martin Fowler on Flaccid Scrum

8. Deliver production quality software every iteration
Because …
Appropriate engineering discipline, skill and practices are not applied
Scrum doesn’t explicitly define engineering practices
But … they are not optional if you want to:
Deliver production quality software every iteration

9. Mounting Technical Debt
Sprint 1
Debt > Sprint
Sprint 2
Sprint 3
Sprint 4
Sprint 5

10. Looking inside the Sprint …
Analysis-Design-Development-Deployment-Testing
Mini waterfall – testing falls off the end

11. Task Focus
Good progress on tasks …
But is this the full story?

12. Story Focus Story completeness reveals a different picture …
Too much work in progress
Not getting stories “Done”
No time to test

13. Other aspects of technical debt
Organic architecture
Little refactoring
Lack of automated Unit Tests
Infrequent integration
Mounting regression test effort
Lack of automated functional testing
No performance testing
Bugs – known and unknown

14. What it should look like …
Sprint 1
Analysis
Design
Dev
Deploy
Testing
Analysis
Design
Dev
Deploy
Testing
Analysis
Design
Dev
Deploy
Testing
Analysis
Design
Dev
Deploy
Testing
Analysis
Design
Dev
Deploy
Testing
Analysis
Design
Dev
Deploy
Testing
Analysis
Design
Dev
Deploy
Testing
Rapid cycle – minimal testing lag

15. Agile Practices Agile Architecture Refactoring Agile Testing
Maximise Value
Transparency
Agile Team

16. Agile Architecture Simple as possible Emergent Architecture
Mitigate technical risks early
Vertical increments
Refactoring
Patterns
TDD/BDD
Regular performance testing
Commit at last responsible moment

17. Refactoring Little and Often Unit and Architectural
Automated Unit Tests, CI, Code Coverage
Automated regression tests
Pair Programing
Code Reviews
Patterns

18. Agile Testing Whole team responsibility Automated Unit Testing
Automated Acceptance tests
Automated regression tests
TDD/BDD
Code Coverage
Continuous Integration (CI)
Regular performance testing
Test environments
Rapid/automated deployment
Zero testing lag
Definition of Done (DoD)

19. Maximise Value Granular Product Backlog Business/Customer feedback
Respond to change
Limit Work In Progress (WIP)
Get Stories “Done”
Cross-functional team
Early/frequent Releases

20. Transparency Definition of Done (DoD) Product Backlog (Stories)
Sprint Backlog (Tasks)
Bugs
Unit Test Code Coverage
Regular deployments
Empirical Driven Decisions

21. Transparency Low friction interaction with tools
Empirical data driven views of progress

22. Agile Team Self Organising Cross-functional Continuous Improvement
Co-located
Dedicated
Provided with the right tools
DoD

23. Agile Engineering Platform
Visual Studio Visual Studio Team Foundation Server 2010
Platform for Agile Engineering Practices
Integrated ALM tooling
Whole team and beyond
Automation
Architecture and refactoring
Test platform
Transparency

24. Thank you!
Contact:

25. 4/23/ :45 PM
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.