Collaboration beats clever
This is the subtitle.
What it is
This section is 2-3 paragraphs that explain the core gist of the method.
It should be clear, simple to read, and explain the whole.
For example, here is the description for User Story (a Jimmy Tool) which demos the system wanted here: A User Story summarises user requirements, typically for software development, in a single, short, easily-understood sentence that concentrates on the why rather than the how.
User Stories are helpful primarily because they keep the focus on the desired outcome instead of on the solution that might deliver it. This permits the development team the freedom to design a solution without being constrained by preconceived ideas.
Why use it
- The problem it solves
- The impact it has on your work
- What
good
looks like
When to use it
- When to use it
- When not to use it
How to apply it
Not step by step instructions, but situational explainers about how to apply.
Common issues
- Ways it gets misused
- Signs you’re taking it too far or misunderstanding it
- How to get back on track
Building the habit
- How to incorporate it as part of your work
- How to introduce it to your team
References
- Links to external or
read more
type books/articles etc.