There are two ways to organize work in Targetprocess 3: Projects and Teams. You can have one team that works on several projects. Or you can have a large project with several teams working on it. Any crazy mix of teams and projects is supported in Targetprocess 3.
Targetprocess 3 connects the 3 major attributes of project management: People – Work – Plan.
Grouping projects into programs.
User Story is a piece of work that helps to implement some business requirement and deliver value. It should try to capture a single functionality, enhancement, use case, scenario or role. User Stories in Agile Approach to Software Development
Task in Targetprocess is one of the entity types in the data model. Tasks are the smallest increments of work. Task is a small chunk of work, typically less than 16 hours. Tasks are technical steps that are taken to complete and deliver
Bug in Targetprocess is one of the key entity types in the data model. Bugs usually represent bugs or defects (errors, flaws, mistakes, typos, failures or faults) in a computer programs or products. Bugs are denoted by light red color. Terms The following custom terms
Feature in Targetprocess is one of the key entity types in the data model. A Feature is a high-level requirement. In most cases, Features are required for large and medium Projects; in small projects, features are optional. A Feature is larger than
a new entity type within Targetprocess data model
With 3.13.0 we've introduced an additional level to the work hierarchy named Portfolio Epics. This is a new entity type above an Epic in a Project. How Portfolio Epics are used It’s supposed to be used for portfolio-level
There are no formal dependencies in agile software development. However, it often comes that way that one piece of work is tied to another piece of work. In Targetprocess you can track such dependencies via Relations.
Cross-project releases allow you to plan and track your backlog from several projects at once. They provide you with aggregated status while still being able to drill into each project.
There are two types of Iterations: Iterations (Project Iterations, Sprints, Project Sprints) and Team Iterations (Team Sprints). Both serve the same purpose: organizing work for planning, tracking, and reporting. The main difference between them is the scope of work each type may contain.
In a case when you have multiple related projects running together you may want to coordinate them with cross-project Releases. When you have a team working on many projects in the same time, you may want to plan and organize work
External users (Requesters) can communicate with Support Agents and Customer Care Managers via Requests at Service Desk portal.
When working with work, planning, or testing entities you may come across a blocking issue that prevents you from moving forward. For example, a key developer is sick halting work on an entity, or the QA team needs to
Milestones are used to represent some important event for your team, project or company. For example, it could be an important demo for a client, or a company deadline.
A Build is an important part of the continuous software delivery process. Usually it represents a set of new features and bug fixes that are going to be released to the end users. By attaching work items to builds you can
The topic of terminology is highly important for clear communication and shared understanding. We often use the same terms talking about different things, while sometimes we speak about the same things naming them differently. In this video we’ll