Sunday, May 25, 2014

9) HUMAN RESOURCE Management

 |  HUMAN RESOURCE Management

Sexism, racism or other discrimination should never be tolerated, no matter what the circumstances. You must separate your team from discriminatory practices, even if those practices are normal in the country where you’re working.

Project Human Resource Management PITTOs:

Processes
Inputs
Tools & Techniques
Output
Plan Human Resource Management
PM Plan
Activity Resource Requirements
Enterprise Environment Factors
Organization Process Assets
Organization Charts and Position Description
Networking
Organization Theory
Expert
Judgment
Meetings
Human Resource Management Plan
Acquire Project Team
Human Resource Management Plan
Enterprise Environment Factors
Organization Process Assets
Pre-assignment
Negotiation Acquisition
Virtual Teams
Multi-criteria Decision Analysis
Project Staff Assignments
Resource Calendars
PM Plan Updates
Develop Project Team
Human Resource Management Plan
Project Staff Assignments
Resource Calendars
Interpersonal Skills
Training
Team-building Activities
Ground Rules
Co-location
Recognition and Rewards
Personnel Assessment Tools
Team Performance Assessment
EEF updates
Manage Project Team
Human Resource Management Plan
Project Staff Assignments
Team Performance Assessments
Issue Log
Work Performance Reports
Organization Process Assets
Observation and Conversation
Project Performance Appraisals
Conflict Managements
Interpersonal Skills
Change Requests
PM Plan Updates
Project Document Updates
EEF Updates
OPA Updates

Plan Human Resource Management

  • plan to organize and lead the project team
  • include roles and responsibilities (identify resources that can take up the responsibilities) as documented (ownership of deliverables) in RAM in the form of RACI chart (matrix) or in a chart/text form, org charts - an organizational breakdown structure (OBS) and staffing management plan – staff acquisition, release, resource calendar, resource histogram, training, rewards, compliance & safety requirements
  • The OBS displays organizational relationships and then uses them for assigning work to resources in a project (WBS)
  • networking is useful in understanding skills of individuals and the political and interpersonal factors within the organization
  • org chart indicated the reporting structure of the project

What is a RACI chart / RACI matrix or RACI graph?

  • The four letters of RACI stands for:
    • Responsible – Which project member is responsible for carrying out the execution of the task?
    • Accountable – The Project member who is held accountable for the tasks and be given the authority to make decisions? In general, there should only be 1 member accountable for the project task.
    • Consulted – The stakeholders that should be consulted for the work or be included in the decision making (to be engaged in two-way communication).
    • Informed – Who should be informed of the decisions or progresses of the work by means of email updates, progress reports, etc. (one-way communication)?
  • The RACI chart is a tool for tracking the tools for tracking the roles and responsibilities of project members for specific project tasks during project execution.
  • While there can be unlimited number of members responsible for the execution of a project task, there should only be one member accountable for the same task. Fixing the accountability to a single person will allow the project team members to know which person to go to should they need to know the progresses or details of the task. This can also avoid the false assumption that the other person (if there are more than one accountable) accountable for the task has taken care of the task but in the end no one has looked after the task.
  • The member responsible and accountable can be the same for small tasks.
  • Below is an example of the RACI chart for a website project:
Project Manager
Graphic Designer
Copywriter
Coder
Logo Design
A
R
C
Web Copy
C
A R
Web Coding
A
 C
R

Acquire Project Team

  • to acquire the final project team
  • pre-assignment is the selection of certain team members in advance
  • acquisition is to acquire resources from outside through hiring consultants or subcontracting
  • includes bringing on contractors / consultants
  • halo effect: a cognitive bias (if he is good at one thing, he will be good at everything)
  • Multi-criteria Decision Analysis: to select team members based on a no. of factors: availability, cost, experience, ability, knowledge, skills, attitude, etc.
  • training is usually paid for by the organization, not project

