PM 2500 Flashcards
(178 cards)
1
Q
Operation Definition
A
- ongoing execution of activities
- same product / repetitive service
- standard processes or procedures
routine - never-ending projects
2
Q
Project Definition
A
- Defined as a temporary endeavour undertaken to create a unique product, service or result
- a definite beginning and end.
- Projects are temporary but the product, service or result can exist beyond the duration of the project.
3
Q
Examples of Projects
A
- Service - website, internet, banking
- Product - (tangible) construction, car, cell phone
- Result - (no tangible product or service) research
4
Q
Examples of Operations
A
- Running routine reports on an organization’s dashboard
- Meeting every Mon, Wed, Fri with the clinical team
5
Q
Operations Vs Projects
A
- Running a B & B vs. establishing a new B & B
- Assembly line producing existing models of cars vs. design of a new model of car
- Management of visiting a tourist destination (Whistler, Butchart Gardens) vs. creating a new tourist destination in Squamish.
6
Q
Outcome
A
An end result or consequence of the process or project”. Outcomes can include outputs and artifacts, but have a broader intent by focusing on the benefits and value that the project was undertaken to deliver.
7
Q
Product
A
An artifact that is produced, is quantifiable, and can be either an end item in itself or a component item.
8
Q
Objectives of a project
A
- Outcomes or Products or a combination of both.
- Need to be determined at the beginning of the project.
- Documented in the project charter, must be clear and achievable.
9
Q
Strategic alignment
A
- Should be in every project charter.
- project initiation should align with company’s strategic goals.
- More likely to be supported if they align.
10
Q
Project Management definition
A
Application of knowledge, skills, tools, and techniques to project activities to meet project requirements.
- Balancing constraints (scope, quality, schedule, budget, resources, HR management).
11
Q
Portfolio
A
Collection of “projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives.
- large number of projects that may or may not be related.
12
Q
Program
A
Group of “related projects, subsidiary programs, and program activities managed in a coordinated way to obtain benefits not available from managing them individually.
- coordinated to maximize benefits and control
13
Q
Project
A
Individual Projects that are either within or outside of a program are still considered part of a portfolio.
Projects are often used as a means for achieving the goals and objectives within an organization’s strategic plan.
14
Q
Project Manager
A
- Responsible for ensuring project objectives are met.
- ## Person assigned to lead the project team.
15
Q
Personal Effectiveness
A
Effective - doing the right thing at the right time.
Efficient - using the appropriate resources
16
Q
Project Manager Functions
A
- Oversight and coordination
- Present objectives and feedback
- Facilitate and support
- Perform work and contribute insights
- Apply expertise
- Provide business direction and insight
- Provide resource and direction
- Maintain governance.
17
Q
Oversight and coordination
A
lead, monitor, and control activities; also includes evaluation and analysis. Includes monitoring and working to improve overall well-being of project team members.
18
Q
Present objectives and feedback
A
collaborate with customers and end users to provide perspectives and insight.
19
Q
Customer
A
individual or group who has requested or is funding the project and the end user is the individual or group who will experience the direct user of the project deliverable
20
Q
Facilitate and Support
A
People in this function encourage participation, collaboration and a shared sense of responsibility for outputs. Includes evaluation of performance and the provision of feedback for learning and growth.
21
Q
Perform work and contribute insights
A
Provide the knowledge, skills, and experience necessary to product the products and realize the outcomes of the project.
22
Q
Apply expertise
A
Subject matter experts and provide expertise in the project, offering advice and support and contribute to the project team’s learning process and work accuracy
23
Q
Provide business direction and insight
A
Guide and clarify the direction of the project or product outcome. - Review requirements to prioritize
- Feedback allows for efficient interaction amongst stakeholders, customers and team.
24
Q
Provide resource and direction
A
Promote the project and communicate the organizations’ vision, goals and expectations”, and are advocates. Useful for escalating issues/risks, this function pushes decisions outside the authority of the project team.
25
Maintain governance
Approve and support recommendations made by the project team and monitor project progress in achieving the desired outcomes.
26
Competencies (Hard Skills) of PMs
Skills are easily quantifiable unlike soft skills which are related to one's personality.
- Technical PM Leadership
- Strategic and Business Management
- Knowing the business (e.g. carpenter, engineer, electrician) if applicable
27
Competencies (Soft Skills) of a PMs
combination of people skills, social skills, communication skills, character traits, attitudes, career attributes, social intelligence and emotional intelligence quotients among others.
- Team Building
- Motivation
- Communication
- Decision making
- Political and cultural awareness
- Negotiation
- Trust building
- Conflict management
- Coaching
28
Other skills
- Conflict management
- Financial Management and Accounting
- Purchasing and Procurement
- Sales and Marketing
- Unions and Collective - Agreements
- Contract and Commercial Law
- Manufacturing and Distribution
- Supply Chain Management
- Strategic Planning
- Organizational Development
- Health and Safety
29
4 major phases of a project
AKA project life cycle. Starting a project, organizing and preparing, carrying out the work, and ending the project.
Involve uncertainty (risks - opportunities and threats). Must produce deliverables to proceed to the next phase.
Once a project is divided into phases, each phase becomes a sub-project and will go through its own process groups. (process groups ARE NOT phases of project).
30
Value
worth, importance, or usefulness of something. Defined differently by groups:
- Customers: ability to use specific features or functions of a product.
- Organizations: business value as determined with financial metrics.
- Societal: contribution to groups of people, communities, or the environment.
31
Tangible vs Intangible Value
Tangible (Monetary assets, Stakeholder Equity, Tools, Market Share)
Intangible (Goodwill, Brand Recognition, Public Benefit, Reputation)
32
5 process groups
Initiating, Planning, Executing, Monitoring & Controlling, and Closing.
Each phase will follow each of of the 5 process groups.
33
Why have phases?
- Added control; easier to control larger projects
- Reduce or mitigate risk
- Logical sub-sets of the work – distinct focus
- Generally sequential, sometimes there may be an overlap
- Significant deliverable
- Celebrate successes between phases prior to commencing next phase
- Go-no-go, stage gates, kill points (all mean the same thing) the opportunity to the organization to close a project
34
Attributes of phases
- The work in the specific phase is different from other phases.
- Deliverables or objectives require processes unique to the phase.
- Closure involves the transfer of deliverable. The closure generally requires approval.
35
Project phase examples
- Feasibility study
- Design
- Build
- Test
- Deploy
- Close
36
Phase-end review
Each phase formally initatied.
During review - explicit goal of obtaining authorization to close current phase and initiate subsequent phase.
AKA: phase exits, phase gates, kill points
37
Kill points
stakeholders decide that the project is not worth completing in its current state. It may be restarted with different criteria.
38
Go/No-Go
- when a project requires a decision being made to continue with the remainder of the project or not
- If you need to pause, recheck or to re-verify in your project, then you have a no-go decision
39
Initiation Process Group
Processes performed to define a new project or a new phase of an existing project by obtaining authorization to start the project or phase.
- initial scope is defined
- initial financial resources are committed
- Internal and external stakeholders identified (initial list)
- PM selected
40
Planning Process Group
Processes required to establish the total scope of the effort, refine the objectives, and define the course of action required to attain the objectives that the project was undertaken to achieve.
- Develop the Project Management Plan
- Develop project documents
Significant changes occurring throughout the project life cycle trigger a need to revisit one or more of the planning processes and possibly some of the initiating processes.
41
Executing Process Group
Processes performed to complete the work defined in the PM Plan to satisfy the project requirements.
- Coordinating people and resources
- Managing stakeholder expectations
- Integrating and performing the activities of the project
- Creates planning updates and re-baselining (changes to activity durations, resource productivity and availability, and deal with unanticipated risks).
42
Monitoring and Controlling Process Group
processes required to track, review and regulate the progress and performance of the project; identify any areas in which changes to the plan are required; and initiate corresponding changes
The key benefit is that project performance is measured and analyzed at regular intervals, appropriate events, or exception conditions, to identify variances, so that corrective action can be taken.
- Recommending corrective or preventive action
- Monitoring the ongoing project activities against the Project Management Plan
- Monitoring the project performance measurement baseline
- Ensuring approved changes are being implemented
43
Preventive actions
proactive actions exercised to eliminate the cause of mistake/error and to prevent the occurrence.
44
Corrective actions
Actions employed to eliminate the cause of the mistake/error in order to mitigate its recurrence. Corrective actions should always be followed by a preventive action.
45
Closing process group
Processes performed to formally complete or close a project, phase, or contract.
- Obtain acceptance by the customer or sponsor to formally close the project or phase
- Conduct post-project or phase-end review
- Record impacts of tailoring to any process
- Document lessons learned
- Apply appropriate updates to organizational process assets
- Archive all relevant project documents in the project management information system (PMIS) to be used as historical data
- Close out all procurement activities, ensuring termination of all relevant agreements
- Perform team members' assessments and release project resources
46
Project Charter
Formally authorizes the project or phase
47
Project Management Plan
- States how the project will be executed, monitored and controlled
- Subsidiary plans to address scope, schedule, cost, quality, etc., management
- Project Documents to address management activities across knowledge areas
48
Project life cycle
The series of phases that a project passes through from its start to its completion
49
Project phase
A collection of logically related project activities that culminates in the completion of one or more deliverables.
50
Phase gate
A review at the end of a phase in which a decision is made to continue to the next phase, to continue with modification, or to end a program or project.
51
Project management processes
A systematic series of activities directed toward causing an end result where one or more inputs will be acted upon to create one or more outputs.
52
Project management process group
a logical grouping of project management inputs, tools and techniques, and outputs. the project management process groups include initiating, planning, executing, monitoring and controlling, and closing. PM process groups are not project phases.
53
PM knowledge area
An identified area of PM defined by its knowledge requirements an described in terms of its component processes, practices, inputs, outputs, tools, and techniques.
54
In which Process Group do the knowledge areas Scope Management and Schedule Management occur?
Planning Process Group
Rationale: Meaningful planning is vital to the successful execution of a project.
55
Would “Organizing the Winter Olympics” be considered a “project” or “operations"? And provide rationale
Project: The Olympics would be a project as it has a defined start and stop. The end is reached at the end of the games. The objectives have been met.
56
Stakeholder Definition
An individual, group, or organizations that may:
affect, be affected by or perceive itself to be affected by a decision, activity, or outcome of a project, program or portfolio
who directly or indirectly influence a project and its performance or outcome in either a positive or negative way
57
Analyze and document stakeholder...
- Requirements (wants)
- Expectations (ambiguous/undefined requirements)
- Interests (do they care?)
- Involvement (if/how) good communication needed, determine timing.
- Interdependencies (who is connected)
- Influence (+ or -)
- Potential impact on project success
58
Stakeholders are impacted by:
A decision
An activity
Outcomes of the project, program or portfolio.
59
Examples of stakeholders
Customers
Sponsors
The Performing Organization
The Public
The Functional Manager
60
Where (documents) can you identify stakeholders
- Project Charter
- Business Documents
- Project Management Plan
- Project Documents
- Agreements
- Procurement Documents
- Enterprise Environmental Factors
- Organizational Process Assets
61
Groups
Groups of individuals that have no organizational title
62
Organizations
Groups of individuals acting with an organizational title (for example, the Health & Safety Department, WorkPlace Health, WorksafeBC)
63
Project balance
balance demands, needs and expectations as they all influence the project based on their amount of power.
Balance project objectives with stakeholder expectations.
64
Failure to identify stakeholders
- delays
- cost increases
- unexpected issues
- project cancellation
65
BCIT has been working on adding another coffee shop to the SW3 Building. The project has been approved and the new coffee shop will be on the main floor. A contractor has been hired to complete the project in three months. Who are the stakeholders for this project?
- Project team
- Health and Safety certification organizations
- Another coffee shop
- Instructors
- Coffee shop suppliers
- Contractors
- BCIT communications department (which class will be affected etc.?)
- BCIT custodian staff
- Finance department
- BCIT staff (administration)
- Hydro and water company (maintenance)
- Students
- Any food and beverage shop
- Patrons
- All those using SW3
- Parking
- Security
- BCIT Board of Directors
66
Why prioritize stakeholders?
- Saves time and resources
- Assists requirement gathering
- Allows for continuous reviews throughout the project
- Enables PM to take charge and communicate
67
Power interest grid
Analyze stakeholders based on level of authority (power) and their level of concern (interest) in relation to project outcome.
68
High power - high interest stakeholders
Decision makers. Greatest impact on project success. Must closely manage their expectations.
69
High power - low interest stakeholders
Keep them in loop and satisfied. Have power. May exploit their power if they become dissatisfied.
70
Low power - high interest
Ensure adequately informed. Can be beneficial to the specifics of project.
71
Low power - low interest
monitor, but don't tire with unnecessary updates or communication.
72
Tools and techniques for stakeholder identification
- Expert Judgement
- Data Gathering
- Data Analysis
- Data Representation
- Meetings
73
Stakeholder register
a project document that includes information about project stakeholders, including an assessment and classification of project stakeholders.
Is not static, changes occur throughout project.
74
Stakeholder identification information
name, organizational position, location, role in project, contact info
75
Stakeholder assessment information
name, organizational position, location, role in project, contact info
76
Stakeholder classification
Internal/external, supporter/neutral/resistor.
77
Collecting Requirements
Criteria for determining, documenting and managing stakeholders' needs and requirements to meet the project objectives.
78
Requirement
condition or capability that is necessary to be present in the final product or outcome of the project.
79
Types of requirements
- Business
- Stakeholder
- Solution
- Transition
- Project
- Quality
80
Business requirement
The "brand look" of a product: e.g., Apple products. Themes, looks, branding.
81
Stakeholder requirements
How much power or interest a stakeholder has (for instance, a lot of power and a lot of interest).
82
Solution Requirements
Available solutions.
Providing solutions to an impass: e.g., renovation in bathroom that you are unable to do unless you 1) provide another option or 2) add more money to project.
83
Transition Requirements
From one area to another, one database to another.
When deliverables are created in phases: e.g., the output of one work package is the Input to another
84
Project Requirements
Location of the project, constraints.
What is the structure forcing you to do? e.g., army projects – behind closed doors.
85
Quality Requirements
Specifications of a product: e.g., longevity of a car, ISO standards
86
Requirements sources of information
- Project Charter (High level project and product requirements)
- Project Management Plan (Scope, Requirement, stakeholder management plans)
- Project Documents (Assumptions Log, Lessons Learned Register, Stakeholder Register)
- Business Documents (Business Case)
- Enterprise Environmental Factors (EFFs)
- Organizational Process Assets (OPAs)
87
Assumption Log
- Contains high level strategic and operational assumptions and constraints identified in Business Case level
- Lower level assumptions and constraints are generated throughout the project.
- Created at the same time as the Project Charter
88
Tools and techniques to collect requirements
- Expert Judgement
- Data Gathering through Interviews
- Focus Groups
- Interpersonal & Team Skills through Facilitated Workshop
- Data representation
- Data Gathering through Brainstorming
- Data Gathering Through Questionnaires and Surveys
- Prototypes
- Benchmarking
- Decision making
- Interpersonal & team skills through observation
- Context diagrams
89
Examples of expert judgement
- Senior management
- Other units within the organization
- identified key stakeholders
- project managers who have worked on projects in the same area (directly or through lessons learned)
- SMEs in business or project area
- industry groups and consultants
- professional and technical associations.
90
Data gathering through interviews
- Direct information discovery from stakeholders – formal or informal
- Questioning – prepared or spontaneous questions, one-on-one or in groups
- Lessons learned and experienced project participants, stakeholders, subject matter experts (SMEs)
- Identifying and defining required functions and features
91
What is the difference between a function and a feature?
Functions are an activity or purpose intended for a thing. Ex: cell phone functions are that it can make a call, receive a call, etc
Features are characteristic attributes of a product, Ex: a cell that has a thumb print password, or panorama photos.
92
What percentage of a Project Manager’s communication is delivered via body language (non-verbal communication) – those behaviour and actions aside from words themselves?
55%
93
What percentage of a Project Manager’s message is attributed to the choice of words?
17%
94
Besides body language and choice or words what else does communication involve?
Tone, intonation, and other aspects of speech.
95
Characteristics of a good interview
- clearly defined goals
- two-way communication
- a trusting relationship is established
- capture the feelings and opinions of the interviewee
- informal gathering of information
96
Data gathering through focus groups
Led by a trained moderator, focus groups consist of authorized and experienced stakeholders and SMEs assembled to gain an understanding about the expectations and attitudes about a proposed product, service, or result.
97
Interpersonal & Team Skills through Facilitated Workshop
- Groups of x-sectional stakeholders to define product requirements.
- quickly define x-functional requirements and reconcile stakeholder differences.
- well-facilitated, build trust, foster relationships, improve communication, leading to improved consensus.
- allow early identification and resolution of issues.
98
Other data gathering methods
- Brainstorming - nominal group technique, multi-criteria decision analysis.
- Questionnaires and surveys (large audience, quick turnaround). Useful for collecting attitudes, beliefs, behaviour, and characteristics.
99
Hawthorne effect
Type of reactivity in which individuals modify an aspect of their behavior in response to their awareness of being observed
100
Requirements Documentation
- Describes how requirements meet the business need for the project
Baseline requires unambiguous requirements: measurable, testable, traceable, complete, consistent, and acceptable to key stakeholders
101
Requirements tracebility matrix
- links requirements to their origin and traces through throughout project
- links requirements to business and project objectives.
- tracks requirements to ensure final delivery
- provides structure for managing changes to the product scope
102
Tracing (columns on traceability matrix)
- Business needs, opportunity, goals and objectives
- Project objectives
- Project Scope/WBS deliverables
- Product design
- Product development
- Test strategy and test scenarios
- High-level requirements to more detailed requirements
103
Context diagrams to collect requirements
Graphical representations that depict project scope, show 'flow' of business processes and how people and systems interact with each other.
104
When to use a questionnaire?
- people are widely dispersed
- large numbers of people are involved in the project
- exploratory study to gauge opinion
- Prior to a series of interviews
105
Open-ended questions advantages
- unlimited number of possible answers
- can elaborate in detail and explain responses.
- unforeseen conclusions can be drawn
- self-expressive responses permitted
- reveal respondent's reasoning, thinking process, and frame of reference
106
Open-ended questions disadvantages
- responses may be unrelated or buried in useless detail.
- hard to apply statistics
- articulate and well-read respondents have an advantage.
- questions may be too general
- increased time needed for thoughtful responses
- respondents could be intimidated by questions.
- may require more space on questionnaire.
107
Close-ended questions advantages
- easy, quick to respond
- easier to explore statistically
- more likely to answer about sensitive topics
- fewer irrelevant or confused answers
- less articulate or less literate are not disadvantaged
- duplication is easier
108
Close-ended questions disadvantages
- ideas can be suggested that respondent may not have thought of.
- respondents with no opinion or knowledge can answer regardless
- can be frustrated their desire answer isn't an option
- confusing if many choices are offered
- misinterpretation if a question can go overlooked
- force respondents to give simplistic responses to complex issues.
109
Methods of applying questionnaires
- all respondents all at once
- hand back questionnaire on their own time
- mailing, giving deadline and providing return envelope.
- Email/web friendly.
110
Prototypes to collect requirements
- Working model of expected results allows stakeholder feedback
- Supports the concept of progressive elaboration
- Provides better quality requirements
111
Benchmarking to collect requirements
compare process/operations with other organizations to identify best practices and improvement ideas.
112
Decision making to collect requirements
voting - including decisions based on unanimity, majority, or plurality.
113
Interpersonal and team skills through observation
direct way of viewing individuals in their environment performing their jobs or tasks and carrying out processes.
Useful way of establishing what is happening - activities, messages, influence, relationships.
114
Project scope
work performed to deliver a product, service, or result with specified features and functions.
115
Project scope mgmt steps
1. Plan Scope Mgmt
2. Collect Requirements
3. Define scope
4. Create WBS
5. Validate scope
6. Control scope
116
Plan Scope Management
creating a scope management plan to outline how the scope will be defined, validated and controlled.
117
Collect Requirements
The process of determining, documenting and managing stakeholder needs and requirements.
118
Define Scope
Developing a comprehensive description of the project and product. Builds on deliverables, assumptions, constraints for project initiation.
119
WBS
Subdividing deliverables into move manageable components.
120
Validate Scope
The process of formalizing acceptance of the completed project deliverables.
121
Control Scope
Monitoring the status of the scope and managing changes to the scope baseline.
122
Product scope
Features and functions that characterize a product. Ex: phone, function = make a call. Features = add ons for marketability (camera).
123
Project scope
Clear and detailed work performed to deliver a product, service or result with specified features and functions.
124
Project scope management
Includes processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully.
125
Why do you want to ensure that only the work required is done?
Prevents scope creep (uncontrolled changes in project scope).
126
Project influences
- Organizational process assets (OPAs)
- Enterprise environmental factors (EEFs)
127
Organizational Process Assets
Plans, processes, policies, procedures, and knowledge bases specific to and used by performing organization. Corporate knowledge base, historical info, lessons learned.
128
Enterprise Environmental Factor (EFF)
Conditions, not under control of the project team, that influence, constrain, or direct the project. EEFs considered inputs to most planning processes. ex: organizational culture, standards and regulations, infrastructure, HR
129
Scope creep
uncontrolled expansion to project or product scope without adjustments to time, cost, and resources. Scope creek not = changes in scope.
130
Where to find information about scope?
Project mgmt plan (risk, quality, stakeholder, communication plan)
- Project charter (high level description)
- EEFs (culture, personnel, infrastructure)
- OPA (policies and procedures, historical information, lessons learned).
131
Tools and techniques to plan scope management
- Expert Judgement: SMEs/consultant
- Data analysis: evaluate options in order to choose approach
- Meetings - develop and define scope.
- Decision making - how does team/organization make decisions (voting, meeting?)
- product analysis - Q&A to describe characteristics about what will be developed.
132
Requirements management plan
How requirements will be analyzed, documented, and managed throughout the project, includes process for: how to plan, track and report. configuration management activities, prioritization process, metrics and rationale.
133
Outputs of scope
- project scope statement
- project document updates (assumption log, requirements documentation, requirements traceability matrix, stakeholder register.
134
Project Scope Statement Definition
Describes, in as much detail, the project’s deliverables and the work required to create those deliverables and result in acceptance of the project.
- contains explicit exclusions (if any)
- live document
135
Assumption Log
Contains high level strategic and operational assumptions and constraints identified at the Business Case level. It is created at the same time as the Project Charter.
lower level ones are generated throughout the project.
136
Constraints
Anything that limits options; a restriction (internal or external) that can affect the performance of a project. (time, money and resources most common).
137
Assumptions
Factors that are considered true, real or certain without proof. Involve a degree of risk. Need plan to mitigate the risk.
138
Components of a project scope statement
- all info re: description, deliverables, acceptance criteria, exclusions.
Shared agreement amongst team and stakeholders.
139
Product scope description
characteristics of product, service or result. Concise description answering what, when, where, why and how of project. All components need to aligned with SMART goals
140
Deliverables
outputs of the project interim or final product, service or results. Reflect customer/stakeholder requirements, required quality level and results foreseen by organizations.
141
Acceptance Criteria
Process and criteria for accepting completed deliverables. Stakeholder's requirements for product/project. *Need acceptance criteria for each deliverable.
142
Project exclusions
What is excluded from the project (not in scope). Helps manage stakeholders expectations.
143
SMART goals
-Specific: focus on specific idea
-Measurable: Quantify how the idea can be measured
-Achievable - Defined so that idea can be achieved with current knowledge, skills and ability
-Realistic - Indicate what can be reasonable achieved, given available resources
-Time-Bound: detail when the result can be attained.
144
Scope validation
Formalized accpetance by customer in regards to deliverables. Reviewing deliverables to esnure completed as per requirements and obtain formal acceptance of delivables.
145
Quality control
Primarily concerned with correctness of the deliverables and meeting the quality requirements specified for the deliverables.
146
Inputs to validate scope
Project mgmt plan
Project docs - lessons learned, quality reports, RTM
Verified deliverables - completed and checked for correctness by the QC process
Work performance data - Degree of compliance with requirements.
147
Data vs information
Data: information in raw, unorganized form that refers to, or represent, conditions, ideas or objects.
Information: when data is processed, interpreted, or organized, make them more useful and meaningful.
148
Inspection
Measuring, examining, verifying to determine whether work and deliverables meet requirements and acceptance critieria. (product reviews, audit, walkthroughs)
149
Group decision-making techniques
Collectively decide.
Unanimity - all consent
Majority - >50% in favor of one group
Plurality - decision by largest block in a group decision (not majority but larger representation, a number greater than another.
150
WBS
tool used to map out decomposition of deliverables.
Organizes and defines total scope.
Each descending level represents increasingly detailed definition of work
151
Why use a WBS?
* Detailed illustration of scope
* Monitors Progress
* Creates an accurate cost and schedule estimation
* Builds project teams and sub-groups
* Establishes framework for managing the work to its completion
* Creates better communication to project sponsors, stakeholders, and team members
* Increases confidence that 100% of the work is identified and included
152
WBS supports PMs by
- separates project deliverables into component parts.
- method for managing complex projects
- framework for specifying performance objectives.
- Planning and supporting assignment of responsibilities.
- Determining resource requirements (technical skill, experience and knowledge)
- Facilitate reporting and analysis (resource allocation, cost estimate, expenditures, performance).
153
100% rule
100% of work needed to accomplish project must be included in the WBS. Captures all deliverables (Internal, external, and interim). Includes project management
154
PM in WBS
always include. only gets broken down if you are outsourcing any tasks.
155
How to build a WBS
Name of project at the top
- 2nd level = deliverables
- Create hierarchical code scheme for WBS starting from 1.0 (project title) 1.1... (deliverables) and another digit for components.
156
Work package
Decompose deliverables tot he level comfortably cost estimated and managed. AKA planned work.
Can be scheduled, cost-estimated, monitored and controlled. AKA activities/tasks
157
WBS development tools
- Outlines and org charts
- Fishbone diagrams
- brainstorming techniques
- top down and bottom up development strategies.
158
Decomposition
- identifying and analyzing deliverables and related work.
- structuring and organizing the WBS
- Decomposing upper WBS into lower level detailed components.
- Developing and assigning ID codes to WBS components.
- Verifying degree of decomposition.
159
8-80 Rule (8-80-10)
Reminder to limit the size of WBS work packages.
8 - 80hrs are right size. < 1 day is too granular, >2 weeks too long to manage properly.
160
Pareto principle
80/20 rule
80% of results/effects comes from 20% of work/causes. Focus on 20% of work that is most important (most productive and fruitful).
161
Just in Time
Means making "only what is needed, when it is needed, and in the amount needed".
162
Control account
mgmt control point of scope, cost, schedule integrated and compared to earned value for performance msmt.
Has 2 or more packages, through each work package.
163
WBS dictionary
Detailed description of work packages and control accounts.
Info about deliverable, activity, scheduling information.
164
WBS dictionary components
* Code of Account
* Description of Work
* Responsible Organization
* List of Schedule Milestones
* Associated Schedule Activities
* Resources Required
* Cost Estimates
* Quality Requirements
* Acceptance Criteria
* Technical References
* Contract Information
165
Problems from WBS defects
- Missed deadlines and extended schedule
- Over budget
- Unable to use new product or feature
- scope changed and is unmanageable
- ongoing project now, no end in sight
- Members confused about responsibilities
- planned work does not get done.
166
Integrated change process
1) Receive request
2) Evaluate how and when change may impact the project
3) Inform stakeholders of impact and receive approval
4) Authorize change and update related documents and work agreements
5) Communicate change to all parties
6) Close change request.
167
Change requests
Expand or reduce scope, modify policies/procedures, modify cost/budget, revise schedules.
168
Defect repair
Formally documented defect with a recommendation repair or place the component.
169
What project mgmt plans need to updated after change?
- Scope mgmt plan
- Scope baseline
- Schedule baseline
- Cost baseline
- Performance msmt baseline.
170
output of collecting requirements
Requirements documentation
Requirements traceability matrix
171
T/F Organization Process Assets are always an input to a process
True. These consist of plans, processes, policies and procedures specific to the internal organization.
172
T/F Stakeholder register is an output of collect requirements
False. It's an input.
173
T/F It is important to use expert judgement in creating WBS
True. Another term is subject matter experts who can provide lessons learned and experience to assist the Project Manager in decomposing the deliverables.
174
T/F A Requirements Traceability Matrix is the Output to Plan Scope.
False. It is an output to Collect Requirements
175
T/F Management Plan updates are the outputs of processes.
True. Updates to plans are always an output.
176
T/F When you Validate Scope you are not agreeing to changes to the scope.
False. During Validate Scope, you are formalizing acceptance of the completed project deliverables and the output can be authorized Change Requests
177
T/F Deliverables, Assumptions, Exclusions and Constraints are found in an output document to Plan Scope Management.
False. The elements described are a part of the Scope Statement; this is an output to Define Scope.
178
T/F Interviews are the best way to gather information about Control Scope
False. Interviews are a tool & technique of Collect Requirements.
