PM
Decision tree analysis
1/3 models for project selection and prioritization are presented. Used to select projects based on estimated value
NPV, IRR, ROI, Payback period
1/3 models for project selection and prioritization are presented. Used to select projects based on estimated value
Scorecard analysis
1/3 models for project selection and prioritization are presented. Used to to select and prioritize values based on qualitative criteria.
4/40
40 hrs/4 hrs min
8/80
80 hrs max, 8 hrs min
True
A benefit of project management is that it creates a structure and process that enables a project to be kept under control.
reserve analysis
A comparison of the contingency reserves of schedule, resources, and budget at a particular time during the progress of a project with the original schedule, resources, and budget to determine if there are enough reserves in schedule, resources, or budget best defines
nominal group technique
A decision-making tool used to understand and use the opinion of each and every project member best describes
UML
A graphical language for visualizing, specifying, constructing, and documenting object-oriented software best defines
burndown chart
A graphical representation of the work left to do versus the total scheduled time of an activity or an entire project best describes
Pareto chart
A simple bar graph where the y-axis represents frequency of occurrence best describes
contingency planning
A systematic approach to identify what can go wrong in a project and be prepared with plans, strategies, and approaches to mitigate and manage risks best defines
requirement traceability matrix
A table captured to map all the requirements of all stakeholders in order to track them until the project is complete best defines
fishbone diagram
A tool that allows teams to identify and graphically detail all possible causes related to a problem and discover root causes of the problem at hand best describes
65%
According to a study cited in the textbook, inadequate management practices are associated with project failure. What is the percentage?
Project Documents of Knowledge area 4: Cost Management
Activity cost estimates Basis of estimates Project funding requirements
Project Documents of Knowledge area 3: Time Management
Activity list and attributes Duration estimates Milestone list Project schedule
False
At the CMMI Level 5, software processes are defined by individuals in an organization.
Functional requirements
Capture and specify the behavior of the product, system, or service that is being developed in a project. Brief summary and a rationale that help project stakeholders and outsourced contractors understand why the requirement is needed and track the requirement through the progress of the project
PMBOOK
Collection of processes and knowledge areas generally accepted as best practices within the project management discipline?
Project Management Plan of Knowledge area 7: Communications Management
Communications management pla
Project Documents of Knowledge area 9: Procurement Management
Contracts Proposals Procurement documents Vendor lists Source selection criteria Teaming agreements</TBL>
Project Management Plan of Knowledge area 4: Cost Management
Cost management plan Cost performance baseline
DOCUMENTS DURING PROJECT PLANNING
Customer requirements, Specifications, Functional requirements, Technical requirements, Project plans and planning documents
WBS Level 2
Deliverables
False
Delivery is one of the PMBOK process groups.
Technical requirements
Detailed description of technology that is suitable for the actual design, development, and production processes of a project.
planning process group and time management knowledge area.
Developing schedules, milestones, and critical paths is associated with the
Proper planning can guarantee project success?
False
Project Documents of Knowledge area 7: Communications Management
Forecasts Stakeholder analysis Stakeholder management strategy Stakeholder register
Project plans and planning documents
Formal, approved documents used to guide both project execution and project control.
Project Management Plan of Knowledge area 6: HR Management
Human resources plan Staffing Management Plan
Cost-plus incentive fee contracts
Incentive on seller to reduce cost. Risk on buyer
Project charter
Includes Project purpose or justification, objectives, success criteria, description, risks at a high level Key milestones, Budget information
Stakeholder
Individuals or organizations who are affected by a project best defines
Target cost
Level of cost that a contractor has negotiated with a client. The contract is based on this cost. Both profits and the ceiling price are calculated from this cost.
risk responses
Options and actions that mitigate risks and reduce project threats best defines
Project Documents of Knowledge area 1:Integration Management
Performance reports Project organizational structure Statement of work Project charter Project closure reports Project change requests Project design documents
Project Management Plan of Knowledge area 9: Procurement Management
Procurement management plan
WBS Level 1
Project
Project Management Plan of Knowledge area 1:Integration Management
Project management plan Change management plan Configuration management plan
Project Documents of Knowledge area 5: Quality Management
Quality control measurements Quality control checklists Quality metrics
Project Management Plan of Knowledge area 5: Quality Management
Quality management plan Process improvement plan
Project Documents of Knowledge area 2: Scope Management
Requirement document Requirements traceability matrix Stakeholder requirements Scope document
Customer requirementS
Requirements that satisfy the needs of the customers and the end users
Project Documents of Knowledge area 6: HR Management
Responsibility assignment matrix or Responsibility, Accountability, Consultative, and Informative (RACI) matrix Resource breakdown structure Resource calendars Resource requirements Roles and responsibilities Team performance assessment
Cost-plus fixed fee contracts
Risk on buyer
Project Management Plan of Knowledge area 3: Time Management
Schedule baseline Schedule management plan
Project Management Plan of Knowledge area 2: Scope Management
Scope baseline (scope statement, WBS, and WBS dictionary) Scope management plan Requirements management plan
analyze
Six Sigma DMAIC phase focuses on why and how defects and errors occur?
work packages
Small project activities possibly with very short durations with definable results best defin
Specifications
Specify the requirement in a complete, precise, verifiable manner.
WBS Level 3
Summary tasks - Sub deliverables
True
The discipline of project management is about providing tools and techniques to enable a project team to organize its work and meet the project success factors.
project scope
The general work that needs to be accomplished to deliver a product, a system, a structure, or a service with the specified features and functions best defines
project schedule
The list of all activities of a project with intended start and end dates linked by dependencies and constraints of a project best defines
Stakeholder register
The most important after charter.
complexity.
The number of products or operations that are performed at the same time and the resulting degree of difficulty best defines
True
The overall success factor of a project is the realized value of the project that can be measured by the project stakeholders.
False
The purpose of the QFD technical requirements step is to evaluate how well customer requirements have been met compared to the competition.
Target Profit
The target profit is the negotiated profit in a contract assuming the target cost is met.
Predictable
The traditional SDLC's popularity is because it is
Guaranteed maximum-shared savings contract
This is a great contract for the client as it protects the client against overcharges by the contractor with a ceiling on the contractor price.
Target Price
This is target cost plus target profit and/or target fee found in a negotiated contract.
Target Fee
This target fee is the negotiated fee in a contract assuming the target cost is met.
product scope
Which of the following consists of the features and functions that characterize a product, a service, a system, or a structure?
WBS Level 4
Work packages - Smallest task with short durations
Can risk be positive?
Yes
The selection and prioritization process of organizational projects
alighs with the goals and strategy of the organization.
The most important benefit of a project charter
authorizes a project and ensures that necessary resources and management commitments are provided to achieve success
project scope is a
baseline for performance measurement
Six Sigma asserts that
continuous efforts to reduce process variation are important to overall performance and customer satisfaction in a project.
QFD's graphical format documents
customer requirements, technical requirements, interrelationships.
The TMAP procedure includes
define the project goals, list the knowns, unknowns, and constraints, and sequence and link all team comments, responses and questions.
Project initiation
focuses on project selection and creation of project charters for selected projects.
Steps for nominal group technique for risk management
gathering the core team for a risk workshop using a flip chart or whiteboard to collect information from the team begin by asking each person to identify potential areas of risk
A project
has a beginning and a definite end, expends resources, has constraints and requirements that may include scope, budget, schedule, and resources, performance factors, and creation of value to stakeholders.
Requirement
is a capability that must be met by a system, product, or service to satisfy stakeholders.
Project charter
is a document that formally recognizes a project, includes a problem statement, project objectives, benefits, process owners, and a project sponsor or a champion
Work breakdown structure
is a list of tasks broken down to small manageable activities.
FMEA
is a process in product development and is used in managing operations by analysis of potential failure modes within a system.
Joint Application Design/Development (JAD)
is a process used in prototyping to collect requirements while developing new information systems.
A prototype
is a sample or a model built usually to test a concept, a process, a system, or a product.
SWOT analysis
is a strategic method for identifying whether to use a component or a feature in a project
Joint Requirements Planning (JRP
is a structured group meeting of stakeholders to gather requirements by actively involving the stakeholders to replace individual interviews.
A check sheet
is a table or form that is used to allow a team to systematically record and compile data from historical sources or observations as they happen in real time.
Document analysis
is a technique used in creating requirements from "as-is" process documents.
Use case
is a technique used in software projects to document the potential requirements of a new system or software by conveying how the system should interact with the end user or another system to achieve a specific business goal graphically.
The Kano model
is a tool to distinguish types of product requirements that influence customer satisfaction.
Scope creep
is the addition of scope after it is defined in the scope document.
project life span / project life cycle
is the total of the phases through which a project passes from the time it is initially conceived until the time it is either in use as a success or abandoned as a failure.
Factor for using Agile methods include
prioritization of tasks is done by key stakeholders. works well with true teamwork and collaboration. shortened development cycles.
Goal of the project selection
process is to analyze project viability, approve or reject project proposals based on established criteria.
Fixed-price incentive fee contracts
risk on both seller and buyer
Cost-plus percentage fee contracts
risk on both seller and buyer. Client faces more because contractor has motivation to increase cost.
Stakeholder analysis includes
stakeholder characteristics, level of interest of the stakeholders in the specific project, ability to affect the project policies through power and/or leadership.
Requirements Traceability Matrix
table captured to map all the requirements of all stakeholders in order to track them until the project is complete.
During the early stages of a project
tactics are NEVER more integral to success than strategy
The more the authority and the responsibility are shared between the functional and project managers
the better the chances of project success.
Fixed-price contracts
this is the cost and that's it. Max. risk on seller. Lowest risk for buyer. For the contractor, any cost-plus contract is better than fixed-price contracts with respect to risks.
