Hello All!
Perhaps we are (wanting to) using Agilo wrong, but here is what we
would like:
A "Milestone" is essentially a feature. So maybe for a website
that started life "anonymously" a new feature called 'Implement User
Accounts' is required. This might take 2 tasks: 'Create web page' &
'Create database table'. So, this milestone is complete when these two
are done.
But, we also do lots of things, so in our next sprint, say 05/03/10 -
05/14/10, we only have time to do one and choose (obviously! grin!)
'Create database table'.
The next sprint, 05/17/10 - 05/28/10, we would also like to
speculatively add 'Create web page'.
Now you have to imagine another milestone, called "Other Milestone",
with other tasks that are also assigned across sprints.
At the end of the sprint we would release our software, usually with a
patch increment: 3.4.6. Unfortunately we do not actually *know* that
this will be the next version number. (Our versions are increasing,
but not necessarily the "next" patch number for example.)
The problem is AFAWCT, a sprint must be associated with ONE milestone.
We want them disassociated and then we can see progress on milestones
(large features) and sprints (individual task contributions to many
different features).
Assuming I am being clear! wink! What are we missing?
Thanks!!
Q
--
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
-----
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en