Develop Project Team

  • enhancing and improving overall team performance
  • offer feedback, support, engage team members, manage conflicts, facilitate cooperation
  • cross-train people
  • team performance assessments : assess team performance as a whole vs project performance appraisals: individual performance
  • training cost can be set within the project budget or supported by the organization
  • PM Authority: legitimate (assigned in project charter), reward, penalty, expert (need to be earned), referent (charisma and likable, or ally with people with higher power), representative (elected as representative)
  • Expert > Reward are best forms of power. Penalty is worst.
  • Tuckman Model: Forming – Stroming – Norming – Performing – Adjourning
  • cultural difference should be considered when determining award and recognition
  • recognition should focus on win-win reward for the team (NOT competitive-based)
  • team building is important throughout the whole project period
  • Motivational Theories
    • Maslow’s Hierarchy of Needs – personal needs (psychological > Security > Social > Esteem > Self Actualization)
    • Herzberg’s Hygiene Theory – satisfaction (motivators) vs dissatisfaction (hygiene factors to avoid dissatisfaction but do not provide satisfaction, also called KITA factors e.g. incentives/punishments), hygiene factors include good working conditions, a satisfying personal life, and good relations with the boss and coworkers
    • Expectancy Theory – Expectancy (extra work will be rewarded) Instrumentality (good results will be rewarded) Valence (the individual’s expected reward), for a person to be motivated, efforts/performance/outcome must be matched – will only work hard for achievable goals
    • Achievement Theory – three motivation needs: achievement (nAch), power (nPow), affiliation (nAff), best is a balanced style for the PM
    • Contingency Theory – task-oriented/relationship-oriented with stress level (high stress -> task-oriented better)
  • Leadership Theory
    • including: analytical (with expertise), autocratic (with power), bureaucratic, charismatic, consultative, driver (micromanagement), influencing, laissez-faire (stay out)
    • Theory X – assumes employees are lazy and avoid work, need incentive/threats/close supervising
    • Theory Y – assumes employees may be ambitious and self-motivated, will perform given the right conditions
    • Theory Z – (japanese) increasing loyalty by providing job for life with focus on well-being of employee (on and off job), produces high productivity and morale
    • Situational Continuum Leadership – directing/telling > coaching/selling (manager define the work) > supporting/participating (subordinate define the work) > delegating according to maturity/capability of the subordinate

Manage Project Team

  • track team member performance, provide feedback, resolve issues
  • when managed properly, differences of opinion can lead to increased creativity and better decision making
  • issue log is fed from Manage Stakeholder Engagement – used to understand who is responsible for resolving specific issues
  • conflict management: conflicts force a search for alternatives, need openness, not personal, focus on present and future
  • conflicts: schedule, project priority, resources, technical opinions, administrative overhead (too much administration work), cost, personality
  • conflict resolution
    • collaborate/problem solve[confrontation of problem] (best)
    • compromise/reconcile (give-and-take, temporary/partially resolve)
    • force/direct (worst/short-lived)
    • smooth/accommodate (emphasis common grounds and avoid/touch lightly the disagreements for harmony/relationship)
    • withdraw/avoid (other leads to lose-lose)
  • compromise is lose-lose
  • Forcing would only provide a temporary solution
  • Award decisions are made during the process of project performance appraisals
  • monitoring and controlling is typically performed by functional managers/HR for functional org

8) QUALITY Management

 |  QUALITY Management
  • everyone in the organization is responsible for the quality (project team for destined parts while PM for project quality), PM is ultimately responsible for the project quality
  • prevention over inspection
  • outliers are singular measurements outside the control limits
  • continuous improvement to ensure quality (quality assurance)
  • some costs of quality will be borne by the organization (organization quality policy, e.g. quality audit, ISO accreditation)
  • Quality: the degree to which a set of inherent characteristics fulfills requirements, decrease rework/costs, increase productivity/stakeholder satisfaction
  • under ‘control’: the process is predictable and repeatable
  • PM: perform continuous improvement activities (quality assurance), verify quality before completion of deliverables (control quality)
  • Grade (fit for use or not) vs Quality (conformance to stated requirements)
  • Accuracy (correctness) vs Precision (consistence, how closely conforms to target, standard deviation is a measure of precision, smaller standard deviation higher precision)
  • Quality Management Concepts
    • Crosby Zero Defects: identify processes to remove defects, quality is built in to the processes
    • Juran Fitness for Use: does the product/service meet customer’s need? i) Grade, ii) Quality conformance, iii) Reliability/maintainability, iv) Safety, v) Actual Use
    • W. Edwards Deming: 85% of quality problem is managers’  responsibility, develop “System of Profound Knowledge” [system = components working together to achieve an aim] i) Appreciation for system, ii) Knowledge about variation (special cause vs common cause) , iii) Theory of Knowledge (built up by prediction/observation/adjustment) , iv) Psychology
    • Six Sigma: achieve 3.4/1 mil defect level (99.999%) using DMAIC (Define, Measure, Analyze, Implement, Control) or [Design for Six Sigma] DMADV (Define, Measure, Analyze, Design, Validate) approach, refine the process to get rid of human error and outside influences with precise measurements, variations are random in nature
    • Just In Time: eliminate buildup of inventory
    • Total Quality Management (TQM): ISO 8402 all members to center on quality to drive customer satisfaction , refine the process of producing the product
    • Kaizen改善: implement consistent and incremental improvement, to reduce costs, cycle time, drive customer satisfaction using PDCA (Plan Do Check Act)
    • The Plan-Do-Check-Act cycle is a way of making small improvements and testing their impact before you make a change to the process as a whole. It comes from W. Edwards Deming’s work in process improvement, which popularized the cycle that was originally invented by Walter Shewhart in the 1930s.
    • Capability Maturity Model Integration (CMMI): improve overall software quality (design, development and deployment)
    • ISO9000: ensures the defined processes are performed in accordance to the plan
  • Quality Management processes are so focused on reviewing EVERY deliverable – not just the final product, but all of the components, designs and specifications too.
