Developing the Project Management Plan
Planning Project Project Scope
Work Breakdown Structure
More WBS
Extra Credit
100

Its the first process in Planning the Process group

What is "Developing Project Management Plan"

100

An agreement between the project management team and the project customer that states precisely what the work of the project will produce.

What is the "Project Scope Statement"

100

A decomposition of the project scope; Subdivides the project work.

What is the "WBS" or  "Work Breakdown Structure"

100

A numbering system given to each deliverable; Gives everything in the WBS a unique identifier.

What is "Code of Accounts"

100

An environment when collecting requirements upfront; A Linear approach  

What is a "Predictive" environment 

200

Communicates the "start" of the project

What is "The Kickoff meeting"

200

Sets the vision for what the project is going to create; How we move from our current state to that desired future state.

What is the "Project Scope"

200

Its the smallest item in the WBS

What is a "work package"

200

There is no "___________" way to construct a WBS

"right"

The WBS can resemble an organizational chart with different levels but could also be composed in outline form as well. The choice is yours.

200

Contains information about the stakeholder, including their contact information.

What is the "Stakeholder Register"

300

Ensures Key deliverables are identified and a common understanding is established among stakeholders

What else does the "Kickoff meeting" do?

300

The first process in the "Project Scope Management" knowledge area.

What is "Plan Scope Management"

300

This is used to summarize cost, schedule, and scope for all the work package levels assigned to it.

What is "Control Account"

300

The lowest level of any WBS

What is "work package level"

300

A Set of values and principles. 

Embraces Change/Responds to customer needs/improves performance

What is Agile

400

The Develop Project Management Plan process brings all the subsidiary plans together, along with outputs of the Planning group processes, into one document

What is the "Project Management Plan"

400

This is a step by step methodology whereby each stage of the project is completed in order.

What is a "Predictive" or "Waterfall" approach


400

An iterative scheduling technique that uses progressive elaboration to plan the project as it unfolds. This is typically used when there is not enough information to create a complete schedule up front

What is "Rolling Wave Planning"

400

Contains a list, in priority order, of all the user stories (deliverables and requirements) that the product owner defined at the beginning of the project.

What is the "Backlog"

400

Might describe specifications, quantities, colors or more.

For software, might describe a behavior, such as a calculation or process that should occur once data is entered.


What is a "Functional Requirement"

500

Refers to the factors outside the control of the project team that have (or might have) significant influence on the success of the project

What is "Environmental Factors"

500

Project scope developed through iterations

What is "Adaptive" 

500

For a long time Mozart was composing but now he is [breaking down].

What is "Decomposing". The WBS is decomposed from the project scope, it is "broken down"

500

An element of the scope baseline, is where work component descriptions listed on the WBS are documented; Takes each work package/deliverable and defines it.

What is the "WBS Dictionary"

500

Refers to elements that are related to the product but don't describe the product directly. 

In the case of software, this could be a security requirement.

What is a "nonfunctional requirement"