Becoming Agile

Hi caccia,

we use it in a very similar way - but it's a mixture of classic and agile approach.

Our requirements entered in Tickets with type = requirements. All approved requirements will be linked to an Activity. Every Activity has a target version - in our case we have two monthly releases (target versions). All efforts booked weekly on Activities.

Report: Current Status - Version Detail shows what will be delivered on what target version. If you enter target version in Activites and Requirements / Tickets, then you will see, what is delivered when.

I hope this supports your deep dive on this topic.

Regards,

Klaus

Hi Klaus,

Thanks for the info - I like your idea of using a ticket type = requirement, sounds like a good idea.
I haven't given the subject much more thought yet, but I'll keep your inputs in mind as well.

Thanks !

There is requirements in projectorria already - what's the point to duplicate it?

Hi ekolossov,

we didn't duplicate. It's an simpler approach for us, to have all requests, tasks and issues in one - we use the Tickets for this purpose. Type differentiate with Ticket type between this types. To be honest, we have had this approach long time before Requirements have been invented.

Regards,

Klaus