Setting tasks
How to phrase a task
Good and bad task statements, and a short cheat sheet.
Buff will clarify the details, but the clearer the statement, the fewer the iterations.
Good
- Describe the problem and the expected result, not just “do X”.
- State the boundaries: what may be changed and what may not.
- Give an example of the desired behaviour, if you have one.
Bad
- Too general (“improve the project”) — nothing to work with.
- Several unrelated tasks in one — better split them.
- Hidden assumptions without context.
Cheat sheet
What is wrong now → what it should become → how to check it is done → what definitely not to do.