Jocodoma

Joco's Tech Blog

0%

Introduction to SCRUM

Posted on Edited on In Disqus:
Symbols count in article: 3.4k Reading time ≈ 3 mins.

Scrum Team

  • Scrum Product Owner
  • Scrum Master
  • Development Team Members

Scrum Product Owner

  • Maximize the value of the product and the Development Team
  • Sole person responsible for managing the order and prioritizing the Product Backlog
  • Must be empowered to make decisions about the product
  • Tell Development Team what to do! (but NOT how to do it!)

Scrum Master

  • Act as a change agent and adapt processes to maximize productivity of the team
  • Remove impediments for the Scrum Team
  • Ensure efficient communication between the Scrum Development Team and the Scrum Product Owner
  • Facilitate the various Scrum Events

Development Team (Dev Team)

  • Self-organizing in pursuit of delivering value
  • Cross-functional with all the skills necessary to delivery the work
  • Breakdown the Product Backlog Item (stories/requirements), create tasks, estimate and distribute them for a Sprint (Sprint Backlog)
  • Perform the short Daily Scrum Meeting (Stand-up Meeting)
  • Ensure that at the end of the Spring potentially shippable functionality is delivered
  • Update the status and the remaining efforts for their tasks to allow creation of a Sprint Burndown Diagram

Scrum Events

Product Backlog Refinement Meetings

  • Every time Scrum Product Owner updates the backlog, all Scrum team members should get together to understand the changes (WHAT and WHY)
  • Scrum Dev Team should be clear about Top 1~3 items in the backlog

Sprint Planning Meetings

  • Confirm with Scrum Product Owner WHAT needs to be done (built) for the Sprint - Sprint Goal
  • Dev Team will figure out HOW to do it (without Scrum Product Owner)
  • Rules:
    • Confirm availability with Scrum Dev Team members
    • Should NOT change or have new assignments from Product Owner (or senior management) to any one of the Dev Team members during the Sprint
    • If the Sprint needs to stop for some reasons by Product Owner, Product Owner should take full responsibility
    • If Scrum Dev Team members have vacations or days off plans, they should bring it up during the planning meeting
  • Guidelines - Coding, Redmine, GitFlow, Peer Review
  • Definition of Done (DoD)

Daily Scrum Meetings

  • What has he/she accomplished since the last daily Scrum meeting?
  • What is he/she is going to accomplish until the next Scrum meeting?
  • What are the impediments that prevent him/her from accomplishing his/her tasks?

Spring Review Meetings (Demo)

  • Scrum Dev Team shows which Scrum Product Backlog items they completed (according to the Definition of Done) during the Sprint
  • Backlog items that are NOT completed shall NOT be demonstrated
  • Incomplete items/remaining activities shall be taken back into the Scrum Product Backlog, re-estimated and completed in one of the following Sprints
  • Meeting should be kept very informal. No PowerPoint slides should be used and time for preparation and performing the meeting should be limited
  • Scrum Product Owner inspects the implemented backlog entries and accepts the solution or adds new stories to the Scrum Product Backlog to adapt the functionality
  • Participants in the Sprint Review typically include the Scrum Product Owner and the Scrum Team. Additionally management, customers, and developers from other projects might participate as well

Sprint Retrospective Meetings

  • The Sprint Retrospective is an integral part of the “inspect and adapt“ process. Without this meeting the team will never be able to improve their overall output and cannot focus on the overall team performance. Therefore, actionable suggestions to improve performance should be available at the end of the meeting
  • All Scrum Team members reflect on the past Sprint and check three things:
    • What went well during the Sprint?
    • What didn’t go well during the Sprint?
    • What improvements could be made in the next Sprint?

References