A presentation that I did at work to explain to non-developers the Scrum process and Agile development philosophy.

1. Scrum and the Agile Development Process

2. Agenda Introduction Empirical vs. Defined Process Agile Development Scrum 101 Scrum Overview Roles and responsibilities New Operations Team

3. Defined Process Requires every piece of work be well understood. Given a well-defined set of inputs, the same outputs are generated every time. Yummy Donuts! Donut Mix

4. “Traditional” Waterfall Job Function E Job Function D Job Function C Job Function B Job Function A Requirements Gathering Design Development Documentation, Signoffs, Handoff Documentation, Signoffs, Handoff Documentation, Signoffs, Handoff Documentation, Signoffs, Handoff Testing Launch & Maintain Advantage: Highly Logical Disadvantage: Human Beings are involved

5. Empirical Process Provides and exercises control through frequent inspection and adaptation Processes are imperfectly defined Generate unpredictable and unrepeatable outputs. Yummy Donuts! Is it soup yet? Yummy Soup! Soup Fixin’s

6. Agile Software Development Feedback Feedback Feedback v 1.0 v 1.1 v 1.2 Short Iterations Incremental Releases

8. Test

9. Design

10. Build

11. Plan

12. Test

13. Design

14. Build

15. Plan

16. Test

17. Design

18. Build

19. Plan

20. Test

21. Design

22. BuildDo a little bit of everything every cycle

23. Empirical Processes “It is typical to adopt the defined (theoretical) modeling approach when the underlying mechanisms by which a process operates are reasonably well understood. When the process is too complicated for the defined approach, the empirical approach is the appropriate choice.” Process Dynamics, Modeling, and Control, Ogunnaike and Ray, Oxford University Press, 1992 Translation into English: Inspect and Adapt

24. What are some other examples of processes suited to an empirical approach? ???

25. Roots in Lean: The Seven Wastes

26. Roots in Lean: The Seven Wastes www.dbo2.com

27. Roots in Lean: The Seven Wastes

28. Agile Manifesto That is, while there is value to the items on the right, we value the items on the left more.

29. What is Scrum? A flexible framework that is: Collaborative Iterative & Incremental Common Sense Very simple but very hard It causes change It takes discipline

30. Scrum Values Respect Commitment Focus Openness Courage

31. Scrum Roles

32. Product Manager Product visionary Maximizes business value Prioritizes and clarifies requirements

33. Product Manager Does Provide clear product direction Work with the team closely to clarify requirements Actively manages the product backlog Represents the business and customer needs

34. Product Manager Does not Assign work to the team members Give fixed date fixed scope projects without team consent Change priorities during a Sprint

35. Scrum Team Cross-functional Possesses all the skills necessary to produce an increment of potentially shippable product Team takes on tasks based on skills, not just official “role” Self-organizing Team manages itself to achieve the Sprint commitment

36. Scrum Master Similar to a Project Manager… yet different A facilitator Removes impediments

37. Scrum Master The Scrum Master does everything in their power to help the team achieve success Serving the team Protecting the team Guiding the team’s use of Scrum

38. Scrum Process

39. Product Backlog A prioritized list of requirements Prioritized by the Product Manager Product Backlog

40. User Stories One way to write a requirement Describes a WHO, WHAT and WHY scenario Describes real business value A “promise for a conversation” Has acceptance criteria to assert its behavior

41. User Story Template Express user needs in terms of what the user wants to achieve Example: As a <type of user>, I want to <goal> so that <reason/value> Always includes acceptance criteria

42. Sprint Planning Planning at the start of a Sprint by the whole team and the Product Manager Team creates tasks, estimates, and volunteers for them Sprint Planning

43. Sprints 2 week timebox of work. During the Sprint: Analysis Design Code Test A little bit of everything Sprint

44. Daily Standup A daily team meeting Keep up to date Help each other to resolve problems Daily Stand-up

45. Sprint Review A demo by the team of: Complete Fully tested Potentially shippable features Anyone can attend Sprint Review

46. Sprint Retrospective A meeting at the end of each Sprint so the team can inspect and adapt the process. Sprint Retrospective

47. Tracking Progress

48. Tracking Progress Highly visible Track the work remaining Don’t care about actual time worked

49. Burndown Charts

50. Tracking Progress Uses inspection and subsequent adaptation to optimize realization of goals. Transparency is required for inspection and adaptation Transparency requires courage and change in reward system

51. Focus My report doesn’t print right. DPR wants to change the Red Zone criteria I didn’t get my scheduled report. I want to keep track of my old comments. Can’t I add contractors during an inspection?

54. New Operations Team

55. New Operations Team Respond to small/moderate customer requests quickly Can focus on support issues when required Can focus on operations issues when required Keeps the other team focused on the release