The document discusses continuous improvement in agile and CMMI processes. It recommends starting continuous improvement with requirements to deliver minimally shippable products each sprint. Improvement loops should happen daily within each sprint and per sprint to refine the product and process based on retrospectives and reviews. Learning from other teams can further help continuous improvement.

1. Continuous Improvement
The Common Heart of Agile and CMMI
Tuesday, November 16, 2010

2. Introduction
Vernon Stinebaker (史文林)
Director of Technology, Perficient Hangzhou
CST
Tuesday, November 16, 2010

3. About Perficient
Tuesday, November 16, 2010

4. Tuesday, November 16, 2010

5. Continuous Improvement - Where should we start?
Tuesday, November 16, 2010

6. Requirements
Tuesday, November 16, 2010

7. Standish Group Findings
Tuesday, November 16, 2010

8. Minimally Shippable Product
Tuesday, November 16, 2010

9. Product Owner
• ROI
• Prioritization
Tuesday, November 16, 2010

10. Design
Tuesday, November 16, 2010

11. Improvement Loops
Tuesday, November 16, 2010

12. Product
• Daily
• CI
• Daily stand-up
• Per Sprint
• Sprint Review
Tuesday, November 16, 2010

13. Process
• Sprint Retrospective
Tuesday, November 16, 2010

14. Continuous Improvement
• Think Big
• Take advantage of the ceremonies
Tuesday, November 16, 2010

15. Learning from others
Tuesday, November 16, 2010

16. Tuesday, November 16, 2010

17. Q&A
Tuesday, November 16, 2010

18. Thank you!
Tuesday, November 16, 2010