RTC 6.0 Scaled Agile Framework© (SAFe™) SolutionSAFe Concepts supported in RTC.............................................................................................. 1

Multiple RTC Project Areas: Portfolio, Program + Teams.....................................................3Process template for Program + Teams.....................................................................................5

Project Area Initialization............................................................................................................................5Program/Team Timeline structure.......................................................................................................10Roles....................................................................................................................................................................11Permissions......................................................................................................................................................12

Project Configuration Permissions....................................................................................................................12Team Configuration Permissions.......................................................................................................................12

Artifacts............................................................................................................................................................. 13Work Item Types...........................................................................................................................................14

Custom attributes......................................................................................................................................................15Program Epic...............................................................................................................................................................16Feature...........................................................................................................................................................................17

Enumerations..................................................................................................................................................17Attribute customization.............................................................................................................................17Planning.............................................................................................................................................................18

General...........................................................................................................................................................................18Plan Attributes............................................................................................................................................................19Work Environment...................................................................................................................................................20Plan Types.................................................................................................................................................................... 21

Program Backlog (new)....................................................................................................................................21Sprint Backlog.......................................................................................................................................................22Sprint Kanban Board..........................................................................................................................................23Release Backlog....................................................................................................................................................23Product Backlog...................................................................................................................................................23Cross-Project Plan...............................................................................................................................................23

Predefined Queries.......................................................................................................................................23Program level..............................................................................................................................................................23Team level....................................................................................................................................................................24

Work Item templates...................................................................................................................................28Reports...............................................................................................................................................................30Role based dashboard.................................................................................................................................32

SAFe Concepts supported in RTCIn RTC 6.0, we provide an out of box process templates that have the necessary SAFe artifacts for Program + Team levels. Figure 1 shows the SAFe V3.0 “big picture”. The SAFe concepts available using these templates are indicated with a green star.

Figure 1: RTC 6.0 SAFe Support - "Big Picture"

SAFe RTC MappingSAFe 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 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 RequirementProgram PI Objective Work Item Type PI Objective work item type with Program value for PI Type.

Team Story Work Item TypeTask Work Item TypeTeam PI Objective Work Item Type PI Objective work item type with Team for PI Type.

Team Backlog Plan ViewQP Planning Views

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

Multiple RTC Project Areas: Portfolio, Program + TeamsThe adoption of agile practices has proven successful in helping teams address the business imperatives to continuously deliver more value quickly, with higher quality and at a lower cost, but agile in isolation does not imply organizational success. The Scaled Agile Framework (SAFe) provides a well-established, industry-standard way to apply lean and agile principles not only at the team level but also across the teams. It takes into consideration the development of code, but also architecture, project funding and governance, and describes the roles and processes applicable at each level. SAFe guidance and best practices enable organizations to improve efficiency and effectiveness by synchronizing the alignment, collaboration and delivery of value to the business driven by portfolio vision and strategy.

Rational Team Concert (RTC) is at the core of IBM’s DevOps solution and the logical starting point for teams looking to get started with SAFe. A single RTC project area can be established to support a small- to mid-sized organization that wants to get up and running quickly when the need for flexibility and scalability is less of a concern. This article provides details of the OOTB SAFe process template provided with RTC 6.0. A single project for Program and Teams is the officially recommended topology for RTC 6.0 for SAFe. It is a simple topology that offers both scalability and flexibility. There are known limitations in schedule roll-up from Programs to Portfolio with this topology.

Establish new programs with Teams

Establish a new Program that tracks work of existing teams

RTC 6.0 provides the following OOTB process templates Process template for Program + Teams

Process template for Program + TeamsA new OOTB process template is provided to support the Scaled Agile Framework (SAFe) 3.0 Program within Rational Team Concert 6.0.

Project Area Initialization Team areas - Initializes the project area with default team areas.

o Team 1 (rename)o Team 2 (rename)

Work Item Categories - Initializes the project area with default categories. For each of the Teams Areas representing SAFe Teams, create a work item category that enables work to be assigned specifically to that Team.

