It's all about the answers!

Ask a question

How shall I start with Work Item?


Jirong Hu (1.5k9290258) | asked Dec 19 '11, 3:49 p.m.
Hi

We are already using RTC 3.0.1 for source control. Now I am wondering if I shall start using Work Item together with source control.

The project teams are all new to RTC, and it's a traditional shop, no Agile at all. I have some thoughts but not sure what's the best way to start.

1. Starting with Task to implement something like CCCQ UCM. e.g. a team lead/PM can create tasks, then assign to developers to work on, and track the status. However, Task or in general Work Item in RTC seems automatically mean planning, or you may say planning is all about Work Item. So this means we have to migrate the current planning in MS Project into RTC too. This complicates things.

2. Our testers are using HP QC so integrating QC with RTC is another thing need to take into consideration.

3. Currently they are using Change Set to manage their work. What's the benefits to bring in Work Item to them?

Can anyone give me some lights?

Thanks
Jirong

One answer



permanent link
Geoffrey Clemm (30.1k33035) | answered Dec 19 '11, 8:38 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, now that your team has a sense of how to use RTC for source
control, it is very likely that they will get significant benefits from
starting to use work items as well.

To keep things simple, initially, you can ignore planning ... just treat
the work items as "structured checkin comments". Have your users create
a new task for themselves whenever they are starting a logical new task
(I usually recommend a separate task for anything that will take more
than 4 hours to complete). Or if there is something you'd like someone
else to do, create a task and assign it to them (it will show up in
their "My Work" view).

In this initial usage, work items don't replace MS Project, but rather
provide a convenient integration point. Store a URL to the appropriate
MS project task as a "related artifact" of the RTC work item and/or
store a URL to the relevant work items in the MS project task.

Similarly, the RTC work item provides the RTC end point for the various
integrations that you can purchase between RTC and HPQC (or you can just
use the manual approach describe above for integration with MS Project.

And once you start collecting RTC task information, there are a variety
of pre-defined viewlets and reports that help you gain visibility into
exactly what your teammates are actually doing.

Cheers,
Geoff

Cheers,
Geoff

On 12/19/2011 3:53 PM, hujirong wrote:
Hi

We are already using RTC 3.0.1 for source control. Now I am wondering
if I shall start using Work Item together with source control.

The project teams are all new to RTC, and it's a traditional shop, no
Agile at all. I have some thoughts but not sure what's the best way
to start.

1. Starting with Task to implement something like CCCQ UCM. e.g. a
team lead/PM can create tasks, then assign to developers to work on,
and track the status. However, Task or in general Work Item in RTC
seems automatically mean planning, or you may say planning is all
about Work Item. So this means we have to migrate the current
planning in MS Project into RTC too. This complicates things.

2. Our testers are using HP QC so integrating QC with RTC is another
thing need to take into consideration.

3. Currently they are using Change Set to manage their work. What's
the benefits to bring in Work Item to them?

Can anyone give me some lights?

Thanks
Jirong

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.