Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What is "Improvement" intended to represent in the Scrum Issue Type Scheme?

The Scrum Issue Type Scheme comes with Epic, Story, Bug, and Improvement as first level "issues". Technical tasks can be created as children of stories, but not as first level cards.

I was thinking of using "improvement" cards to represent work like refactoring, or non-user exposed technical tasks that don't relate to a specific user story. (This would elimiinate my need to go through the IT department to reconfigure my project to include a new "Task" card type).

Before I do that, though, I'd like to understand what the "improvement" concept was initially intended for in an agile context. It appears to me that it is simply a carryover from the default scheme from my research so far.



1 answer

2 votes


I think you're research is accurate that this is a carryover from the default scheme, but the use case you've described fits perfectly with the original intent of the issue type in both Agile and non-Agile contexts.

I don't recall exactly when, but I'm pretty sure the 'Improvement' issue type was there before the Agile plugin (the artist formerly known as GreenHopper) became available for JIRA.

Your use case makes sense though. The main thing is to just make sure everyone in your organization understands how and when the issue type should be used.

Say you had a whole lot of the type of "improvement" work that Adrian was talking about for a sprint. Since JIRA doesn't allow you to assign any estimate to improvement issues, wouldn't that defeat the purpose of accurate estimation. Say that the improvements account for 40% of the work. Using JIRA the estimate would be the same whether you plan to do these improvements or plan to sun bathe every afternoon instead.

I concur with Blaine's assessment. An improvement is a story about improving something. IMO improvement is superfluous and can even cause inaccurate velocities. But I'm always open to thought that makes me rethink these things.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Agile

Master the art of thinking big, working small: A conversation with John Cutler

Hello all! It has been 20 years since the agile manifesto was introduced, and closer to 40 years since software development began moving away from a waterfall-type approach. While many teams have ...

1,455 views 11 27
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you