Download The Complete Targetprocess Data Structure Guide Work Plans

ommon.
r specific
The Complete
Targetprocess
Data Structure
Guide
e completed. Think
. Usually created
o item later.
Programs
are who
a group
oftogether.
projects with
Teams are a group
of people
work
Bothsomething
functional in common.
Teams are a group of people who work together. Both functional
This could
be a set of A
a product
components,
projects for specific
and cross-functional
are supported.
person can
be included
customers
or any other grouping.
into many teams
simultaneously.
and cross-functional are supported. A person can be included
into many teams simultaneously.
Projects
of can
workhave
that needs to be completed. Think
Users are anybody who need
accessrepresent
a project.aAset
user
Users are anybody who need access a project. A user can have
of itand
as aprojects
productthey
or aare
project
within your company. Usually created
different roles for each teams
a part
a highorlevel
idea
first and
managed
of and be assigned to useras
stories
other
entities
to work
on. as a portfolio item later.
different roles for each teams and projects they are a part
of and be assigned to user stories or other entities to work on.
Epics
are part
of a project, represent
but are something
too large to fit in a single
Project
Allocations
the duration
too large to fit in a single
e piece of functionality
aracteristic.
ecific piece of functionality.
t steps. A test case
d executed multiple times.
People
Work
Project Allocations represent the duration
release.
An epic can
usedon
to arepresent
a large piece of functionality
and availability
forbe
a user
specific project.
or to
simply
featurestoby
some
specificsimultaneously.
characteristic.
Users
cangroup
be allocated
many
projects
and availability for a user on a specific project.
Users can be allocated to many projects simultaneously.
Features are large pieces of work. Normally something
too large to be implemented during a single iteration,
but small enough to fit inside a release.
User Stories are a distinct piece of customer
visible functionality. They can be planned
to a release, iteration or team iteration.
Tasks are the smallest piece of work
in Targetprocess. They must be part
of a user story and can’t exist on its own.
Plans
Releases represent some kind of phase in a project.
Normally when some meaningful functionality for customers has completed
and can be shipped. Bugs represent items of work related to fixing an error, typo
or just something broken. They are also used to represent
defects or failures which are found during testing.
Iterations are a short period of time, when the planned work should
be developed, tested and demonstrated. An iteration can only include work from
a single project. At any time in a release there can only be one current iteration.
Impediments
are used to track what has
slowed or blocks progress.
It can be anything such
as broken pc, or something
more intangible like
a dependency on another
task.
Team Iterations are the same as iterations, but can contain work from
many different projects and are related to a team. Team iterations cannot
overlap, so each team can have only one current team iteration.
Requests are used for issue management and idea tracking. Initial
requirements can be collected and requesters can be used to keep track
of who’s interested. A request cannot be planned, but a work item can
be created and planned for implementation.
Builds are used to help track of what was included into a specific software
build. Use relations to link user stories, features, bugs, etc to a build.
Tests Area
are aplan
set of test cases, which is created to test some specific
Test plan runs are the execution of Test
a test plans
plan. A test
functionality
for repeating testing activities. A test plan can include other test
run needs to be created each time a test
plan will beor
executed.
plans,
allows the reuse tests, and can be executed multiple times.
Multiple test plan runs can be created for
eachwhich
test plan.
are
used
test
a specific piece of functionality.
Test cases runs are theTest
resultcases
of a test
case.
A to
test
case
has aa description
and a set of test steps. A test case
run is automatically createdIt with
test plan run.
can
be for
a part
of test
many
test plans and executed multiple times.
There can be many test case
runs
each
case.
Test plan runs are the execution of a test plan. A test plan
run needs to be created each time a test plan will be executed.
Multiple test plan runs can be created for each test plan.
Test cases runs are the result of a test case. A test case
run is automatically created with a test plan run.
There can be many test case runs for each test case.
Related bugs can be created
while executing test cases.