TargetProcess Product Blog - Latest Comments

Re: Metrics and Effort Improvements

anadin — Tue, 01 Sep 2015 21:50:16 -0000

Just thinking as well as a Story's progress being a x out of y tasks complete, can a release completion be x out of y stories complete?

Re: Metrics and Effort Improvements

anadin — Fri, 28 Aug 2015 00:59:08 -0000

This post is very exciting. the simple concept of using counts top drive my metrics is very pleasing (it does raise the old T-Shirt sizing request again). And like my (misplaced reply below), being able to have the metrics auto populate Planned End or Estimated End fields which in turn would make the timeline views so much more useful

Re: We are going to remove Targetprocess v.2 in Jan 2016

Tobias Carlstedt — Wed, 26 Aug 2015 08:52:42 -0000

Also the feature in TP2 under "People" where you can see how many unused licenses you have would be nice to move to TP3.

Re: Metrics and Effort Improvements

anadin — Tue, 25 Aug 2015 03:30:33 -0000

I would love to have a way to have estimated end or planned end get auto populated with current cycle time. This way stories could have projected completion on time line views without us placing arbitrary dates on them

Re: People Allocations Management

Sigurjon Kolbeins — Wed, 19 Aug 2015 10:17:02 -0000

I'm happy to see the upcoming improvements to people allocation. I agree it would be beneficial to be able to allocate within a project down to release and iterations. In my case we run in parallel more than one release or overlap more than one release under same project and would help to be able to plan allocation within a single project. It would also be good to have the ability to plan available burn down hours based on peoples holidays, working buffer and new task buffer for instance. It would also be good to be able to have the allocation history, e.g. on periods within a project.

Re: People Allocations Management

Kenneth Solvik — Wed, 19 Aug 2015 07:17:34 -0000

We have the same need - check my post! Even if we divide in multiple project as we should, allocation by sprint/iteration is needed. Olga Ikhelis can you reply to this request?

Re: People Allocations Management

Kenneth Solvik — Wed, 19 Aug 2015 07:06:28 -0000

People Allocations Management is critical for us to efficiently use TP in our company. A show stopper for us to use TP for that purpose is the limited possibility to only allocate people by Project! In practice we allocate people by sprints, and they may jump from one project to another!
Is there any plans to support allocation of poeple by sprint/iteration?

Re: People Allocations Management

Olga Ikhelis — Mon, 17 Aug 2015 16:23:46 -0000

MCedergren, Rene, thank you very much for your feedback! Appreciate it a lot! I am really glad to hear, that the features such as capacity management and vacations support would be useful in your organisations. The allocations management feature is the first step on the way. I'd be glad to know more about your use cases, so if you don't mind I'll contact you via email for a quick chat to get more details. Thank you!

Re: People Allocations Management

Rene Sørensen — Sat, 15 Aug 2015 03:31:37 -0000

I agere with MCedergren. Today when we plan a sprint in Vestas, we need to calculate our velocity, we have to do that with another application like excel. When we do that we have to figurer out, if the sprint team members has any planned vacation. Next step is to figurer out if there are any holidays. Next step is to figurer out how many hours of none sprint activities each members has. All that eaquls a velocity for the team sprint. So now when the sprint is running and team members gets sick, we need to re-evaluate the content of the team sprint due to the fact, that the teams sprint velocity has changed. In my organizatione we would have no use for planning resources at the described level, planning at sprint leve makes much more sens.

Re: People Allocations Management

MCedergren — Thu, 13 Aug 2015 08:16:35 -0000

We are in need to allocate and plan peoples time more based on iteration than based on project alone.
We just has one big product/application and only one active project.

Re: Upcoming feature: Hierarchical Test Plans

Alvin Schatte — Tue, 11 Aug 2015 11:30:14 -0000

I'm sorry if this is a bit of a trivial question, but, is there a way to make a test run of a test case directly and record its results, or are test cases always run as a part of a test plan?

