Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XS✔ ◾ Adjust "be specific in communication" section title to reference PBIs as well as emails #8253

Merged
merged 3 commits into from
Mar 26, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 9 additions & 19 deletions rules/communication-are-you-specific-in-your-requirements/rule.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,40 +20,30 @@ When you're scoping the work to be completed, ensure you are as accurate as poss

<!--endintro-->

### Be Specific


### Be specific

::: greybox
"I want to keep contact details on my clients"

_"I want to keep contact details on my clients"_
:::


::: bad
Figure: Bad example - likely to require later clarification

Figure: Bad example - Likely to require later clarification
:::


::: greybox
"I want to record my clients' firstname, surname, mobile phone, email address & Instant Messenger address."
_"I want to record my clients' firstname, surname, mobile phone, email address & Instant Messenger address."_
:::


::: good
Figure: Good Example - You'll get exactly what you want. Even better, use screenshots 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](/management-do-you-spec-in-bite-sized-pieces) and ensure that those pieces are in the project plan explicitly.
### One email or Product Backlog Item per task

Sometimes software developers miss a related item that 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!
The best way for this to work is to break tasks into the smallest possible [bite-size pieces](/management-do-you-use-just-in-time-speccing) and ensure that those pieces are in the project plan explicitly.

### Get Approval for UI Changes
Sometimes software developers miss a related item that 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 3 other forms that the same type of combo appears on. So if you also want them fixed, then let them know about them!

### Get approval for UI changes

Insist your software consultants [conduct specifications by creating mock-ups](/storyboarding-do-you-conduct-specification-analysis-by-creating-mock-ups).
Make sure software consultants [conduct specifications by creating mock-ups](/storyboards).
Loading