SAFe Concepts supported in RTC - Jazz Community Site



RTC 6.0 Scaled Agile Framework? (SAFe?) Solution TOC \o "1-5" SAFe Concepts supported in RTC PAGEREF _Toc293001839 \h 1Multiple RTC Project Areas: Portfolio, Program + Teams PAGEREF _Toc293001840 \h 3Process template for Program + Teams PAGEREF _Toc293001841 \h 5Project Area Initialization PAGEREF _Toc293001842 \h 5Program/Team Timeline structure PAGEREF _Toc293001843 \h 10Roles PAGEREF _Toc293001844 \h 11Permissions PAGEREF _Toc293001845 \h 12Project Configuration Permissions PAGEREF _Toc293001846 \h 12Team Configuration Permissions PAGEREF _Toc293001847 \h 12Artifacts PAGEREF _Toc293001848 \h 13Work Item Types PAGEREF _Toc293001849 \h 14Custom attributes PAGEREF _Toc293001850 \h 15Program Epic PAGEREF _Toc293001851 \h 16Feature PAGEREF _Toc293001852 \h 17Enumerations PAGEREF _Toc293001853 \h 17Attribute customization PAGEREF _Toc293001854 \h 17Planning PAGEREF _Toc293001855 \h 18General PAGEREF _Toc293001856 \h 18Plan Attributes PAGEREF _Toc293001857 \h 19Work Environment PAGEREF _Toc293001858 \h 20Plan Types PAGEREF _Toc293001859 \h 21Program Backlog (new) PAGEREF _Toc293001860 \h 21Sprint Backlog PAGEREF _Toc293001861 \h 22Sprint Kanban Board PAGEREF _Toc293001862 \h 23Release Backlog PAGEREF _Toc293001863 \h 23Product Backlog PAGEREF _Toc293001864 \h 23Cross-Project Plan PAGEREF _Toc293001865 \h 23Predefined Queries PAGEREF _Toc293001866 \h 23Program level PAGEREF _Toc293001867 \h 23Team level PAGEREF _Toc293001868 \h 24Work Item templates PAGEREF _Toc293001869 \h 28Reports PAGEREF _Toc293001870 \h 30Role based dashboard PAGEREF _Toc293001871 \h 32SAFe 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 SEQ Figure \* ARABIC 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 LevelSAFe ConceptRTC ConceptNotesProgram?????Roadmap & VisionPlan ViewVision can be a tab on the plan editor or it can be reflected in an HTML widget on the dashboardProgram BacklogPlan View?Program RoadmapPlan ViewArchitectural RunwayPlan View?Program EpicWork Item TypeEpic Type (Business/Architectural) attribute on the Program Epic work item typeFeatureWork Item TypeFeature Type (Business/Architectural/NFR*) attribute on Feature work item type?* Non Functional RequirementProgram PI ObjectiveWork Item TypePI Objective work item type with Program value for PI Type.Team??StoryWork Item Type?TaskWork Item TypeTeam PI ObjectiveWork Item TypePI Objective work item type with Team for PI Type.Team BacklogPlan ViewQP Planning Views?<All Levels>RoleRole Assigned to appropriate Project Area or Team AreaCreated in the Project Area for the right levelMultiple 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 TeamsEstablish a new Program that tracks work of existing teamsRTC Project Area or Team AreaRTC Project AreaCLM LPA or RTC Project AreaSAFe Portfolio (Coming Soon!)SAFe Program 1SAFe Team ASAFe Team BSAFe Program 2SAFe Team CSAFe Team DSAFe Team ERTC Project Area or Team AreaRTC Project AreaCLM LPA or RTC Project AreaSAFe Portfolio (Coming Soon!)SAFe Program 1SAFe Team ASAFe Team BSAFe Program 2SAFe Team CSAFe Team DSAFe Team ERTC 6.0 provides the following OOTB process templatesProcess template for Program + TeamsProcess 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 InitializationTeam areas - Initializes the project area with default team areas.Team 1 (rename)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. Team 1 (rename)Team 2 (rename)Plans - Initializes the project area with the plans.Reports - Deploys the following pre-defined reports to the project area.Actual as a Percentage of Estimated WorkAdvanced Release BurndownBlocking Work ItemsBuild HealthBuild ResultsBurndownBurnupClosed Work Items DailyCode HealthCumulative Value FlowDefect BacklogDefect Backlog by Project AreaDefect Discovery RateDeferred Work ItemsEstimate ChangesEstimated vs Actual WorkFrequent Test FailuresFrequent Test RegressionsMicro Advanced Release BurndownMicro Blocking Work ItemsMicro Build DurationMicro Build HealthMicro BurndownMicro BurnupMicro Change Set ActivityMicro Closed Work Items DailyMicro Closed Work Items by PriorityMicro Compilation WarningsMicro Cumulative Value FlowMicro Deferred Work ItemsMicro Estimated vs Actual WorkMicro File Change ActivityMicro Frequent Test FailuresMicro Frequent Test RegressionsMicro New Work Items by SeverityMicro Open Work Items by PriorityMicro Open Work Items by TypeMicro Open vs Closed Story Points by IterationMicro Open vs Closed Work ItemsMicro Release BurndownMicro Story PointsMicro Story Points RemainingMicro Story Points by IterationMicro Team VelocityMicro Test FailuresMicro TestsMicro Work Item ComparisonNew Work Items by SeverityOpen Work ItemsMicro Open Work ItemsOpen Work Items by TypeOpen vs Closed Story Points by IterationOpen vs Closed Work ItemsPlanning BurndownPlanning Release BurndownPlanning Team VelocityProject ActivityRelease BurndownStory PointsStory Points ProgressMicro Story Points ProgressStory Points RemainingStory Points by IterationTeam VelocityWork Item ComparisonWork Item Comparison by Project AreaWork Items by OwnerWork Items by PriorityWork Items by Team AreaRisks by ExposurePost 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 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 structureCreates 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 (Program Name) Timeline [Project Timeline](Program Name) Agile Release TrainPI1, 10 w durationSprint 1.1, 2 w durationSprint 1.2, 2 w durationSprint 1.3, 2 w durationSprint 1.4, 2 w durationSprint 1.5, 2 w durationPI2, 10 w longSprint 2.1, 2 w durationSprint 2.2, 2 w durationSprint 2.3, 2 w durationSprint 2.4, 2 w durationSprint 2.5, 2 w durationPI3, 10 w longSprint 3.1, 2 w durationSprint 3.2, 2 w durationSprint 3.3, 2 w durationSprint 3.4, 2 w durationSprint 3.5, 2 w durationBacklogRolesSAFe LevelSAFe RoleCommentsProgramProduct ManagerThe 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 AnalystThe business analyst defines initiatives (business epics) and determines the impact on the internal and external value streams of the enterprise.UX DesignerThe 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 ArchitectThe 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 (Program Manager)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 events, such as release planning, inspect and adapt, and the scrum of scrums.Business OwnerThe 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 OwnerThe 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 MasterThe 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 MemberThe 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.PermissionsProject Configuration PermissionsActivityGrant PermissionsDashboards > Save Personal DashboardEveryoneSave Project DashboardProduct ManagerRelease Train EngineerProcess>Save Project AreaProduct ManagerWork Items>Save Attachment > Delete attachmentProduct ManagerRelease Train EngineerSave Attachment > Modify attachmentEveryoneSave Category> Modify a work item categoryProduct ManagerRelease Train EngineerSave Release> Modify releaseProduct ManagerRelease Train EngineerTeam Configuration PermissionsActivityGrant PermissionsDashboards > Save Team DashboardsProduct ManagerRelease Train EngineerProduct OwnerScrum MasterTeam MemberPlanning (All)Product Manager Release Train EngineerScrum Master Team MemberProcess > Generate Team InvitationProcess > Save process Description > Modify process descriptionProcess > Save Team AreaReports > Deploy Report Reports > Manage Report FolderProcess > Save process Description > Create process descriptionProcess > Save process Description > Delete process descriptionProduct Manager Scrum MasterReports > Display ReportEveryoneWork Items > Delete QueryWork Items > Save QuerySave Work ItemArtifactsProgram LevelProgram Vision – free format description of the Program Project AreaProgram Backlog / Road map - a new plan type Program Backlog, containing Kanban view, Roadmap, and WSJF Ranked ListProgram PI Objective – PI Objective work item type with a type attribute-indicating its Program.Program Epic - the “epic type” attribute to indicate whether the Epic work item is Business or ArchitecturalFeature – the “feature type” attribute to indicate whether the Feature work item is Business, Architectural or NFRTeam LevelSprint BacklogStories, Tasks, Defects, Risks, RetrospectivesTeam PI Objective – PI Objective work item type with a type attribute indicating its Team.Sprint Kanban BoardWork 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 TypeRTC IDNotesPlan ItemsProgram Epiccom.ibm.team.workitem.workItemType.programEpicEpics that are constrained to a single train.Featurecom.ibm.team.workitem.workItemType.featureFulfill 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.Storycom.ibm.team.apt.workItemType.storyRequirements 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 Objectivecom.ibm.team.workitem.workItemType.piObjectiveDescribes 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.Defectcom.ibm.team.workitem.workItemType.defectA 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.Taskcom.ibm.team.workitem.workItemType.taskDefines a unit of work planned for a sprint and is estimated in hours. Tasks are linked to a Story using a parent/child link.Retrospectivecom.ibm.team.workitem.workItemType.retrospectiveUsed to capture the findings of the Sprint retrospective meeting.Riskcom.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 attributesAttributeData TypeRTC IDNotesProgram EpicEpic TypeEpic Type (Enumeration)com.ibm.team.workitem.attribute.epicTypeArchitectural, BusinessValue Statement Wikicom.ibm.team.workitem.attribute.valueStatementReplaces the Description field in Program EpicsFeature Feature TypeFeature Type (Enumeration)com.ibm.team.workitem.attribute.featureTypeArchitectural, Business, NFRProgram Epic, FeatureJob SizeJob Size (Enumeration)com.ibm.team.workitem.attribute.jobSizeRelative valueAccording to SAFe, use a relative scale (like story points): 1, 2, 3, 5, 8, 13, 20Could also use “T-Shirt size” (H-M-L, L-M-S)Used in WSJF calculationCan 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 ValueUser/Business Value (Enumeration)com.ibm.team.workitem.attribute.ubValTime CriticalityTime Criticality (Enumeration)com.ibm.team.workitem.attribute.timeCritRR/OERROE(Enumeration)com.ibm.team.workitem.attribute.rroeWSJFIntegercom.ibm.team.workitem.attribute.wsjfCalculated (read-only)PI ObjectivePI Objective TypePI Objective Tpe (Enumeration)com.ibm.team.workitem.attribute.piTypeProgram, TeamBusiness Value (Planned)Business Value (Enumeration)com.ibm.team.workitem.attribute.busValuePlannedOn a scale of 1-10 Business Value (Actual)com.ibm.team.workitem.attribute.busValueActualAssociated IterationIterationcom.ibm.team.workitem.attribute.associatedIterationStoryAcceptance TestLarge HTMLcom.ibm.team.apt.attribute.acceptanceStory PointsComplexity (Enumeration)com.ibm.team.apt.plexityRisk Contingency PlanLarge HTMLcom.ibm.team.workitem.attribute.contingencyPlanExposure(%)Longcom.ibm.team.workitem.workItemType.risk.exposureImpactImpact (Enumeration)com.ibm.team.workitem.workItemType.risk.impactMitigation PlanLarge HTMLcom.ibm.team.workitem.attribute.mitigationPlanOccurrence DateTimestampcom.ibm.team.workitem.workItemType.risk.occurrencedateProbabilityProbability (Enumeration)com.ibm.team.workitem.workItemType.risk.probabilityRisk CategoryRisk Category (Enumeration)com.ibm.team.workitem.workItemType.risk.riskcategoryProgram EpicValue 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:FunnelAnalysisBacklogClosedThese state groups are aligned to the kanban system referred to at is key component to capture on Features. WSJF attributes captured in normalized way (Fibonacci), calculated WSJF value.Feature Type attributeEnumerationsEnumerationRTC IDEnum ValuesDefaultUnassignedEpic Type epicTypeArchitecturalBusinessBusinessBusinessFeature TypefeatureTypeArchitecturalBusinessNFRBusinessBusinessJob SizejobSizeUnassigned1, 2, 3, 5, 8, 13, 20UnassignedUnassignedUser/Business Value ubValTimeCrittimeCritRROE rroePI Objective TypepiTypeProgramTeamProgramProgramBusiness Value businessValue1, 2, 3, 4, 5, 6, 7, 8, 9, 10 11Attribute customizationCalculated ValuesWSJF - Supplies the Weighted Shortest Job First algorithm as per 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 ValuesDefault Value statement in Program Epic PlanningGeneralProgress on work items is tracked as Time Remaining;Display estimates in hours.Backlog is set as backlog iteration.Plan AttributesComplexity Attribute – Story PointsCustom attributes that can be added as a column on a planWork 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 TypesQuick Planner Planning views:Program Backlog (new)Kanban View – is based on the portfolio kanban system example provided at all items except the Program Epics, sorted by WSJF, shows the Summary, Owned By, WSJF and Planned For values on the cardsRoadmap – tree view using the parent-child link type,items are sorted by WSJF value, shows Summary, Id, WSJF, Status and Planned For columnsWSJF Ranked List – flat ranked list sorted by WSJF, excludes all items except Features, I knoshows Summary, ID, Status, WSJF, Job Size, User/Business Value, Time Criticality, RROE columnsSprint BacklogTaskboard – 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 BoardRelease BacklogProduct BacklogCross-Project PlanPredefined QueriesProgram levelPredefined QueryRTC IDDescriptionOpen featurescom.ibm.team.workitem.queries.predefined.openFeaturesUnresolved open featuresOpen program epicscom.ibm.team.workitem.queries.predefined.openProgramEpicsProgram epics that are unresolvedOpen program PI objectivescom.ibm.team.workitem.queries.predefined.openProgramPIObjectivesUnresolved program PI objectivesOpen team PI objectivescom.ibm.team.workitem.queries.predefined.openTeamPIObjectivesUnresolved team PI objectivesOpen non -feature work itemscom.ibm.team.workitem.queries.predefined.openNotFeaturesUnresolved open non-feature work itemsTeam levelPredefined QueryRTC IDDescriptionOpen Riskscom.ibm.team.workitem.queries.predefined.openRisksRisks that is unresolved.Retrospectivescom.ibm.team.workitem.queries.predefined.allRetrospectivesFind all Retrospectives.Open work items created by mecom.ibm.team.workitem.queries.predefined.openCreatedWork items I have created which are open or in progress.Closed work items created by mecom.ibm.team.workitem.queries.predefined.closedCreatedWork items I have created which have been resolved.Work Items resolved by mecom.ibm.team.workitem.queries.predefined.myResolvedWork items I have resolved.Open work items subscribed by mecom.ibm.team.workitem.queries.predefined.openSubscribedMy subscriptions to open or in progress work items.Closed work items subscribed by mecom.ibm.team.workitem.queries.predefined.closedSubscribedMy subscriptions to resolved work items.Open work items assigned to me (current sprint)com.ibm.team.workitem.queries.predefined.myOpenCurrentTo do list for the current sprint.Recently modified work itemscom.ibm.team.workitem.queries.predefined.recentlyModifiedModified in the last 12 hours.Recently closed work itemscom.ibm.team.workitem.queries.predefined.recentlyClosedClosed in the last 12 hours.Pending approvals for mecom.ibm.team.workitem.queries.predefined.pendingApprovalsPending requests for approvals or reviews that involve me.Blocked work itemscom.ibm.team.workitem.queries.predefined.blockedWork items that have a "Depends On" link to an open work item.Open storiescom.ibm.team.workitem.queries.predefined.openStoriesStories that is unresolved.Stories ready for testingcom.ibm.team.workitem.queries.predefined.readyForTestingStories with the "In Test" status.Stories (current sprint)com.ibm.team.workitem.queries.predefined.allStoriesCurrentStories in the current sprint.Recently modified by mecom.ibm.team.workitem.queries.predefined.myRecentlyModifiedWork Items I have modified in the last 12 hours.Recently created by mecom.ibm.team.workitem.queries.predefined.myRecentlyCreatedWork Items I have created in the last 12 hours.My current workcom.ibm.team.workitem.queries.predefined.myInProgressWork Items in progress and assigned to me.My work items pending approvalcom.ibm.team.workitem.queries.predefined.myPendingApprovalsWork items created by me that are pending approval.Open defects (current sprint)com.ibm.team.workitem.queries.predefined.openDefectsCurrentOpen defects planned for the current sprint.Open stories (current sprint)com.ibm.team.workitem.queries.predefined.openStoriesCurrentCurrent Stories that are unresolved.Stories Needing Business Valuecom.ibm.team.workitem.queries.predefined.storyNeedingBusinessValueStories that have an unassigned Business Value attribute.Stories unassigned (current sprint)com.ibm.team.workitem.queries.predefined.storyNeedingOwnerCurrentSprintStories with no owner in the current sprint.Stories without children (current sprint)com.ibm.team.workitem.queries.predefined.storyNoChildrenCurrentSprintStories without any children (e.g tasks) in the current sprint.Tasks Unassigned (current sprint)com.ibm.team.workitem.queries.predefined.tasksNoOwnerCurrentSprintTasks that do not have an owner in the current sprint.Tasks without a parent work itemcom.ibm.team.workitem.queries.predefined.tasksNoParentTasks that do not have a parent work item.Tasks without estimatescom.ibm.team.workitem.queries.predefined.tasksNoEstimateTasks that do not have an estimate greater than zero.Stories needing story pointscom.ibm.team.workitem.queries.predefined.storiesNoStoryPointsStories with zero story points. (?? (0 pts))Stories in progress (current sprint)com.ibm.team.workitem.queries.predefined.storiesInProgressCurrentStories that have started work but not closed in the current sprint.Stories closed (current sprint)com.ibm.team.workitem.queries.predefined.storiesClosedCurrentStories that are closed in the currrent sprint.My defects by severitycom.ibm.team.workitem.queries.predefined.myDefectsInProgressWork Items in progress and assigned to meWork 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.Program initiation - Work items for starting a new program.Create a vision – See, . Can use the Notes tab in a plan to document the visionCreate a roadmap – See, . The new Program Backlog plan type has a Roadmap plan view, which can be used.Populate program backlog – See, . 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.Program increment - Work items for a program incrementPrepare for release planning - Work items for preparing for release planningRefine and prioritize the Program Backlog (architecture) - See, and prioritize the Program Backlog (features) - See, executive briefing - See, product vision briefing - See, architecture vision briefing - See, planning readiness – Organizational/Content/Facility readiness. See, planning event – See, the program - Work items for executing the program during a program increment.Release management meeting – See, scrum of scrums – See Scrum of Scrums section in demo – See, program-level inspect and adapt work shop – Retrospective work item that also provides a link to the sample program self assessment checklist. See, Development Iteration: Use before the start of each development iteration and for each team to create work items for typical iteration events.Development Iteration - Work items for typical development iteration events.Backlog refinement – See, planning – See, and tracking – See, demo – See, retrospective – Retrospective work item that also provides a link to the sample team self-assessment checklist. See, demo – See, and Planning: Use prior to each Innovation and Planning Sprint and for each team, to create work items for typical Sprint events.Innovation and Planning – See, planning readiness - See, validation - See, for PI Next - See, education - See, and adapt workshop - See, planning – See, : Iteration MetricsRTCOpen vs Closed Story Points by Iteration – Measure of velocityOpen vs Closed Work Items – Measure of velocityRelease Burndown – Amount of outstanding work for the release broken down by iterationAdvanced Release Burndown – Amount of outstanding work for the release broken down by iterationStory Points – Magnitude of story points achieved Story Points by Iteration – Measure of planned velocity Story Points Progress – Measure of velocity Team Velocity – Measure of velocityStory Points Remaining – Measure of achievement/progressCumulative Value Flow – An area plot of open work items, in progress work items and closed work items overtime Work Items Statistics – Graph based on query JRSJRS 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-AssessmentDevelopment Iteration work item template creates a work item with summary Iteration retrospective. This contains the link to IBM’s SAFe Team-level Self Assessment - : Agile Release Train Self-AssessmentProgram 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 - : Release Progress ReportsNone available OOTBM5 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 dashboardProgram OverviewTeam MembersTeamsVision Statement ExampleResourcesProgram DetailsCurrent PlansRelease PlanningHTML Widget describing how to add SAFE JRS Reports to Program DashboardShow all Program PI ObjectivesDependency ManagementHTML Widget describing how to add SAFE JRS Reports to Program DashboardBlocked Work ItemsTrendsHTML Widget describing how to add SAFE JRS Reports to Program DashboardTeam VelocityTeam dashboardGeneralTeam DescriptionDefinition of DoneBookmarksMessage BoardCurrent PlansEvents LogAll Stories (current sprint)Team MembersScrum MasterWork Items Needing AttentionStories Needing Owner (Current Sprint)Stories with no Children (Current Sprint)Stories with no Story PointsTasks with out ParentTeam VelocityEstimated vs Actual WorkSprint BurndownRelease BurndownSprint Cumulative Value FlowStories that Need Story PointsOpen RisksProduct OwnerCurrent PlansRelease BurndownPending Approvals for MeStories in Progress (Current Sprint)Stories ready for testing (Current Sprint)Stories Closed (Current Sprint)Open vs Closed Story Points by IterationTeam MemberBlocked Work ItemsTasks without OwnersOpen Defects (Current Sprint)Open Work Items by TypeWork Items by OwnerStories (Current Sprint)Team Sprint BurndownTeam VelocityBuilds FeedPersonal dashboardGeneralAbout MeWelcome to Rational Team ConcertCustomize Your DashboardMy Work Item ChangesMy Work – open current workPending Approvals for me ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download