SAFe Solution Overview

Continuous Client Feedback

SAFe Support in RTC V6.0http://bit.ly/ibmsafesupport

• Project Area Initialization– Program/Team Timeline structure– Roles & Permissions– Artifacts

• Work Item Types• Planning• Queries, Templates, Dashboards• Reports

2

SAFe Concepts Supported

3

SAFe – RTC MappingSAFe Level SAFe Concept RTC Concept NotesProgram

Roadmap & Vision Plan View Vision can be a tab on the plan editor or it can be reflected in an HTML widget on the dashboard

Program Backlog Plan View

Program Roadmap Plan View

Architectural Runway

Plan View

Program Epic Work Item Type Epic Type (Business/Architectural) attribute on the Program Epic work item type

Feature Work Item Type Feature Type (Business/Architectural/NFR*) attribute on Feature work item type * Non Functional Requirement

Program PI Objective Work Item Type PI Objective work item type with Program value for PI Type.

Team

Story Work Item Type Task Work Item TypeTeam PI Objective Work Item Type PI Objective work item type with Team for PI Type.Team Backlog Plan View

QP Planning Views

<All Levels> Role Role Assigned to appropriate Project Area or Team AreaCreated in the Project Area for the right level

4

SAFe RTC Infrastructure

RTC Project Area or Team Area

RTC Project Area

CLM LPA or RTC Project Area

SAFe Portfolio (Coming Soon!)

SAFe Program 1

SAFe Team A

SAFe Team B

SAFe Program 2

SAFe Team C

SAFe Team D

SAFe Team E

Establish new Program with Teams

Establish a new Program that tracks work of existing Teams

New environments

Existing environments

5

FAQsUse the SAFe Program process template to establish a new Program project area. If your Teams have their own RTC project areas already established, track the work of those teams from Features in the Program via the tracks link type.

What if I already have established Teams using

RTC or third-party tooling?

Use the published SAFe RTC Configuration Guidelines document to apply the very same customizations to any other process template already in use in your organization to create the infrastructure, artifacts and plans.

What if I am not moving to RTC V6.0 any time soon?

No, you will need to use the SAFe RTC Configuration Guidelines described above to apply the SAFe-related customizations.

Can I migrate an existing project area to the new SAFe process template?

Yes

Can I use the SAFe process template and apply my own

customizations?

Once you have a project area based on the SAFe process template, you can take advantage of any updates we make to this template going forward.

What is the advantage of establishing a new

environment with the SAFe template?

6

Project Area Initialization SAFe Program Project Area – Initializes Program project area SAFe Team Team Areas – Initializes two Team Areas:

– Team 1 (rename)– Team 2 (rename)

Work Item Categories - Initializes the project area with default categories for Program and Teams:– Team 1 (rename) – Team 2 (rename)

Post-Project Initialization Tasks work item – Created to describe the post-project initialization activities to perform

Artifacts – Initializes the project area with SAFe artifacts and associated dashboards, plans, plan type, and plan views

7

Work Item Types

Program Epic

Story

PI Objective [Team]

Feature

Risk

Task

Ch

ild

ren

[1

-M]

Ch

ild

ren

[1

-M]

Tra

ck

s [

1-M

] (c

ros

s-p

roje

ct)

Tracks [1-1]

Ch

ildre

n [1

-M]

PI Objective [Program] C

hild

ren

[1-M

]

Tracks [1-1]

• Suggested link types/cardinality, not enforced by process

• State constraints in place (cannot resolve parent unless all of the children are resolved)

Defect

Retrospective

8

Work Flow - Plan Items

Draft Reviewed Analyzing Ready (for Approval) Approved Implementing Done

Funnel BacklogAnalysis

Pro

gra

m E

pic

New Implementing Integration Testing Done

New DoneIn Progress

Fea

ture

Closed

9

Work Flow – Execution Items

New Closed

PI

Ob

ject

ive

New Done

New In Progress ClosedRis

k

New DoneIn Progress

10

Work Flow - Execution Items (continued)

New In Development Done

New DoneIn Progress

Task

New In Development In Test Done

New In Progress

Sto

ry

Done

11

Work Item Attributes

Program Epic• Value Statement• Epic Type [Business, Architectural]

Feature • Feature Type [Business, Architectural, NFR]

Program Epic/Feature

• Job Size (1, 2, 3, 5, 8, 13, 20)• User/Business Value (1, 2, 3, 5, 8, 13, 20)• RR/OE (1, 2, 3, 5, 8, 13, 20)• Time Criticality (1, 2, 3, 5, 8, 13, 20)• WSJF [calculated]

PI Objective

• PI Objective Type [Program, Team]• Business Value (planned) [1-10]• Business Value (actual) [1-10]• Planned For , Filed Against

12

Planning• Progress on work items tracked as Time Remaining

– Display estimates in hours selected– In single SAFe Program project area with Team Areas, progress rolls up

from Team Tasks > Stories to Program Features

• Complexity Attribute – Story Points• Custom Attributes – Attribute Mapping• Program Backlog plan type

– Kanban View: Implements SAFe Kanban System for Program Epics– Roadmap: Epic > Feature [> Story > Task]– WSJF Ranked List: Feature ranking by WSJF

• Team plans as per Scrum process template– Except Kanban and Taskboard views customized with updated work

flow

13

Queries, Templates, DashboardsPre-Defined Queries

Work Item Templates

Program/Team DashboardsProgram: Activity-basedTeam: Role-based (as per Scrum and Agile ALM templates)

SAFe Level Predefined Query DescriptionProgram Open features Unresolved open features

Open program epics Program epics that are unresolvedOpen program PI objectives Unresolved program PI objectivesOpen team PI objectives Unresolved team PI objectivesOpen non -feature work items Unresolved open non-feature work items

SAFe Level Template Name DescriptionProgram Program Initiation Use to create work items applicable when a Program is first initiated

Program Increment Use at the start of each Program increment to create work items for the typical program events, activities, requirements and ceremonies

Development Iteration Use before the start of each development iteration and for each team to create work items for typical iteration events

Innovation and Planning Use prior to each Innovation and Planning Sprint and for each team to create work items for typical Sprint events

14

Reports• What I really want to know? Analysis• SAFe Reports

– Out of the box– Additional Program-level reports as downloadable bundle

• Self-Assessments– Linked from tasks created by Program Increment and Development

Iteration work item templates

15

What I really want to know and how I find out…

16

Look at status of Tasks, Stories, Features and PI Objectives What is behind?

Explore burn down of Stories, Features, PI Objectives

How much are we behind?

Explore dependencies: who is impacting/impacted; consider changes during execution to time spent and scope added/removed.

What is at risk? Where are there dependencies

that cause risk?

View discussion threads in work itemsWhy are we behind?

Risk ownership

What actions should be taken by whom?

Velocity and predictability data over time

How have we performed so I can plan better?

SAFe OOTB ReportsReport Description SAFe

MetricAnswers the question…

Burndown by Story Points Number of story points assigned to work items that are either open or in progress over daily intervals

M1M4

Are we behind? How much are we behind?

Burnup by Story Points Number of story points associated with completed work over daily intervals

M1M4

Are we green, yellow, orange?

Changes to Time Spent Work items where the time spent has been updated within the last 7 days

M1 Why are we behind? What is at risk?

Defects by Priority Chart (List) Total number of defects by priority M1 Are we improving our quality?

Incomplete Stories Stories targeted for current iteration that are still incomplete M1 What is behind?

Iteration Health Visualization based on various statistics that can be used to interpret the health of the current iteration filtered by timelines

M1 Are we green, yellow, orange?

Release Status Chart (List) Number of open and closed stories for a release M1 Are we green, yellow, orange?

Scope Added Work added to the current iteration scope after iteration start M1 Why are we behind?

Scope Removed Work removed from the current iteration scope after iteration start

M1 Why are we behind?

Team Dependencies List of open work items blocked by another team’s open work items

M1M5

What is at risk?

Team Velocity Number of story points completed in each iteration M1M5

How well did we do?

17

Additional SAFe Reports (in progress)

Report Description SAFe Metric Answers the question…

Release Predictability Trend report that shows Program velocity by Team over time

M5 Are we improving our ability to deliver? Which teams are still struggling? Where are our bottlenecks?

Program Increment (PI) Burndown

Story Points burn down by Sprints in the PI M4 Are we behind ?How much are we behind?

Feature Progress Based on # of stories completed vs remaining for Feature

M4 Are we green, yellow, red?

Velocity planned/actual As measure of Story Points rolled up to Feature M5 How well did we do?

Number of Business Features planned/delivered/accepted by customer

M5 Are we improving our value delivery?

Number of Architecture Features

M5 Measure of risk/instability

Program Self-Assessment M3 Where can we improve as a program?

Team Self-Assessment M2 Where can we improve as a team?

18

What do I do next?o Visit the SAFe Landing Page: bit.ly/

ibmsafesupport Examine the self-assessments and provide feedback Review the SAFe solution details document (coming soon!) Watch the YouTube videos and various recorded webinars

o Download RTC V6.0 RC1 and try out the new template Provide feedback via jazz.net (Forum, Work Items)

If you are interested in being a formal reference for our SAFe solution, please let us know!

19