Content production using scrum
Download as PPTX, PDF1 like27 views
The document discusses Agile content production using Scrum. It describes the Scrum roles of Product Owner, Scrum Master, and Content Team. It outlines the Scrum events of Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. It also discusses the Scrum artifacts of Product Backlog, Sprint Backlog, and Product Increment (website content). The document provides details on how each role, event, and artifact is used in the Scrum process for agile content production.
Content production using scrum
- 2. Product Owner Scrum Master Development Team = Content Team Stakeholders Roles Sprint Planning Daily Scrum Sprint Review Sprint Retrospective (Product Backlog Refinement) Events Product Backlog Sprint Backlog Product Increment = Content Increment Artifacts Scrum Definition Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum is simple to understand, but hard to master. Openness: Being open drives continuous improvement. Focus: Teams focus to deliver customer value incrementally. Commitment: Teams commit to goals and improvement. Respect: Accept & respect the strengths of different people. Courage: Be brave. Be honest. Embrace failure. Scrum Values The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable Product Increment is created. Product Increment developed in this context is the Website Content. No changes are made during the Sprint that would endanger the Sprint Goal. The Scope may be clarified and re-negotiated between the Product Owner and Content Team. Sprint Definition
- 3. Scrum Process 2 WEEK SPRINT DAILY SCRUM 24 H Product Backlog Sprint Planning Meeting Sprint Backlog ‘Done’ work = Product Increment = Content Increment Scrum Master Business Stakeholders Content Team Design & Copywriting Product Owner Product Backlog Refinement Sprint Review Daily Stand-up Meetings Visible Progress Sprint Retrospective
- 4. Roles ● The Product Owner owns the Product Backlog as he/she has to maximize Return of Investment. ● The Product Owner is responsible for expressing backlog items and prioritizing them. ● The Product Owner discusses and agrees with Stakeholders what to do, why and when to release. ● Collaborates with the Content Team on the details of the Product Backlog during the Sprint. ● The Content Team is a cross-functional team with an optimal size between 3 and 9 members. ● The Content Team delivers a Product Increments at the end of each Sprint, in this case the Website Content. ● They are self-organizing. No one (not even the Scrum Master) tells the Content Team how to turn the Product Backlog into Increments of potentially releasable functionality. ● The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules. ● The Scrum Master is a servant-leader for the Scrum Team, supporting the Product Owner with managing the Product Backlog and coaches the team in self-organization and cross-functional collaboration. ● Helps with removing impediments to the Content Team's progress. ● The Scrum Master leads and coaches the organization in its adoption of Scrum. ● The Stakeholders can be identified as extra roles outside the Scrum Team within the organisation with interest in the project. ● The Customer who is financing the work (also known as the Sponsor) communicates mostly with the Product Owner and hopefully also participates in the Sprint Review events. ● Managers who enable the organisational framework in which the team operates are mostly taken care of by the Scrum Master. In this way they understand how they can best support the team to be effective.
- 5. Events ● Sprint Planning is a two part meeting time-boxed to a maximum 8 hours for a 1 month Sprint. ● Part 1: The Development Team creates a forecast of the items that will be developed in the Sprint. ● The Scrum Team crafts a Sprint Goal for the Sprint through the implementation of the Product Backlog. ● Part 2: The items in the Sprint Backlog are broken down into units of work of one day or less by the Content Team. ● The Daily Scrum is a daily 15-minute time-boxed event for the Content Team to synchronize activities and create a plan for the next 24 hours. ● This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. ● The Sprint Review is held at the end of the Sprint to inspect the product increment (website content). ● During the Sprint Review, the Scrum Team and stakeholders review what was done in the Sprint. ● The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. ● The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. ● The purpose is to inspect the process of the last Sprint and identify potential improvements. ● The Scrum Team creates a plan to incorporate these improvements into the way they do their work. ● Not specifically an event, The Scrum Team regularly does Product Backlog Refinement together with the stakeholders to add detail, estimates, and order to items in the Product Backlog. ● The Scrum Team decides how and when refinement is done. ● Product Backlog Refinement usually consumes no more than 10% of the capacity of the Content Team.
- 6. Artifacts ● The Product Backlog is an ordered list of Product Backlog Items (PBI’s). ● Product Backlog Items are requirements for changes to the website (e.g: landing page ...). ● The Product Backlog is ordered by priority, the highest items need to be more detailed. ● The team needs to be able to estimate and test all of the Product Backlog Items. ● The list of items is constantly evolving, changing and updating, the Product Owner is responsible for reflecting the changes in the Product Backlog. ● The Sprint Backlog is list of Product Backlog Items selected by the Content Team for delivery in the sprint, plus a plan to deliver the increment. ● Only the Content Team can change its Sprint Backlog during a Sprint. This happens throughout the Sprint and in particular in the Daily Scrum when necessary changes are understood. ● The Development Team tracks total work remaining in every Daily Scrum to forecast the likelihood of achieving the Sprint Goal. ● The Product Increment (Content Increment) is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. ● An Increment must meet the Scrum Team’s Definition of “Done”. ● It must be in useable condition regardless of whether the Product Owner decides to actually release it. Artifact Transparency is crucial in Scrum. Decisions to optimize value and control risk are made based on the perceived state of the artifacts. The Scrum Master must work with the Scrum Team, and other involved parties to make sure the artifacts are transparent and understood.