Bob Hartman's presentation on 'Simple Agile' outlines principles for effective agile practices, emphasizing collaboration, prioritization, and continuous improvement. The document also discusses the importance of simplicity in agile processes, with a focus on delivering value daily and respecting all team members and stakeholders. It includes questions to evaluate agile effectiveness and highlights the benefits of incremental improvements in team performance.

1. Simple AgilePresented by Bob HartmanAgile Cooperative Founding Memberbob.hartman@agilecooperative.comhttp://www.agilebob.com Presentation Copyright © 2009, Agile For All, LLC. All rights reserved.

2. Bob Hartman (Agile Bob)30+ years of software industry experience

3. Certified Scrum Coach (CSC)

4. Bachelor and Masters degrees in Computer Science

5. Roles included Tester, Developer, Dev Manager, QA Manager, Product Manager, Project Manager, VP…

6. Started with agile in 1999bob.hartman@agileforall.com303-766-0917blog: www.agilebob.com2

7. About YouHow 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

8. Which system is “simpler”?AB4

9. Principles for “Simple Agile”CollaborateWork togetherHonor prioritiesRespect the customer, the process, the product, the team and each otherDo the simplest thing that works – then stop!Improve every iteration5

10. 6Collaborate

11. What was actually said"They inherited the earth and then the army came and scorched it."7

12. 8Work Together

13. 9Planning

14. Honor Priorities10Honor Priorities

15. Why is this NOT a goodProduct Backlog???Reports, Admin functions, Single sign-on, Expert mode, External API, DB speedups11

16. Why is this NOT a goodProduct Backlog???Prio:FunctionA: ReportsA: Admin functionsA: Single sign-onB: Expert modeB: External APIC: DB speedups12

17. 13Swarm

18. 14Deliver Value – Every Day!Photo credit: woodsy on sxc.hu

19. 15Respectthe customer, the process, the product, the teamand each other

20. Do the simplest thing that works – then stopIt should be a swingIt should rotate easilyGiven it is solid, when it is under pressure, it should still workFrom the acceptance criteria on the flip chart, what are we building?16

21. Do the simplest thing that works – then stopIt should be a swingIt should rotate easilyGiven it is solid, when it is under pressure, it should still workWould this work?Would this work?17

22. Do the simplest thing that works – then stopIt should be a swingIt should rotate easilyGiven it is solid, when it is under pressure, it should still workWhat about this?18

23. Do the simplest thing that works – then stop19How do we make sure we get the right one?

24. Improve20“I do one thing. I do it very well. Then I move on.” – Charles Emerson Winchester III on M*A*S*H

25. 2155% of agile teams answering surveys have improved at least 25% in:ProductivityTime to MarketReduction of DefectsStakeholder Satisfaction

26. 22Getting 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 Hartmanwww.agilebob.combob.hartman@agilecooperative.com303-766-091724

29. 25Agile Adoption: The Real StoryOctober 20, 20099am-4:30pmHoliday Inn Express7380 SOUTH CLINTON STREETENGLEWOOD, CO 80112(Across from Maggiano’s restaurant)Learn more at www.agilecooperative.com