I don't agree with Phlip, that's not necessarily "Big Requirements
Up-Front". If you want to build a complete system, or even a complete new
set of features, you at least do have to identify the User Stories that are
important and put them on your Product Backlog. However, you should resist
detailing the User Stories until they are nearing development in an upcoming
Sprint. Personally I would encourage you to discuss the users and their
roles, before turning to the user goals and expressing those as User
Stories.
Kelly.
2008/9/24 Phlip <phlip2...@gmail.com>
> brupm wrote:
> > Our current plan is to start the meeting with features discovery, then
> > jump into roles discovery as a team.
> > We plan to allow the team members to write out roles on index cards
> > and we can then pick the common ones.
> > My question is, how do I make sure we are not missing important roles?
> > Should I be considering personas as well, such as a user who is over
> > 25? Or should it be limited to a user, or an admin or a visitor?
> > The second question I have is that it that it seams like roles need to
> > be extracted based on the features but the stories are what seems to
> > bring the roles out. In other words, a feature like "Implement user
> > search" does not seem to aid role discovery as much as a story... " As
> > some role need to be able to edit find users so that I can edit their
> > accounts".
> This is Big Requirements Up Front. You need to do all that stuff over time,
> mixed in with actually cutting code and building releases.
> --
> Phlip
|
