Jared Quinert's Groups
-
Bloggers
35 members
-
Software Testing Mentors
59 members
-
ANZACS
42 members
Jared Quinert's Discussions
ISEB Intermediate Certificate in software testing
Replied Oct. 13, 2008
ISEB Intermediate Certificate in software testing
Replied Oct. 9, 2008
*New* addition - Events
Replied Feb. 26, 2008
Jared Quinert's Page
Latest Activity
A group for testers who blog.
Our MAST group in Melbourne, Australia is basically set up for practitioners want to discuss testing practice. If anyone wants help with anything testing-related, all they need to do is turn up with a problem (and a laptop if the problem is techni...
A group for people who can mentor software testers or for testers on the hunt for mentors.
Profile Information
- About Me:
- Testing generalist, occasional Agile ranter.
- Website:
- http://www.software-testing.com/blog
- Twitter profile
- http://twitter.com/xflibble
- LinkedIn Profile
- http://www.linkedin.com/in/jaredquinert
Jared Quinert's Blog
Look elsewhere :)
All my posts are on http://www.quinert.com/blog/
Posted on August 27, 2007 at 12:39pm — 5 Comments
Comment Wall (3 comments)
You need to be a member of Software Testing Club - online QA & software testing community to add comments!
- At 3:57am on February 6, 2008,
Jared Quinert said…
- Hi Sarah,
The simple answer is 'Yes'. I have used JIRA for bug tracking.
Mostly though, the projects or organisations in which I've used JIRA have been shooting for an agile approach. On an agile project, I'm *hoping* that the number of bugs that need to be tracked outside an iteration are minimal. Once a bug 'lives' outside of an iteration, then it really becomes work to be done just like any other story, so the distinction between a user story and a bug isn't that important.
I have a few criticisms of JIRA as a tool for agile projects:
- Managing and prioritising backlog is painful.
- Linear workflow isn't what we're aiming for. I think the way that tools model our development process can sometimes be interpreted as the 'right' way to do things. This is definitely a situation in which I don't like to defer my thinking to tools. I don't think JIRA's workflow model is helpful beyond 'Story open' and 'Story closed'. Matt Heusser discussed some of my thoughts on that here: http://xndev.blogspot.com/2007/01/agile-metrics-ii.html
I added some additional notes here: http://quinert.com/blog/index.php?itemid=19
I don't have any experience using JIRA for tracking defects in a traditional (ie. waterfall) development model. I can't see any obvious problems with it in that environment though, other than if you wanted some of the traditional integration with your test process that proprietary test management tools provide.
If you have a more specific question or problem, I'd be happy to try and answer it for you.
- At 2:50am on February 6, 2008,
Sarah said… - Hi Jared - on your blog you refer to using JIRA as a repositiry for high level agile stories - do you also use JIRA for defect tracking? I would like to hear more about your experience using JIRA for this purpose. Thanks, Sarah
- At 2:36pm on November 12, 2007,
Srinivas Radaram said… - HI Jared,
I wanted to get few of my quries clarified, can u pls reply me at srinivas.radaram@gmail.com
Regards,
Srini.
Become a member!
Tester Feeds
© 2009 Created by Rosie Sherry
