par Salb Salb Il y a 2 années
432
Plus de détails
Serves
Organization
Helping employees and stakeholders understand and enact an empirical approach for complex work
Removing barriers between stakeholders and Scrum Teams
Planning and advising Scrum implementations within the organization.
Leading, training, and coaching the organization in its Scrum adoption.
Facilitating stakeholder collaboration as requested or needed.
Facilitating the establishment of empirical product planning for a complex environment.
Assisting the Scrum Team understand the need for clear and concise Product Backlog items.
Assisting PO to find techniques for effective Product Goal definition and Product Backlog management.
Guaranteeing that all Scrum events take place and are positive, productive, and kept within the timebox.
Inducing the removal of impediments to the Scrum Team’s progress.
Aiding the Scrum Team in focusing on creating high-value Increments that meet the Definition of Done.
Guiding the team members in self-management and cross-functionality.
Responsibilities
Team's effectiveness is influenced by the Scrum Master through enabling the team to improve their practices with in the scrum framework.
Establish Scrum as defined in the scrum guide.
The product owner is responsible for backlog management Developing and explicitly communicating the Product Goal; ● Creating and clearly communicating Product Backlog items; ● Ordering Product Backlog items; and, ● Ensuring that the Product Backlog is transparent, visible and understood.
The product owner is responsible for maximizing the value of product produced by the Scrum team.
Developers are always accountable for: ● Creating a plan for the Sprint, the Sprint Backlog; ● Instilling quality by adhering to a Definition of Done; ● Adapting their plan each day toward the Sprint Goal; and, ● Holding each other accountable as professionals.
Developers are committed to creating a working, valuable, useful increment each sprint
The definition of Scrum is included in the Scrum Guide. The Scrum framework contains essential elements that serve a specific purpose that is essential to the overall value and results realized with Scrum.
Scrum is potentially rendered useless when core design ideas are changed, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum.
The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.
Increment is born when DOD is met
The agile way of working means that each feature has to follow steps of design, build and test. So the documentation is created and adjusted per feature.
Formal description of increment that meets the measured quality for the product
The Sprint Goal also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives.
It is a single objective
Actionable plan for delivering the Increment (how).
The set of Product Backlog items selected for the Sprint (what)
The Sprint Backlog is composed of the Sprint Goal (why),
A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a service, a physical product, or something more abstract.
The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next.
The rest of the Product Backlog emerges to define “what” will fulfill the Product Goal.
The product goal is in the backlog
This describes the future state of the product
Sprint Retro
Retrospective
The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
Identify
The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.
inspection
How the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.
Plan ways to increase quality and effectiveness.
Sprint Review
Review
Scrum team and stakeholders review what was created. Discuss what has changed in their environment. Collaborate on next items. Backlog may need to be adjusted. The sprint review is a working session and should not be limited to a presentation.
Second to last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
Inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
Daily Scrum
Improves
Communications, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings.
Goal
progress toward the Sprint Goal and produces an actionable plan for the next day of work. This creates focus and improves self-management.
Timeboxed
15 minutes and held at the same time daily to reduce complexity
Purpose
Inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.
Sprint Planning
Topic 3 - How will the chosen work get done?
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are together referred to as the Sprint Backlog.
Developers plan the work necessary to create an Increment that meets the Definition of Done. This done by breaking Product Backlog items into smaller work items of one day or less. Developers are the only ones that determine how to do this. No one else tells them how to turn Product Backlog items into Increments of value.
Topic 2 - What can be Done this Sprint?
Developers discuss what can be pulled into the sprint based on prior velocity and upcoming capacity and the choose items that meet the sprint goal with PO input.
Topic 1 - Why is the sprint valuable?
Sprint Goal is finalized before Sprint Planning is over.
Team collaborates to determine the sprint goal that communicates the value of the sprint to the stakeholders.
PO tells how the increment of work will add value
The team collaborates about the work and the PO guides the discussion to the most important and most valuable work.
Lays out the work to be completed in the sprint
Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective