1. IBM’s SAFe® Solution Overview
Rational Team Concert V6.0
Amy Silberbauer
Solution Architect, DevOps Steer & Enterprise Scaled Agile
IBM Systems – Application Platform & Middleware

2. SAFe Support in RTC V6.0 Project Area Initialization Work Item Details
Program/Team Timeline structure
Roles & Permissions
Artifacts (work item types, work item templates, plans, plan type, plan views)
Work Item Details
Planning
Program Backlog plan type
Kanban, WSJF Ranked List, Roadmap plan views
Dashboards
Queries & Reports

3. SAFe Concepts Supported

4. SAFe – RTC Mapping SAFe Level SAFe Concept RTC Concept Notes Program
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
Program Roadmap
Architectural Runway
Program Epic
Work Item Type
Epic Type (Business/Architectural) attribute on the Program Epic work item type
Feature
Feature Type (Business/Architectural/NFR*) attribute on Feature work item type
* Non Functional Requirement
Program PI Objective
PI Objective work item type with Program value for PI Type.
Team
Story
Task
Team PI Objective
PI Objective work item type with Team for PI Type.
Team Backlog
QP Planning Views
<All Levels>
Role
Assigned to appropriate Project Area or Team Area
Created in the Project Area for the right level

5. SAFe RTC Infrastructure
RTC Project Area or
Team Area
RTC Project Area
CLM LPA or
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

6. FAQs
Use 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?

7. 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:
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

8. Tracks [1-M] (cross-project)
Work Item Types
Program Epic
Risk
Defect
Retrospective
Children [1-M]
Feature
Tracks [1-1]
PI Objective [Program]
Tracks [1-1]
Tracks [1-M] (cross-project)
Children [1-M]
Story
Children [1-M]
PI Objective [Team]
Children [1-M]
Task
Suggested link types/cardinality, not enforced by process
State constraints in place (cannot resolve parent unless all of the children are resolved)

9. Work Flow - Plan Items Analysis Backlog Funnel Closed Program Epic
Draft
Reviewed
Analyzing
Ready (for Approval)
Approved
Implementing
Done
In Progress
New
Done
Feature
New
Implementing
Integration
Testing
Done

10. Work Flow – Execution Items
New
Closed
PI Objective
Done
In Progress
New
In Progress
Closed
Risk
Done

11. Work Flow - Execution Items (continued)
New
In Development
In Test
Done
In Progress
Story
New
In Development
Done
In Progress
Task

12. 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