Project Quality Management PITTOs:

Processes
Inputs
Tools & Techniques
Output
Plan Quality Management
Project Management Plan
Stakeholder Register
Risk Register
Requirements Documentation
Enterprise Environment Factors
Organization Process Assets
Cost-benefit Analysis
Cost of Quality
Seven Basic Quality Tools
Benchmarking
Design of Experiments
Statistical Sampling
Additional Quality Planning Tools
Meetings
Quality Management Plan
Process Improvement Plan
Quality Metrics
Quality Checklists
Project Document Updates
Perform Quality Assurance
Quality Management Plan
Process Improvement Plan
Quality Metrics
Quality Control Measurements
Project Documents
Quality Management and Control Tools
Quality Audits
Process Analysis
Change Requests
PM Plan Updates
Project Document Updates
Organization Process Assets Updates
Control Quality
Quality Management Plan
Quality Metrics
Quality Checklists
Work Performance Data
Approved Change Requests
Deliverables
Project Documents
Organization Process Assets
Seven Basic Quality Tools
Statistical Sampling
Inspection
Approved Change Requests Review
Verified Deliverables
Change Requests
Validated Change
Quality Control Measurements
Work Performance Info
PM Plan Updates
Project Document Updates
Organization Process Assets Updates
Plan Quality Management
  • quality policy (either organizational or just for the project), methods and procedures to meet the objectives and satisfy customer’s needs
  • identify the quality requirements and document how to achieve
  • Cost-benefit Analysis: cost of implementing quality requirements against benefits
  • Cost of Quality: lowest quality cost is prevention, highest quality cost (poor quality) is rework and defect repair (as high as 5000 times the cost for carrying out unit testing), lost reputation and sales, failure cost may be internal/external (found by customer)
  • Warranty claims are external cost of quality
  • Cost of Quality is the total cost of quality efforts throughout the product’s lifecycle
  • cost of conformance (prevention cost, appraisal cost) vs cost of non-conformance (failure cost [internal/external])
  • internal/external is reference to the project (not the organization)
  • Poka Yoke (mistake proofing), Zero Quality Control (100% source inspection), Voice of Customer and FEMA (Failure Modes of Effects Analysis) are planning tools for quality management
  • Quality Metrics: function points, MTBF (mean time between failure), MTTR (mean time to repair)
  • Marginal Analysis: ROI of quality measures
  • 7 Basic Quality Tools
    • Cause-and-effect / Ishikawa / Fishbone Diagram: for identifying the cause
    • Flowchart: (e.g. SIPOC diagram) for identifying failing process steps and process improvement opportunities
    • Check Sheets (tally sheets): collecting data/documenting steps for defeat analysis
    • Histograms: does not consider the influence of time on the variation that exits within a distribution
    • Pareto Chart: based on 80/20 principle, a prioritization tool to identify critical issues in descending order of frequency, sort of a histogram
    • Statistical Process Control (SPC) Chart: determine if a process is stable/predictable using statistical sampling (assessed by accuracy[conformance] and precision[standard deviation]), identity the internally computed control limits (UCL/LCL) and specification limits (USL/LSL) by the customer/PM
    • run chart is similar to control chart, but without the control
    • usually +-3sigma i.e. a range of 6 sigma
    • a form of time series
    • if a process is within control limit but beyond specification limit, the process is experiencing common cause variation (random) that cannot be corrected by the system, management help is needed (special cause can be tackled but NOT common cause)
    • Stability Analysis / Zone Test: rule of seven (7 consecutive on either side of the mean = out of control), rule of six (six consecutive with a trend = out of control), rule of ten (10 as a saw-tooth pattern around the mean), rule of one (1 point beyond control limit) [signal in the noise]
    • Scatter Diagram: for trending, a form of regression analysis
  • Benchmarking: compare to past activities/standard/competition
  • Design of Experiments (DOE): change several factors at a time for each experiment, to determine testing approaches and their impact on cost of quality
  • Additional Quality Planning Tools
  • Loss Function: a financial measure of the user’s dissatisfaction with product performance
  • Matrix Diagrams: House of Quality (HOQ) used in Quality Function Deployment (QFD) (method to transform user demands [VOC]  into design quality)
  • Kano Model: differentiate features as satisfy, delight or dissatisfy
  • Marginal Analysis: cost-benefits analysis
  • Force Field Analysis (FFA): reviews any proposed action with proactive and opposing forces
  • Process Improvement Plan: process boundaries, configuration, process metrics/efficiencies, targets for improved performance
  • Quality Checklists: checklist to verify a series of steps have been performed
  • The goal is to refine the process so that human errors and outside influences no longer exist, and any remaining variations are completely random
