Udemy Course Terms Flashcards
Steering Commitee
helps choose the projects, goals, vision of the projects, priortizing between projects.
Transactional Leadership
Gives rewards to top performers and punishments the bottom performers.
Servant Leader
Focuses on the needs of the project team and people served. Makes certain that team members have what they need to get the work done.
Laissez-Faire Leadership
Hands off approach. Dont make decisions. Team is all self-led and on their own.
Transformational Leader
Inspiring and motivating. Tells team they can do more than you think possible, empowers team to get work done
Charasmatic Leader
Does the work with you. “Do as I do now”. Someone who is high energy and takes part in the activity
Interactional Leader
Hybrid type leadership between transactional, transformational, and charasmatic leader blended together
Positional Power
power due to position as PM
Informational Power
PM can control data gathering and distribution. All data goes through them, PM has control of data
Referent Power
Project Team or Stakeholders have workedwith PM in past. Respected due to past projects.
Situational Power
Due to certain situations (ie change in power or leadership, new person emerges with power)
Personal or Charasmatic Power
power due to being likeable or friendly
Reward Power
Team see the PM as someone who can reward them. Respect and behave to get award
Ingratiating power
Gain flavor through flattery. “You are so great, etc” False power, wears down over time
Pressure based Power
PM can restrict choices to get team to do the work “You have to do the 5 assignments by Friday”
Guilt-based Power
PM can make project team feel guilty in order to gain compliance, “I let you take off last Friday but now we’re really behind” hoping to get extra work done
Persuasive Power
PM has the ability to persuade the project team through Sales Pitch
Avoiding Power
refuses to act, get involved, or make decisions
Cognitive Level Integration
based on experience and maturity of PM. You have insight in project work and know what needs to be done (ie see problems coming, know how to fix)
Context-Level integration
How the project is managed by changing times (technology changes, environment changes, etc)
Benefits Measurement
Tool/technique to compare benefits among multiple projects to choose the project most valueable to the company
Benefits-Cost ratio (BCR)
ratio summarizing the relationship between the costs and benefits of a proposed project
BCR greater than 1.0 the project is expected to deliver a positive net present value to a firm and its investors. (Benefits greater than costs - B>C)
Scoring Model
Benefit Measuring Method (Choosing a project)
Break characteristics of project (cost, time, benefits, etc) into categories and give individual scores
Murder Board
PM, sponsor, etc (whoever is representing project) goes in front of group of executives who asks questions about the project and then determine if they want to invest or not. “Murder” or kill project in that room.
Payback Period
How long will it take to payback the investment for the project. If someone invests 100k and it takes 6 months before you break even, payback period is 6 month (time before creating ROI)
Future Value
Future value of money - What is your current money worth in the future
FV=PV(1+i)^n
i= interest rate
n=number of time periods (# of years)
Present Value
Present Value of money -
PV= FV/(1+i)^n
i= interest rate
n=number of time periods (# of years)
Net Present Value (NPV)
finds true value of a project. NPV greater than 0 is good
If you invested $80,000 in a project and 5 years later that project is worth $130,000, you need to find the present value (or orignal value) of that $130,000. It the present value of $130,000 when n=5 (assuming i=6%), than present value is $97,143.56. Therefore, NPV is $17,143.56 (97,143-80,000)
Internal Rate of Return
Present value equals cash inflow (money coming in)
IRR with higher values are good
Greater than zero means income (decent project selection)
Assumption Log
A document that has a record of all of your assumptions, but also has all of your constraints.
Kickoff Meeting
The purpose of the kickoff meeting is to ensure that everyone is aware of the project details and his or her role within the project
A kickoff meeting typically occurs at the end of the planning process, prior to beginning the project work.
What 3 documents make up the Scope Baseline
Scope Statement
WBS
WBS Dictionary
Requirements Traceability Matrix
Table where we track requirements throughout the project.
PMIS (Project Management Information Systems)
Typically one or more software applications for collecting and using information. Helps PM’s plan, execture, and close the project (ie Microsoft Project)
3 Types of Action in Execution
- Corrective Action
- Preventative Action
- Defect Repair
All 3 action require change requests
Corrective Action
In corrective action, you have found defects and you take action so the future products can be defect-free.
Realigns project back on track. “Current Results”
Preventative Action
Prevents future issues. Ensuring future performance. “Dont want to make the same mistake twice”
Defect Repair
Defect repair is about fixing the product. Modifies nonconformance to meet requirements again
Scope creep
refers to how a project’s requirements tend to increase over a project lifecycle, e.g. what once started out as a single deliverable becomes five. Approved changes by customer have increased project scope
Gold Plating
refers to the Project Team adding the extra features that were not part of the product scope. Adding scope above the baseline that customer may or may not be happy with.
Deliverables
Throughout your project, you’ll be creating things. Things that your project create are deliverables. Basically, anything that gives us product, result, or capability. An output of the work you do.
Example: In planning, we create a quality management plan, that is a deliverable. Customer never sees it, but the project still created it so it is a deliverable.
Configuration management
Managing the configuration of all products and assets in a project (to control multiple versions of a deliverable)
Examples: Blueprints, documents, plans revisions (Rev 1.1, Rev 3.4, etc) keep everyone on same page by controling all versions of documents/products.
Issue Log
An issue log is a simple list or spreadsheet that helps managers track the issues that arise in a project and prioritize a response to them
Two types of Project Knowlege
Explicit and Tacit
Explicit Knowledge
knowledge that can easily be communicated through conversations, documention, etc.
“To use this equipment, you have to hit this button and this button to turn it on” or “There’s 10 boxes on the left side of warehouse when you first walk in, grab those”.
In short, easily to expain.
Tacit Knowledge
More difficult to explain. Its the knowledge that comes from years of experience and doing the same task over and over.
Reverse Shadowing
Opposite of shadowing, the “expert follows you”
Alternative Analysis
Corrective and preventative actions to fix problems and to prevent problems. “What are my alteratives? What are the different solutions I can use to fix this?”
Cost Benefit Analysis
cost of the proposed corrective actions compared the the benefits it brings. “Its going to cost us $1200 to fix this issue. What benefits will it bring to fix it? Should we just keep it, is it worth fixing”
Earned Value Analysis
A suite of formulas that helps show project performance. Formulas to show how healthy the project is.
Root Cause
Not looking to treat the symptoms, looking to treat the cause.
Example - You have a runny nose. Blowing nose or wiping nose is symptom. Having an allergy or cold is the cause.
Causal Analysis
What is actual causing an issue? Looking for causal factors contribuiting to the effect
Trend analysis
Finding a trend (recurring problems, threats, opportunities)
Variance analysis
Difference between what was planned and what was experienced (Cost variance, schedule variance, etc)
Helps us find root cause
Autocratic decision making
One person decides
Requirements Management Plan
How you will plan, track, and report progress on requirements
Product Scope vs Project Scope
Product Scope - Features and Functions - A way to describe things or characteristics or usability customer will receive as a result of the project.
Project Scope - The work completed to create product.
Business Analyst
Individual who can gather requirements, package them, and define what the project scope will be.
PM vs Business Analyst Relationship
Collaborative Partnership- Business Analyst has requirement responsibilities and PM has project delivery responsibilities.
Affinity Diagram
Similar to brainstorming but we group ideas into clusters. Each of those can be broken down again to analyze each subset. Logically structured into groups
Mind mapping
A way to brainstorm ideas and helps generate ideas. A way to visualize ideas.
Not very logically structured, all over the place
Nominal Group technique
Nominal Group technique is a way for the group to sort of anomonsly rank requirements.
1)Each participant individually brainstorms the problem or opportunity with their ideas
2)The facilitator will add all ideas to a white board
3)The ideas are all discussed so everyone clearly understands the ideas
4)Then privately vote on each idea from 1 to 5.
Whichever requirements get highest score and highest ranked on requirements list
Context Diagram
Shows the flow of data through a system or flow of a process through the system.
Requirements Traceability Matrix
document which defines the requirements, status of each requirements, details of each requirement. (Table tracking or tracing all requirements and its status)
Project Scope Statement
The actual document that defines the project scope. Detailed desciption of the product and project scope.
Create a WBS from Scope Statement
Validate Scope
Customer inspects the project deliverables (ie. walkthrough of new house). Typically done at end of each phase and at completion of project.
Quality Control vs Validate Scope
Quality refers to the PM or project team inspecting the work before the customer sees it.
Scope validation is when customer inspects to provide approval.
Both inspections driven processes, but quality is an internal inspection.
Rolling Wave Planning
Planning in adaptive environment (activities added to backlog for next iteration and then you complete). “Plan then do, plan then do”
Delivers incremental value (complete in iterations)
Each wave is an iteration (2-4 weeks)
Lean Manufacturing
We have backlog of assignments and then as team members become available, it goes to next available team member.
Not as much planning as we dont decide which team member does what, we just assign next project in line to next available team member
Theory of Constraints
Examine the most limiting factor in our processs and we then improve that trait to where its no longer our most limiting factor.
8/80 rule
Each work package should take between 8 hours and 80 hours. Anything smaller than 8 hours is too granular. More than 80 hours needs to be broken down further.
Milestone Chart
A way to visualize when milestones are planned and when you actually hit the milestone.
Mandatory dependencies - Hard Logic
Activities that must follow a particular order
Have to have a foundation before you can frame house
Discrentionary dependencies (Soft Logic)
You can change the order and it would still work
You should paint before you replace carpet, but you can replace carpet and then paint after if you needed to
External dependencies
external constraints (vendors/inspectors - very little control over them) (Cant start building until inspector improves foundation)
Internal dependencies
A type of hard logic (No external factors - Team member B cant start work until team member A is done his part)
The precedence diagram method (PDM)
A tool for scheduling activities in a project plan. Successors and Predessesors
Network Diagram
A way to visualize the project work and sequence activities
Activity-on-node (AON)
Network Diagram a precedence diagramming method which uses boxes to denote schedule activities
Lead time
negative time (accelerated time -allows activies to overlap)
Lag time
positive time (waiting time - moves activities further apart)
Ex. Waiting for concrete to dry
Law of Diminishing returns
You can only get so much return when one factor remains the same
(ie. Wheat Field - Theres only so much wheat in the field. Just because you add more people, more machines, etc, doesnt mean you’ll get more wheat. You might get it faster, but theres still only so much wheat)
Parkinson’s Law/Student syndrome
Work will expand to fill the time alotted to it
Analogous Estimating
Creating an analogy between projects (similiar project work and comparing to current work). Also called Topdown estiimating
Fast but least reliable
Example:
Project A took 6 months to complete. Project B is similiar, just a little larger, so I estimate it will take 8 months
Parametric Estimate
Uses parameters for estimating. Used for repetitive work when a learning curve is involved.
Examples: It takes 2 hours to install each light fixture. 100 fixtures will take 200 minutes.
Duration vs Effort (not the same)
Duration is how long the activity will take.
Effort is the billable time for the labor.
Three-Point Estimating
ind the average of the three following:
1) Optimistic
2) Most likely
3) Pessimistic
(O+ML+P)/3 = Estimate
PERT Estimates
(Also Three-Point Technique but weighted towards most likely)
Formula is (O+ (4ML) +P)/6= Estimate
Bottom Up estimating
Starting at bottom and accounting for all time (or costs) in WBS. Add up all very detailed activities on WBS
Have to have WBS to use bottom up estimating.
Takes longest to estimate durations with this method, but it is the most reliable.
Two types of reserves
Management Reserves and Contigency Reserves
Contingency Reserve
Usually associated with money. For risk events that disrupt project. Known/unknowns. Controlled by PM