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

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

Expand Messages
  • Tompkins, Andrew
    Oct 19, 2007
    • 0 Attachment

      We are starting to use Jira here as well.  But which ever tool we use for tracking issues, it is only for the tracking issues portion (more for QA).  When an issue is found in the application by QA (or anyone) an issue is created and we also create a sticky to put on the scrum wall under a priority, and they are treated like tasks.

       

      Andrew

       


      From: scrumdevelopment@yahoogroups.com [mailto:scrumdevelopment@yahoogroups.com] On Behalf Of Jobe Lloyd
      Sent: October 18, 2007 3:42 PM
      To: scrumdevelopment@yahoogroups.com
      Subject: RE: [scrumdevelopment] Re: Sprint whiteboard and issue tracking tools?

       

      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/

       

       

      Thanks,

       

      Jobe


      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
      >

      This e-mail and any attachments may contain confidential and
      privileged information. If you are not the intended recipient,
      please notify the sender immediately by return e-mail, delete
      this e-mail and destroy any copies.

      Any dissemination or use of this information by a person other
      than the intended recipient is unauthorized and may be illegal.

    • Show all 22 messages in this topic