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

24727Re: [scrumdevelopment] Re: Sprint whiteboard and issue tracking tools?

Expand Messages
  • an.narasimhan
    Oct 22, 2007
    • 0 Attachment
      Thats what I also did. I just wanted to alert the group so that everyone knows.


      Roy Morien wrote:

      so am I? Do they present a problem apart from beign a nuisance? I hve jyst deleted them without trying to open the attachments.

      To: scrumdevelopment@ yahoogroups. com
      From: an.narasimhan@ yahoo.co. in
      Date: Mon, 22 Oct 2007 18:08:42 +0530
      Subject: Re: [scrumdevelopment] Re: Sprint whiteboard and issue tracking tools?

      I am getting lots of spam mails containing three attachments almost from everyone in this group. The attachments are :GWAVA_1#message. txt, GWAVA_2#TEXT. htm, GWAVADAT.TXT. The subject of the mails is varying.


      Jobe Lloyd wrote:

      We use JIRA for this purpose, and are trying to get Green Hopper approved to replace the physical board


      Check out

      http://www.greenpep persoftware. com/en/products/ GreenHopper/






      From: scrumdevelopment@ yahoogroups. com [mailto:scrumdevelo pment@yahoogroup s.com] On Behalf Of rhythmstar
      Sent: Thursday, October 18, 2007 2:22 PM
      To: scrumdevelopment@ yahoogroups. com
      Subject: [scrumdevelopment] Re: Sprint whiteboard and issue tracking tools?


      Depends on your context. We have clients who have some fairly
      demanding process requirements, even some Six Sigma shops. It's hard
      to satisfy their "needs" without a tracking tool of some kind. I think
      as long as one does not let the tool interfere with the flow, it can
      be a good thing. Particularly when there might be some future
      disagreements on what was asked for, etc., being able to produce a
      hard copy of requirements (i.e., User Stories with Conditions of
      Satisfaction) and task completion history can be handy. :-)

      Bill House

      PS - we use ScrumWorks Pro from Danube.

      --- In scrumdevelopment@ yahoogroups. com, "Sebastien ARBOGAST"
      <sebastien.arbogast @...> wrote:
      > Hi,
      > We are just starting to implement SCRUM on a few projects and one of our
      > teams is asking us to set up an issue tracking tool like JIRA or Trac in
      > order to monitor bugs and improvements.
      > The thing is that it would be just for them as there hasn't been any
      > production release yet so the product owner would not have any
      visibility on
      > it.
      > The first thing I answered them is that it would be redundant with the
      > whiteboard/post- it technique they're using.
      > Moreover, in my experience, when issue tracking systems are used
      during the
      > development phase of a project, issues pile up but are rarely treated.
      > What do you think? What are the best practices in that matter?
      > --
      > Sébastien Arbogast
      > http://www.sebastie n-arbogast. com

      Find it at www.seek.com. au Your Future Starts Here. Dream it? Then be it!

    • Show all 22 messages in this topic