Term
| The features and functions of the product or service that you and your team are building |
|
Definition
|
|
Term
| All the work that needs to be done to make the product |
|
Definition
|
|
Term
| In this process, you will find out all of the stakeholder's needs and write them down so that you know what to build and how to measure and track the requirements |
|
Definition
| Collect Requirements process |
|
|
Term
| In this process of Scope Management, you will break down all the work into discrete pieces |
|
Definition
| Create Work Breakdown Structure |
|
|
Term
| In this process, you need to make sure that what you are delivering matches what you wrote down in the scope statement |
|
Definition
|
|
Term
| This input to the collect requirements process is a list of all of the people you need to talk to work out the requirements for the project |
|
Definition
|
|
Term
| This input to the collect requirements process tells you at a summary level what the project is supposed to accomplish |
|
Definition
|
|
Term
| This process of scope management involves talking to the people who are affected by you rproject to find out what they need |
|
Definition
|
|
Term
| This decision-making technique means that everyone agrees on the decision |
|
Definition
|
|
Term
| This decision-making type means that the idea that gets the most votes wins |
|
Definition
|
|
Term
| This decision-making technique means that more than half the people in the group agree on the decision |
|
Definition
|
|
Term
| This tool of scope management is a form of brainstorming where you write down the ideas as you find them and have the group vote on the ones that they like best. You then use votes to rank all of the ideas |
|
Definition
|
|
Term
| This output of the Collect Requirements process needs to list all of the functional and non-functional requirements of your deliverable |
|
Definition
|
|
Term
| Usually outlined in the Requirements Document, this type of requirement is sometimes called a quality attribute and describe performance, reliability, error handling, and ease of use |
|
Definition
| Non-functional requirements |
|
|
Term
| This output of the Collect requirement process tell you how requirements will be gathered and analyzed |
|
Definition
| Requirement Management Plan |
|
|
Term
| This output of the collect requirements process shows where the requirements came from, where they get implemented, and how they are verified |
|
Definition
| Requirement Traceability Matrix |
|
|
Term
| This output of the collect requirements process is a great way to take a high level look at all of the requirements and make sure that they are mapped to specific test cases |
|
Definition
| Requirements Traceability Matrix |
|
|
Term
| This output of the collect requirements process is a great way to take a high level look at all of the requirements and make sure that they are mapped to specific test cases |
|
Definition
| Requirements Traceability Matrix |
|
|
Term
| The five Scope Management Processes |
|
Definition
Collect Requirements
Define Scope
Create WBS
Control Scope
Verify Scope |
|
|
Term
| This knowledge area is about figuring out all of the work that is needed and making sure that work is done- and nothing else |
|
Definition
|
|
Term
| This subset of the Project Management Plan defines the process you will use for defining scope and managing changes to it |
|
Definition
|
|
Term
| This input to the define scope process tells you the business needs, and who your sponsor and stakeholders are |
|
Definition
|
|
Term
| This tool of the define scope process explores different ways to do the work in order to find the most efficient path for the project |
|
Definition
| Alternatives Identification |
|
|
Term
| This tool of the define scope process defines what deliverables the team needs to work on in order to build the scope statement |
|
Definition
|
|
Term
| The two outputs of the define scope process |
|
Definition
Scope Management Plan updates
Scope Statement |
|
|
Term
| This output of the Create WBS process doesn't show the order of the work packages or any dependencies between them. It's only goal is to show the work involved in creating the product |
|
Definition
|
|
Term
| This tool of the Create WBS process is all about taking the deliverables and coming up with work packages that will create them |
|
Definition
|
|
Term
| This output of the Create WBS process contains the details of every work package |
|
Definition
|
|
Term
| This entry on the WBS dictionary is tied to your company's accounting system. That way you can make sure that all of the work is paid for |
|
Definition
|
|
Term
| This output is used to figure out WHAT work needs to be done BEFORE you start to figure out how the work packages depend on each other |
|
Definition
|
|
Term
| This output of the Create WBS process is used to compare how well the project is going to what you planned for. |
|
Definition
|
|
Term
| This will help you figure out how a change will affect the project constraints-and make sure your sponsors and stakeholders are ok with that impact |
|
Definition
|
|
Term
| Anytime the PM receives a change request, it needs to be approved first and then this needs to be updated |
|
Definition
|
|
Term
| This output of the Create WBS process is updated when you figure out that there are pieces of the scope that you missed and you may need to change your plan |
|
Definition
|
|
Term
| This output to the Create WBS process describes each work package |
|
Definition
|
|
Term
|
Definition
|
|
Term
| This process makes sure that only those changes to scope that you need to make are implemented and that everyone is clear on what the consequences are |
|
Definition
|
|
Term
| The only tool of the control scope process |
|
Definition
|
|
Term
| Using this tool of the Control scope process, you constantly compare the information that you are gathering about the way the project's going to your scope baseline |
|
Definition
|
|
Term
| Whenever a change is received, the first step is to consult this management plan to figure out how to handle the change |
|
Definition
|
|
Term
| Changes to the scope baseline are managed in this process |
|
Definition
|
|
Term
| you wil gather all the stakeholders together and have them make sure that all the work was really done during this process |
|
Definition
|
|
Term
| this is the only tool of the Verify Scope Process |
|
Definition
|
|
Term
| This tool of he verify scope process is where stakeholders look closely at what the team did to make sure that every single piece of work was completed |
|
Definition
|
|
Term
| These two outputs of the Verify Scope process are created when the stakeholders do not think that all the work was done. |
|
Definition
| Change Requests and project document Updates |
|
|
Term
| This output of the Verify scope process means that the stakeholders formally accept the product of the project |
|
Definition
|
|
Term
| This type of diagram helps to synthesize large amounts of data by finding relationships between ideas. The information is then gradually structured from the bottom up into meaningful groups. From there you can clearly "see" what you have, and then begin your analysis or come to a decision. |
|
Definition
|
|
Term
| The process where you write the project scope statement |
|
Definition
|
|
Term
| Figuring out how big a change is by comparing it to the baseline is called |
|
Definition
|
|
Term
| A quantified and documented need or expectation of a stakeholder |
|
Definition
|
|
Term
| A JAD session is an example of this tool of the collect requirements process |
|
Definition
|
|
Term
| A version of the scope management plan, WBS, and product scope |
|
Definition
|
|
Term
| This input to scope management was an ouput created during the Identify Stakeholder process |
|
Definition
|
|
Term
| This input to scope management was an output created during the Develop Project Charter process |
|
Definition
|
|
Term
|
Definition
|
|
Term
| the goal of this process is to gain formal acceptance of the project deliverables from the sponsor and stakeholder |
|
Definition
|
|
Term
| Historical information and lessons learned are a part of this common input |
|
Definition
| organizational Process Asset |
|
|
Term
| This output is used to trace each requirement back to a specific business case |
|
Definition
| Requirement traceability Matrix |
|
|
Term
| Following a deliverable from its initial description all the way through the project throught testing, so that you can make sure that every deliverable meets expectations is done with this |
|
Definition
| Requirement traceability matric |
|
|
Term
| As a general rule, if you ever find that there is no WBS, you should check this management plan to find out why |
|
Definition
|
|
Term
| This management plan is used to verify that the deliverables match the stakeholder's expectations |
|
Definition
|
|
Term
| When you look at a few ways to produce a deliverable and decide on the best one |
|
Definition
|
|
Term
| These types of changes are NOT an input to the control scope process because they haven't yet gone thru integrated change control |
|
Definition
|
|
Term
| this out put of the Create WBS process explains who a work package is assigned to, the control account to bill it against, and what work is involved |
|
Definition
|
|
Term
| If during the project you the PM noticed that some items were left out of the WBS. This is the NEXT thing you should do. |
|
Definition
| Redo the WBS to uncover anything else has been omitted |
|
|
Term
| The primary functions of the WBS |
|
Definition
| To get buy-in from the team members that all of the work has been accounted for and estimates of duration are accurate |
|
|
Term
| Saying- There are many points on which we agree. I am sure we can find a solution is an example of this type of conflict resolution |
|
Definition
|
|
Term
| This PM is accountable to this stakeholder above anyone else impacted by the project |
|
Definition
|
|
Term
| The most effective way of handling the disconnect between what users actually want and what management thinks they want |
|
Definition
|
|
Term
| Regardless of what a stakeholder believes to be true about a project, always check this for verification FIRST |
|
Definition
| Project Management plan/Documents |
|
|
