24635RE: [scrumdevelopment] Re: Sprint whiteboard and issue tracking tools?
- Oct 18, 2007
We use JIRA for this purpose, and are trying to get Green Hopper approved to replace the physical board
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of rhythmstar
Sent: Thursday, October 18, 2007 2:22 PM
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. :-)
PS - we use ScrumWorks Pro from Danube .
--- In scrumdevelopment@ yahoogroups. com, "Sebastien ARBOGAST"
<sebastien.arbogast @...> wrote:
> 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
> it.during the
> 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
> 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
- << Previous post in topic Next post in topic >>