o Team 1 (rename)o Team 2 (rename)

Plans - Initializes the project area with the plans.

SAFe Team D

SAFe Team C

SAFe Program

SAFe Team B

SAFe Team A

SAFe Program

1

SAFe Portfolio (Coming Soon!)

CLM LPA or

RTC Project Area

RTC Project Area

RTC Project Area or

Team Area

Reports - Deploys the following pre-defined reports to the project area.o Actual as a Percentage of Estimated Worko Advanced Release Burndowno Blocking Work Itemso Build Health

o Build Resultso Burndowno Burnupo Closed Work Items Dailyo Code Healtho Cumulative Value Flowo Defect Backlogo Defect Backlog by Project Areao Defect Discovery Rateo Deferred Work Itemso Estimate Changeso Estimated vs Actual Worko Frequent Test Failureso Frequent Test Regressionso Micro Advanced Release Burndowno Micro Blocking Work Itemso Micro Build Durationo Micro Build Healtho Micro Burndowno Micro Burnupo Micro Change Set Activityo Micro Closed Work Items Dailyo Micro Closed Work Items by Priorityo Micro Compilation Warningso Micro Cumulative Value Flowo Micro Deferred Work Itemso Micro Estimated vs Actual Worko Micro File Change Activityo Micro Frequent Test Failureso Micro Frequent Test Regressionso Micro New Work Items by Severityo Micro Open Work Items by Priorityo Micro Open Work Items by Typeo Micro Open vs Closed Story Points by Iterationo Micro Open vs Closed Work Itemso Micro Release Burndowno Micro Story Pointso Micro Story Points Remainingo Micro Story Points by Iterationo Micro Team Velocityo Micro Test Failureso Micro Tests

o Micro Work Item Comparisono New Work Items by Severityo Open Work Itemso Micro Open Work Itemso Open Work Items by Typeo Open vs Closed Story Points by Iterationo Open vs Closed Work Itemso Planning Burndowno Planning Release Burndowno Planning Team Velocityo Project Activityo Release Burndowno Story Pointso Story Points Progresso Micro Story Points Progresso Story Points Remainingo Story Points by Iterationo Team Velocityo Work Item Comparisono Work Item Comparison by Project Areao Work Items by Ownero Work Items by Priorityo Work Items by Team Areao Risks by Exposure

Post project initialization – when the project is instantiated using this template it create a work item with the summary of Post-Project Initialization Tasks is created. The description in the new work item describes tasks that the program manager or release train engineer should perform to get started working in the new project area.

Note: Users assigned to product manager or release train engineer roles must perform these post-initialization tasks.1) Add members to the project and assign appropriate process roles:- Open the Project Area editor.- In the Members section, click Add.- Select the users.- Assign the process roles for the selected users.- Click Finish.- Save the project area.

2) Rename the team areas:- Open the Team Organization view in Eclipse client.

- Double-click the team area that has "rename" in its name , such as "Team 1 (rename)".- In the Team Area editor, type the team area name.- Create any other teams as applicable.- Save the project area.

3) Rename the categories and associate them with project / team areas:- Open the project area editor.- Click the Work Item Categories tab.- In the Categories section, double-click the category names that contain "rename", and replace them with the category names for your organization.- Add more categories as applicable.- Map the team areas to work item categories (Filed Against attribute).- In the left column, select the category for the program. Then, in the right column, select the project. Click Associate.- Associate any other categories to their respective team areas for one-to-one associations.- Save the project area.

4) Rename the plans:- From the web client, click Plans>All Plans.- Click on the plan to open it and edit the plan name.- Go back to Plans>All Plans and repeat above step to rename other plans.

5) Optional: Create and assign work items for program initiation activities:- Click Work Items> Create from Template ...- Select the Program Initiation template.- In the Filed Against field, choose the program category for the work items.- In the Planned For field, choose the first program increment for the work items.- Click on Create from Template.

