Sunday, May 25, 2014

6) TIME Management

 |  TIME Management

Project Time Management PITTOs:

Processes
Inputs
Tools & Techniques
Output
Plan Schedule Management
Project Management Plan
Project Charter
Enterprise Environment Factors
Organization Process Assets
Expert Judgment
Analytical Techniques
Meetings
Schedule Management Plan
Define Activities
Schedule Management Plan
Scope Baseline
Enterprise Environment Factors
Organization Process Assets
Expert Judgment
Decomposition
Rolling Wave Planning
Activity List
Activity Attributes
Milestone List
Sequence Activities
Schedule Management Plan
Activity List
Activity Attributes
Milestone List
Project Scope Statement
Enterprise Environment Factors
Organization Process Assets
PDM
Dependency Determination
Applying Leads and Lags
Project Schedule Network Diagram
Project Document Updates
Estimate Activity Resources
Schedule Management Plan
Activity List
Activity Attributes
Resource Calendars
Activity Cost Estimates
Risk Register
Enterprise Environment Factors
Organization Process Assets
Expert Judgment
Alternatives Analysis
Published Estimating Data
Bottom-up Estimating
PM Software
Activity Resource Requirements
Resource Breakdown Structure
Project Document Updates
Estimate Activity Durations
Schedule Management Plan
Activity List
Activity Attributes
Activity Resource Requirements
Resource Breakdown Structure
Resource Calendars
Project Scope Statement
Risk Register
Enterprise Environment Factors
Organization Process Assets
Expert Judgment
Analogous Estimating
Parametric Estimating
Three Point Estimates
Group Decision Making Technique
Reserve Analysis
Activity Duration Estimates
Project Document Updates
Develop Schedule
Schedule Management Plan
Activity List
Activity Attributes
Activity Resource Requirements
Activity Duration Estimates
Project Schedule Network Diagram
Resource Breakdown Structure
Resource Calendars
Project Scope Statement
Risk Register
Project Staff Assignments
Enterprise Environment Factors
Organization Process Assets
Schedule Network Analysis
Critical Path Method
Critical Chain Method
Resource Optimization Techniques
Modeling Techniques
Leads and Lags
Schedule Compression
Scheduling Tools
Schedule Baseline
Project Schedule
Schedule Data
Project Calendars
PM Plan Updates
Control Schedule
Project Management Plan
Project Schedule
Work Performance Data
Project Calendars
Schedule Data
Organization Process Assets
Performance Reviews
Project Management Software
Resource Optimization Technique
Modeling Techniques
Leads and Lags
Schedule Compression
Scheduling Tools
Schedule Forecasts
Work Performance Info
Change Requests
PM Plan Update
Project Document Update
Organization Process Assets Update
Plan Schedule Management
  • define policies, procedures and documentation for managing and controlling project schedule
  • including scheduling methodology, tools, level of accuracy, control thresholds (limit beyond which preventive/corrective actions needed), rules of performance measurement (e.g. earned value)
  • lead and lags are NOT schedule constraints
Define Activities
  • the scope baseline is used here as it represents the approved (stable) scope
  • further decompose work packages into activities for more detailed and accurate estimations
  • ‘activities’ is the PMI terminology for ‘tasks’ and ‘work efforts’
  • activity is more related to the actual work/process to produce the deliverables
  • activity types: level of efforts (support, measured in time period), discrete efforts or apportioned effort (in direct proportion to another discrete effort)
  • activities have durations while milestones do not (zero duration)
