3 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• David Anderson commented  ·  Dec 20, 2010 5:43 am  ·  Delete

  We run iterations of 2 weeks, but have have multiple projects

  | Iteration 1 | Iteration 2 | Iteration 2 |
  | Project 1 ---------------------->|
  | Project 2 ---------------------->|
  
  In TinyPM at the moment, each project has iterations.
  We work differently in that we have iterations with multiple (overlapping) projects.
  With the system as it is, we have to define the same iterations in each project.

  I would prefer to define iterations first, then projects, then estimate effort. From this we could then estimate required resources and end times for each project.

• josschne commented  ·  May 19, 2010 1:05 pm  ·  Delete

  I have a similar need. Basically multiple customer teams but a single developer team working with a single velocity and within a single iteration. The developer team needs to see a burndown of total work, but the customer teams don't care about each other and want to see a burndown specific to their projects. It appears with tags you can almost do this, but I don't see a way to get a burndown based on a specific tag. Maybe that's an easy way to satisfy this use case?

• AdminAgilers Sp z o.o. (Admin, tinyPM) commented  ·  Oct 05, 2008 5:02 pm  ·  Delete

  Can you write a bit more about "managing those shared iterations separately" as we don't understand the requirement behind it.