Scrum without the Sugar Coating

1. Scrum without the Sugar Coating

2. You want me to do what?!

3. Introductions Panel members/roles • Gigi Zenk– Sponsor • Dianne Foster- Developer • Ben Hopkins– Developer • Ann Deuell– Analyst • Chad Baker– Tester • Irene Hill– Product Owner • Melodi Cottongim– Scrum Master • Mara Tallman– Scrum Master

4. Agenda • How we got started • Q&A (10 minutes) • Scrum process at DOL • Q&A (7 minutes) • Outcomes & what we’re doing now • Q&A (15 minutes)

5. When we started Scrum • Summer 2011 – training (6 PM’s, analysts) • 2011 Nov/Dec/Jan 2012–2 teams, training, coaching, working

6. How we got started with Scrum • Executive and staff interest • Articles from CIO • Curiosity in the Project Office

7. How we got started with Scrum • Forced ‘opportunity’ • Project – impossible timeframe for Waterfall

8. How we got started with Scrum • Formed team • Hired Coach, trainer

9. How we got started with Scrum • Team training in 3 hour blocks over six week period • Parallel to planning and running Sprints

10. How we got started with Scrum • Professional coach on-site 80 hours • Coaching spread over 3 months • Helped with • Planning • New ways of working • New ways of communicating, collaborating

11. Misconceptions getting started • Misconception: No documentation, no need to do architecture planning

12. Misconceptions getting started • Misconception: Release every sprint • Reality: It will take a while (several months) before you Might need a release every sprint

13. Misconceptions getting started • Misconception: Must have software tool to manage Scrum • Reality: Until you have your process running smoothly, a tool will get in the way

14. Misconceptions getting started • Misconception: Agile/Scrum is flexible, fluid we can do things however works for us • Reality: Scrum is a disciplined, and specific process

15. Barriers getting started • Getting enough time from team members • Changing team members

16. Barriers getting started • Product owner – big cultural shift of accountability • Confusion on roles of PM’s, analysts, product owners

17. Q&A How we got started

18. Scrum Process at DOL 2 Week Cycle

19. Roles Scrum Team Stakeholders Sponsors Steering Committee Product Users IS Supervisors Architects DBA Configuration Management • Analyst • Designer • Developers • Testers • UAT Testers • Scrum Master • Product Owner

20. Form a Team

21. Create a Roadmap 2 Week Cycle

22. Create a Roadmap

23. Sprint Planning 2 Week Cycle

24. Sprint Planning • Team members provide available hours for next sprint. • Team pulls in stories by priority, decomposes the stories into tasks, team members volunteer to complete the tasks and assign hour estimates. • Analyze the plan: fill in gaps and adjust workloads. • Team commits to delivering the sprint backlog. Save 20% of available hours.

25. Sprint Work 2 Week Cycle

26. Sprint Work Task Board Burn Down Chart 15 Minute Daily Stand Ups

27. Backlog Grooming 2 Week Cycle

28. Backlog Grooming Create Stories Prioritize Backlog Story Time = Team Communication

29. Demo 2 Week Cycle

30. Demo Burn Up Chart Completed Stories Incremental Releases

31. Retrospective 2 Week Cycle

32. Retrospective Facilitated Activity Action Plan Continuous process improvement

33. Re-start the Cycle 2 Week Cycle

34. Let’s see a team in action…

35. Q&A Scrum Process at DOL

36. Outcomes • Dedication and loyalty to team grew quicker than expected

37. Outcomes • Accomplishing what didn’t seem possible In a timeframe that didn’t seem possible • Requirements current, accurate, just in time

38. Outcomes • Collaboration, breaking down barriers between roles • Improved communication

39. Outcomes • Desire for informal training in the agency • Monthly lunch and learn sessions on Scrum

40. Outcomes • Cultural shift – drive to expand and have more Scrum teams is coming from the ground-up. • People WANT to participate.

41. Lessons learned – why first two projects succeeded • Hiring coach for first two projects prevented failure, gave team confidence • Project sponsors and executives provided 100% support • Initial teams were had people who wanted to participate • Authority and responsibility was enabled at all levels • Dedicated room/walls for planning, meeting

42. What we’re doing now • Training 40 more IT staff

43. What we’re doing now • Forming more permanent Scrum teams • Teams formed around products for all work coming in

44. What we’re doing now • Consultant for forming the new teams • Internal coaches

45. What we’re doing now • Contractor’s working within our Scrum teams • Contract deliverables – sprints

46. What we’re doing now • Trying Team Foundation Server – for Scrum

47. Q&A Outcomes and what we’re doing now

48. Thank you for your time

49. DOL Scrum Process 2 Week Cycle 1 2 Product Roadmap Product owner describes the marquee features, sequences them in priority order. Release Roadmap Scrum Master facilitates feature t-shirt sizing poker with team and product owner groups into releases. 3 4a 4b 4c 5 6 Sprint PlanningTeam provides availability, breaks top priority stories into tasks, and teammates volunteer for tasks. Stand Ups 15 minute team chat: state tasks done yesterday, plan for today, identify roadblocks. Complete Tasks Work tasks, help teammates and maintain task board: move tasks into doing or done and update remaining hours. Backlog Grooming Analyst facilitates story creation workshop, Scrum Master facilitates story time point sizing, and Product Owner prioritizes the stories. DemoProduct Owner describes the business value and team demos the functionality only for stories that meet ‘done’ criteria. Product Owner collects feedback. RetrospectiveScrum Master facilitates discussion about what went well and things to improve. Team commits to an action plan.