Scrum Elements

BY Guanqiao Huang

Posted by HUANG on December 14, 2020

Scrum Elements

Terms:

Roles

Product Owner

  • Maximizing the value of the product
  • Managing the product Backlog
  • Maximizing the Development Team work
  • Entire organization must respect PO decisions
  • Responsible for Return On Ivestment(ROI)
  • Final arbiter of requirements questions
  • Focused more on the what than on the how

Tips: Produce Product backlog, May not have the whole roadmap. Vision of the product, One product owner for multiple teams

Scrum Development Team

  • Professionals delivering increment of “Done” product
  • Tries to develop a “potentially shippable product increment” every Sprint
  • Empowered to organize and manage their own work
  • Cross-functional group
  • Collaborates
  • Self-organizing
  • 3-9 members
  • No sub-teams

Tips: Work together, As a learning team, No job title, Natural relation between each others, normally no more than 5 people in a team (break into small team), as a family, work naturally in a team room

Scrum Master

  • Has no management authority
  • Does not have a project manager role
  • Facilitator 促进者
  • Ensuring Scrum is understood and enacted
  • Servant-leader for the Scrum Team
  • helps everyone in interactions
  • To maximize the value created
  • Provide service to the Product Owner, the Dev Team and the Organization

Tips: Scrum master protect the team from various influence, teach people how to use scrum, improve engineer practices, time boxes, felxibility, manangement power, srummaster checklist

Artifacts

Product Backlog

  • A list everything we might ever do
  • Included Product Backlog item
  • Everyone can add item to the product backlog
  • High priority to low priority (Product owner do this, to adujst the priority)
  • Only one product backlog in multiple teams for same product !!!

Sprint Backlog

  • A list what we have planned to do during the current Sprint
  • Selected backlog items into Not started, In Progress, Completed Status

Meetings

Sprint Planning Meeting

  • Product Increment selected during the Sprint Planning Meeting
  • Team and Product Owner pickup the product backlog item to sprint backlog
  • The team choose the task in the selected backlog items in sprint backlog

Daily Scrum

  • 15 Mins short meeting
  • “Look what I did yesterday”
  • “I should take care of these tasks”
  • Each team have their own daily scrum meeting

Backlog Refinement Meeting

Srint Review Meeting

Spring Restrospective Meeting

Scurm Framework

  1. Product owner prioritizes a backlog of work (for the team to do).
  2. Team decides what work can be done next (two weeks).
  3. Team develops and tests solutions to the backlog items until done (ready for use).
  4. End of the two weeks, team demonstrates its completed work wo the product owner and stakeholders.
  5. Finally, Team reflects on how it can improve the practices. (how things went during the two weeks)

Three Theories

  • Transparencyy: Whole process must be visible to those responsible for the outcome, people agree on what do they see, the process and roles are definied.
  • Inspection: frequent inspection of the process and progress to adjust it according to findings.
  • Adaptation: If process deviate outside acceptable limits the process must be adjusted as soon as possible.

Values

  • Commitment: People personally commit to achieving the goals of the Scrum Team.
  • Courage: Scrum Team members have courage to do the right thing and work on tough problems.
  • Focus: Everyone focuses on the work of the Sprint and the goals of the Scrum Team.
  • Openness: Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work.
  • Respect: Scrum Team members respect each other to be capable, independent people.

Some Links

The Scrum Master Checklist

[Scrum Project Management Who, Why, and When to Implement](https://careeremployer.com/project-management/scrum-project-management/#what-is-scrum-project-management)