Taking Requirements to the Next Level Series

$12.95

Many project teams lack a consistent method of ensuring their business requirements document, which identifies the project What’s”, is complete before delving into detail design activities. Some of the most commonly overlooked or underdeveloped types of project requirements are those associated with reporting, user interaction and usability and user acceptance testing.

One of the biggest risks associated with addressing reporting ate in the project lifecycle, after a solution has been designed or built, is the team may have overlooked core functionality expected as part of the solution or may find that core project capabilities related to reporting Business Questions are missing from the business requirements document.

Use Cases and User Interfaces should be developed prior to finalizing the project’s business requirements. Both of these deliverables provide transitional information between defining project What’s and project How’s. They provide a way for stakeholders to look at their project needs from a usability versus a functional perspective and gain insight into unclear or missing business requirements.

User acceptance test objectives provides a project team with valuable insight for how the stakeholders will verify that the new project solution actually meets their expectations and will be accepted at the end of the project. When acceptance testing is delayed until after the business requirements are approved, the ability to uncover gaps in the business requirements or misunderstood capabilities is handicapped and may result in an unusable project solution.

During this 3 part webinar series you will learn how to:

  • Define core Business Questions expected to be asked and answered about the use of the project’s solution which will drive reports
  • Identify high level data entities necessary to answer Business Questions
  • Create business driven Use Cases to identify actors and their requests on the systems being developed to understand the requirements from a usability perspective
  • Drill down business requirements into User Interfaces
  • Develop acceptance test objectives which can be mapped to business requirements and drive out clarity for how the project’s solution will be used to perform work
  • Uncover gaps in the business requirement document by looking at the project need from multiple perspectives

 

All webinars in this series align to the PMI Talent Triangle – Technical

$12.95
$12.95
$12.95

Description

Many project teams lack a consistent method of ensuring their business requirements document, which identifies the project What’s”, is complete before delving into detail design activities. Some of the most commonly overlooked or underdeveloped types of project requirements are those associated with reporting, user interaction and usability and user acceptance testing.

One of the biggest risks associated with addressing reporting ate in the project lifecycle, after a solution has been designed or built, is the team may have overlooked core functionality expected as part of the solution or may find that core project capabilities related to reporting Business Questions are missing from the business requirements document.

Use Cases and User Interfaces should be developed prior to finalizing the project’s business requirements. Both of these deliverables provide transitional information between defining project What’s and project How’s. They provide a way for stakeholders to look at their project needs from a usability versus a functional perspective and gain insight into unclear or missing business requirements.

User acceptance test objectives provides a project team with valuable insight for how the stakeholders will verify that the new project solution actually meets their expectations and will be accepted at the end of the project. When acceptance testing is delayed until after the business requirements are approved, the ability to uncover gaps in the business requirements or misunderstood capabilities is handicapped and may result in an unusable project solution.

During this 3 part webinar series you will learn how to:

  • Define core Business Questions expected to be asked and answered about the use of the project’s solution which will drive reports
  • Identify high level data entities necessary to answer Business Questions
  • Create business driven Use Cases to identify actors and their requests on the systems being developed to understand the requirements from a usability perspective
  • Drill down business requirements into User Interfaces
  • Develop acceptance test objectives which can be mapped to business requirements and drive out clarity for how the project’s solution will be used to perform work
  • Uncover gaps in the business requirement document by looking at the project need from multiple perspectives

 

All webinars in this series align to the PMI Talent Triangle – Technical