Hi Felix!
Awesome! Thanks for the reply!
Of course, I am an idiot and was not very clear in my first attempt to
ask my question. I will also admit to a lack of Scrum correctness/
proficiency.
So let me try again (which of course may or may not be helpful!); and
start by taking back my statement: A "Milestone" is essentially a
feature. Very bad of me! grin! Also, if you have resources, eg. books,
links I ought to read and then return, that is a sufficient answer!
wink!
Let me try this:
I have a big python app. It runs on linux. I am porting to Win7. I
want a Milestone called 'Win7'. I want to create a number of Tasks for
that, say 50. I then want to put them in our sprints over the next
3months. There will be more than just me working on this. I want to
make this a Milestone because of the nice Task tracking features of
Agilo. It is also the case that I can do subsets of these 50 and
release them to my users; IOW I can do some during Sprints and part of
my product's release, effectively giving my product partial Win7
support.
But, we are not the only people on the team. There is another
Milestone called 'Automated Test Discovery' worked on by a couple of
other developers. They have 25 Tasks spread over 2 or 3 sprints.
Again, this is a Milestone because it is "big" and we want the
tracking. Like the Milestone above, I can release subsets of Tasks
that are useful to my users but are not the full 'Automated Test
Discovery' solution.
Now, we/I are/am probably not very Scrum'ish, but User Stories would
just be another level of hierarchy and only within sprints. We ignore
User Stories and mostly just use Tasks it seems. This means often one
or more of our Tasks are User Stories; but I can not see how adding a
User Story would help us. (Example: When we add to our backlog we tend
to say something like: Oh! We need to do X. And to do X I need to do
Tasks T1, T2, and T3. We add the Tasks to the Backlog and pretty much
never create the User Story associated; and we are likely unclear on
the Scrum way and therefore misunderstanding that User Stories are not
useful to us.)
What we want is to use the nice tracking features of Agilo for
Milestones: A group of Tasks all towards one large goal and their
completion progress, and Sprints: A group of Tasks for a specific
timeframe towards an incremental release of our product moving its
capabilities as definited by Milestones progressively forward.
I had probably better stop there!
Thank you for your time!
Q
On Apr 15, 7:25 am, Felix Schwarz <[email protected]> wrote:
> 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
