Sunday, 14 September 2014

allforquiz2

Scope Planning


Web Intelligence Solutions from Tera data

"An effective scope management approach fosters open communications and sound decision making to ensure all parties get business value expected from the project"


  • Describe how to collect requirements
  • Define scope processes.
  • Create a requirements trace-ability matrix, project scope statement, and change request form.
  • Describe a work breakdown structure (WBS) is
  • Compare/contrast methods of developing a WBS.
  • Create a WBS for a project
  • Set up a WBS in MS Project

Scope Planning Processes

  • Collect project requirements
  • Define project's scope
  • Create a work breakdown structure (WBS)
  • Establish change control

Flow of Scope Planning



Plan Scope Management

Plan Scope Management - "the process of creating a scope management plan that documents how the project will be define, validated, and controlled." PMBOK GUIDE

  • Total scope = product scope + project scope
Project scope - "the features and functions that characterize a product, service, or result." PMBOK Guide

  • Identify and organize all project work
Project scope - "the work performed to deliver a product, service, or result with the specified features and functions." PMBOK Guide




Collect Requirements

  • Make sure the project team is absolutely clear on the project objectives
Collect requirements - "the process of defining, documenting, and managing stakeholder needs and requirements to meet project objectives." PMBOK Guide



Gather Stakeholder Input

  • Use voice of the customer techniques (VOC)
    • Ask questions
    • Place yourself in the customer's situation
  • State customer desires in operational terms
  • Seek a high-level description
What do we not understand about the request?
What is the business reason for the request?
What is the impact of not providing this feature?
What action items need to be accomplished if we do this?
What impact will this have on other parts of the project or elsewhere?




Requirements Trace-ability Matrix

-traceable
-identified
-clear-
-measurable
-prioritized






Define Scope

Define scope - "the process of developing a detailed description of the project and product." PMBOK Guide

  • Reasons to Define Scope
  • How to Define Scope
    • List deliverable and acceptance criteria 
    • Establish project boundaries
    • Create a project work statement
  • How to Define Scope in Agile Projects


Reasons to Define Scope

  • All other planning is based on the project scope 
  • Aid to preventing scope creep




How to Define scope

  • List project deliverable
    • Determine acceptance criteria
  • Establish project boundaries
    • In scope
    • Out of scope
    • Understand constraints
  • Create a Scope Definition






How to Define Scope in Agile Projects





Work Breakdown Structure (WBS)
  • What is the WBS?
  • Why use a WBS?
  • WBS Formats
  • Work Packages
  • How to Construct a WBS




What is the WBS?

  • A tool used to divide project deliverable into smaller pieces
  • Identify deliverables

What are the components of this deliverable?
  • A framework for further planning, execution, and control
Define activity - "the process of identifying the specific actions to be performed to produce  the project deliverables" PMBOK GUIDE




Why use WBS?

  • Adds discipline and visibility to project planning
  • basic for planning schedule, resources, cost,  quality, and risk
  • Useful in determining where and why problems occur
  • Helpful in project communications


WBS Formats

  • Indented outline
  • Organizational chart
  • Free format

WBS - Indented Outline Format





WBS in Org Chart Format




WBS in Free Format



Work Packages

  • Lowest level element
  • Basis for subsequent planning and control
work activities are defined
Schedule is formed
Resources are aligned
Control features are developed

Work packages - "the work defined at the lowest level of the work breakdown structure for which cost and duration can be estimated and managed." PMBOK Guide



Work Packages





  • State succinctly in very few words
WBS component - "an entry in the WBS that can be at any level." PMBOK Guide

WBS dictionary - " a document that provides detailed deliverable, activity, and scheduling information about each component in the WBS." PMBOK Guide



Work Package Detail






How to construct a WBS

  • Include a subject matter expert (SME)
  • Use a top down approach
  • Consider WBS from a previous project as a starting point
  • Use brainstorming


Steps in WBS Construction

  1. Identify major deliverables
  2. Divide into smaller deliverables 
  3. Continue until deliverables are the right size
  4. Review


Identify Major Deliverables

  • Organize by project phase
  • Facilitates rolling wave planning
  • Rolling wave planning -->  quick start 
  • Helps avoid:
  • Analysis paralysis - never starting anything because the plan is not complete
  • Ready, fire, aim - not planning at all
