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

Re: [scrumdevelopment] Re: Plans are there for planning

Expand Messages
  • Steve Blais
    An issue to be resolved. Is it with the team, the product owner, the process, or the culture? From: Ron Jeffries Sent: Monday, June 29, 2009 12:29 PM To:
    Message 1 of 29 , Jun 29 10:01 AM
    • 0 Attachment
      An issue to be resolved.  Is it with the team, the product owner, the process, or the culture?

      Sent: Monday, June 29, 2009 12:29 PM
      Subject: Re: [scrumdevelopment] Re: Plans are there for planning

      Hello, inanc_gumus. On Monday, June 22, 2009, at 6:57:54 AM, you

      > CEO said that: "I don't know in scrum how can I hold
      > accountable. Is the team motivated enough, is the team
      > You say that, we have a deadline, but we can drop a
      > unimportant stories in the run. I want you to commit to all of
      > stories for a given date. I want you to work over time w/the
      > to increase the production if it's needed. Should I hold
      > accountable, or PO? Can you please create a release plan
      > tomorrow, I and PO would conclude that it's viable and let you

      > I am wondering now, how can we hold the team, and SM
      > (I know how to hold PO) How can we know are they productive
      > not? What do you think about CEO's responses?

      As we've talked about, I am troubled by the whole notion of "holding
      accountable" . Here's a potentially interesting story:

      In a really nifty project simulation that Elisabeth Hendrickson
      held for us Saturday, we were watching a team producing "software"
      according to their chosen process.

      For the /very first time/, the team accomplished its Sprint Goal,
      shipping acceptable software. They finished 12 minutes into a 15
      minute Sprint. Instead of congratulating the team, indeed instead
      of getting with the Customer, the "Product Manager" pushed the
      team to try to produce just one more feature since there were
      three minutes left. The team said they didn't think there was
      time. The PM pushed. The team tried, and failed.

      The results included these:

      1. Instead of ending on success, the team ended on FAIL.
      2. Instead of reflecting on the /very first/ success of
      their process, the team went off process.

      This is the kind of thing that a focus on "accountability" does. It
      does it more in real life than it does in a game, and the
      consequences are much worse.

      Ron Jeffries
      www.XProgramming. com
      www.xprogramming. com/blog
      A man hears what he wants to hear, and disregards the rest. -- Paul Simon

      No virus found in this incoming message.
      Checked by AVG - www.avg.com
      Version: 8.5.375 / Virus Database: 270.12.94/2208 - Release Date: 06/29/09 05:54:00
    Your message has been successfully submitted and would be delivered to recipients shortly.