Message from discussion All About Agile: Roles during release planning

Received: by 10.114.80.4 with SMTP id d4mr2632398wab.11.1222263814185;
        Wed, 24 Sep 2008 06:43:34 -0700 (PDT)
Return-Path: <phlip2...@gmail.com>
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174])
        by mx.google.com with ESMTP id k19si3914200waf.2.2008.09.24.06.43.33;
        Wed, 24 Sep 2008 06:43:34 -0700 (PDT)
Received-SPF: pass (google.com: domain of phlip2...@gmail.com designates 209.85.200.174 as permitted sender) client-ip=209.85.200.174;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of phlip2...@gmail.com designates 209.85.200.174 as permitted sender) smtp.mail=phlip2...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by wf-out-1314.google.com with SMTP id 28so3069946wfc.11
        for <allaboutagile@googlegroups.com>; Wed, 24 Sep 2008 06:43:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from
         :user-agent:mime-version:to:subject:references:in-reply-to
         :content-type:content-transfer-encoding;
        bh=vHazNXhLADZoPJJMkeVBUW7JrL41pL0+brB3/t+y9nQ=;
        b=B72UuUhz5sQB8S+1NKchUDvmmht2wGDjCgH+iNtBrLhlb1bUNg2hZ6CQ9/uHtTJQkm
         hK/TkeYVx19jnqcMO3VWIBjMTl8LYNkmmnYjuAAVcF4CrhPEbkn+hPbpA5aITqvozk55
         u8LP0Um4/FS7J1WV17dAQFbhVXkyZhIPd+Ow4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=x1gAf6zOkwVVGzlUAl45t7f4AN9MSQYjUpOTMpXZWbAahDm0rpWU3qFdBMfSG0mJCX
         0VunH5LJ57UuITqOF3nrCVRs4mTEPqV+naO48eCrtY3kY9FyNgpQ56bAl9JPkuOdjmoI
         G6n3gegAhra7hdayE06vgHosVGxH5hcmqg2PQ=
Received: by 10.114.122.2 with SMTP id u2mr8123685wac.21.1222263813035;
        Wed, 24 Sep 2008 06:43:33 -0700 (PDT)
Return-Path: <phlip2...@gmail.com>
Received: from ?10.100.0.112? ( [70.165.47.100])
        by mx.google.com with ESMTPS id l30sm37954596waf.25.2008.09.24.06.43.31
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Wed, 24 Sep 2008 06:43:32 -0700 (PDT)
Message-ID: <48DA4401.5010...@gmail.com>
Date: Wed, 24 Sep 2008 06:43:29 -0700
From: Phlip <phlip2...@gmail.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
To: allaboutagile@googlegroups.com
Subject: Re: All About Agile: Roles during release planning
References: <50af7198-8b15-454e-98fa-3a3ea6980...@f36g2000hsa.googlegroups.com>
In-Reply-To: <50af7198-8b15-454e-98fa-3a3ea6980...@f36g2000hsa.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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