Rolling wave planning - "an iterative planning technque in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level." PMBOK Guide



WBS Organization Examples






Work Function Organization


  • Allows functions to focus on specific activities
  • Does not promote cross-functional discussion
  • Extra care required to establish inter-functional communication


Decompose deliverables


  • Brainstorm a list of interim and final deliverables (use Post It Notes)
  • Assemble deliverables on a large work space
  • Group deliverables into related groups
Decomposition = "a technique for dividing and subdividing the project scope and project deliverables into smaller more manageable parts." PMBOK guide


Continue Until deliverables are the right size







Review

  • Consider the parent-child concept 
    • Have between 3 and 9 child elements for each parent
  • Uniquely name each component in the WBS
  • Assign a unique number to each component


Establish Change Control

  • Projects are conducted in an atmosphere of uncertainty
  • Plans must be made for dealing with change
Change control
 system - "approved set of procedures that describes how modifications to the project deliveraables and documentation will be managed and controlled." PMBOK Guide



Baseline - "the approved version of a work product that can be changed only through formal change control procedures and is used as a basis for comparision." PMBOK Guide


  • Document potential changes to a project with a change request 
  • Every change to a project must be formally proposed
Change request - "a formal proposal to modify any document, deliverable, or baseline." PMBOK Guide




Change request Form




Using MS Project for Work Breakdown Structures  (WBS)

  • Set Up the WBS
Understand WBS definitions and displays.
Enter summaries.
Create the outline for your WBS. Insert row number column.
Hide (or show) the desired amount of detail.





Step 1. Understand WBS displays and definition

  • Summaries are display:
    • Tables as an outline
    • Gantt view




Step 2. Enter WBS Elements (Summaries)







Step 3. Create the Outline for your (WBS)






Step 4. Insert Row Number Column

  • Project will automatically number summaries
  • Right-click the Task Name heading
  • Insert - Column - WBS

Ready to Insert WBS Column



WBS Column Inserted



Step 5. Hide (or Show) Underlying Detail




Summary

  • Use scope planning to determine interim deliverables and work to perform
  • Organize scope into work breakdown structure (WBS).
  • Decompose the project into smaller and smaller pieces.
  • Assign WBS components
  • Create the project by hand or use MS Project to create the WBS

Work Breakdown Structure Template


  • Management and Technical activities for banks in South Africa



























Scheduling Projects


Web-based software implementations

"Establishing scope that can be accomplished in a 30 - to 60-day schedule helps our clients get started using their web-based applications faster..Project planning for the future becomes more realistic, improving the odds of success.



  • Describe project schedule limitations and how to deal with them
  • Describe potential problems in estimating time accurately and how to overcome them
  • Use the activity on node (AON) method to develop a project schedule.
  • Describe project schedule limitations and how to deal with them
  • Describe potential problems in estimating time accurately and how to overcome them
  • Use the activity on node (AON) method to develop a project schedule
  • Describe how to adjust a project's sequence logic
  • Identify the critical path using prescribed methods
  • Depict a project schedule

Plan Schedule Management

  • Building blocks of a project schedule are activities





Plan Schedule Management








Project time management processes

  1. Plan schedule management
  2. Define activities
  3. Sequence activities
  4. Estimate activity resources
  5. Estimate activity duration
  6. Develop schedule
  7. Control schedule
Adapted from PMBOK guide




Purposes of a Project Schedule

What is the earliest a particular activity can start, and when will it end?

What activity must begin before which other activities can take place?

When will the project be complete?


What would happen if a delivery of material was one week late?

Can a key worker take week vacation the first week of march?


If one worker is assigned to do two activities, which one must go first?


 How many hours do we need from each worker next week or month?


Which worker or other resource is a bottle neck, limiting the speed of our project?

What will the impact be if the client wants to add another module?

If I am willing to spend an extra $10,000, how much faster can the project be completed?

Are all of the activities completed that should be by now?





Historical Development of Project Schedules


  • Scheduling as a result of competition
  • Program Evaluation and Review Technique (PERT) and Critical Path Method (CPM) – 1 950s
    • Identify activities
    • Determine their logical order
    • Estimate the duration of each activity