6) Create and assign work items for the program increment:- Click Work Items> Create from Template ...- Select the Program Increment template.- In the Filed Against field, choose the program category for the work items.- In the Planned For field, choose the first program increment for the work items.- Click Create from Template.

7) The SAFe process template includes calculated scripts for WSJF calculation. To use scripts deployed as process attachments you need to enable this functionality:- Go to administrative page of your RTC server

https://your.server.name:9443/ccm/admin.- From the left side-bar open Configuration > Advanced Properties- In the Work Item Component find the Enable Process Attachment Scripts property and set its value to true.- You may need to restart the server before this takes effect.

For additional guidance on configuring your SAFe environment, refer to the SAFe Template instructions referenced on the IBM SAFe Landing Page .

Program/Team Timeline structure Creates a project timeline, with one top level iteration representing the Agile

Release Train, 3 Program Increment – each 10 week long (contains 5 sprints), 5 Sprints per PI – each 2 week long and 1 Backlog iteration

o (Program Name) Timeline [Project Timeline] (Program Name) Agile Release Train

PI1, 10 w durationo Sprint 1.1, 2 w durationo Sprint 1.2, 2 w durationo Sprint 1.3, 2 w durationo Sprint 1.4, 2 w durationo Sprint 1.5, 2 w duration

PI2, 10 w longo Sprint 2.1, 2 w durationo Sprint 2.2, 2 w durationo Sprint 2.3, 2 w durationo Sprint 2.4, 2 w durationo Sprint 2.5, 2 w duration

PI3, 10 w longo Sprint 3.1, 2 w durationo Sprint 3.2, 2 w durationo Sprint 3.3, 2 w durationo Sprint 3.4, 2 w durationo Sprint 3.5, 2 w duration

Backlog

Roles

SAFe Level

SAFe Role Comments

Program Product Manager

The product manager defines and prioritizes the program backlog, develops the vision and roadmap, works with product owners to optimize feature delivery to the customers, and sets PI Objectives. This person has content authority.

Business Analyst The business analyst defines initiatives (business epics) and determines the impact on the internal and external value streams of the enterprise.

UX Designer The UX designer works with stakeholders to understand the specific business targets of the user-system interaction. Responsibilities include UI design, UX guidelines, design elements, and the validation of user experience through user-experience testing.

System Architect The system architect defines a technological vision and implementation scenarios with architectural epics that support the business strategy. This person maintains a high-level understanding of user needs, system requirements, and business benefits for a release train.

Release Train Engineer

The release train engineer facilitates the agile release train processes and program execution, escalates impediments, manages risk, and drives continuous, program-level improvement. This person also facilitates

(Program Manager)

program events, such as release planning, inspect and adapt, and the scrum of scrums.

Business Owner The business owner is responsible for the value delivered by a specific ART. This person understands the strategic themes that influence the train, knows about the current business context, has decision-making influence on epics moving through the Kanban systems, is involved in driving or reviewing the program vision and road map, and has a significant role in release planning.

Team(Scrum based)

Product Owner The product owner defines and prioritizes the requirements backlog, helps to elaborate those requirements with the team, and accepts completed stories into the baseline. A team has only one product owner, who might be dedicated to one or two teams.

Scrum Master The scrum master facilitates team interactions and meetings, enforces the rules in a scrum, and helps drive the team's efforts to continuously improve. A team member or a scrum master might have a full- or part-time role that is shared across two or three teams.

Team Member The team member is usually a developer or tester, but this role might include other roles as well, such as a technical lead, a system architect, or a technical writer. A team normally has five to nine members.

Permissions

Project Configuration PermissionsActivity Grant PermissionsDashboards >Save Personal Dashboard EveryoneSave Project Dashboard Product Manager

Release Train Engineer

Process>Save Project Area Product Manager

Work Items>Save Attachment > Delete attachment

Product ManagerRelease Train Engineer

Save Attachment > Modify attachment

Everyone

Save Category> Modify a work item category

