This content is retired but we have related up-to-date content below.
Trial lock

This Research is for Members Only

Not a member? Unlock a free sample of our research now!

Already a member?

Sign in now

When you have to communicate decisions to stakeholders, one possibility is to use a requirements document. Unfortunately, requirements documents are seldom read promptly, and you risk that your project will run out of steam before stakeholders get back to you.

Another strategy is to use something different in order to avoid the risk of "taking a couple of days to get everyone on the same page": the task analysis grid is an interesting alternative to the standard requirements documents.

  • Map the steps required to successfully undertake the task.
  • Indicate the resources required to complete each step. Include human resources, stationery, equipment, and costs.
  • Indicate the time taken to accomplish each step.
  • Highlight any areas where you believe errors could occur or any areas where you receive contradicting information regarding how a step is completed.

The goal is to see the scope of the project and the whole features of the first and future releases on the same page in a unique schematic description.

Related Content

Hide Details

Search Code: 74139
Published: February 4, 2014
Last Revised: February 4, 2014


Get Access

Get Instant Access
To unlock the full content, please fill out our simple form and receive instant access.