Scrum from the Trenches - 10 Power ups that work!
•Download as PPTX, PDF•
1 like•381 views
Scrum is the most popular Agile framework in the world for effective team collaboration on complex projects. Scrum provides a small set of rules that create just enough structure for teams to be effective. By design Scrum is incomplete, come learn some of the tips and tricks that have helped accelerate teams all over the world. We'll dive into areas like, key-ways to improve stand up, how to forecast and effectively communicate progress to the business, protect your quality and make the most of your Scrum team and the Scrum framework.
Recommended
More Related Content
More from Caleb Jenkins
More from Caleb Jenkins (15)
Recently uploaded
Recently uploaded (20)
Scrum from the Trenches - 10 Power ups that work!
- 15. Sprint 2 to 4 Weeks Shippable Release Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog
- 16. Sprint 2 to 4 Weeks Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog Product Owner Customer Needs
- 17. Sprint 2 to 4 Weeks Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog
- 18. Sprint 2 to 4 Weeks Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Done Definition of Ready Sprint Planning Sprint Backlog Product Backlog
- 19. Sprint 2 to 4 Weeks Shippable Release Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog
- 20. Sprint 2 to 4 Weeks Shippable Release Burn Down Daily Scrum (stand-up) Team Scrum Master SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Product Backlog Sprint Review (including demo) Retrospective Burn Up Velocity Definition of Done
- 21. Sprint 2 to 4 Weeks Shippable Release Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog
- 22. WAIT! What about … Task boards, Information Radiators Reducing Work In Progress, Time Boxing Self Organization, Pull vs Push, Empowerment, Continuous Learning, Planning Poker, Story Sizing, Velocity, Team Swarming… etc, etc, etc..
- 23. Facilitates and protects the process ● removes team impediments ● Represents the business interests ● sets priorities ● owns the product backlog Does the work ● self organizes ● owns sprint backlog ● dev, test, arch, DBA, BA, SME, etc ● Scrum Master Product Owner The Team
- 24. know your why what are your values?
- 26. Stop talking about what you worked on. Talk about what you finished
- 27. What did I do yesterday What I’m planning on doing today Do I have any blocks What did I do yesterday What I’m planning on doing today Do I have any blocks
- 28. What did I do yesterday What I’m planning on doing today Do I have any blocks What did I do yesterday What I’m planning on doing today Do I have any blocks What did I finish yesterday What I’m planning on finishing today Do I have any blocks
- 30. scrum is a team sport
- 31. 31 Tuckman’s Stages of Group Development
- 32. Virginia Satir Change Process Model
- 33. Virinia Satir Change Process Model
- 34. every change in a team is a change to that team
- 38. --Sprint1BackLog-- --Sprint2BackLog-- --Sprint3BackLog-- --Sprint4BackLog-- --Sprint5BackLog-- best
- 39. scrum is a team sport move the work not the people
- 42. when you need to forecast
- 43. useful when Sprints are building on each other.. to larger goal.
- 44. Sprint 1 Month to 2 Weeks Shippable Release Burn Down Daily Scrum (stand-up) Team Scrum Master Sprint Review (including demo) Retrospective Burn Up Velocity SCRUM Product Owner Customer Needs Definition of Ready Sprint Planning Sprint Backlog Definition of DoneProduct Backlog
- 45. - Helmuth von Moltke. (German military strategist 1800-1891) “No Battle Plan Survives Contact With the Enemy” “Plans are worthless. Planning is invaluable.” – Sir Winston Churchill (1874 – 1965) “Everyone Has A Plan Until They Get Punched In The Face” - Mike Tyson American Philosopher (1966 - )
- 48. em·pir·i·cal ADJECTIVE 1.based on, concerned with, or verifiable by observation or experience rather than theory or pure logic. 2."they provided considerable empirical evidence to support their argument" em·pir·i·cal ADJECTIVE 1.based on, concerned with, or verifiable by observation or experience rather than theory or pure logic. 2."they provided considerable empirical evidence to support their argument"
- 53. Monday Tuesday Wed Thursday Friday Sprint Planning (4 Hours) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Stand Up (15 Min) Team Share (45 min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Team Share (45 Min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Stand Up (15 Min) (if in the am) Sprint Demo (1 hour) Sprint Retro (3 Hours) Monday Tuesday Wed Thursday Friday Sprint Planning (4 Hours) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Stand Up (15 Min) Team Share (45 min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Team Share (45 Min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Stand Up (15 Min) (if in the am) Sprint Demo (1 hour) Sprint Retro (3 Hours) schedule grooming
- 54. Monday Tuesday Wed Thursday Friday Sprint Planning (4 Hours) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Stand Up (15 Min) Team Share (45 min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Team Share (45 Min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Stand Up (15 Min) (if in the am) Sprint Demo (1 hour) Sprint Retro (3 Hours) Monday Tuesday Wed Thursday Friday Sprint Planning (4 Hours) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Stand Up (15 Min) Team Share (45 min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Team Share (45 Min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Stand Up (15 Min) (if in the am) Sprint Demo (1 hour) Sprint Retro (3 Hours) Monday Tuesday Wed Thursday Friday Sprint Planning (4 Hours) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Stand Up (15 Min) Team Share (45 min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Team Share (45 Min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Stand Up (15 Min) (if in the am) Sprint Demo (1 hour) Sprint Retro (3 Hours) Monday Tuesday Wed Thursday Friday Sprint Planning (4 Hours) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Stand Up (15 Min) Team Share (45 min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Team Share (45 Min) Stand Up (15 Min) Stand Up (15 Min) Grooming Session (PO +Stake Holders) Stand Up (15 Min) Sizing Session (PO + Scrum Team) Stand Up (15 Min) Stand Up (15 Min) (if in the am) Sprint Demo (1 hour) Sprint Retro (3 Hours) product owner should regularly meet with stake holders product owner should regularly meet with the team… or a representation of the team schedule grooming
- 67. sprint length
- 68. stop saying distributed if you’re not co-located, you’re dis-located
- 69. stop saying distributed if you’re not co-located, you’re dis-located
- 70. bonus! work with a coach… for a while, at various times
- 71. know your why talk about finished move work not people burn ups…use ‘em schedule grooming sessions empowered product owners quality radiators
- 72. tech leads pair don’t own try a gap admit when you’re dislocated bonus: coaching
- 76. final words of wisdom?
- 84. End
Editor's Notes
- 10 Scrum Power Ups! Scrum from the trenches – 10 Scrum power ups that work!
- Who is already doing some sort of Agile process?
- How many people here lead people?
- How many people here are deveopers?
- My name is Caleb Jenkins
- You can follow me on twitter at http://twitter.com/calebjenkins
- Follow my blog at http://developingux.com
- Visit http://solera.com
- Visit http://soleragdc.com
- 1. Know your why – what are your values?
- Have the “values” conversation with your leadership and with your team. Scrum is a Framework, not a process – so there is a lot of flexibility, but you should know what your tradeoffs are when you make changes, and how those align with your values (and when they don’t).
- Tuckman’s Team Formation Model Virginia Satire Change Model
- Tuckman’s Stages of Group Development
- Tuckman’s Team Formation Model Virginia Satire Change Model
- Tuckman’s Team Formation Model Virginia Satire Change Model
- Tuckman’s Team Formation Model Virginia Satire Change Model
- Tuckman’s Team Formation Model Virginia Satire Change Model
- Tuckman’s Team Formation Model Virginia Satire Change Model
- Tuckman’s Team Formation Model Virginia Satire Change Model
- Stacey Matrix, developed by Ralph D. Stacey (a Professor of Management).
- Stacey Matrix, developed by Ralph D. Stacey (a Professor of Management). Why we use an Emperical process (Scrum) em·pir·i·cal [əmˈpirik(ə)l] ADJECTIVE based on, concerned with, or verifiable by observation or experience rather than theory or pure logic. "they provided considerable empirical evidence to support their argument"
- Stacey Matrix, developed by Ralph D. Stacey (a Professor of Management).
- Stacey Matrix, developed by Ralph D. Stacey (a Professor of Management).
- Stacey Matrix, developed by Ralph D. Stacey (a Professor of Management).
- Empower your PO – Trust, willing to live with.. (no Proxy PO’s)
- Stop saying distributed, If you’re not co-located, than you’re dislocated
- Stop saying distributed, If you’re not co-located, than you’re dislocated
- Stop saying distributed, If you’re not co-located, than you’re dislocated
- Know your why – What are your values – know your tradeoffs. Finished (speak to tasks not stories) Move work, not people – 100% of Team, for % of stories Burn Up – Communicate Cone of Uncertainty Grooming Sessions (Sizing Session) Empower your PO – Trust, willing to live with.. (no Proxy PO’s) Code Quality – broadcast Sonar Code Coverage Broken Windows (100 %) Complexity Tech Lead – Pairs, doesn’t pull tasks Try a Gap – 17days + 3 gap Stop saying distributed, If you’re not co-located, than you’re dislocated Bonus: Work with a coach… for a while, at various times.
- Know your why – What are your values – know your tradeoffs. Finished (speak to tasks not stories) Move work, not people – 100% of Team, for % of stories Burn Up – Communicate Cone of Uncertainty Grooming Sessions (Sizing Session) Empower your PO – Trust, willing to live with.. (no Proxy PO’s) Code Quality – broadcast Sonar Code Coverage Broken Windows (100 %) Complexity Tech Lead – Pairs, doesn’t pull tasks Try a Gap – 17days + 3 gap Stop saying distributed, If you’re not co-located, than you’re dislocated Bonus: Work with a coach… for a while, at various times.