Scrum framework for the basic series of scrum entry

The scrum framework for the basic series of Scrum basics 3 replies.

Scrum framework for the basic series of scrum entry

People who have read a few scrum books must be able to very familiar the scrum framework, such as 3 roles for Scrum, 5 meetings, and 3 artifacts. Before I expand on this, I'd like to start by introducing the values of scrum and the Agile Manifesto.

Agile Manifesto [1]

Individuals and interactions are better than processes and tools

Working software is better than detailed documentation

Customer collaboration is better than contract negotiation

Responding to change is better than following a plan

In other words, even though the right item has its value, we prefer the left.

Scrum values [2]

Focus: Focus on only a few things over a period of time. Stop starting, Start finishing. The team's ability (energy) is limited, and within limited capacity and limited time, focus on the most valuable things to achieve better results.

Courage: We need the courage to meet all the challenges.

Public: Public progress in the team (Progress), i.e. visualization and transparency, can easily expose risk problems and obstacles. and transparency is the basis of respect and trust.

Commitment: Make a commitment at the beginning of your organization's team and do your best to fulfill your commitments during the iteration.

Respect: The team is sitting together, long-term stability, which helps deepen mutual respect and understanding.

Scrum framework

The scrum framework is not a silver bullet, nor a panacea. Practicing scrum does not require team members to be elites. Because scrum simply exposes the problem quickly so that we cannot ignore it and endure it. The scrum framework is a team's process framework that is improved by self-organizing teams. The framework mainly contains the roles, meetings and artifacts of the three parts.

Role

The sole person responsible for the product in product owner –scrum. The product owner needs to create and maintain the product backlog and need to participate in the necessary scrum meetings, such as Sprint planning, Sprint review, and so on. The details can look forward to the next post (Scrum role).

scrummaster– This role is the new role proposed by the scrum framework. He needs to be very familiar with the entire scrum framework and need to be a master of change. In scrum, ScrumMaster does not have authorization and needs to do a lot of work, such as removing risks.

Development team – The development team refers to a cross-functional, self-organizing team. The development team may include developers, testers, user experience engineers, database specialists, and so on. The development team is responsible for completing the end-to-end work so that the product increments can be completed at the end of the sprint.

Meeting

The Sprint Planning –sprint program is divided into 2 main parts: What to do and how to do it. The scrum team together decide what they are going to do, and how to build and test the promised work. During the planning meeting, one of the important responsibilities of the product owner is to explain the ambiguous requirements. The final output is sprint goals and Sprint Backlog. Please look forward to the next blog post for details.

Daily meetings (Daily Scrum) – 15 minutes of daily standing meetings. The Scrum team answers three questions: What have I accomplished since the last regular session (with a focus on fulfilling the commitments and exposing the risks)? What do I plan to accomplish from now to the next meeting (the focus is on commitment)? What are the risks or obstacles (early exposure to problem risk)?

Sprint review Session (Review) – at the Sprint review session, the product owner accepts or rejects the user story that the team completed. (Note: Product owners should be judged in their usual work, not just at the Review Conference) This is an informal meeting with no more than 1 hours of preparation time. (Note: But the necessary preparation is still needed.)

The Sprint Review (retrospective) –scrum team examines and adjusts their working methods to achieve a mature and efficient self-organizing team.

Product Backlog Refinement – the product owner organizes coordinating stakeholders or teams to perform product backlog grooming, including but not limited to new requirements, deleting requirements, modifying requirements, splitting requirements, changing the order of requirements, and more.

Artifacts

A list of requirements stored in a product backlog–scrum, a common format for user stories, or other types of content, such as defects, use cases, epic stories, and so on.

Sprint backlog– is made up of the stories and tasks that are promised in the sprint. During the sprint, the team updates the sprint backlog every day, discussing and synchronizing information about the sprint backlog at the daily meeting.

Product Increment – The product increment that the team can deliver at the end of each sprint. This should be potentially available, referring to the quality of the product reaching the published standard. Whether or not to publish the final decision by the product owner.

[1] Agile Manifesto –http://agilemanifesto.org

[2] Scrum values –http://scrumalliance.org

Basic Scrum Basics Series:

• Scrum origins in the basic series of scrum entry
• Scrum framework for the basic series of scrum entry
• Scrum roles for the basic series of scrum entry
• Scrum Conference for the basic series of scrum entry
• Scrum artifacts for the basic series of scrum entry
• Scrum requirements grooming for the basic series of scrum entry
• Scrum estimates for the basic series of Scrum basics (please expect)

Scrum framework for the basic series of scrum entry