Avoid headaches: Use an Agile issue-type decision tree

02 06–2015

Avoid headaches: Use an Agile issue-type decision tree

First published on arcbees blog:

At Arcbees, we’ve had more discussions that I’d like to admit about issue types in sprint planning. On any given day, the same issue might be reclassified from story to improvement and back again, for reasons that seemed to have little to do with the issue itself.

If issue definition was inconsequential, this would pose no problem for us, but we have found that mis-categorizing issues actually impacts morale, velocity, estimation, and a host of other factors that have real consequences for the success of the project.

The realities and constraints of our work amplify the consequences of improperly classifying issues. We’ve come to identify five key factors that determine how smoothly the development process will unfold for us at Arcbees. All of them are impacted by improperly classified issues.

Continue reading here

Thanks for the read, you can visit my website: www.philippearaujo.com to discover more or follow me directly on social media:
Instagram: instagram.com/philnpa 
Twitter: twitter.com/philnpa 
Facebook: facebook.com/philnpa
Snapchat: businessknight
My digest:
subscribe

One last thing, it just take two seconds of your time and it will be awesome for me! If you can click on the button below to recommend it or share it, it will be amazing.


Originally published at blog.arcbees.com