Critical Path Method (CPM) – “a method used to estimate the
minimum project duration and determine the amount of scheduling flexibility on the logical network paths within the schedule model." PMBOK Guide






PERT


  • Estimate most likely time needed to complete a project
  • Estimate level of confidence in completing a project in a particular time
  • Useful in (R&D) projects



DEPARTMENT OF THE 
NAVY POLARIS 
WEAPONS SYSTEM



CPM


DUPONT
ENGINEERING 
SERVICES
DIVISION




  • Used to plan very large projects
  • Used single time estimates for Used single time estimates for each activity
  • Focus on longest sequence of Focus on longest sequence of activities
  • Used to determine how to complete a project early
  • Useful in the construction industry


Activity Activity () on Node on Node (AON) or Precedence or Precedence
Diagramming Method (PDM)




Precedence Diagramming Method (PDM) – “a technique in which
the scheduled activities are represented by nodes and are graphically 
linked by one or more logical relationships to show the sequence in by one or more logical relationships to show the sequence in
which the activities are performed” PMBOK® Guide






5 Factors Limit Project Completion


  1. Logical order in which activities need to be completed to be completed
  2. How long each activity will take
  3. How many key resources are  available at specific points in the project
  4. Imposed dates Imposed dates
  5. Cash flow


Creation of Project Schedules

  • Identify all activities
  • Determine logical order Determine logical order
  • Assign resources to each activity
  • Estimate time required for that activity
  • Compare schedule with imposed Compare schedule with imposed dates
  • Consider project budget and cash Consider project budget and cash flow, quality demands, and risk factors


The Project Manager’s Responsibility

  • Resist pressure to dictate a schedule
  • Determine a schedule that is possible Determine a schedule that is possible
  • Persuade stakeholders that the scheduled make sense
  • Deliver the project according to the agreed-upon schedule


Define Activities

  • WBS with WBS with deliverables only



  • Don’t omit activities
  • Activity sequencing may uncover Activity sequencing may uncover missing activities
  • The schedule will not be approved until all related planning is in place

  • Avoid adding activities after the final  schedule is approved 
  • Use previous projects, templates, or checklists as a starting point checklists as a starting point


List Project Milestones List Project Milestones

  • Completion of a major deliverable
  • Completion of a critical activity
  • Prior to a large financial commitment
  • Merging point in the project schedule

WBS with Milestone List




Sequence Activities


Scope Planning

Scope Planning


Web Intelligence Solutions from Tera data

"An effective scope management approach fosters open communications and sound decision making to ensure all parties get business value expected from the project"


  • Describe how to collect requirements
  • Define scope processes.
  • Create a requirements trace-ability matrix, project scope statement, and change request form.
  • Describe a work breakdown structure (WBS) is
  • Compare/contrast methods of developing a WBS.
  • Create a WBS for a project
  • Set up a WBS in MS Project

Scope Planning Processes

  • Collect project requirements
  • Define project's scope
  • Create a work breakdown structure (WBS)
  • Establish change control

Flow of Scope Planning



Plan Scope Management

Plan Scope Management - "the process of creating a scope management plan that documents how the project will be define, validated, and controlled." PMBOK GUIDE

  • Total scope = product scope + project scope
Project scope - "the features and functions that characterize a product, service, or result." PMBOK Guide

  • Identify and organize all project work
Project scope - "the work performed to deliver a product, service, or result with the specified features and functions." PMBOK Guide




Collect Requirements

  • Make sure the project team is absolutely clear on the project objectives
Collect requirements - "the process of defining, documenting, and managing stakeholder needs and requirements to meet project objectives." PMBOK Guide



Gather Stakeholder Input

  • Use voice of the customer techniques (VOC)
    • Ask questions
    • Place yourself in the customer's situation
  • State customer desires in operational terms
  • Seek a high-level description
What do we not understand about the request?
What is the business reason for the request?
What is the impact of not providing this feature?
What action items need to be accomplished if we do this?
What impact will this have on other parts of the project or elsewhere?




Requirements Trace-ability Matrix

-traceable
-identified
-clear-
-measurable
-prioritized






Define Scope