Perform Quality Assurance
  • in the Executing Process Group
  • ensures the quality standards are being followed, to ensure unfinished works would meet the quality requirements
  • by quality assurance department or sponsor/customer not actively involved in the project
  • primarily concerned with overall process improvement for activities and processes (rather than the deliverable)
  • utilize the data collected in Control Quality Process
  • Quality Management Tools
    • Affinity Diagrams: like a mind-mapping diagram, organize thoughts on how to solve problems
    • Process Decision Program Charts (PDPC): defines a goal and the steps involved, useful for contingency planning
    • Interrelationship Digraphs: maps cause-and-effect relationships for problems with multiple variables/outcomes
    • Tree Diagrams
    • Prioritization Matrices: define issues and alternatives that need to be prioritized for decision, items are given a priority score through brainstorming
    • Activity Network Diagrams
    • Matrix Diagrams: e.g. ‘house of quality’ in QFD
    • Kaizen改善, Kanben看板: quality assurance methods developed by Japanese
  • Quality Audit: to verify quality of processes, to seek improvement, identify best practices, reduce overall cost of quality, confirm implementation of approved changes, need quality documentations
  • Quality Review: to review the quality management plan
  • change requests are mostly procedural changes
Control Quality
  • verify the deliverables against customer’s specifications to ensure customer satisfaction
  • validate the changes against the original approved change requests
  • conditional probability (events somewhat related) vs statistical independence (events not interrelated) vs mutual exclusivity
  • statistical sampling for control quality
  • variable (continuous) data: measurements, can do maths on e.g. average
  • attribute (discrete) data: yes/no, no.123, just an identifier, can’t do maths on
  • QC includes the PM process (lesson learnt, budget, scope)
  • tolerance (spec limits, deliverables acceptable) vs control limits (process acceptable)
  • if within control limit but outside tolerance: rework the process to give better precision
  • all control and execution processes may generate lesson learned

7) COST Management

  |   COST Management
  • sunk cost – cost already incurred in the past and cannot be recovered, do not consider anymore
  • opportunity cost – difference in value between one path vs alternative (= 100% of value of next best alternative)
  • value analysis/ engineering – cost reduction without affecting the scope
  • Benefit Cost Analysis (BCA) / Cost Benefit Analysis (CBA) – determine feasibility, bigger benefit/cost ratio (BCR)
  • Payback Period – the length of time to recover the investment
  • Return on Investment (ROI) – the efficiency of investment = (Gain-Cost)/Cost
  • Time Value of Money – Present Value (PV) = value / (1+interest rate)*year, Future Value (FV) = value * (1+interest rate)*year
  • Net Present Value (NPV) = PV of cash inflows – PV of cash outflows (cost)
  • funding for project: self-fund, funding with equity, funding with debts
  • discount rate - rate used to calculate present value of expected yearly benefits and costs
Project Cost Management PITTOs:

