Am 08.04.2010 22:33, schrieb czrpb:
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.
Actually that does not match with Scrum.
I'll explain how this works with Agilo:
A 'feature' is always a user visible feature. This is described in User
Stories. You break down user stories into tasks like 'create db'. Every
User Story is done in one sprint - you need to shape your user stories
so that you can finish at least one of them in one sprint. (otherwise
you get a lot of problems with projects not getting finished, technical
debt etc).
Therefore you don't use milestones to capture features.
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 agile way in this situation is not to do everything 100% and
complete every component/layer but to pick one tiny feature, implement
what you need for that tiny feature and refactor/extend afterwards.
fs
--
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
To unsubscribe, reply using "remove me" as the subject.