Define scope - "the process of developing a detailed description of the project and product." PMBOK Guide

  • Reasons to Define Scope
  • How to Define Scope
    • List deliverable and acceptance criteria 
    • Establish project boundaries
    • Create a project work statement
  • How to Define Scope in Agile Projects


Reasons to Define Scope

  • All other planning is based on the project scope 
  • Aid to preventing scope creep




How to Define scope

  • List project deliverable
    • Determine acceptance criteria
  • Establish project boundaries
    • In scope
    • Out of scope
    • Understand constraints
  • Create a Scope Definition






How to Define Scope in Agile Projects





Work Breakdown Structure (WBS)
  • What is the WBS?
  • Why use a WBS?
  • WBS Formats
  • Work Packages
  • How to Construct a WBS




What is the WBS?

  • A tool used to divide project deliverable into smaller pieces
  • Identify deliverables

What are the components of this deliverable?
 
  • A framework for further planning, execution, and control
Define activity - "the process of identifying the specific actions to be performed to produce  the project deliverables" PMBOK GUIDE




Why use WBS?

  • Adds discipline and visibility to project planning
  • basic for planning schedule, resources, cost,  quality, and risk
  • Useful in determining where and why problems occur
  • Helpful in project communications


WBS Formats

  • Indented outline
  • Organizational chart
  • Free format

WBS - Indented Outline Format





WBS in Org Chart Format




WBS in Free Format



Work Packages

  • Lowest level element
  • Basis for subsequent planning and control
work activities are defined
Schedule is formed
Resources are aligned
Control features are developed

Work packages - "the work defined at the lowest level of the work breakdown structure for which cost and duration can be estimated and managed." PMBOK Guide



Work Packages





  • State succinctly in very few words
WBS component - "an entry in the WBS that can be at any level." PMBOK Guide

WBS dictionary - " a document that provides detailed deliverable, activity, and scheduling information about each component in the WBS." PMBOK Guide



Work Package Detail






How to construct a WBS

  • Include a subject matter expert (SME)
  • Use a top down approach
  • Consider WBS from a previous project as a starting point
  • Use brainstorming


Steps in WBS Construction

  1. Identify major deliverables
  2. Divide into smaller deliverables 
  3. Continue until deliverables are the right size
  4. Review


Identify Major Deliverables

  • Organize by project phase
  • Facilitates rolling wave planning
  • Rolling wave planning -->  quick start 
  • Helps avoid:
  • Analysis paralysis - never starting anything because the plan is not complete
  • Ready, fire, aim - not planning at all
Rolling wave planning - "an iterative planning technque in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level." PMBOK Guide



WBS Organization Examples






Work Function Organization


  • Allows functions to focus on specific activities
  • Does not promote cross-functional discussion
  • Extra care required to establish inter-functional communication


Decompose deliverables


  • Brainstorm a list of interim and final deliverables (use Post It Notes)
  • Assemble deliverables on a large work space
  • Group deliverables into related groups
Decomposition = "a technique for dividing and subdividing the project scope and project deliverables into smaller more manageable parts." PMBOK guide


Continue Until deliverables are the right size







Review

  • Consider the parent-child concept 
    • Have between 3 and 9 child elements for each parent
  • Uniquely name each component in the WBS
  • Assign a unique number to each component


Establish Change Control

  • Projects are conducted in an atmosphere of uncertainty
  • Plans must be made for dealing with change
Change control
 system - "approved set of procedures that describes how modifications to the project deliveraables and documentation will be managed and controlled." PMBOK Guide



Baseline - "the approved version of a work product that can be changed only through formal change control procedures and is used as a basis for comparision." PMBOK Guide


  • Document potential changes to a project with a change request 
  • Every change to a project must be formally proposed
Change request - "a formal proposal to modify any document, deliverable, or baseline." PMBOK Guide




Change request Form




Using MS Project for Work Breakdown Structures  (WBS)

  • Set Up the WBS
Understand WBS definitions and displays.
Enter summaries.
Create the outline for your WBS. Insert row number column.
Hide (or show) the desired amount of detail.





Step 1. Understand WBS displays and definition

  • Summaries are display:
    • Tables as an outline
    • Gantt view




Step 2. Enter WBS Elements (Summaries)







