Loading ...
Sorry, an error occurred while loading the content.

47049Re: [scrumdevelopment] Prioritization of Stories in Business Productivity Automation

Expand Messages
  • Dan Rawsthorne
    Jun 1 3:38 AM
    • 0 Attachment
      Perfect.

      Dan Rawsthorne, PhD, CST
      Senior Trainer/Coach, CollabNet
      drawsthorne@..., 425-269-8628



      Michael James wrote:
      >
      > Point taken. Continuous backlog refinement is a whole team
      > responsibility, with PO making final call on prioritization.
      >
      > --mj
      >
      > On May 31, 2010, at 8:12 PM, Dan Rawsthorne wrote:
      >
      > > Great statement, mj, but I have one small nit... I think that an
      > > attentive TEAM is always looking... it is putting too much reliance on
      > > the PO the way it is stated. BTW, I think that too many people think of
      > > the PO as some sort of superhuman person, rather than as a role that
      > can
      > > share some of its responsibilities with the rest of the team - as part
      > > of the self-organizing team.
      > >
      > > Dan Rawsthorne, PhD, CST
      > > Senior Trainer/Coach, CollabNet
      > > drawsthorne@... <mailto:drawsthorne%40collab.net>, 425-269-8628
      > >
      > >
      > >
      > > Michael James wrote:
      > >> Adding to George's response, keep reminding both the Product Owner
      > and development team that the Product Backlog is subject to constant
      > revision and reprioritization. Chet Hendrickson wrote "We know less
      > about the project today than at any time in the future." Even though
      > those business processes appear to be locked down at the moment, it's
      > likely that people will think of improvements, clarifications, fall
      > behind schedule, etc. Some of your requirements can probably be split
      > so that 80% of the value is derived from 20% of the effort of the
      > original requirement. An attentive Product Owner is always looking for
      > opportunities to slice and dice so high value work is done first.
      > >>
      > >> --mj
      > >>
      > >> On May 31, 2010, at 12:24 PM, Tara Santmire wrote:
      > >>
      > >>
      > >>> George - Thanks for taking the time to reply.
      > >>>
      > >>> I like the concept of taking the simplest path through the process
      > first.
      > >>> My guess is that the PO will want to do the most likely case first
      > as that
      > >>> has more business value. That could still be a valuable
      > prioritization. At
      > >>> each choice point say which is more likely and go down that path.
      > Gets you
      > >>> one way through the entire process.
      > >>>
      > >>> Tara E. Santmire, CSM, PMP
      > >>> tara@... <mailto:tara%40maresreach.net>
      > >>>
      > >>> -----Original Message-----
      > >>> From: scrumdevelopment@yahoogroups.com
      > <mailto:scrumdevelopment%40yahoogroups.com>
      > >>> [mailto:scrumdevelopment@yahoogroups.com
      > <mailto:scrumdevelopment%40yahoogroups.com>] On Behalf Of George Dinwiddie
      > >>> Sent: Monday, May 31, 2010 1:25 PM
      > >>> To: scrumdevelopment@yahoogroups.com
      > <mailto:scrumdevelopment%40yahoogroups.com>
      > >>> Subject: Re: [scrumdevelopment] Prioritization of Stories in Business
      > >>> Productivity Automation
      > >>>
      > >>> Tara,
      > >>>
      > >>> Tara Santmire wrote:
      > >>>
      > >>>> I am the Scrum Master on a software development project building
      > a web
      > >>>> portal and automating a set of business processes. We are at the
      > very
      > >>>> beginning of the product/project and are building enough of the
      > product
      > >>>> backlog to have work for several sprints. The product owner has
      > picked
      > >>>> a particular business process to automate first (highest business
      > >>>> value). We have identified some high level capabilities (home page,
      > >>>> task lists, request lists, friendly nags, reporting, etc.) that
      > cross
      > >>>> business processes and steps within a process and have associated
      > user
      > >>>> stories which are identified as high priority. The rest of the user
      > >>>> stories have to do with specific capabilities necessary for the
      > various
      > >>>> steps in the business process. The team has agreed that there are no
      > >>>> big technical risks in any of these user stories. The product owner
      > >>>> wants to prioritize these stories in the same order that they
      > occur in
      > >>>> the business process. I don't see any problems with this, but I
      > have a
      > >>>> nagging feeling that I am missing something. Does this seem like a
      > >>>> reasonable way of prioritizing the stories? Does it have any
      > potential
      > >>>> drawbacks?
      > >>>>
      > >>> That /seems/ like a reasonable order, but I suspect that the stories
      > >>> you've identified may not really be the most functional stories. For
      > >>> example, what sort of story is "home page?"
      > >>>
      > >>> I would suggest slicing things differently. Make the first slice the
      > >>> /entire/ business process, for the simplest case you can imagine and
      > >>> with little or no choices along the way. Make it work all the way
      > >>> through, but only for that one narrow set of circumstances. Then
      > start
      > >>> to flesh it out for choosing other circumstances.
      > >>>
      > >>> I think you'll find this an easier route, and you'll generate a
      > better
      > >>> app, if you approach it this way. It's just a simple trick of the
      > mind
      > >>> to envision it this way rather than the steps of the business process.
      > >>>
      > >>> Please report back how things go for you.
      > >>>
      > >>> - George
      > >>>
      > >>> --
      > >>> ----------------------------------------------------------
      > >>> * George Dinwiddie * http://blog.gdinwiddie.com
      > >>> Software Development http://www.idiacomputing.com
      > >>> Consultant and Coach http://www.agilemaryland.org
      > >>> ----------------------------------------------------------
      > >>>
      > >>> ------------------------------------
      > >>>
      > >>> To Post a message, send it to: scrumdevelopment@...
      > <mailto:scrumdevelopment%40eGroups.com>
      > >>> To Unsubscribe, send a blank message to:
      > >>> scrumdevelopment-unsubscribe@...
      > <mailto:scrumdevelopment-unsubscribe%40eGroups.comYahoo>! Groups Links
      > >>>
      > >>>
      > >>>
      > >>
      > >>
      > >>
      > >> ------------------------------------
      > >>
      > >> To Post a message, send it to: scrumdevelopment@...
      > <mailto:scrumdevelopment%40eGroups.com>
      > >> To Unsubscribe, send a blank message to:
      > scrumdevelopment-unsubscribe@...
      > <mailto:scrumdevelopment-unsubscribe%40eGroups.comYahoo>! Groups Links
      > >>
      > >>
      > >>
      > >>
      > >>
      > >>
      > >>
      > >> =======
      > >> Email scanned by PC Tools - No viruses or spyware found.
      > >> (Email Guard: 7.0.0.18, Virus/Spyware Database: 6.15110)
      > >> http://www.pctools.com/
      > >> =======
      > >>
      > >>
      > >
      > >
      > > ------------------------------------
      > >
      > > To Post a message, send it to: scrumdevelopment@...
      > <mailto:scrumdevelopment%40eGroups.com>
      > > To Unsubscribe, send a blank message to:
      > scrumdevelopment-unsubscribe@...
      > <mailto:scrumdevelopment-unsubscribe%40eGroups.comYahoo>! Groups Links
      > >
      > >
      > >
      >
      >
      >
      >
      >
      >
      >
      > =======
      > Email scanned by PC Tools - No viruses or spyware found.
      > (Email Guard: 7.0.0.18, Virus/Spyware Database: 6.15120)
      > http://www.pctools.com
      > <http://www.pctools.com/?cclick=EmailFooterClean_51>
      > =======
    • Show all 28 messages in this topic