Sequence Activities
  • WBS is no longer needed, so the Project Scope Statement is the input rather than scope baseline
  • Precedence Diagramming Method (PDM) to diagram dependencies
  • Network Diagramming Tools are software tools that graphically represent activity sequences
  • network diagrams: shows dependencies, duration, workflow, helps identifying critical paths
  • precedence relationships (also known as ‘activity on node (AON)‘ approach): finish-to-start (~95%), start-to-start, finish-to-finish, start-to-finish (least)
  • Activity on Arrow (AOA) or Arrow Diagramming Method (ADM) activities are represented as arrows, dashed arrows represent dummy activities (duration: 0) that shows dependencies
  • Graphical Evaluation and Review Technique (GERT) allows for conditional branching and loops
  • Network Dependency Types (to be determined during Sequence Activities Process):
    • Mandatory Dependency (hard logic): A must be completed before B begins/ technical dependencies may not be hard
    • Discretionary Dependency (preferred, soft logic): sequence preferred by the organization, may be removed should fast-tracking is required
    • External Dependency: dependency required by external organization
    • Internal Dependency: precedence relationship usually within the project team’s control
  • Milestones: the completion of a key deliverable/a phase in the project, as checkpoints/summary for progress, often used in funding vendor activities
  • Milestone list is part of i) project plan, ii) project scope statement, iii) WBS dictionary
  • Leads: begin successor activity before end of predecessor, for schedule compression (fast tracking) (negative lags)
  • Lags: imposed delay to successor activity, e.g. wait 2 weeks for concrete to cure (FS +14 days)
  • Network Diagram Setup : 7-box method, usually using software tools or 5-box method
  • if the ES and LS are identical, the activity is on the critical path
Estimate Activity Resources
  • closely related to Estimate Cost Process (in Cost Management)
  • resource calendar spells out the availability of resources (internal/external) during the project period
  • matches human resources to activities (as human resources will affect duration)
  • effort (man day, work week, etc.) vs duration vs time lapsed (total time needed, including holidays, time off)
  • alternative analysis includes make-or-buy decisions, different tools, different skills, etc.
  • Activity Resource Requirements may include the basis of estimation
Estimate Activity Durations
  • consults SME (subject matter experts, i.e. the one carrying out the actual work) to come with with the estimation, not on the PM’s own
  • Analogous Estimating: based on previous activity with similar nature (a form of expert judgement), used when little is known or very similar scope, works well when project is small, NOT ACCURATE
  • Parametric Estimating: based on some parameters, e.g. the time for producing 1000 component based on that for 1 component * 1000, use an algorithm based on historical data, accuracy depends on the parameters selected, can be used on [a portion of / the entire] project
  • One-Point Estimating: based on expert judgement, but highly unreliable
  • Three-Point Estimating: best (optimistic), most likely (realistic), worst (pessimistic) cases, Triangular Distribution vs PERT (Project Evaluation and Review Techniques, Beta Distribution, weighted average using statistical methods [most likely * 4 - 95% confidence level with 2 sigma]), triangular distribution (non-weighted average of three data points), uncertainties are accounted for
  • In real world applications, the PERT estimate is processed using Monte Carlo analysis, tie specific confidence factors to the PERT estimate
  • Bottom-Up Estimating: a detailed estimate by decomposing the tasks and derive the estimates based on reliable historical values, most accurate but time-consuming
  • Heuristics: use rule of thumb for estimating
  • standard deviation (sigma value, deviation from mean, to specify the precision of measurement): 1 sigma: 68%, 2 sigma 95%, 3 sigma 99.7%, 6 sigma 99.99%
  • accuracy is the conformance to target value
  • contingency reserve: for known unknowns, owned by PM, may be updated, part of schedule baseline
  • management reserve: for unknown unknowns, owned by management, included in overall schedule requirements
  • update to documents: basis of estimates, assumptions and contingencies
  • activity duration estimate may be in a range, don’t include lags
