Agile series - Scrum

1,617
-1

Published on

This presentation is part of the series of Agile presentations shared as part of the Agile training, workshops and coaching. Focus is on providing wholesome information about using Agile beyond the skeleton frameworks.

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,617
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
77
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Agile series - Scrum

  1. 1. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Speed, Scale, Skills, Simplicity http://www.flowcracker.com 1
  2. 2. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Principle Consultant – Durgaprasad B. R 2  Durgaprasad B. R  20+ Years of IT experience  B. E (E & C), Alumni of IIM,Bangalore  Certifications  PMI-PMP, PMI-ACP  SCP from Scaled Agile Academy  Durgaprasad B. R  20+ Years of IT experience  B. E (E & C), Alumni of IIM,Bangalore  Certifications  PMI-PMP, PMI-ACP  SCP from Scaled Agile Academy  Developer, Project/Program Manager, Location Delivery Head, Agile Coach  Industries: Telecom, Healthcare, Consumer Electronics, Automotive  Past few Clients: Avaya, Nortel, ALU, Microsoft, Qualcomm, Intel, Toshiba, Continental  Technologies: Web Technologies, Embedded, Legacy large systems  Developer, Project/Program Manager, Location Delivery Head, Agile Coach  Industries: Telecom, Healthcare, Consumer Electronics, Automotive  Past few Clients: Avaya, Nortel, ALU, Microsoft, Qualcomm, Intel, Toshiba, Continental  Technologies: Web Technologies, Embedded, Legacy large systems  Led large Telecom programs, IP Switches, Voice Messaging System, Contact Center, Consumer Electronics products, Automotive product development  Well versed in new age technologies as well as sun- set technologies  Trained and coached individuals and teams on Agile, Kanban, Scrum and SAFe methodologies  Regular public workshops on PMP, ACP and SAFe Certifications  Led large Telecom programs, IP Switches, Voice Messaging System, Contact Center, Consumer Electronics products, Automotive product development  Well versed in new age technologies as well as sun- set technologies  Trained and coached individuals and teams on Agile, Kanban, Scrum and SAFe methodologies  Regular public workshops on PMP, ACP and SAFe Certifications http://www.flowcracker.in/about-durgaprasad-b-r/ Contact: prasadbr@flowcracker.com. Cell: 9845558474
  3. 3. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Lean Development Toward being SAFe™ Agile Scrum Kanban XP – Extreme Programming
  4. 4. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. THE OATH OF NON-ALLEGIANCE I promise not to exclude from consideration any idea based on its source, but to consider ideas across schools and heritages in order to find the ones that best suit the current situation. - DURGAPRASADhttp://oathofnonallegiance.com/
  5. 5. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Lean Development Toward being SAFe™ Agile Scrum Kanban XP – Extreme Programming
  6. 6. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum - Background Scrum – an event in Rugby, where likeminded people get together and discuss the ownership of the ball • Term coined by Hirotaka Takeuchi and Ikujiro Nonaka • Scrum – as described by them as a new approach to software product development • They studied firms like Fuji Films, Toyota, Xerox and 3M which were operating in tough markets • They call it as Rugby Approach – As the whole process is done by a cross functional teams. The teams try to go the distance as a unit, passing the ball back and forth
  7. 7. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Scrum like Chess, has limited set of rules. With those rules, different situations arise and the team as a whole should use their collective intelligence to come up with the next best move …… Scrum is so popular in Agile, that people interchangeably use Scrum for Agile Unlike Chess, there is no “Touch and Move” rule On a wrong move (feedback from customer), you can immediately revert back the last few moves easily
  8. 8. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. What is Scrum? Scrum is a Software Management Process not a Software Engineering Process Greatness of Scrum is its independence from Software Engineering Process Generally, XP Engineering practices are popular with Scrum
  9. 9. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Overview • Everything in scrum is within an iterative, incremental framework consisting of timeboxes called “Sprints’. Each sprint duration is fixed (2 to 4 weeks). • Everything is done by small cross functional team (8-9 members) who are responsible for managing themselves • At the beginning of every sprint, team commits to implement a set of high priority items from a prioritized list called ‘Product Backlog’ within sprint • During the sprint, everyday team briefly discusses the progress during Daily Scrum, and plans next steps to complete the work • Team should deliver something “done” called increment, at the end of each iterations which is of value of customer • At the end of the spring, the team does a Sprint review with the stakeholders to demonstrate the build and get valuable feedback. • The team also does an Sprint Retrospective at the end of every sprint, to look at things to improve for the next sprint (continuous improvement)
  10. 10. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Master Responsible for Process Support the team Remove Impediments Product Owner Prioritization Voice of Customer Owns the Product Backlog Scrum Team Cross Functional Deliver Each Sprint Product Backlog Daily Scrum (15 min) - 3 Questions 2-4 weeks Sprint Refine Product Backlog (8-10% for next Sprint) Potentially Shippable Product IncrementMinimum Releasable Features (Use burndown charts & dashboards to track progress) Scrum FLOW TDD, ATDD, Simple Design, Coding Standards, Pair Programming, Refactoring, CI, CD, Test Automation, ………. . Engineering Practices I & A Release Planning Sprint Planning (2-4 hr) Prioritization Task Breakdown & Estimate Team Commitment Sprint Backlog Sprint Retrospective (2-3 hr) - Continuously Improve Sprint Review (2-4 hr) Demo Sprint Backlog VisionVision Analyze Design Build Integrate Test
  11. 11. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Sprint • Fixed duration Iteration (2 to 4 weeks) • Smaller the iteration, the better • Includes requirement gathering to UAT • Each sprint delivers tested functionality of value to user • The teams are not interrupted during sprint • Once the sprint scope is committed, no changes can be added “except” by the development team • XP: 1-4 Week, Scrum: 30 days, RUP : 2-6 weeks. • 4 weeks – Waterfall trap. 1 Week – Too short. Ideal : 2 weeks Sprint Sprint duration once fixed, cannot be changed
  12. 12. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum – Roles, Artifacts • 3 Roles – Scrum Master – Product Owner – Team members • 4 Artifacts – Product Backlog – Sprint Backlog – Burndown charts – Increments Scrum Framework – Roles, Artifacts and Ceremonies • 4 Ceremonies  Sprint Planning  Sprint Review • Sprint Retrospective • Daily Scrum
  13. 13. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Master Responsible for Process Support the team Remove Impediments Product Owner Prioritization Voice of Customer Owns the Product Backlog Scrum Team Cross Functional Deliver Each Sprint Product Backlog Daily Scrum (15 min) - 3 Questions 2-4 weeks Sprint Refine Product Backlog (8-10% for next Sprint) Potentially Shippable Product IncrementMinimum Releasable Features (Use burndown charts & dashboards to track progress) Scrum FLOW TDD, ATDD, Simple Design, Coding Standards, Pair Programming, Refactoring, CI, CD, Test Automation, ………. . Engineering Practices I & A Release Planning Sprint Planning (2-4 hr) Prioritization Task Breakdown & Estimate Team Commitment Sprint Backlog Sprint Retrospective (2-3 hr) - Continuously Improve Sprint Review (2-4 hr) Demo Sprint Backlog Analyze Design Build Integrate Test Vision + Roadmap
  14. 14. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Roles – Chicken & Pig Story Pig Roles – core team members. Performers. People who do the work. Chicken Roles – who gain by the Pigs work. Do not contribute on daily basis to “get things done” Anti-Scrum’ists argue that this is anti Lean. Management is supposed to not just support but lead Lean transformation. Hence, it may be time to get rid of this story. • You cannot be a chicken and a pig at the same time (especially middle management) • This is a old story and good for some startups, which wants to keep the management away.
  15. 15. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Roles – Scrum Master • Helps team to learn and apply Scrum • Protects, guides and serves the team while also acting as change agent • Primary role is of a coach and not a facilitator • Has no delivery responsibility, does not commit to dates, budgets or profits etc. • Full time role and a servant leader Servant Leader, Coach • Removes Impediments • Prevents interruptions • Supports Agile process • Manage management • Continuous Improvement • Team Development • 3 C’s of Servant Leader – Character to influence others – Courage to pursue a purpose – Commitment to develop others Represents the management for the team
  16. 16. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Roles – Product Owner • Responsible for maximizing product value. • Subject Matter Expert (Domain) • Single “neck to break” for the product • Responsible for ROI. Answerable to management and customer • Busy role. Can take help from other team members • Decision maker – handles conflicting goals in the best interest of the customer • Ideally customer/end user who can dedicate their time. Activities • Responsible for product vision • Evolve Product vision into Product backlog (list of features) • Backlog grooming – Define Epics, Features, User stories – Define Release contents & dates – Rightsize user story for iterations • Participate in Ceremonies (daily scrum & retrospectives are optional) • Has authority to accept/reject deliverables. Provides feedback • Status updates to customer & management regularly Represents the customer to the team. Works with the business to get feedback from the end client/customer.
  17. 17. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Roles Product Owner and Scrum Masters are like Siamese twins attached to each other. Rain or Shine, they need to be aligned with each other’s goals. Every sprint for them is a three legged race. 17
  18. 18. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Roles - Team Like a Rugby/Football team • Have positions not roles • Generalizing specialists – If required can play in any position • Cross functional – Help team win • Have clear objectives • Self Organizing, Empowered • Mutually accountable • Focused on value delivery • Co-located • Open honest & has fun Small team of 5-9 people • Define tasks • Estimate efforts • Develop product • Ensure Quality • Evolve process “If your team cannot be fed on two Pizzas, then cut people” - Amazon’s CEO Jeff Bezo aka “Two pizza rule”
  19. 19. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Master Responsible for Process Support the team Remove Impediments Product Owner Prioritization Voice of Customer Owns the Product Backlog Scrum Team Cross Functional Deliver Each Sprint Product Backlog Daily Scrum (15 min) - 3 Questions 2-4 weeks Sprint Refine Product / Release Backlog (8-10% for next Sprint) Potentially Shippable Product IncrementMinimum Releasable Features (Use burndown charts & dashboards to track progress) Scrum FLOW TDD, ATDD, Simple Design, Coding Standards, Pair Programming, Refactoring, CI, CD, Test Automation, ………. . Engineering Practices I & A Release Planning Sprint Planning (2-4 hr) Prioritization Task Breakdown & Estimate Team Commitment Sprint Backlog Sprint Retrospective (2-3 hr) - Continuously Improve Sprint Review (2-4 hr) Demo Sprint Backlog Analyze Design Build Integrate Test Vision + Roadmap
  20. 20. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Ceremonies Ceremony Frequency Duration Strategy Typically once a year 4-16 hours Release Planning 1st day of every release 4-8 hours Sprint Planning 1st day of every iteration 2-4 hours Sprint Backlog Grooming Mid Sprint or every week 1-2 hours Sprint Review Last day of the iteration 1-2 hours Retrospective Last day of the iteration 1-2 hours Daily standup/Scrum Every day 15 minutes Effective ceremonies/routines build habit and habit's build character (both for team and individuals)
  21. 21. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Master Responsible for Process Support the team Remove Impediments Product Owner Prioritization Voice of Customer Owns the Product Backlog Scrum Team Cross Functional Deliver Each Sprint Product Backlog Daily Scrum (15 min) - 3 Questions 2-4 weeks Sprint Refine Product Backlog (8-10% for next Sprint) Potentially Shippable Product IncrementMinimum Releasable Features (Use burndown charts & dashboards to track progress) Scrum FLOW TDD, ATDD, Simple Design, Coding Standards, Pair Programming, Refactoring, CI, CD, Test Automation, ………. . Engineering Practices I & A Release Planning Sprint Planning (2-4 hr) Prioritization Task Breakdown & Estimate Team Commitment Sprint Backlog Sprint Retrospective (2-3 hr) - Continuously Improve Sprint Review (2-4 hr) Demo Sprint Backlog Analyze Design Build Integrate Test Vision + Roadmap
  22. 22. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum – 2 Week Team Calendar Week 1
  23. 23. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum – 2 Week Team Calendar Week 2
  24. 24. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Product Backlog • Contains prioritized list of everything – user stories, features, change requests, bugs (differed to future sprints) and other requests • Team pick up a very small subset of work items, which can be implemented within an iteration • Product backlog items can be hierarchical - epics, themes, stories etc. • High level entities need to be broken down into lower level entities i.e. user stories If an work item, does not exist in Product Backlog it will not be done
  25. 25. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Product Backlog • Teams implement work items which are of high priority • Work items may be added, removed or reprioritized by the PO anytime • High priority work items are detailed & granular • Product Owner is responsible for managing the backlog • Work items are sized by story points only Product Backlog : Prioritized list of everything that is needed in a product.
  26. 26. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Product Backlog - Planning
  27. 27. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Product Backlog - Sample Id Description Priority Size How to demo Comments 1 Service Contract renewal notification High M Email notification to the Service administrator 2 weeks prior to expiry 2 Log “Field Change Requests” Calls Medium S Allow creation, modification and deletion of FCR calls with call type as “Field Change Request’ 3 Part Pickup reminder Medium M Email notification to the Service administrator for parts not picked up beyond 2 days of service call closure 4 ……. Low XL ….. 5 ….. Low L …..
  28. 28. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Sprint Backlog • Contains a prioritized list of user stories and related work breakdown tasks to be implemented within an iteration • Each task item in the backlog contains – Unique identifies – Description – Author and Owner – Status – Efforts remaining in hours – Data is updated in the backlog on a daily basis
  29. 29. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Sprint Burndown chart • Shows the work remaining in the sprint • Scrum Master is responsible for tracking this chart • Helps to estimate the remaining effort involved in completing the iteration
  30. 30. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Other concepts not covered • Visual Process controls – Task board, information radiators • Shared workspaces • Other ceremonies – Discovery sessions • Other artifacts – User stories, CFD • Technical Debt
  31. 31. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. “There will be no Scrum Release 2.0… Why not? Because the point of Scrum is not to solve [specific problems of development]…. Scrum unearths the problems caused by the complexity and lets the organization solve them, one by one over and over again” Ken Schwaber 31 Regular Scrum is simple. It exposes organizational problems.
  32. 32. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Scrum Master Responsible for Process Support the team Remove Impediments Product Owner Prioritization Voice of Customer Owns the Product Backlog Scrum Team Cross Functional Deliver Each Sprint Product Backlog Daily Scrum (15 min) - 3 Questions 2-4 weeks Sprint Refine Product Backlog (8-10% for next Sprint) Potentially Shippable Product IncrementMinimum Releasable Features (Use burndown charts & dashboards to track progress) Scrum FLOW TDD, ATDD, Simple Design, Coding Standards, Pair Programming, Refactoring, CI, CD, Test Automation, ………. . Engineering Practices I & A Release Planning Sprint Planning (2-4 hr) Prioritization Task Breakdown & Estimate Team Commitment Sprint Backlog Sprint Retrospective (2-3 hr) - Continuously Improve Sprint Review (2-4 hr) Demo Sprint Backlog VisionVision Analyze Design Build Integrate Test
  33. 33. Copyright © Flow Cracker 2014. All other trademarks held by their respective owners.Copyright © Flow Cracker 2014. All other trademarks held by their respective owners. Flow Cracker #7, 3rd Floor, Srishti Building, 8th Main, Basaveshwar Nagar, Bangalore - 560079 Email : prasadbr@flowcracker.com Or contactus@flowcracker.com Cell: +91 984 555 8474 Thank You 33
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×