Why using proper Agile stories is important

I’m currently working with a very large American bank, implementing Agile. I began here late last March, and almost the first meeting I attended was to agree the statuses required by the Product Owners to track their stories. We probably needed about half an hour, plus (given that we are using Jira) about 20 minutes to implement the entire ‘story’.

Quickly, the conversation spiralled off into listing every status anyone could want to track status – Product Owners, senior management, test leads – you name it. They were trying to save time later, of course, by looking at status tracking in the round. A typical waterfall requirement, I thought – and certainly no Agile story. In fact the basic Agile story model – ‘As a Product Owner, I want to track story statuses, so that I can see where my requests are making progress – went completely by the board.

Of course, we never finished – that day or since. In fact today we went around a familiar old topic one more time: project statuses. More than three months later!

Stick to Agile, but do it properly. The ideas are not just nice-to-haves – they’re there for a reason!

By |2018-01-18T14:44:26+00:00Monday, July 20 2015|Categories: Agile, All, Business and IT, Management systems|0 Comments

About the Author:

Chief Architect, Agile201.com.

Leave A Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Want to do more than just build systems?             
error: Agile201 is wholly copyright and copy-protected.