Product ManagerRelease Train Engineer

Save Release> Modify release Product ManagerRelease Train Engineer

Team Configuration PermissionsActivity Grant PermissionsDashboards > Save Team Product Manager

Dashboards Release Train EngineerProduct OwnerScrum MasterTeam Member

Planning (All) Product ManagerRelease Train EngineerScrum MasterTeam Member

Process > Generate Team InvitationProcess > Save process Description > Modify process descriptionProcess > Save Team AreaReports > Deploy ReportReports > Manage Report FolderProcess > Save process Description > Create process descriptionProcess > Save process Description > Delete process description

Product ManagerScrum Master

Reports > Display Report EveryoneWork Items > Delete QueryWork Items > Save QuerySave Work Item

Artifacts Program Level

o Program Vision – free format description of the Program Project Areao Program Backlog / Road map - a new plan type Program Backlog,

containing Kanban view, Roadmap, and WSJF Ranked Listo Program PI Objective – PI Objective work item type with a type attribute-

indicating its Program.o Program Epic - the “epic type” attribute to indicate whether the Epic

work item is Business or Architecturalo Feature – the “feature type” attribute to indicate whether the Feature

work item is Business, Architectural or NFR Team Level

o Sprint Backlogo Stories, Tasks, Defects, Risks, Retrospectiveso Team PI Objective – PI Objective work item type with a type attribute

indicating its Team.o Sprint Kanban Board

Work Item TypesSAFe artifacts that require workflow and are used in planning are instantiated as RTC work items. For each SAFe artifact, we have a corresponding work item type

which have a set of defined and customized attribute. Each work item type is associated with an Editor Presentation view and a Workflow. Attributes may be re-used across work item types. Descriptions of these artifacts can be found on the Scaled Agile Framework web site.

Work Item Type

RTC ID Notes

Plan ItemsProgram Epic com.ibm.team.workitem.workItemType.programEpic Epics that are constrained to a single train.Feature com.ibm.team.workitem.workItemType.feature Fulfill one or more stakeholder needs. Maintained in the Program Backlog. Can

be fit in a Program Increment. Bridge gaps between User Stories (sized to fit in iterations) and Program Epics (which span PIs). Uses Weighted Smallest Job First (WSJF) for continuous prioritization.

Story com.ibm.team.apt.workItemType.story Requirements specifications in Agile world. Small, independent behaviors that can be implemented incrementally, each of which provides value to the business. Negotiable and statement of intent rather than a contractually required behavior. Sized to fit in a single iteration.

Execution ItemsPI Objective com.ibm.team.workitem.workItemType.piObjective Describes the business and technical goals for the upcoming Program Increment

of an Agile Release Train. Each team summarizes their specific business and technical objectives for that PI (Team’s PI Objectives), once committed the team’s PI objectives are aggregated into the Program PI Objectives.

Defect com.ibm.team.workitem.workItemType.defect A bug, error, flaw in the implementation. Defects related to a Story can be associated with a Story using a parent/child link. Defects and Tasks associated with the Story are shown on the task board.

Task com.ibm.team.workitem.workItemType.task Defines a unit of work planned for a sprint and is estimated in hours. Tasks are linked to a Story using a parent/child link.

Retrospective com.ibm.team.workitem.workItemType.retrospective Used to capture the findings of the Sprint retrospective meeting.Risk com.ibm.team.workitem.workItemType.risk Identifies an uncertain event, which can negatively affect the project. It includes

an assessment of its probability of occurrence and impact.

Custom attributesAttribute Data Type RTC ID NotesProgram EpicEpic Type Epic Type

(Enumeration)com.ibm.team.workitem.attribute.epicType Architectural, Business

Value Statement

Wiki com.ibm.team.workitem.attribute.valueStatement Replaces the Description field in Program Epics

FeatureFeature Type Feature Type

(Enumeration)com.ibm.team.workitem.attribute.featureType Architectural, Business, NFR

Program Epic, FeatureJob Size Job Size

