Presentation for Agile Denver on September 28, 2009.
Abstract:
Everyone knows Agile is hard to do effectively. So how can it be simple?
It can't be simple, but keeping simple in mind can help avoid a number
of problems which tend to make agile harder! Confused? Then come to this
presentation which is designed to illuminate certain areas of agility
where teams and organizations tend to make things hard on themselves
rather than taking a simple approach.
"Simple Agile" is all about living the common agile phrase "Do the
simplest thing that works." This presentation will explore Simple Agile
planning, meetings, development, and testing along with other tangential
areas. The presentation combines some PowerPoint slides, some audience
participation and some group discussion. Come prepared to participate!
5. Roles included Tester, Developer, Dev Manager, QA Manager, Product Manager, Project Manager, VP…
6. Started with agile in 1999bob.hartman@agileforall.com 303-766-0917blog: www.agilebob.com 2
7. About You How many are currently using agile? How many are going to use agile within a year or know someone else who will use agile within a year? How many are getting all stories accepted prior to the iteration demo during at 75% of your iterations? How many want to get better at agile? 3
9. Principles for “Simple Agile” Collaborate Work together Honor priorities Respect the customer, the process, the product, the team and each other Do the simplest thing that works – then stop! Improve every iteration 5
15. Why is this NOT a goodProduct Backlog??? Reports, Admin functions, Single sign-on, Expert mode, External API, DB speedups 11
16. Why is this NOT a goodProduct Backlog??? Prio:Function A: Reports A: Admin functions A: Single sign-on B: Expert mode B: External API C: DB speedups 12
20. Do the simplest thing that works – then stop It should be a swing It should rotate easily Given it is solid, when it is under pressure, it should still work From the acceptance criteria on the flip chart, what are we building? 16
21. Do the simplest thing that works – then stop It should be a swing It should rotate easily Given it is solid, when it is under pressure, it should still work Would this work? Would this work? 17
22. Do the simplest thing that works – then stop It should be a swing It should rotate easily Given it is solid, when it is under pressure, it should still work What about this? 18
23. Do the simplest thing that works – then stop 19 How do we make sure we get the right one?
24. Improve 20 “I do one thing. I do it very well. Then I move on.” – Charles Emerson Winchester III on M*A*S*H
25. 21 55% of agile teams answering surveys have improved at least 25% in: Productivity Time to Market Reduction of Defects Stakeholder Satisfaction
26. 22 Getting 1% better every two weeks will make a team more than 25% better at the end of a year.
27. How “simple” is your agile? How many people make decisions? Do you honor product backlog priorities? How often are stories accepted? If someone has a question about how to test a particular part of a story who do they talk to? What does the Project Manager control? Are your daily standup meetings useful? What is your team working on this iteration to be better than last iteration? 23
28. Questions? Bob Hartman www.agilebob.com bob.hartman@agilecooperative.com 303-766-0917 24
29. 25 Agile Adoption: The Real Story October 20, 2009 9am-4:30pm Holiday Inn Express 7380 SOUTH CLINTON STREETENGLEWOOD, CO 80112 (Across from Maggiano’s restaurant) Learn more at www.agilecooperative.com
Notes de l'éditeur
"They inherited the earth and then the army came and scorched it."
“Mayfield College”
Pair programming demonstrationTester/Dev pairs for building tests
Planning pokerTeam estimation game
Deliver maximum value
Swarm demonstration
Means it is completed!
If you focused solely on this how would things change?
Build something small and then adjust!
You can’t improve it all, so improve one or two things at a time