Business Analysis
Writing Requirements
Tools and Templates
Analyze
In the Mix
100

A usable representation of a business need that describes the features and characteristics a solution should have 

What is a Requirement?

100
Plan, Elicit, Analyze, Document, Collaborate & Deliver

What are the 5 phases of writing requirements?

100

Used to list project contacts

What is the requirements contact list?

100

Business requirements, Solution requirements, Transition requirements, Business Rules

What are requirement classifications?

100

Unambiguous, traceable, testable

What are characteristics of a good requirement

200

Responsible for eliciting and documenting the business need a solution must meet.  

Who are PMTs? 

200

Which phase will most business analyst ignore or rush through

What is the Plan phase

200

This outlines an orderly method for the requirements process and includes timelines.

What is the Requirements Management Approach?

200

These sub categories describe the characteristics of a solution 

What are Functional and Non Functional requirements

200

Co-worker review of your project deliverable

What is peer review

300

These are project methodologies

What are Agile and Waterfall?

300

Missing project timelines is a result of this



What is poor project planning


300

This is an important skill to have as a Program Manager 

What is facilitation skills

300

Daily Double

Traditional requirements are documented in what

Traditional User Stories are documented in what

300

Bonus

These should be stored on the project SharePoint site in case the project is audited

Acceptance and Approval

400

These capture how the business need should be designed

What are technical requirements?

400

Name the source document that kicks off most engineering projects

What is the PRFAQ

400

These types of questions prompt conversation and build trust

What are open ended questions?

400

The voice of a good requirement

What is active voice?

400

Daily Double

What does RTM stand for?


Requirements Traceability Matrix

500

A simple question to ask during root cause analysis

What is "Why"?

500

What is the source document that kicks off most projects 

What is the OP Intake Request Intake Form

500

The most important task of a Product and Program manager

What is elicitation of requirements

500

These are often referred to as "parent requirements" or "higher level" statements

What are business requirements

500

This should always be included in your project meeting invites, especially when stakeholders are included.

What is an agenda?

M
e
n
u