Processes
Inputs
Tools & Techniques
Output
Plan Cost Management
Project Management Plan
Project Charter
Enterprise Environment Factors
Organization Process Assets
Expert Judgment
Analytical Techniques
Meetings
Cost Management Plan
Estimate Costs
Cost Management Plan
Human Resource Management Plan
Scope Baseline
Project Schedule
Risk Register
Enterprise Environment Factors
Organization Process Assets
Expert Judgment
Analogous Estimating
Parametric Estimating
Three Point Estimates
Reserve Analysis
Cost of Quality
Project Management Software
Vendor Bid Analysis
Group Decision Making Techniques
Activity Cost Estimates
Basis of Estimates
Project Document Updates
Determine Budget
Cost Management Plan
Scope Baseline
Activity Cost Estimates
Basis of Estimates
Project Schedule
Resource Calendars
Risk Register
Agreements
Organization Process Assets
Cost Aggregation
Reserve Analysis
Historical Relationships
Funding Limit Reconciliation
Expert Judgment
Cost Baseline
Project Funding Requirements
Project Document Updates
Control Costs
Project Management Plan
Project Funding Requirements
Work Performance Data
Organization Process Assets
Earned Value Management
Forecasting
To Complete Performance Index (TCPI)
Performance Reviews
Project Management Software
Reserve Analysis
Cost Forecasts
Change Requests
Work Performance Info
Organization Process Assets Updates
PM Plan Updates
Project Document Updates
Plan Cost Management
  • The Cost Management Plan establishes: i) level of accuracy and level of precision, ii) unit of measurement, iii) WBS procedure links (to control account (CA)), iv) control threshold, v) earned value rules of performance, reporting, funding and processes
  • Life cycle costing = total cost of ownership : production cost, running and maintenance cost, etc.
Estimate Costs
  • similar to Estimate Activity Resources
  • look for ways to reduce cost
  • ensure the SME to deliver the estimates (more accurate)
  • based on WBS
  • Cost Types
    • Variable costs - costs change with the amount of work, e.g. hourly consultants
    • Fixed costs - costs that are constant, e.g. equipment leases
    • Direct costs – directly attributed to the project
    • Indirect costs – shared costs like AC, lighting, etc.
  • Cost Estimate Tools
    • Analogous Estimating (Top Down Estimate) – compare to a similar project in the past (an estimating heuristic/rule of thumb)
    • Parametric Estimating – use a parameter and repetitive units of identical work
    • Bottom-up Estimating – detailed estimates of each individual activity from historical data, more accurate and time-consuming
  • Activity Cost Estimates may include indirect cost and contingency reserves
  • usually in a range of values
  • Basis of Estimates - detailed analysis on how the cost estimate was derived (assumptions, constraints, possible range (+/-15%), confidence level of final estimate)
Determine Budget
  • Budget is more about when to spend money
  • Historical Relationships - analogous/parametric estimation
  • Reserve Analysis – addresses Management Reserve (unknown unknowns) and Contingency Reserve (known risks) [not included in calculation of earned value management]
  • Funding Limit Reconciliation – addresses variance between funding limit (e.g. monthly or yearly limit) and planned expenditure, may require rescheduling of work to level of the rate of expenditure
  • Value Engineering – to improve quality/shorten schedule without affecting the scope
  • Project Budget = Cost baseline (the approved time-phased budget) + Management Reserve
  • when management reserve is used during project execution, the amount is added to the cost baseline
  • S-curve : total project expenditure over project lifecycle
Control Costs
  • Check against the Project Funding Requirements
  • including informing stakeholders of all approved changes and their costs
  • Earned Value Calculation
    • Index > 1: under budget/ahead of schedule
    • Index < 1: over budget/behind schedule
  • Estimate at Complete: 1) new estimate required (original flawed), 2) no BAC variance, 3) CPI will continue, 4) sub-standard cost/schedule will continue
  • TCPI: >1 not enough funding remain (over budget), <1 more fund available than needed (under budget)
  • Earned Value Accrual
    • Discrete Efforts – describes activities that can be planned/measured for output, including Fixed Formula (activity given a % of budget of work package at start and earn the remaining when completed, e.g. 50/50, 20/80 or 0/100), Weighted Milestone (earn value for milestones of deliverables of the work package), Percentage Complete, Physical Measurement 
    • Apportioned Efforts – describes work that has a direct/supporting relationship to discrete work, e.g. testing, pm activities, calculated as % of the discrete work
    • Level of Efforts (LOE) – describes activities without deliverables, e.g. troubleshooting, assigned the earned value as scheduled, without schedule variance but may have cost variance
  • e.g. perform Control Cost weekly during execution where money is spent fastest
  • Variance Analysis – to check against the baseline for any variance
  • SPI at end of project must be 1
  • SPI is NOT telling much information to whether the project is on schedule as the Critical Path must also be investigated to get a meaningful picture