(Enumeration)com.ibm.team.workitem.attribute.jobSize Relative value

According to SAFe, use a relative scale (like story points): 1, 2, 3, 5, 8, 13, 20

Could also use “T-Shirt size” (H-M-L, L-M-S) Used in WSJF calculation Can use the same Data Type for all three but

this provides you the flexibility to change the enum values later for each of the WSJF components.

User/Business Value

User/Business Value (Enumeration)

com.ibm.team.workitem.attribute.ubVal

Time Criticality

Time Criticality (Enumeration)

com.ibm.team.workitem.attribute.timeCrit

RR/OE RROE(Enumeration)

com.ibm.team.workitem.attribute.rroe

WSJF Integer com.ibm.team.workitem.attribute.wsjf Calculated (read-only)PI ObjectivePI Objective Type

PI Objective Tpe (Enumeration)

com.ibm.team.workitem.attribute.piType Program, Team

Business Value (Planned)

Business Value (Enumeration)

com.ibm.team.workitem.attribute.busValuePlanned On a scale of 1-10

Business Value (Actual)

com.ibm.team.workitem.attribute.busValueActual

Associated Iteration

Iteration com.ibm.team.workitem.attribute.associatedIteration

StoryAcceptance Test

Large HTML com.ibm.team.apt.attribute.acceptance

Story Points Complexity (Enumeration)

com.ibm.team.apt.attribute.complexity

RiskContingency Plan

Large HTML com.ibm.team.workitem.attribute.contingencyPlan

Exposure(%) Long com.ibm.team.workitem.workItemType.risk.exposure

Impact Impact (Enumeration)

com.ibm.team.workitem.workItemType.risk.impact

Mitigation Plan

Large HTML com.ibm.team.workitem.attribute.mitigationPlan

Occurrence Date

Timestamp com.ibm.team.workitem.workItemType.risk.occurrencedate

Probability Probability (Enumeration)

com.ibm.team.workitem.workItemType.risk.probability

Risk Category Risk Category (Enumeration)

com.ibm.team.workitem.workItemType.risk.riskcategory

Program Epic Value Statement - used to capture, organize and communicate key information

about an epic. This is developed in the Kanban Review state and contains enough information to discuss the proposed initiative. Pre-configured with free-form text Value Statement entry field (in place of Description) with text that reminds the creator of what to specify.

Program Epics have different state groups than the other work item types. The state groups are:

– Funnel– Analysis– Backlog– Closed

These state groups are aligned to the kanban system referred to at http://www.scaledagileframework.com/business-epic-kanban/

Feature WSJF is key component to capture on Features. WSJF attributes captured in

normalized way (Fibonacci), calculated WSJF value.

Feature Type attribute

EnumerationsEnumeration RTC ID Enum Values DefaultEpic Type epicType Architectural

BusinessBusiness

Feature Type featureType ArchitecturalBusinessNFR

Business

Job Size jobSize Unassigned1, 2, 3, 5, 8, 13, 20

UnassignedUser/Business Value ubValTimeCrit timeCrit

RROE rroe

PI Objective Type piType ProgramTeam

Program

Business Value businessValue 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 1

Attribute customization Calculated Values

o WSJF - Supplies the Weighted Shortest Job First algorithm as per http://scaledagileframework.com/wsjf/

o Exposure Provider – depends on the Probability and Impact attributes in a Risk work item type.

Probability: The likelihood that the risk will occur. Impact: The degree to which the risk affects the project. Exposure: The magnitude or scope of the risk. Multiplying the

probability and impact and dividing that number by 100 determine the exposure.

Default Valueso Default Value statement in Program Epic

Planning

GeneralProgress on work items is tracked as Time Remaining;Display estimates in hours.Backlog is set as backlog iteration.

Plan AttributesComplexity Attribute – Story Points

Custom attributes that can be added as a column on a plan

Work EnvironmentAgile says that a working day is 6 hours, following that principle the working day in this template is set for 6 hours as the team using the Scrum process.