13. Helps with SAFe methodology adoption – “learn while doing”
Work Item Templates
SAFe Level
Template Name
Description
Program
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
Innovation and Planning
Use prior to each Innovation and Planning Sprint and for each team to create work items for typical Sprint events
Team
Development Iteration
Use before the start of each development iteration and for each team to create work items for typical iteration events
Use work item templates to create the set of tasks related to completion of a SAFe ceremony, event or activity
Tasks provide links to in-context guidance (specific SAFe concept on Scaled Agile Framework web site
Helps with SAFe methodology adoption – “learn while doing”

14. 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

15. Dashboards – Program Program: Activity-based Team: Role-based
Tabs: Program Overview, Program Details, Release Planning, Dependency Management, Trends
Suggested content included:
Plan widgets
Query widgets
JRS report widgets cannot be created by the process template, so widget included on specific tabs to provide instructions on how to add those widgets
Team: Role-based
Tabs: General, Scrum Master, Team Member, Product Owner
Consistent with Scrum and Agile ALM templates

16. Queries Pre-Defined Queries SAFe Level Predefined Query Description
Program
Open features
Unresolved open features
Open program epics
Program epics that are unresolved
Open program PI objectives
Unresolved program PI objectives
Open non -feature work items
Unresolved open non-feature work items
Team
Open team PI objectives
Unresolved team PI objectives

17. Reports SAFe Reports Self-Assessments 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

18. What I really want to know and how I find out…
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 items
Why 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?

19. SAFe Metrics
The SAFe ART (Agile Release Train) metrics for Program and Team can be found here on the Scaled Agile Framework web site: The metrics are broken down into sections, briefly described here:
M1: Team-based iteration metrics to gauge status and progress and to measure quality
M2: Team Self-Assessment*
M3: Program (ART) Self-Assessment*
M4: Release Progress Reports
M5: Program Increment metrics to gauge status and process and to measure quality
*Our self-assessments for Program and Team can be found on the SAFe Landing Page in the

20. “Orange” reports part of downloadable archive
SAFe Team Reports
SAFe Metric
Report
Description
Answers the question…
Suggested Dashboard Tab M1
Burndown by
Story Points
Number of story points assigned to work items that are either open or in progress over daily intervals
Are we behind?
How much are we behind?
Scrum Master
Burnup by Story Points
Number of story points associated with completed work over daily intervals
Are we green, yellow, orange?
Changes to Time Spent
Work items where the time spent has been updated within the last 7 days
Why are we behind?
What is at risk?
Defects by Priority Chart (List)
Total number of defects by priority
Are we improving our quality?
Incomplete Stories
Stories targeted for current iteration that are still incomplete
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
Product Owner
Release Status Chart (List)
Number of open and closed stories for a release
Scope Added
Work added to the current iteration scope after iteration start
Scope Removed
Work removed from the current iteration scope after iteration start
Team Dependencies
List of open work items blocked by another team’s open work items
Team Velocity
Number of story points completed in each iteration
How well did we do?
All [scope to] Team Stories
Bottoms-up view of Stories with objectives, aligned to Features for the specific Team
What capabilities have we delivered?
What capabilities are we delivering?
Is all of the Team’s work aligned to business value?

21. “Orange” reports part of downloadable archive
SAFe Program Reports
SAFe Metric
Report
Description
Answers the question…
Suggested Dashboard Tab M5
All [scope to] Team Stories
Bottoms-up view of Stories with objectives, aligned to Features for the specific Team. If no Team is specified, the scope of results is the Program level.
What capabilities have we delivered?
What capabilities are we delivering?
Is all of the Team’s work aligned to business value?
Program Details
Business Features By Status for [select PI]
Shows business features by status for the specified Program Increment. If no PI is specified, the scope is all PIs for the Program.
Are we improving our value delivery?
What value are we delivering?
Release Planning
Features By Type for [select PI]
Pie chart that shows percentage of Features by type for the specified Program Increment. If no PI is specified, the scope is all PIs for the Program.
How much architectural risk does this PI have?
Do we have a reasonable balance of architecture and business work?
Program Overview
Features with Child Story Status for [select PI]
This report displays a bar chart showing, by Feature, the status of each of its child stories. The report is scoped to a Program Increment. If no PI is specified, the scope is the Program roadmap.
What is the status of the Program Increment? What is behind?
Ready for System Demo
List of Features completed, along with related PI Objectives, that are ready for a System Demonstration
What value can we demonstrate?
PI Objectives in Progress
Shows PI Objectives for Features related to Team Stories current in progress
What value do we have planned to deliver in this PI?
Program Roadmap
Shows all Program Epics on timeline with breakdown into Features and Stories (graphical and list views)
What is on our Program roadmap?
Cross-Team Dependencies
Shows cross-team dependencies from the perspective of the dependent work item.
Where do we have dependencies? Where are we blocked?
Dependency Management

22. Resources IBM’s SAFe Landing Page: Agile Learning Circle
IBM's SAFe Support POV: IBM’s vision for supporting SAFe
Configuration Guidelines: Step-by-step guide to configure CLM for SAFe support
YouTube Channel
Recorded Webinars
Agile Learning Circle
A SAFe Learning Roadmap
IBM DevOps Community
IBM DevOps Blog Series – Our Journey
Rational Deployment Wiki
Some key resources related to IBM’s support for SAFe are accessible from IBM’s SAFe Support web page.
Ideally customers should start with the RTC SAFe template provided in the open beta, but if that is not possible (i.e., they are already using another template), they can use the SAFe configuration guidelines to customize their RTC implementation to leverage some of the new SAFe features.
Other resources:
Agile Landing Page on IBM.com:
IBM DevOps Landing Page on DeveloperWorks:
Agile Landing Page on DeveloperWorks: 22

23. Thank You!
Before we end the session today, we are happy to take your questions at this time. After the question and answer period, we will wrap up the program with a few closing remarks.