Re: Metrics and Effort Improvements

brookwarner — Thu, 06 Aug 2015 23:16:51 -0000

We would really appreciate the changes that are discussed here. We spent aaaaages when we first adopted TP3 trying to figure out how the progress bars are calculated, and in the end we gave up relying on them or using them since they just don't give us helpful information. The other thing that we really need is the ability to see how much _planned_ work is remaining, rather than how much _total_ work is remaining. We often have entities in "open" state and we don't need to see these in our calculations or progress bars. We are currently using a CCF for this but it is not ideal. Lastly, we would love to see better summation of hours / progress etc in views (such as views that show how much work is assigned per user, or per iteration, or per release, etc.)

Re: Targetprocess v.3.7.6: Improved Axes Ordering, Stacked Bar Charts

Michael Dubakov — Tue, 04 Aug 2015 08:32:20 -0000

@florianschmitz Any specific bugs you expect to be fixed?

Re: Metrics and Effort Improvements

Maxwell Correya — Tue, 04 Aug 2015 06:46:03 -0000

Metrics concept would be really a good thought and that shall be give solution to most of the already shared difficulties. Meanwhile what are the metrics input parameter consideration could be a question of vagueness,
and how it can be applied at various level needs to be practice out.

Believe following shall be addressed, though I wanted to share for your information:

1. When a user story is marked to be completed (Done), its actual should not be changed to effort; rather effort and actuals to be retained as it is. And similarly when a user story marked to be completed (Done), its remaining time should be retained.
a). Even when a user story marked to be completed (Done), there is possibility that time shall be recorded against the user story/task; and is always need to retain actual remaining time to identify effort Vs actual.

2. Remaining time calculation needs to be worked out by considering multiple developer/users entering time at the same time.
a) Consider the situation, were we have General User Story specific to each release plan such as “Project Meetings and Discussion”, in which we have task such as “Standup Meeting”, “Scrum Meeting” etc; here
based on the meeting time more than one member shall be entering their actual time.

Example :-

i. “Standup Meeting” Task Effort allocated supposed to be 100 hr for entire team corresponding to a release plan.
ii. A resource tries to enter 1 hour, and remaining shows while entering will be 99 hr.
iii. Simultaneously, if another resource also tries to enter 1 hour, there also it shows remaining
time 99 hr.
iv. When these are saved, total spend time will be 2 hr, whereas total remaining still shows 99 hr, which has to be actually 98 hr?

3. There has to be a facility to select user role instead of default role against a Task allocation. Since current workflow is restricted specific to stage and role responsibility against Task we are find it difficulty in setting actual user role against a task where everybody restricted under “Developer” default role.

a. Consider the example of user story and task template something like below.

b. Effort Metrics Implementation (User story)
i. Design workshop (Task)
ii. Design workshop Review (Task)
iii. Design workshop presentation (Task)
iv.TestCases - Developer (Task)
v. Test Cases - Developer - Review (Task)
vi. Test Cases - QA (Task)
vii. Test Cases - QA - Review (Task)
viii. Development (Task)
ix. Code Review (Task)
x. Documentation (Task)

In this sample, we wanted to separate each task corresponding to each user role, such as with Production Manager, Project Leader, Product Developer, QA Role etc. Please note that, these Task state are changed to “In-Progress” and “Done” by individual assigned to it.

4. We have situation like defects are identified and recorded at various levels during User Story completion. Where effort to address that defect is estimated, but since these are affecting schedule plan we are capturing time to address this defect against task level with special task called “Re-work” (no effort estimation for this Re-work task and only actuals are recorded). There has been Re-work at various levels in the process such as at Design phase, Development Phase, Testing Phase etc. Here for the progress calculation, we want effort specific along with its actual time recorded based Task and certain occasion Bug also into User Story Progress plotting; but at the same time wanted to see the impact on the user story due to time recorded
without having any specific effort estimation?

