How do you know when you’ve completed a user story?

How do you know when you’ve completed a user story?
– functionality has been built in sandbox?
– test classes completed at 95%?
– functionality deployed to QA box for testing?
– QA has tested and signed off functionality?
– Show & Tell for functionality completed?
– Users have tested and approved?
– technical solution updated?
– wiki/user documentation updated?
– training video / walkthrough completed?

… or all of the above?

DoD (#DefinitionOfDone) needs to be defined and agreed up front, or you might get caught with your pants down later down the line! 😁

Or, if you’re running a hybrid methodology on a project, when is the system done, tested, and ready for handover to client?

Exit criteria in a Test Strategy/Approach document that is signed off by stakeholders.
What quality threshold is ‘acceptable’ to enter UAT (User Acceptance Testing) before Go-Live?

I talk about the above in my Consulting Masterclasses, no-charge for out-of-work #Salesforce peeps and .org charity customers – starting on 4 May.

#SalesforcePartners – register your team now to level up their consulting/delivery skills, as I am not sure of the dates of the next public course (DM me if you want in-house training).

More details in comments 👇


Leave a Reply

Your email address will not be published. Required fields are marked *