SEPARATE USER STORY ESTIMATES – A SIGN THAT SOMETHING IS WRONG

I once observed a practice where story cards were only estimated based on the development effort. This is problematic as it has one specific focus and not looking at the total work that needs to be completed for a story to be moved into done. Product development is not just about writing code.

A SHORT GUIDE TO AGILE USER STORIES …

I have written this article in the hope that it will remove a lot of confusion in our industry on what a user story is. If you are transitioning from heavyweight to agile methods you may find this useful. I have not included estimation and how we manage stories on the backlog etc and [...]