Skip to Main Content
Skip to Navigation
Project Management Orientation

Deciding: Requirement or Exclusion

After you have gathered needs, categorize them as either requirements or exclusions.  In effect, you are deciding to:

Documenting Requirements

Documented requirements must be clear and concise, because they form the basis of your project plans.  As you write requirements, determine whether they can be misinterpreted.  Writing requirements that can't be misinterpreted is a difficult task.  To help ensure that requirements are clear, include graphics, models, and other visual representations, where appropriate.
  
After you have written the requirements document, ask your team to review it to be sure they have the detail they need to get started.

1: Getting Started
2: Define the Project Team
3: Team Management
4: Identify and Validate Requirements
5: Create Decomposition Structures
6: Risk Management
7: Project Estimates
8: Project Schedules
9: Change Management
10: Project Control and Execution
Defining the Project
11: Project Management Review
12: Project Closeout
13: Project Management Tool Suite
14: Self-Assessment and Final Exam
Fast Points
Concepts
Seven Keys
Case Study
WWPMM
Mentor
Check Point
Previous button
Next button
Print button
Help button
Glossary button
Exit course button