Communication - Are you specific in your requirements?
Rules to Better Product Owners|29c34567-f635-4815-8265-c7b02f503521
v8.0
Posted at
24/06/2013 5:39 PM by
Ulysses Maclaren
Rule Intro
Be Specific
When you're scoping the work to be completed, ensure you are as accurate as possible in your requirements.
Page Content
"I want to keep contact details on my clients"
Figure: Bad example - likely to require later clarification.
"I want to record my clients' firstname, surname, mobile phone, email address & Instant Messenger address."
Figure: Good Example - You'll get exactly what you want. Even better, use screen shots or mock-ups.
One Email per Item
The best way for this to work is to break tasks into the smallest possible bite size pieces and ensure that those pieces are in the project plan explicitly.
Sometimes software developers miss a related item which you might consider 'blindingly obvious.' For example you might ask them to fix a combo box on one form in a legacy application. But they mightn't know about the three other forms that the same type of combo appears on. So if you also want them fixed, then let them know about them!
Get UI Changes OKed
Insist your software consultants conduct specifications by creating mock-ups.
{37B7EE60-97E9-4026-BD85-ABA543767710}
Do you feel this rule needs an update?