Develop Schedule
  • the schedule baseline is the approved and signed version of project schedule that is incorporated into the PM plan
  • the schedule is calendar-based taking into accounts holidays/resource availability/vacations
  • vs the time estimate (work effort/level of effort) just describes the man hours / man days
  • Slack/Float: activities that can be delayed without impacting the schedule
  • Free slack/float: time an activity can be delayed without delaying the Early Start of the successor
  • Total slack/float: time an activity can be delayed from early start without delaying the project end date (scheduling flexibility), can be negative, 0 (on the critical path) or positive
  • Project Float: without affecting another project
  • Negative float: problem with schedule, need schedule rework
  • Project slack/float: time the project can be delayed without delaying another project
    • Early Start (ES) – earliest time to start the activity
    • Late Start (LS) – latest time to start without impacting the late finish
    • Early Finish (EF) – earliest time to end the activity
    • Late Finish (LF) – latest time to finish without impacting successor activity
    • Slack/Float = LS – ES or LF – EF
    • The float is the highest single value along the critical path, NOT the sum of them
  • Critical Path: the longest path that amount to shortest possible completion time (usually zero float, activities with mandatory dependency with finish-to-start relationship), can have more than 1 critical paths (more risks), critical paths may change (keep an eye on near-critical paths)
  • activities on the critical path are called critical activities
  • Path with negative float = behind schedule, need compression to eliminate negative float
  • Forward Pass : compute the early start
  • Backward Pass : compute the late start
  • Fast Tracking : allow overlapping of activities or activities in parallel, included risks/resource overloading
  • Crashing : shorten the activities by adding resources, may result in team burnout
  • Scheduling Techniques
  • Critical Path Method (CPM) – compute the forward and backward pass to determine the critical path and float
  • Critical Chain Method (CCM) – deal with scarce resources and uncertainties, keep the resources levelly loaded by chaining all activities and grouping the contingency and put at the end as project buffer, for activities running in parallel, the contingency is called feeding buffer (expect 50% of activities to overrun)
  • Buffer is determined by assessing the amount of uncertainties, human factors, etc.
  • Parkinson’s Law: Work expands so as to fill the time available for its completion.
  • Resource Optimization Techniques
  • Resource leveling is used to adjust the variation in resource loading to stabilize the number of resources working each time and to avoid burnout, may need to extend the schedule in CPM
  • Resource smoothing is to adjust resource requirements so as not to exceed predetermined resource limits, but only optimized within the float boundaries
  • Modeling Techniques
  • What if analysis: to address feasibility/possibility of meeting project schedule, useful in creating contingency plan
  • Monte Carlo: run thousand of times to obtain the distribution using a set of random variables (stochastic variables), use a combination of PERT estimate and triangular distributions as end point estimates to create the model to eliminate schedule risks, the graph is a ‘S’ curve
  • Network Diagram: bar charts with logical connections
  • Hammock activities: higher-level summary activities between milestones
  • Milestone Charts: show only major deliverables/events on the timeline
  • data date (status date, as-of date): the date on which the data is recorded
  • the Schedule Data includes schedule milestones, schedule activities, activities attributes, and documentation of all assumptions and constraints, alternative schedules and scheduling of contingency reserves
  • the Project Calendars identify working days
Control Schedule
  • measure result, make adjustments, adjust metrics
  • Performance Review includes: Trend Analysis, CPM, CCM, Earned Value Management
  • Change Requests generated are to be assessed in the Perform Integrated Control Process


5) SCOPE Management

 |  SCOPE Management
  • ensure the inclusion of all and only the work required to complete the project successfully
  • Product Scope – requirements needed to be fulfilled to create the product, assessed against the product requirements and WBS
  • Project Scope – activities and processes needed to be performed to deliver the product scope, assessed against the scope baseline (scope statement, WBS and WBS dictionary), e.g. including testing & quality assurance, assessed against the PM plan
  • scope management to prevent scope creep (additional requirements added without any proper control)
  • The completion of project scope is measured against the project management plan whereas the completion of product scope is measured against the product requirements/WBS
  • gold plating – additional requirements initiated by the team members to exceed expectation, considered a subset of scope creep
  • Scope Baseline: scope statement + WBS + WBS dictionary
  • WBS includes only the deliverables/outcomes/results (not actions)

