In Jira Agile when should I use a "Story" and when should I use an "Improvement"

jira agile scrum jira-agile
Kyle West picture Kyle West · Dec 30, 2010 · Viewed 7.1k times · Source

We just started using Jira (with the Jira Agile plugin - Scrum template) for our issue tracker and agile planning.

I am confused about the difference (or intended difference) between story and improvement. All our "stuff" is written as stories. Those stories describe both new functionality and improvements to existing functionality. Should those all be listed as a Story or should the improvements be listed as an Improvement?

I think we should keep things simple and just have Epic, Story, Bug; however, I don't want to hide Improvement and end up with some unintended effects or end up missing useful functionality.

Thanks in advance for your advice.

Answer

Mark Kofman picture Mark Kofman · Dec 30, 2010

We use "improvement" for functionality improvements in user stories delivered in previous sprints. In other words we use "story" for new user centric functionality and "improvement" for functionality improvements of current features and non-user centric functionality.

hope it helps

Related questions

Free alternative to Atlassian Greenhopper/PivotalTracker?

I'm working with my brother on a website idea we have, and we'd like to use a tool to plan sprints and assign estimates to individual tickets. Atlassian's JIRA+Greenhopper looks fantastic but costs $20/month and at this stage we're …

Read More
JQL to retrieve all stories and sub tasks related to specific epic

Is it possible to use raw JQL (not using any plugins) to filter for ALL stories AND their respective sub-tasks? Currently, I have the following which successfully retrieves all stories for EPIC-123: project = PROJ1 AND "Epic Link" = EPIC-123 AND issuetype = …

Read More
JIRA JQL: Issues resolved in the current sprint

I would like to be able to filter for issues that are have been resolved in the current sprint. Generally this would be used to prevent issues resolved in a previous sprint but delayed in testing (not reopened) showing up …

Read More