Message from discussion
All About Agile: Re: Roles during release planning
Received: by 10.214.244.8 with SMTP id r8mr736464qah.9.1222264502205;
Wed, 24 Sep 2008 06:55:02 -0700 (PDT)
Return-Path: <allaboutag...@googlemail.com>
Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.182])
by mx.google.com with ESMTP id 7si13053329yxg.0.2008.09.24.06.55.01;
Wed, 24 Sep 2008 06:55:02 -0700 (PDT)
Received-SPF: pass (google.com: domain of allaboutag...@googlemail.com designates 66.249.90.182 as permitted sender) client-ip=66.249.90.182;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of allaboutag...@googlemail.com designates 66.249.90.182 as permitted sender) smtp.mail=allaboutag...@googlemail.com; dkim=pass (test mode) header...@googlemail.com
Received: by ik-out-1112.google.com with SMTP id c30so1551926ika.5
for <allaboutagile@googlegroups.com>; Wed, 24 Sep 2008 06:55:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlemail.com; s=gamma;
h=domainkey-signature:received:received:message-id:date:from:to
:subject:in-reply-to:mime-version:content-type:references;
bh=6PkhzUZ+cE1qVWiP8DLYrWIuiBJPei4eNB8aY8uISks=;
b=g5vsP0JeJqtSz/9WVxYZfsOZLmcYapv+mQc77Qn79rU+l11jCMWtJeW+e+XqBtDVUT
mKFfjOEWt6pFDJfxsMaevcBRMLw3ze16Djk7eBsgzfZ2scaS9mttuYfWhAUNr0mRQPdZ
maGF1jlZ2JXt2dCs+qJHlkmqV3QZX9U+EOG3s=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=googlemail.com; s=gamma;
h=message-id:date:from:to:subject:in-reply-to:mime-version
:content-type:references;
b=YPGaxITqKdAkh+TF7eP04dce3ojhxv/QcT3LS+Yl8cJkE61folIK2UHSNeMI6B/Y2o
zWBZaLWrwUd363wFDsKtQd8a8ibAtsFv3FtIOyewWUmLsWvv+NgSL2apXGlSARHR/JvX
2rA1baQ+DUibFi35GcO3BDL8CjJdoz75kB6X4=
Received: by 10.210.82.7 with SMTP id f7mr5813868ebb.194.1222264501263;
Wed, 24 Sep 2008 06:55:01 -0700 (PDT)
Received: by 10.210.142.3 with HTTP; Wed, 24 Sep 2008 06:55:01 -0700 (PDT)
Message-ID: <d714a9930809240655qeff8c70m7752bd966c701910@mail.gmail.com>
Date: Wed, 24 Sep 2008 14:55:01 +0100
From: "Kelly Waters" <allaboutag...@googlemail.com>
To: allaboutagile@googlegroups.com
Subject: Re: All About Agile: Re: Roles during release planning
In-Reply-To: <48DA4401.5010...@gmail.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_110672_14599097.1222264501255"
References: <50af7198-8b15-454e-98fa-3a3ea6980...@f36g2000hsa.googlegroups.com>
<48DA4401.5010...@gmail.com>
------=_Part_110672_14599097.1222264501255
Content-Type: text/plain; charset=ISO-8859-1
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
>
>
> >
>
------=_Part_110672_14599097.1222264501255
Content-Type: text/html; charset=ISO-8859-1
<div dir="ltr">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.<br>
<br>Kelly.<br><br><br><div class="gmail_quote">2008/9/24 Phlip <span dir="ltr"><<a href="mailto:phlip2...@gmail.com">phlip2...@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
brupm wrote:<br>
<br>
> Our current plan is to start the meeting with features discovery, then<br>
> jump into roles discovery as a team.<br>
> We plan to allow the team members to write out roles on index cards<br>
> and we can then pick the common ones.<br>
><br>
> My question is, how do I make sure we are not missing important roles?<br>
> Should I be considering personas as well, such as a user who is over<br>
> 25? Or should it be limited to a user, or an admin or a visitor?<br>
><br>
> The second question I have is that it that it seams like roles need to<br>
> be extracted based on the features but the stories are what seems to<br>
> bring the roles out. In other words, a feature like "Implement user<br>
> search" does not seem to aid role discovery as much as a story... " As<br>
> some role need to be able to edit find users so that I can edit their<br>
> accounts".<br>
<br>
This is Big Requirements Up Front. You need to do all that stuff over time,<br>
mixed in with actually cutting code and building releases.<br>
<br>
--<br>
Phlip<br>
<br>
<br>
<br>
</blockquote></div><br></div>
------=_Part_110672_14599097.1222264501255--
|
