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

27734RE: [scrumdevelopment] Re: Freeware/open source SCRUM tool

Expand Messages
  • Michelle Ammerman
    Mar 3 2:55 PM
    • 0 Attachment

      In our office, I constantly ask our staff to be mindful of implementing cures for which there is no disease, because often, those cures cause new diseases.  The scenario that Pete describes did just that.

       

      From: scrumdevelopment@yahoogroups.com [mailto:scrumdevelopment@yahoogroups.com] On Behalf Of Ken Schwaber
      Sent: Monday, March 03, 2008 3:39 PM
      To: scrumdevelopment@yahoogroups.com
      Subject: RE: [scrumdevelopment] Re: Freeware/open source SCRUM tool

       

      Excellent, Pete. Another problem I run into is that enterprises using a Scrum tool mistake that for doing Scrum.

      Ken

       


      From: scrumdevelopment@yahoogroups.com [mailto:scrumdevelopment@yahoogroups.com] On Behalf Of Pete Deemer
      Sent: Monday, March 03, 2008 7:23 AM
      To: scrumdevelopment@yahoogroups.com
      Subject: Re: [scrumdevelopment] Re: Freeware/open source SCRUM tool

       


      let me share a story. I once knew a team that was doing scrum quite
      happily, using pencils and paper and post-it notes and not much else.
      but it felt very low tech and old-fashioned to them. as one of them put
      it: this is how my grand-dad used to do things back in his day! so they
      decided to come up with a better approach. they set up a database to
      store all the info that previously was living on paper, and they built a
      bunch of nice web pages for entering and viewing the data. with each
      week that passed, they added more and more features, to the point where
      the tool was getting quite complicated. unfortunately, they found
      themselves spending more and more fixing and extending the tool, which
      took time away from other things. but it was very powerful. instead of
      just one simple burndown chart for the whole team, they now could look
      at individual burndown charts for every member of the team, and they
      could see who was ahead and who was behind. and someone added a wiki
      page that allowed everyone to type in their daily update and blocks,
      which allowed the team to stop doing the daily scrum meeting in person.
      and someone else built a clever tool that automatically create a task
      queue for each team member, so that they always knew exactly what to
      work on; they didn't need to even think about it, the system just told
      them what to do. and management learned about the tool (the team showed
      it off during a sprint review), and asked for the team to create a
      single page for the exec team to look at, which showed the burndown
      chart for every single person in the department, and anyone who was
      behind on their tasks, or on their "delivered versus predicted task
      hours per day" (a new metric someone suggested they monitor, since the
      data was all there in the tool) would show up with a bright red blinking
      flag next to their name. The execs liked this dashboard so much they
      asked for a wap version of the page, so they could check it via their
      blackberry from the car, train, etc., a couple times a day if they
      wanted. Over the course of about two months, what had been a happy and
      productive team somehow evolved into a group of stressed out, unhappy
      individuals all constantly looking over their shoulder, and none of them
      had the faintest idea how they were doing during the sprint, which led
      to missed goals and even closer executive monitoring. Getting them back
      on track was very costly and painful, and it was doubly disappointing
      because the whole detour occurred for no good reason.

      I'm not saying that tools are wrong, by any means; for larger projects
      and multi-location teams, they can be helpful. But before going that
      route, I would get very clear on the problem you're trying to solve, and
      be certain that your tool is going to address the underlying issue, and
      not simply disguise it.

      -------------------------------------
      Pete Deemer
      GoodAgile
      CSM in Delhi (Gurgaon), March 5-6 - seats still available - full details
      at goodagile.com

      poojawandile wrote:

      >
      >
      > I am looking for a tool to manage spint backlog, product backlog,
      > issues, risks, burndown chart, etc. Though this can be acheived
      > through an excel also, I just thought a tool may offer some more
      > features which may not be exactly and easily possible through an
      > excel spreadsheet, for delegating activities to team emmebers and
      > allowing them to update their tasks on their own. With my limited
      > knowledge on Scrum, yes, I would be interested in knowing the pros
      > and cons of using a tool against an excel sheet or the need of a
      > tool itself.
      >
      > Thanks,
      > Pooja
      >
      > --- In scrumdevelopment@ yahoogroups. com
      > <mailto:scrumdevelopment%40yahoogroups.com>, Pete Deemer
      > <petedeemer@ ...> wrote:
      > >
      > > Hi Pooja, I get this quite often. My first question is always:
      > What are
      > > the problems you're having that you'd like the tool to solve?
      > >
      > >
      > > ------------ --------- --------- -------
      > > Pete Deemer
      > > GoodAgile
      > > CSM in Delhi (Gurgaon), March 5-6 - seats still available - full
      > details
      > > at goodagile.com
      > >
      > >
      > >
      > >
      > > poojawandile wrote:
      > > >
      > > >
      > > > Hi,
      > > > Could you please suggest any freeware SCRUM tool?
      > > >
      > > > Thanks,
      > > > Pooja
      > > >
      > > >
      > >
      >
      >

    • Show all 25 messages in this topic