Collecting Requirements and Defining Scope

acceptance criteria
are those criteria, including performance requirements and essential conditions, which must be met before project deliverables are accepted
Define Scope Inputs
Project Charter
Requirements Documentation
Organizational Process Assets
Scope Management Plan
affinity diagrams
provide for illustrating ideas that are sorted into groups and analyzed accordingly
Define Scope Tools and Techniques
Expert Judgment
Product Analysis
Alternatives Identification and Generation
Build vs. Buy
Facilitated Workshops
audit trail
provides details pertaining to work package consistency and completeness that is acceptable to the stakeholders
brainstorming
is an information-gathering technique that is a tool and technique of the Identify Risks process. It involves assembling in one place subject matter experts, team members, risk management team members, and anyone else who might benefit from the process and querying them on possible risk events
Collect Requirements
contributes to the documentation of stakeholder needs that will determine project objectives. This process includes reviewing the project charter and other documents that will become project artifacts
Create Work Breakdown Structure
is an iterative process that employs the outputs of the Define Scope process to identify the tasks and work packages that will be included in the Work Breakdown Structure
decompose
relates to the process by which the project team breaks down a requirement to its lowest level
Define Scope
results in delivering detailed descriptions of the project’s work. It helps identify all the work that must be performed and only the work that must be performed to meet the requirements identified in the Collect Requirements process
Delphi Technique
is used to gain consensus among a team of experts. Within this technique, experts participate anonymously and are asked a series of questions provided by a facilitator
enterprise environmental factors
are internal or external factors based on an organization’s culture that can impact, negatively or positively, project management options
focus groups
bring together stakeholders that have been identified as subject matter experts. They are moderated and designed for a group consensus, as opposed to one-on-one activities, such as interviews
functional requirements
provide specific details about how the product of the project will work. Based on these requirements, activities will be identified for development to complete a work package that will meet the needs of the project
group creativity techniques
are activities organized to develop project requirements
joint application development session (JAD)
is a process originating from IBM to help application developers arrive at consensus in regard to project requirements. The benefit of a JAD session is that it drives the group, based upon expert judgment, facilitated by a subject matter expert
Mind Mapping
is an activity that involves individualized brainstorming that consolidates all individual findings into a map
Monitoring and Controlling Process Group
includes processes required to track progress and performance of a project; determine required changes to the project plan and integrate those changes into the project
Nominal Group Technique
encourages participants to have equal say in participation, ideas are collected by a facilitator in an individual manner (say ideas submitted to an ‘idea box’ or collecting post-it notes, then the group discuses and ranks or votes on each idea
non-functional requirements
provide parameters of the product that detail how it works as compared to specifics that are required to build the product
organizational process assets
are an accumulation of tools, processes, and techniques that are retained by the business in order to standardize processes and practices
Plan Scope Management
is a process that existed in prior editions and was always done. It is the process of creating the plan on how you and your team should manage the scope activities of the project
Planning Process Group
involves processes required to determine the scope of a project, decompose project objectives and determine how the project will progress via the project management plan
Project Management Body of Knowledge (PMBOK®)
is the sum of knowledge within the profession of project management. Includes proven traditional practices that are widely applied and innovative practices that are emerging in the profession. Includes both published and unpublished materials
product analysis
is analysis performed on line item requirements of a project allows you to develop specific requirements based upon findings
Product Scope
is a more focused concept that is centered on the features and requirements of the product delivered via the project
project charter
describe a project in the initial approach toward the project’s product. Helps illustrate what needs to be accomplished and provides a preliminary approach on how the project will proceed
Project Management Institute® (PMI®)
is a not-for-profit professional organization developed from a group of working project managers. Today its primary goal I to advance the practice, and profession of project management throughout the world
project manager
is the individual charged with managing a temporary endeavor from beginning to end who monitors project progress and ensures that project activities stay on task, under budget, and finishes on time
Project Scope
is the larger of the two concepts. It is relative to the project as a whole, and includes such ideas as work to be performed and resources to be allocated to the project
Project Scope Management
details best practices, skills and processes required for project managers to properly manage scope details best practices, skills and processes required for project managers to properly manage scope
Project Scope Statement
is an important communications tool that provides all project participants with a shared and common understanding of the project’s deliverables and the work that will be performed to create those deliverables. It is a key project management document that provides the project team with guidance on the work to be performed during project execution
requirements documentation
describes how each requirement impacts the project
Requirements Management Plan
centers on the project’s requirements and how they are to be managed throughout the project lifecycle. The plan incorporates tools and activities the project team will utilize in driving the project toward completion
requirements traceability matrix
aids in helping the project team visualize developed versions of activities within a project
scope
defines and details activities necessary to deliver a project to completion
scope creep
phenomena that occurs when additional work gets incorporated in a project
sponsor
is the individual or group outside the project team that initiates the project by requesting for the service or product and beginning the project charter
Stakeholder Register
is a communication tool that a project manager can customize. Helps provide the answers up front in regard to engaging and coordinating efforts amongst stakeholders
stakeholders
are identified individuals who have influence and impact in a project’s outcome. They can either be internal or external to an organization
Work Breakdown Structure (WBS)
gives the project manager and team the ability to decompose project-based features to their lowest elements that can be monitored, managed, measured, and delivered upon. Details developed within the WBS permit the project manager to determine the project’s critical path and schedule, and provide a tool to develop and deliver project metrics
Define Scope Outputs
Project Scope Statement
Project Document Updates
Plan Scope Management Inputs
Project Management Plan
Enterprise Environmental Factors
Project Charter
Organizational Process Assets
Plan Scope Management Tools and Techniques
Expert Judgment
Meetings
Plan Scope Management Outputs
Scope Management Plan
Requirements Management Plan
Inputs for Collect Requirements
Project Charter
Scope Management Plan
Stakeholder Management Plan
Requirements Management Plan
Brief Explanation
Stakeholder Register
Tools and Techniques for Collect Requirements
One-on-one Interviews
Focus Groups
Facilitated Workshops
Group Creativity Techniques
Group Decision Making Techniques
Questionnaires and Surveys
Observations
Prototypes
Delphi Technique
Outputs for Collect Requirements
Requirements Documentation
Requirements Management Plan
Requirements Traceability Matrix