Project Scope Management PITTOs:

Processes
Inputs
Tools & Techniques
Output
Plan Scope Management
Project Management Plan
Project Charter
Enterprise Environment Factors
Organization Process Assets
Expert Judgments
Meetings
Scope Management Plan
Requirements Management Plan
Collect Requirements
Scope Management Plan
Requirements Management Plan
Stakeholder Management Plan
Stakeholder Register
Project Charter
Interviews
Focus Groups
Facilitated Workshops
Group Creativity Techniques
Group Decision-making Techniques
Questionnaire and Surveys
Observations
Prototypes
Benchmarking
Context Diagram
Document Analysis
Requirements Documentation
Requirements Traceability Matrix
Define Scope
Scope Management Plan
Project Charter
Requirements Documentation
Organization Process Assets
Expert Judgments
Product Analysis
Alternatives Identification
Facilitated Workshops
Project Scope Statement
Project Document Updates
Create WBS
Scope Management Plan
Project Scope Statement
Requirements Documentation
Enterprise Environment Factors
Organization Process Assets
Decomposition
Expert Judgments
Scope Baseline
Project Document Updates
Validate Scope
Project Management Plan
Requirements Documentation
Requirements Traceability Matrix
Verified Deliverables
Work Performance Data
Inspection
Group Decision Making Techniques
Accepted Deliverables
Change Requests
Work Performance Info
Project Document Updates
Control Scope
Project Management Plan
Requirements Documentation
Requirements Traceability Matrix
Work Performance Data
Organization Process Assets
Variance Analysis
Work Performance Info
Change Requests
Project Management Plan Updates
Project Document Updates
Organization Process Assets Updates
Plan Scope Management
  • Scope Management Plan: how the scope will be defined, validated and controlled
  • including how to prevent scope creep, how to handle change requests, escalation path for disagreement on scope elements between stakeholders, process for creating scope statement, WBS, processing CR, how the deliverables will be accepted
  • Requirements Management Plan: how the requirements will be managed, documented and analyzed,
  • including how to process requirements, address missed requirements, configuration management, prioritize requirements, metrics (and rationale) for defining the product, define the traceability structure (in RTM), authorization level for approving new requirements
  • important: primary means to understand and manage stakeholder expectations
Collect Requirements
  • Requirement: a condition/capability that must be met /possessed by a deliverable to satisfy a contract/standard/etc., including quantified/documented needs, wants, expectation of the sponsor/stakeholder/customer
    • Business requirements – support business objectives of the company
    • Stakeholder requirements
    • Solution requirements - functional (product behavior) and nonfunctional requirements (reliability, security, performance, safety, etc.)
    • Transitional requirements : temporary capability including data conversion/tracking/training
    • Project requirements : actions/processes/conditions the project needs to met
    • Quality requirements : quality criteria defined by stakeholders
  • Requirements Collection Tools
    • interviewing (expert interviewing)
    • focus groups (with SME and pre-qualified stakeholders)
    • facilitated workshops (QFD (Quality Function Deployment) – capture VOC voice of customer, translate customer needs into requirements; JAD (Joint Application Design) – facilitated workshop for IT and knowledge workers)
    • questionnaires and surveys
    • observation (shadowing or Gemba)
    • prototypes
    • context diagrams (diagrams showing input/source and output, to show how people interact with the system)
    • document analysis
  • Product analysis includes techniques such as product breakdown, systems analysis, requirements analysis, systems engineering, value engineering, and value analysis
  • Group Creativity Techniques: brainstorming, nominal group technique (to rank brainstormed ideas by voting anonymously), mind-mapping, affinity diagram (KJ method – group ideas into larger categories based on their similarity and give titles to each group), Delphi technique (for experts with widely varying opinions, all participants are anonymous, evaluation of ideas funneled by a facilitator), Multi-criteria Decision Analysis (with a decision matrix)
  • Group Decisions-making Techniques: Analytic Hierarchy Process (AHP, for complex decisions, give different weighs to factors to build an hierarchy), Voting (unanimous, majority >50%, plurality, dictatorship)
  • Requirements Traceability Matrix tracks requirements from origins to deliverables, including source of requirements and completion status, effective to prevent gold plating (also work with work authorization system)
  • requirement documentation needs to be unambiguous, traceable, compete, consistent and acceptable to key stakeholders and is approved by the customer and other stakeholders
