“We want to make sure the client’s Wordpress site has all its plugins fully updated, ensuring that there is no security risk from outdated plugins”


For a “Problem to Solve” task, the task should include a “Problem Statement”. This is a succinct and easily digestible description of what is going on and why it is a problem. It should not contain any sort of solution. Note that this part of the task is not just for the artisan working on the problem – it is for the PM, QA, and any other staff who find this task. The problem should be clear to non-developers and non-designers.

For an “Outcome to be achieved” task, the task should include a similar statement, but oriented as a positive, not a negative.