“Do we really need them?” 🙄
Strong, tight #AcceptanceCriteria is something we consultants are used to when documenting requirements.
It tells us the outcome we are looking for.
It tells us how to build it.
It tells us how to test it.
It tells the client how to check whether we have done what we promised to do.
(So we can get paid) 😁
But what if you’re in-house admin?
Isn’t it all just “red tape” and “unnecessary admin”?! 🤷🏻♀️
Whut the…!
Nooo! 😖
This solution architect I’m coaching started their journey a few years ago as a solo admin and have cut their technical teeth on new clouds and expanding platform integrations.
But that meant poor governance and unstructured way of working.
😬
She connected with me to level up her #leadership and people skills, but we found out that she also needed help on proper documentation when I saw how requirements were captured.
I also had to introduce her to the salesforce “Well-Architected Framework!” 😮
She’s technically capable, however I think there’s a lot I can help with her gaps around #BusinessAnalysis and #governance.
Adding good ACs to user stories is a good start.
Also the user stories could use a bit of tightening with a wrench 🔧
😁
I have to say tho, when I saw those requirements … I almost turned green!
Hulk smash!
