Penguicon 2018

Who do you call when your agile process is broken, when you’re suffering from "clogging of the iterations" and your user stories have become monsters which threaten to devour your entire Release Train? There are monsters living under your bed and they want to eat you – In agile they are called User Stories. This will be run like a work shop, so please bring in your most troubling User Stories for an open discussion. I will provide a case study workshop to get the conversation rolling. I will be using the INVEST criteria plus a few extra’s to evaluate User Stories. We will take a walk-through of User Stories using the specific:
Independent – Is it self-contained, without inherent dependencies on other User Stories?
Negotiable – Is there room for a discussion?
Valuable – Does it deliver value to the stakeholders?
Estimable – You must always be able to estimate the size of a User Story.
Small – It should not be so big as to become impossible to plan or prioritize.
Testable – You must be able to verify that solution is correct.