SAFe Scrum 1.0.1

Solution Overview

SAFe Scrum is an Agile methodology employed by teams within an Agile Release Train (ART) to deliver customer value within a short time frame. It involves Team Iterations, Kanban systems, and Scrum events for effective planning, execution, demonstration, and retrospective analysis of their work.

The solution supports SAFe Scrum Cycle from the picture below.

Solution Flow

Work Item Hierarchy List

On the first view of the solution you can find the list of Epics, Features, User Stories, and Bugs, and simply filter them by an Agile Release Train (ART) and Team. This provides a clear overview of all the Work Items assigned to a Team.

Team Backlog

The SAFe Scrum Cycle begins with the Team Backlog, which contains upcoming work necessary for progress. On a Team Backlog view you can see a prioritized list of not started User Stories and Bugs.

Story Mapping

Story Mapping is a collaborative agile technique that visually organizes User Stories to create a holistic view of a product's Features filtering them based on Business Values, and prioritizing development efforts accordingly.

Iteration Cadence

On the Iteration Cadence view you can see a schedule of Team Iterations, which are typically 1-4 weeks of duration periods, in which Agile teams complete their work and create a product increment that is ready for potential release or delivery.

Team Iteration Capacity

Team Iteration Capacity in iteration planning is the amount of work a Scrum team can realistically complete within a specific Team Iteration or Sprint based on their available resources and capacity. On this view you can define what Capacity is available for a Team based on the Team Velocity and planned vacations.

Iteration Planning

Iteration Planning follows, where team members collaborate to determine achievable goals for the upcoming iteration. During iteration planning, the team refines Acceptance Criteria, estimates effort, selects User Stories and Features based on capacity, and plans work to create valuable increments meeting the Definition of Done.

You can enable the following solutions to support Team and ART PI Objectives, Iteration Goals, Acceptance Criteria and Definition of Done.

• Team and ART PI Objectives (786941ff-055a-4b1e-a9de-6d12fd35ca8d)
• Iteration Goals (84b88da3-9bb0-40ab-ac31-2c0304c55702)
• Acceptance Criteria for Feature (54cd155b-888b-4eb8-abc9-398474f29b23)
• Acceptance Criteria for User Story (a56a7b30-d7d0-4246-ba32-e4010ab53033)
• Feature Definition of Done (DoD) (e117946f-b943-4e33-b615-70be388d0b54)
• User Story Definition of Done (DoD) (a4e9184a-0123-4b39-8cba-695659fbf43d)
• Bug Definition of Done (DoD) (02430c79-7f57-4b3e-9f63-8cfef1992930)

On the Iteration Planning view a Team can select User Stories and Bugs from the backlog and plan them into Team Iteration determining the work they can accomplish during the Team Iteration.

Iteration Backlog

The Iteration Backlog is created during planning, containing items the team intends to complete. On the Iteration Backlog view you can see a prioritized list of User Stories and Bugs that the Agile Team commits to completing during a specific Team Iteration.

System Demo Features Board by Teams

The team engages in regular Team Syncs and Iteration Reviews to assess progress and adapt as needed. Participation in the System Demo provides stakeholders with an integrated view of new Features, and tracking progress using a Kanban board helps ensure steady delivery of work items throughout the iteration.

During the System Demo, all teams within the Agile Release Train (ART) present an integrated view of new Features delivered in the most recent iteration, allowing ART stakeholders to objectively assess the progress made during the Planning Interval (PI), with active participation or attendance from everyone involved in the ART. The Demo Completed checkbox on a Feature provides visibility into which Features have already undergone a demonstration.

Team Velocity

Team Velocity refers to the measure of an Agile Team's productivity and capacity, calculated by summing the number of story points or work items successfully completed in a given iteration or sprint.

US & B Progress

On this board Team members provide updates on the status and progress of specific User Stories and Bugs, organizing them based on the related Features they are associated with. This allows the team to focus on the advancement of work items within each Feature, gaining insights into the overall progress and identifying potential dependencies or challenges.

Task Board

The Task Board refers to a visual representation of the team's Tasks, organized based on the associated User Stories, allowing the team to focus on the specific work items being addressed and track their progress effectively.

Tasks by Person

The board refers to the discussion and update on the Tasks assigned to each team member, providing visibility into individual responsibilities and progress during the iteration or sprint.

Team Kanban Board

It is a visual tool that displays the team's work items (User Stories and Bugs) and their current status, facilitating discussions on task progress, bottlenecks, and overall workflow during the iteration or sprint.

Burn Down Chart (effort)

The report shows the remaining work or effort required to complete a set of User Stories and Bugs over time, allowing teams to track progress toward completing their planned work for the iteration or sprint.

Burn Up Chart (effort + count)

It is a visual representation that tracks both the completed work (count) and the remaining work (effort) over time, providing a comprehensive view of progress toward completing a set of User Stories and Bugs during the iteration or sprint.

Dependencies

The list of Dependencies shows the interconnections between Tasks, User Stories, or Bugs that rely on each other, and it is needed in the daily team sync to identify potential obstacles, coordinate efforts, and ensure smooth progress in completing the work.

Scrum Dashboard

The Scrum dashboard is needed to provide a visual and real-time representation of key metrics and progress indicators related to the Scrum team's performance, allowing stakeholders to gain insights, track project status, and make data-driven decisions more effectively.

Retrospectives

A Retrospective allows a team to reflect on a specific period of work, project, or event. Its primary purpose is to assess what went well, what didn't go as planned, and what improvements can be made in the future.

Create a Retrospective for the team

On the Collecting Feedback view collect feedback from the participants on what worked or didn't work well and their improvement ideas.

Create Feedback Groups and organize your previously created Feedback to the groups by adding relations between Feedback and Feedback Groups.

Use tags to vote for the Feedback Groups to choose those to discuss first (e.g. put an emoji or your name as you wish).

Open each Feedback Group and go through the linked Feedback. Close them when discussed.

Create Action Items to improve your performance and what your team should do.

See the list of Action Items, prioritize them, and assign to Team Iterations.

Team Happiness Score

It allows teammates to rate their happiness level on a numeric scale (0–10) during each retrospective. A new Happiness icon will appear on the top right panel for Retrospectives:

• Click the Happiness icon
• Copy the session link and send it to participants of the retrospective
• Let them provide their happiness level
• See the results
• Save the results as a retrospective comment

Start happiness score collection:

Share the session link:

Provide your happiness score: