Acceptance Criteria is an essential part of a Story or a Feature and is used to define when the Story or Feature is successfully completed.
Resources
How-Tos
Improvements discovered during Retrospectives can be added as Action items so they can be tracked and acted on. Action Items can be converted to Stories to be included in future planning.
To add updates to a Story while it is being worked on, you can use the Comments in a Story.
Work can be assigned to a specific team member or multiple team members by assigning the Story to the individual(s).
When you copy a Story or Feature, many details are copied, including Title, Description, Assignee, Effort, etc., and some details are not, such as Acceptance Criteria, Definitions of Done, and others.
Capabilities are entities that represent a significant effort that spans multiple Agile Release Trains (ARTs). They are intended to be completed in a single Planning Interval (PI).
A Feature represents a body of work that will deliver value and can be completed within one Program Increment (PI). Features are broken down into Stories.
During PI Planning, the Team PI Objectives can be added to the corresponding University Commitments.
The Retrospective tool in Targetprocess is designed for team Iteration Retrospectives.
This tool can also be useful to solicit feedback in a PI Inspect and Adapt (I&A) event.
Stories are the breakdown of the total work needed to complete a Feature. They are a short description of a small piece of work that can be completed within one Iteration.
Epics are entities that represent large scale work.
When starting a new Iteration, your Iteration goals can be added to the Team's Objectives & Goals view.
This article provides instructions for creating and viewing Products in Targetprocess.
Only users with the following roles in Targetprocess have the ability to create and modify Products:
Audience: Administrators, Release Train Engineers, Product Managers
Audience: Product Managers, Release Train Engineers
Audience: Product Managers, Release Train Engineers, Product Owners, and Scrum Coaches
Before creating a Report, it's helpful to identify some information:
Audience: Product Managers, Release Train Engineers, Product Owners, and Scrum Coaches
Product Managers, Product Owners, and Scrum Coaches can add dependencies on other teams directly into Targetprocess but also must communicate with the team whose time is being requested to negotiate and coordinat
Sometimes your work needs to be completed before other work can begin, or your work might depend on other work being completed first. These types of time-based dependencies are referred to as inbound and outbound:
Issues that might impact work getting done are referred to as Risks. Risks that are identified during PI Planning are documented in the Risks view.
Capacity is the estimated amount of work a person or a team can accomplish in an Iteration.
Story Points are referred to as Effort within Targetprocess. Effort is managed within the Assignments section of the Story details.
Audience: All Targetprocess users
You can export reports and aggregated results by selecting the Actions button in the upper right of the report.
Audience: All Targetprocess users
Any view in Targetprocess, regardless of type, can be exported. Anyone in Targetprocess can export any view to which they have access.
Audience: All Targetprocess users
You can filter Reports to refine the data set being used for the report.
Audience: All Targetprocess users
Use the Team Kanban to view Stories in the workflow.
In Targetprocess, you have the ability to add, edit, present, and extract data about your work. Views are how you interact with that data.
Priorities can change mid-PI. When this happens, Product Managers and Product Owners need to communicate the change in priorities to Scrum Coaches and the team.
If a Story is incomplete at the end of an Iteration, it may need to be moved to another Iteration, postponed, or canceled.
When a team becomes aware that a committed Feature will not be completed by the end of a PI, the Scrum Coach should communicate with the Product Manager and Product Owner.
Teams are empowered to change Stories at any point during a PI or iteration to reflect the actual work that is needed.
When a Feature is being worked on and/or completed, it can be moved through the workflow.
As Stories move through the workflow, their State changes.
A Story can be moved from one iteration to another if the work needs to be delayed or moved forward.
Audience: Product Managers, Release Train Engineers, Product Owners, and Scrum Coaches
Audience: All Targetprocess users
The Retrospective tool in Targetprocess is designed for team Iteration Retrospectives.
Features are prioritized in Targetprocess using the WSJF (Weighted Shortest Job First) method.
Product Managers and Product Owners need to communicate any change in priorities to Scrum Coaches and the team. Changed priorities can result in changes to Features and/or Stories.
Targetprocess is an enterprise agile planning (EAP) tool.
Scrum Coaches should be planning with their Line Managers for expected surges in operational work, such as increased operational requests around the start of each semester.
Use ART Metrics to review how much work the ART completed during the PI.
During PI Planning, teams can review their features from the Team Backlog view.
Teams establish PI Objectives during PI Planning to help focus and drive work, as well as to communicate goals to Product Owners and Product Managers.
Use Team Metrics to review how much work the Team completed during the planning interval (PI).
Views and folders can be added as Favorites at the top of the navigation menu for easy access.
To share a work item (Feature, Story, Epic, person, Iteration, team) with others, a link can be copied and sent.
Audience: All Targetprocess users
You can set and share specific filtered Views with others in Targetprocess.
This article provides information about how to share views in Targetprocess.
What are Value Types?
Value Types are used to categorize and group different types of work (both features and stories) in Targetprocess.
Targetprocess is an enterprise agile planning (EAP) tool.
Audience: All Targetprocess users
Data in Targetprocess is presented in views. Some views allow you to:
Audience: All Targetprocess users.
To view all work that is assigned to you in Targetprocess, use the filters in the Team Kanban.
Product Managers, Product Owners, and Scrum Coaches can add dependencies on other teams directly into Targetprocess, but also must communicate with the team whose time is being requested to negotiate and coo
During PI planning, teams should be aware of their capacity, velocity, and available effort for the upcoming PI.
The ART Backlog provides a list view of Features, which can be filtered by a variety of criteria. A Feature represents a body of work that will deliver value and can be completed within one Program Increment (PI).
The Team Backlog provides a list view of Features, which can be filtered by a variety of criteria. A Feature represents a body of work that will deliver value and can be completed within one Program Increment (PI).
Resources
Targetprocess support from the vendor.
As an independent agile team, you don’t need to follow scaled agile processes to track your projects in Targetprocess.
Self-Help Guides
This self-help guide provides guidance on the use of Targetprocess for core and common Agile and scaled Agile processes.
In Targetprocess, you have the ability to add, edit, present, and extract data about your work.