• Stephen Stofanak

T-Assess Project Requirements

Updated: Nov 6, 2021

The people impacted by your project will determine success or failure. Focus on their requirements.

  • Review all project requirements up to this point.

  • Requirements can come from multiple groups, such as customers, management, project sponsor, stakeholders, users of the intended solution, groups impacted by the problem and proposed solution, regulators, citizens, local, state, and federal government.

  • Identify the individuals, departments, or groups that will be most impacted by this project.

  • Determine if you're comfortable that you have & understand the summary & detailed requirements from these most impacted groups.

  • If you're not sure you have & understand all the requirements, consider facilitating a focus group of representatives from the most impacted groups to gather and validate their requirements.

Elements to discuss & gather from each group:

  • Their view of the project’s goals

  • Their needs & wants

  • Their current business state

  • Key assumptions

  • Technology requirements

  • Quality requirements

  • Organizational considerations.

Uncovering assumptions while gathering requirements:

  • Why do they believe that…?

  • It appears that they are assuming…?

  • What are the assumptions that appear to be driving resistance within the groups?

  • What are the assumptions that appear to be driving support within the groups

  • What’s the risk of proceeding with certain assumptions?

  • What are the group’s requirements and specifications?

  • How will we assess and validate the requirements and specifications?

  • What are the technology requirements and specifications?

  • How will we assess and validate the technology requirements and specifications?

  • What are the quality / performance requirements?

  • How will we assess and validate the quality requirements and specifications?

  • How will we know this item has been completed?