“Mum, you know in that movie where King Midas wished that everyhing he touched turn to gold?”
“Mm-hmm?”
“How did he pee then?” 😳😝
Err good question!
I am sure that lawyers like Laura Frederick would find a way to make a wish that had ironclad clauses so that the peeing issue is a.. um… non-issue. 😁
When building #Salesforce solutions, requirements need to be ‘groomed’ to provide details on what they are meant to be (think Acceptance Criteria).
The skill is in gathering enough detail to provide clarity without drowning it in irrelevant noise (has anyone ever tried to pin down real requirements by wading through comments on a JIRA ticket?!) 😱
From a consulting point of view, if you’re on a Fixed Price project, then it needs to be VERY detailed.
If it’s Time & Materials (T&M), then detailed enough to get started, and then finessing in design.
If T&M and pure Agile (instead of hybrid – the more common consulting project approach), then the requirement will need to be detailed enough to be ‘Ready’ under an agreed definition between the scrum team as to what it means to be ‘Ready’.
Anyway, today’s short and sweet post was brought to you by the letter “C”, for clarity.
Do you have a funny anecdote about requirements or wishes that were a bit too vague to be useful?
#OnThePeiroll
#SomeoneFindMeAWishingWellOrAGenieInABottle
#GimmeSomeCrypto
