IT Consultant @ Own Company
location_on United Kingdom
Member since 2 years
Product magician, Agile practitioner and conference speaker.
Brand new shiny' project(s), no legacy, everything to build and design from scratch… Dream scenario, innit?
Well, can be a nightmare when under this description is hidden few years old project which is still under ‘construction’ and can't be used by business/users even though it's kinda 'working'. Yep, this means mess and few years legacy code even before going to the production. Yay, what a fun!
But, even if you're lost in the darkest forest, there is a hope! Always.
During my talk I present the sins that leads to this situation:
-No product vision
-Too big backlog
... and cures for them!
Feature gluttony is a common sin among IT projects. Customers deliver never ending wish list of features they want. However, the key is not to build everything, but only things that are really needed. Learn how to defeat feature gluttony by... saying NO ;) And support this by:
- setting common aim
- finding relation: feature <-> value
- defining most important use cases
- defining critical process from the business perspective
- decide what should be delivered first
… and build excellent piece of software :)
User stories are supposed to reflect the 'human' side of the IT. The should be easy to understand and not too technical. Ok, but what should happen when you're asked to prepare user stories for strictly technical projects/products?
1. Understanding target audiences
2. Understanding scope
3. Use or not to use user stories -> scope management
4. Fitting the requirements to 'user stories' oriented tools