Step 3. Create the Outline for your (WBS)






Step 4. Insert Row Number Column

  • Project will automatically number summaries
  • Right-click the Task Name heading
  • Insert - Column - WBS

Ready to Insert WBS Column



WBS Column Inserted



Step 5. Hide (or Show) Underlying Detail




Summary

  • Use scope planning to determine interim deliverables and work to perform
  • Organize scope into work breakdown structure (WBS).
  • Decompose the project into smaller and smaller pieces.
  • Assign WBS components
  • Create the project by hand or use MS Project to create the WBS

Work Breakdown Structure Template
  • Management and Technical activities for banks in South Africa

Wednesday, 10 September 2014

Introduction to Project Management V2

Introduction to Project




The Element of Discipline




“A key to success in project management, as well as in mountain climbing, is to identify the pillars that will be practiced with discipline...I believe that project management is about
applying common sense with uncommon

discipline.”


—  Define a project using characteristics that are common to most projects and describe reasons why more organizations are using project management.
—  
Describe major activities and deliverables, at each project life cycle stage.

—  List and define the ten knowledge areas and five process groups of the project management body of knowledge (PMBOK®).


—  Delineate measures of project success and failure, and reasons for both.
—  Contrast predictive or plan-driven and adaptive or change-driven project life cycle approaches.
—  Identify project roles and distinguish key responsibilities for each.






What is a project?

project – “a temporary endeavor undertaken to create a unique product, service, or result.” PMBOK® Guide 

Projects require:
an organized set of work efforts.
◦ progressively elaborated detail.
a defined beginning and ending.
a unique combination of stakeholders.

—  
Projects are subject to time and resource limitations






stakeholders – “an individual, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project.” PMBOK® Guide






Project Management (PM)






Project management  “the application of knowledge, skills, tools and techniques to project activities to meet project requirements." PMBOK® Guide



  • Work processes that  initiate, plan, execute, close, work.
  • Trade-offs among Scope, Quality, Cost, Schedule, Resources, Risks



  •  Administrative tasks planning, documenting, controlling
  • Leadership tasks for work associates visioning, motivation, promoting.
  • Knowledge, skills, and methods apply for most projects








History of PM



  • — Emerged as a formal discipline in the 1950s
  • — Developed for aerospace and construction
  • — Involved determining project schedules
  • Manufacturing, R&D, government, and construction refined techniques
  • Software (1980s and 1990s) for planning and controlling
  • —  Risk management techniques
    •  applied to less complex projects
  • —  Communication and leadership role emerged
  • —  Information technology and telecommunications fueled use (1990s and 2000s)








How Can Project Work Be Described?



  • Projects versus operations
  • Soft skills and hard skills
    • Soft skills activities
      • communication
      • Leadership
    • Hard skills activities
      • Risk analysis
      • Quality control
      • Scheduling work
      • Budgeting work
  •  Authority and responsibility
    • One person being assigned accountability
    • Project managers negotiate with functional managers
    • Strong communication and leadership skills to persuade subordinates.
Functional manager – “someone with management authority over an organizational unit.…the manager of any group that actually makes a product or performs a service.” PMBOK®
Guide
  •   Project Life Cycle
    • Predictable stages
    • Life cycle allows for control
Project life cycle – “the series of phases that a
project goes through from its initiation to its closure.” PMBOK® Guide



d

Project Life Cycle Stages

  • Selecting and initiating
  • Planning
  • Executing
  • Closing and realizing

A project must pass an approval of to move from one stage to the next

The project life cycle is highly formalized and very specific

Projects are measured at additional points
  • Selection
  • Progress reporting,
  • Benefits realization




Predictive (Plan-Driven) PLC






Predictive (Change-Driven) PLC




Adaptive extreme ---->  Agile






Midland Insurance PLC for QualityImprovement Projects








Understanding Projects

  • Project Management Institute
  • Project Management Body of Knowledge (PMBOK)
  • Selecting and Prioritizing Projects
  • Project Goals and Constraint
  • Project Success and failure
  • Using MS Project
  • Types of Projects
  • Scalability of Project Tools



