1 / 27

The Agile Primer

The Agile Primer. patrick.kua@thoughtworks.com. July 2008. Hopes and Concerns. Agile Methods. Agile Values & Principles. Software Engineering. Agile Practices. Our Roadmap. Agile Methods. Agile Values & Principles. Software Engineering. Agile Practices. Our Roadmap. The Start.

myrna
Télécharger la présentation

The Agile Primer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Agile Primer patrick.kua@thoughtworks.com July 2008 © ThoughtWorks 2008

  2. Hopes and Concerns © ThoughtWorks 2008

  3. Agile Methods Agile Values & Principles Software Engineering Agile Practices Our Roadmap © ThoughtWorks 2008

  4. Agile Methods Agile Values & Principles Software Engineering Agile Practices Our Roadmap © ThoughtWorks 2008

  5. The Start © ThoughtWorks 2008 © ThoughtWorks 2008

  6. We started with Software Engineering © ThoughtWorks 2008

  7. © ThoughtWorks 2008

  8. © ThoughtWorks 2008

  9. NASA’s Defect Density Pretty good, right? © ThoughtWorks 2008

  10. NASA’s Defect Density (another data point) © ThoughtWorks 2008

  11. Other Heavy Weight Methodologies Waterfall SEI/IEEE Project Standards and Definitions Requirements Engineering Project Management Body of Knowledge (PMBOK) Sometimes, heavy weight methodologies work, but there are extensive costs, and the risk in using themin dynamic environments is high. © ThoughtWorks 2008

  12. Agile Methods Agile Values & Principles Software Engineering Agile Practices Our Roadmap © ThoughtWorks 2008

  13. Agile Lean Software Development XP DSDM Iterative and Incremental Development (1930) RUP ASD CMMI Crystal Family FDD Scrum Mercury Space Program (Iterative) (1957) 2 Pass Development (1970) © ThoughtWorks 2008

  14. Agile Methods Agile Values & Principles Software Engineering Agile Practices Our Roadmap © ThoughtWorks 2008

  15. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Working Software Comprehensive Documentation Individuals and Interactions Customer Collaboration Responding to Change Processes and Tools Contract Negotiation Following a Plan OVER OVER OVER OVER That is, while there is value on the right, we value the items on the left more. © ThoughtWorks 2008

  16. 12 Principles Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Working software is the primary measure of progress. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Continuous attention to technical excellence and good design enhances agility. Business people and developers must work together daily throughout the project. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. © ThoughtWorks 2008

  17. Agile Methods Agile Values & Principles Software Engineering Agile Practices Our Roadmap © ThoughtWorks 2008

  18. Time 3 months Waterfall Methodology Deployment Analysis Design Coding Testing Effort © ThoughtWorks 2008

  19. 3months Agile Methodology Deployment Analysis Design Testing Coding Time Iteration 1 Effort © ThoughtWorks 2008

  20. Iterations Common Agile Practices Release Iterations Iterations User Stories User Stories User Stories User Stories User Stories User Stories User Stories User Stories © ThoughtWorks 2008

  21. Story writing (future) Development (current iteration) Testing (current iteration) Co located teams Retrospective Showcase Daily stand up What an iteration might look like Start of Iteration Iteration Planning Code reviews © ThoughtWorks 2008

  22. Story writing (future) Development (current iteration) Testing (current iteration) Daily stand up A specific practice… Start of Iteration Iteration Planning © ThoughtWorks 2008

  23. The daily stand up… Yesterday, I tried working on that invoice report but couldn’t because our test environment wasn’t up I worked on the billing agent yesterday and refactored out a common utility for the printout of the bill Let’s go see Dylan’s team after this to try and resolve it I spoke to the infrastructure team yesterday and we won’t get a build environment until next week. Can we make do with what we have for now? Today, we’ve got the customer showcase for the last iteration. I’m sure we can get some useful feedback and would be good if everyone heard it firsthand. Hey, that’s great. I’ll need that when I get to the overdue bill story later this week. Can you show me that after stand up? I’ll be there I guess so Me too Sure No worries © ThoughtWorks 2008

  24. Story writing (future) Development (current iteration) Testing (current iteration) Co located teams Daily stand up A specific practice… Start of Iteration Iteration Planning Code reviews © ThoughtWorks 2008

  25. Co-located team + Code reviews This is turning out harder than I thought. Maybe I should for help. I’m currently in the middle of … and keep seeing … What do you reckon I should do? Right! That’s great. Maybe we can try … or … I’m not sure if I really understand the problem. Let’s white board this Sure Hey Ava, Can I get you to look at this? So it’s a bit like … and a bit like … type typetype... Ok, so first … and then … right? type typetype... Hey Connor. I heard you talk about adding in … When we talked about that story, you remember that the user would be happy with just … instead of that? Hang on! We can do this and it’d be much simpler Yup! Really? That makes it really simple then! © ThoughtWorks 2008

  26. Back to… Hopes and Concerns © ThoughtWorks 2008

  27. Questions? © ThoughtWorks 2008

More Related