Define Scope
  • project & product scope, outlines what will be and what will NOT be included in the deliverables, including details of risks, constraints and assumptions
  • vs project charter which includes high-level descriptions
  • provides alternatives if the budget and schedule could not meet management’s expectations
  • value engineering is a part of the product analysis technique (Value Engineering (value analysis, value management, value methodology) – finding alternatives to constraints to improve product/reduce cost without sacrificing the scope)
  • project scope statement includes objectives, (project and product) scope, requirements, boundaries, deliverables, acceptance criteria, constraints, assumptions, milestones, cost estimation, specifications, configuration management requirements, approval requirements, etc.
  • The scope statement is progressively elaborated
Create WBS
  • the WBS must be created (if take on a running project without WBS, stop the project and prepare the WBS first)
  • WBS is a structured hierarchy created by the organization/stakeholders, can be in an organization chart or table form, based on the project deliverables (not tasks needed)
  • can be a template in OPA
  • a higher level above a work package is ‘control account‘ (control point where scope, cost and schedule are compared to earn value for performance measurement), a work package can have only ONE control account
  • WBS includes 100% of scope (100% rule)
  • code of accounts: a numbering system to identify WBS components
  • chart of accounts: a list of all account names and numbers
  • 1.1 for the 2nd level, 1.1.1 for the 3rd level
  • WBS is a decomposition tool to break down work into lowest level manageable (time and cost can be estimated, work package can be assigned to a team member) work packages, e.g. by phase or major deliverables
  • different work packages can be at different levels of decompositions
  • WBS does not show dependencies between work packages, but a WBS dictionary does (WBS dictionary clarifies WBS by adding additional information)
  • the major deliverables should always be defined in terms of how the project will actually be organized, for a project with phases, the decomposition should begin with the phase first
  • scope baseline, an output from Create WBS, is created by the project team
  • the work packages are broken down enough to delegate to a staff, usu. 8 – 80 hours work
Validate Scope
  • gain formal acceptance of deliverables from customer/stakeholders (e.g. obtain customer sign off, requirements validations, etc.) near the end of project/phase/each deliverable, e.g. user acceptance test
  • work performance data tells how the deliverables were created, work performance data includes non-conformance and compliance data
  • change requests may be an output
  • if no formal sign off is received as stipulated, follow the pre-defined process in PM plan, e.g. escalation to management
  • often preceded by Control Quality Process to give the verified deliverable as input to this process, verified deliverables is fed from the control quality process
  • vs Control Quality: the process of monitoring/recording results of executing quality activities to assess performance and recommend necessary changes, e.g. unit testing -> high quality vs low quality
  • need to perform even in case of early termination/cancellation of the project to save any usable deliverables for other projects
Control Scope
  • assessing additional requirements by the customer or proactively overlooking the project scope
  • measure the work product against the scope baseline to ensure the project stays on track proactively, may need preventive, corrective actions or defect repair
  • to prevent unnecessary changes (either internally or externally requested) to the project
  • a documented and enforced change control process
  • the customer has the ultimate authority to change scope while the senior management can make use of management reserves
  • variance analysis – method to compare planned (baseline) and actual work and determine the causes/actions e.g. update baseline (keep the variance) or preventive/corrective actions, both need CR
  • work performance info – scope variance, causes, recommended action
  • may update the inputs – requirements documentation & requirement traceability matrix & lessons learnt in OPA
  • in general, disagreement should be resolved in favor of the customer