The Project management Institute

  • The largest professional organization
  • A Guide to the Project Management Body of Knowledge (PMBOK Guide)
  • Project management Professional (PMP) certification
  • Certification
  • Certified Associate inProject Management (CAPM) certification



 Project management Body of Knowledge (PMBOK)

  • Project Life Cycle
  • 5 process groups
  • 10 knowledge areas


Project management process group – “a logical grouping
of the project management inputs, tools and techniques, and outputs.” PMBOK® Guide






 PMBOK Process groups



Initiating---"define a project or a new phase by obtaining authorization"

Planning---"establish the project scope, refine objectives and define actions to attain objectives"

Executing--"complete the work defined to satisfy project specifications"

Monitoring and controlling---"track, review, and regulate progress and performance, identify changes required, and initiate changes"

Closing---"finalize all activities to formally close project of phase"


PMBOK Knowledge Areas


Integration management - "processes and activities to identify, define, combine, unify, and coordinate the various processes and project management activities"

Scope management - "process to ensure that the project includes all the work required, and only the work required, to complete the project successfully"

Time management - "processes to management timely completion of the project"

Cost management  -  "processes involved in planning, estimating, budgeting, financing, funding, managing, and controlling costs so that the project can be completed within the approved budget"


Quality management - "processes and activities of the performing organization that determine quality policies, objectives, and responsibilities so that the project will satisfy the needs for which it was undertaken"

Human Resource management - "processes that organize, manage, and lead the project team"

Communications management - "process to enure timely and appropriate planning, collection, creation, distribution, storage, retrieval, management, control, monitoring, and ultimate disposition of project information"


Risk management - "processes of conduction risk management planning, identification, analsis, response planning, and control...to increase the likelihood and impact of positive events and decrease the likelihood and impact of negative events in the project"



Procurement management - "processes to purchase or acquire products, services, or results from outside the project team"

Stakeholder management - "processes to identify the people, groups, or organizations, that could compactor be impacted by the project, analyze their expectations and impact, and develop strategies for engaging them and managing conflicting interests"






Selecting and Prioritizing Projects



  • Identify potential projects
  • All parts of the organisation are involved
  • Determine which projects align best with major goals of the firm
  • Organizational priorities:
    • Understood
    • Communicated
    • Accepted


What value does each potential project bring to the organization?

Are the demands of performing each project understood?

Are the resources needed to perform the project available?

Which projects will best help the organization achieve its goals?



Is there enthusiastic support both from the external customers and from one or more internal champions?


Project Goals and Constraints

  • Projects are undertaken to accomplish specific goals
  • Scope and quality are performance goals

Scope - "the sum of the products, services, and results to be provided as a project." PMBOK Guide




Quality - "the degree to which a set of inherent characteristics fulfills requirements."




  • Subject to constraints of time and cost







Project Goals and Constraints

  • Obstacles or challenges may limit the ability to perform
  • Opportunities may allow projects to exceed original expectations.
  • Project Managers (PMs) decide which goals and constraints take precedence
  • Additional constraints
    • Amount of resources available
    • Decision maker's risk tolerance





Project Customer Trade-off Matrix








Project Success and failure


  • Completed without heroics
  • Learn new and/or refine skills
  • Organisational learning
  • Reap business-level benefits




Project Success











Why Projects Fail

  • Not enough resources available
  • Not enough time given to the project
  • Project expectations are unclear
  • Changes in the scope not understood or agreed upon
  • Stakeholders disagree on expectations 
  • Inadequate project planning

Types of Projects

  • Classifying by industry
  • Classifying by size
  • Classifying by understanding of project scope
  • Classify by application


Success PMI Communities of Practice


  • Projects in different industries often have unique requirements







Classifying by Size

Large projects often require more detailed planning and control


Classifying by timing of Project Scope Clarity

How early in the project the project manager and team are able to determine the project scope



Classification by Application

  • All projects require planning and control
  • The art of project management:
when to use certain techniques 


how much detail to use


how to tailor techniques to the needs of a project.


Scalability  of Project Tools

  • All projects require
    • Projects specifications
    • Understanding of work involved
    • Budget and schedule determinations 
    • Assignment of available workers to tasks
    • Project management
  • Projects are scaled up or down to meet the complexity of the task



Project Roles 





















































































Project Roles