Plan Types

Quick Planner Planning views:

Program Backlog (new)

Kanban View – is based on the portfolio kanban system example provided at http://www.scaledagileframework.com/business-epic-kanban/

o excludes all items except the Program Epics, o sorted by WSJF, o shows the Summary, Owned By, WSJF and Planned For values on the cards

Roadmap – o tree view using the parent-child link type,o items are sorted by WSJF value, o shows Summary, Id, WSJF, Status and Planned For columns

WSJF Ranked List – o flat ranked list sorted by WSJF, o excludes all items except Features, o I knoshows Summary, ID, Status, WSJF, Job Size, User/Business Value, Time

Criticality, RROE columns

Sprint Backlog

Taskboard – Workflows of Story, Task and Defect is simplified to show a simplified sprint taskboard and kanban view. These views exclude all items except Stories, Tasks and Defects.

Sprint Kanban Board

Release Backlog

Product Backlog

Cross-Project Plan

Predefined Queries

Program level

Predefined Query RTC ID DescriptionOpen features com.ibm.team.workitem.queries.predefined.openFeatures Unresolved open features

Open program epics com.ibm.team.workitem.queries.predefined.openProgramEpics Program epics that are unresolved

Open program PI objectives

com.ibm.team.workitem.queries.predefined.openProgramPIObjectives

Unresolved program PIobjectives

Open team PI objectives

com.ibm.team.workitem.queries.predefined.openTeamPIObjectives Unresolved team PI objectives

Open non -feature work items

com.ibm.team.workitem.queries.predefined.openNotFeatures Unresolved open non-feature work items

Team level

Predefined Query RTC ID DescriptionOpen Risks com.ibm.team.workitem.queries.predefined.openRisks Risks that is unresolved.

Retrospectives com.ibm.team.workitem.queries.predefined.allRetrospectives Find all Retrospectives.

Open work items created by me

com.ibm.team.workitem.queries.predefined.openCreated Work items I have created which are open or in progress.

Closed work items created by me

com.ibm.team.workitem.queries.predefined.closedCreated Work items I have created which have been resolved.

Work Items resolved by me

com.ibm.team.workitem.queries.predefined.myResolved Work items I have resolved.

Open work items subscribed by me

com.ibm.team.workitem.queries.predefined.openSubscribed My subscriptions to open or in progress work items.

Closed work items subscribed by me

com.ibm.team.workitem.queries.predefined.closedSubscribed My subscriptions to resolved work items.

Open work items assigned to me (current sprint)

com.ibm.team.workitem.queries.predefined.myOpenCurrent To do list for the current sprint.

Recently modified work items

com.ibm.team.workitem.queries.predefined.recentlyModified Modified in the last 12 hours.

Recently closed work items

com.ibm.team.workitem.queries.predefined.recentlyClosed Closed in the last 12 hours.

Pending approvals for me

com.ibm.team.workitem.queries.predefined.pendingApprovals Pending requests for approvals or reviews that involve me.

Blocked work items

com.ibm.team.workitem.queries.predefined.blocked Work items that have a "Depends On" link to an open work item.

Open stories com.ibm.team.workitem.queries.predefined.openStories Stories that is unresolved.

Stories ready for testing

com.ibm.team.workitem.queries.predefined.readyForTesting Stories with the "In Test" status.

Stories (current sprint)

com.ibm.team.workitem.queries.predefined.allStoriesCurrent Stories in the current sprint.

Recently modified by me

com.ibm.team.workitem.queries.predefined.myRecentlyModified Work Items I have modified in the last 12 hours.

Recently created by me

com.ibm.team.workitem.queries.predefined.myRecentlyCreated Work Items I have created in the last 12 hours.

My current work com.ibm.team.workitem.queries.predefined.myInProgress Work Items in progress and assigned to me.

My work items pending approval

com.ibm.team.workitem.queries.predefined.myPendingApprovals Work items created by me that are pending approval.

Open defects (current sprint)

com.ibm.team.workitem.queries.predefined.openDefectsCurrent Open defects planned for the current sprint.

Open stories (current sprint)

com.ibm.team.workitem.queries.predefined.openStoriesCurrent Current Stories that are unresolved.

Stories Needing Business Value

com.ibm.team.workitem.queries.predefined.storyNeedingBusinessValue Stories that have an unassigned Business Value attribute.

Stories unassigned (current sprint)

com.ibm.team.workitem.queries.predefined.storyNeedingOwnerCurrentSprint

Stories with no owner in the current sprint.

Stories without children (current sprint)

com.ibm.team.workitem.queries.predefined.storyNoChildrenCurrentSprint Stories without any children (e.g tasks) in the current sprint.

Tasks Unassigned (current sprint)

com.ibm.team.workitem.queries.predefined.tasksNoOwnerCurrentSprint Tasks that do not have an owner in the current sprint.

Tasks without a parent work item

com.ibm.team.workitem.queries.predefined.tasksNoParent Tasks that do not have a parent work item.

Tasks without estimates

com.ibm.team.workitem.queries.predefined.tasksNoEstimate Tasks that do not have an estimate greater than zero.

Stories needing story points

com.ibm.team.workitem.queries.predefined.storiesNoStoryPoints Stories with zero story points. (?? (0 pts))

Stories in progress (current sprint)

com.ibm.team.workitem.queries.predefined.storiesInProgressCurrent Stories that have started work but not closed in the current sprint.

Stories closed (current sprint)

com.ibm.team.workitem.queries.predefined.storiesClosedCurrent Stories that are closed in the currrent sprint.

My defects by severity

com.ibm.team.workitem.queries.predefined.myDefectsInProgress Work Items in progress and assigned to me

Work Item templatesProject areas that are based on the SAFe process template include the following templates that you can use to create work items:

Program Initiation: Use to create work items applicable when a program is first initiated.

o Program initiation - Work items for starting a new program.o Create a vision – See, http://www.scaledagileframework.com/vision/.

Can use the Notes tab in a plan to document the visiono Create a roadmap – See,

http://www.scaledagileframework.com/roadmap/. The new Program Backlog plan type has a Roadmap plan view, which can be used.

o Populate program backlog – See, http://www.scaledagileframework.com/program-backlog/. Use the new Program Backlog plan type.

Program Increment: Use at the start of each Program Increment to create work items for typical program events.

o Program increment - Work items for a program incremento Prepare for release planning - Work items for preparing for release

planning

o Refine and prioritize the Program Backlog (architecture) - See, http://www.scaledagileframework.com/program-backlog/

o Refine and prioritize the Program Backlog (features) - See, http://www.scaledagileframework.com/program-backlog/

o Prepare executive briefing - See, http://www.scaledagileframework.com/release-planning/

o Prepare product vision briefing - See, http://www.scaledagileframework.com/release-planning/

o Prepare architecture vision briefing - See, http://www.scaledagileframework.com/release-planning/

o Release planning readiness – Organizational/Content/Facility readiness. See, http://www.scaledagileframework.com/release-planning/

o Release planning event – See, http://www.scaledagileframework.com/release-planning/

o Execute the program - Work items for executing the program during a program increment.

o Release management meeting – See, http://www.scaledagileframework.com/release-management/

o Conduct scrum of scrums – See Scrum of Scrums section in http://www.scaledagileframework.com/agile-release-train/

o System demo – See, http://www.scaledagileframework.com/system-demo/

o Conduct program-level inspect and adapt work shop – Retrospective work item that also provides a link to the sample program self assessment checklist. See, http://www.scaledagileframework.com/inspect-and-adapt/

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

o Development Iteration - Work items for typical development iteration events.

o Backlog refinement – See, http://www.scaledagileframework.com/team-backlog/

o Iteration planning – See, http://www.scaledagileframework.com/iteration-planning/

o Executing and tracking – See, http://www.scaledagileframework.com/iterations/