Something like:

Total Effort Estimation : 45
Actual Time captured against Estimated Task : 10
(Actual time entry without estimation : 3)

Ideal Progress corresponding to Plan : 22.22%
Actual Progress : 20.83%

Thanks,

Re: Targetprocess 3.6.6: Calculated Custom Fields (beta)

Ben Parish — Fri, 31 Jul 2015 11:46:54 -0000

Will there be the option to have cross-process custom fields for entities other than Projects in the future?

Re: We are going to remove Targetprocess v.2 in Jan 2016

Xin Jiang — Wed, 22 Jul 2015 13:27:53 -0000

Here is the list of things that we miss the most in TP2:

1. Able to print test cases in User stories. TP2 has very nice printable format for printing out the test cases.
2. Bulk update tags - you can select multiple user stories in TP3 and right-click Change Tags, but it only update one user story (could be a bug, we are using 3.6.1)
3. Continue to provide the same ReST API - hopefully this won't change in the future.

Re: We are going to remove Targetprocess v.2 in Jan 2016

Natalia — Tue, 21 Jul 2015 08:04:24 -0000

In TP2 one can "batch" copy multiple cards from one project to another (or to the same project), while in TP3, there is NO such function

Re: Targetprocess Mobile for iOS 2.0 Release

Fabio Bianchini — Thu, 16 Jul 2015 04:22:51 -0000

I'm trying the App but the push nothification dosent work on my iPhone 6 :(

Re: Coming Feature: Team Workflow

martin — Thu, 02 Jul 2015 04:19:58 -0000

Good feature! Good idea. Go on :-)

Re: Targetprocess 3.7.2: Project Statuses, Sorting by Custom Field, Find Bug Duplicate

Nadia Bulynia — Mon, 29 Jun 2015 08:27:14 -0000

As of duplicate bugs functionality in v.3, no changes done to primary Bug will apply to its related duplicates.
However, you mignt want to use our next feature – ‘Merge Duplicates’ – which is going to be released soon, v.3.7.6, approximately. [Merge] button will appear in 'Duplicates' section of the view. If you decide to merge duplicate entities, then all their comments and attachments will be copied to a primary Bug (or Request) and their states will be changed to final.

Re: Targetprocess 3.7.2: Project Statuses, Sorting by Custom Field, Find Bug Duplicate

mb963 — Thu, 18 Jun 2015 20:16:31 -0000

Duplicate Bugs in v.3: If 2 bugs are linked by using the Duplicate option. Do the changes made to one traverse to the other?

Re: Upcoming Feature: Entity Test Plan

yuu — Mon, 08 Jun 2015 23:41:46 -0000

So as this update, this tool recommend user to design test case in related test plan ?? I can see there are many test cases which are designed in related test plan show on No User Story field when i'm in the Test Coverage or Test Case per User Story view. I don't know what can i do with this. If i link it to the US again then there are duplicated. As my need, i want to view how many TCs are designed in the US (in timeline not open each US) so currently, i MUST create new test case in US (not in related Test plan). Please help me to handle it cause i don't want to see many TCs which are designed for US show on 'No User story'.

Thanks

Re: We are going to remove Targetprocess v.2 in Jan 2016

Cualquiera — Wed, 03 Jun 2015 06:53:02 -0000

It is specially important for us to extract time entries. In plain TP3 today it is not possible to display. (as far as I know)

Re: We are going to remove Targetprocess v.2 in Jan 2016

Cualquiera — Tue, 02 Jun 2015 06:32:23 -0000

TP2 old reporting (Create Lists and export to csv) is from time to time very useful...
Are you planning to export this functionality?

Re: We are going to remove Targetprocess v.2 in Jan 2016

Andre Nelson — Fri, 29 May 2015 09:10:13 -0000

I definitely support this move. One feature I still use in v2 from time to time is in the people area. It shows how many unused accounts are left. Is there another place I can check this in v3?