o Team demo – See, http://www.scaledagileframework.com/team-demo/o Iteration retrospective – Retrospective work item that also provides a link

to the sample team self-assessment checklist. See, http://www.scaledagileframework.com/iteration-retrospective/.

o System demo – See, http://www.scaledagileframework.com/system-demo/

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

o Innovation and Planning – See, http://www.scaledagileframework.com/innovation-planning/

o Release planning readiness - See, http://www.scaledagileframework.com/innovation-planning/

o System validation - See, http://www.scaledagileframework.com/innovation-planning/

o Innovation/hackathon/spikes for PI Next - See, http://www.scaledagileframework.com/innovation-planning/

o Continuing education - See, http://www.scaledagileframework.com/innovation-planning/

o Inspect and adapt workshop - See, http://www.scaledagileframework.com/inspect-and-adapt/

o Release planning – See, http://www.scaledagileframework.com/release-planning/

Reports M1: Iteration Metrics

RTCo Open vs Closed Story Points by Iteration – Measure of velocityo Open vs Closed Work Items – Measure of velocityo Release Burndown – Amount of outstanding work for the release

broken down by iterationo Advanced Release Burndown – Amount of outstanding work for the

release broken down by iterationo Story Points – Magnitude of story points achieved o Story Points by Iteration – Measure of planned velocity

o Story Points Progress – Measure of velocity o Team Velocity – Measure of velocityo Story Points Remaining – Measure of achievement/progresso Cumulative Value Flow – An area plot of open work items, in progress

work items and closed work items overtime o Work Items Statistics – Graph based on query

JRSo JRS reports not included as part of the template however instructions on

how the user can set it up is provided as a HTML widget on the Program dashboard.

M2: SAFe ScrumXP Self-Assessmento Development Iteration work item template creates a work item with

summary Iteration retrospective. This contains the link to IBM’s SAFe Team-level Self Assessment - http://bit.ly/ibmsafeteamselfassessment

M3: Agile Release Train Self-Assessmento Program Increment work item template creates a work item with

summary Conduct program-level inspect and adapt work shop. This contains the link to IBM’s SAFe Program-level Self Assessment - http://bit.ly/ibmsafeprogramselfassessment

M4: Release Progress Reports

o None available OOTB

M5 similar to M1 metrics but at Program level

Role based dashboardProvide an OOTB dashboard configuration. Instantiate one each for Program and Team with the set of widgets SAFe prescribes to measure and report on that level of the planning and execution.

Program dashboard

o Program Overview Team Members Teams Vision Statement Example

Resources

o Program Details Current Plans

o Release Planning HTML Widget describing how to add SAFE JRS Reports to Program

Dashboard Show all Program PI Objectives

o Dependency Management HTML Widget describing how to add SAFE JRS Reports to Program

Dashboard Blocked Work Items

o Trends HTML Widget describing how to add SAFE JRS Reports to Program

Dashboard

Team Velocity

Team dashboardo General

Team Description Definition of Done Bookmarks Message Board Current Plans Events Log All Stories (current sprint) Team Members

o Scrum Master Work Items Needing Attention

Stories Needing Owner (Current Sprint) Stories with no Children (Current Sprint) Stories with no Story Points Tasks with out Parent

Team Velocity Estimated vs Actual Work Sprint Burndown Release Burndown Sprint Cumulative Value Flow Stories that Need Story Points Open Risks

o Product Owner Current Plans Release Burndown Pending Approvals for Me Stories in Progress (Current Sprint) Stories ready for testing (Current Sprint) Stories Closed (Current Sprint) Open vs Closed Story Points by Iteration

o Team Member Blocked Work Items Tasks without Owners Open Defects (Current Sprint) Open Work Items by Type Work Items by Owner Stories (Current Sprint) Team Sprint Burndown Team Velocity Builds Feed

Personal dashboardo General

About Me Welcome to Rational Team Concert Customize Your Dashboard My Work Item Changes My Work – open current work Pending Approvals for me