Work Breakdown Structure and Activity List Workshops

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Degree and Graduation Seminar Scope Management
Jeopardy Game! Scope Management Time Management Integration Management.
Elisati Hulu. Definition  “a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project.
Inspiring Your Next Success! ® Company Confidential - Copyright 2008 Hitachi Consulting 1 Work Plan Development Or answering the question: “So... what.
Project Management Session 7
Six Steps to a Better WBS Presented by 41 Bloomfield Street Lexington, MA USA © 2011 Project Management Partners.
How to integrate the parts of your project to achieve success.
Task: Copyright © 2003 PM tec, Inc; D. Sankey; D. Padelford. All rights reserved. 1 Fast Start For Projects  Electric Dipole Moment Project Facilitator:
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Geog 469 GIS Workshop Project Management.
Work Breakdown Structure Kathy S. Schwaig. What is a Work Breakdown Structure (WBS)? A WBS is a logical hierarchy of work packages involved in a project.
Work Breakdown Structure Use and Demo
GLOBAL SCHOOL OF PROJECT MANAGEMENT UNIVERSITY FOR INTERNATIONAL COOPERATION Ing. Osvaldo A. Martínez Gómez, MAP, MSc. Essential Topics - Project Management.
Team-Based Development ISYS321 Managing the Information Systems Project.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
Project management Topic 2 Product based planning.
Project Management Fundamentals - Planning Tools 1.
SOW / Open Workbench By Wilmer Arellano Spring 2008.
Creating a Work Breakdown Structure with Microsoft Project.
3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
For Life™ [Insert Date Here] [Insert Instructor Name Here] Project Management Skills.
BSBPMG502A Manage Project Scope Manage Project Scope Project Scope Processes Part 2 Diploma of Project Management Qualification Code BSB51507 Unit.
THE MANAGERIAL PROCESS Clifford F. Gray Eric W. Larson PowerPoint Presentation by Charlie Cook The University of West Alabama Defining the Project Chapter.
Project Management PTM721S
Project Management 6e..
A Brief intro to Project Management What can it do for you
Work Breakdown Structure (WBS)
Project Management 6e..
CMGT 410 aid Education Begins/cmgt410aid.com
IF 3507 Manajemen Proyek Perangkat Lunak
Project Management Systems
By Wilmer Arellano Spring 2010
Managing the Information Systems Project
Scope Planning.
Module nine PMP® Mastery 2016 APMG Create WBS
Project Management Chapter 3.
Project Management 1040 Bus Week 6. June9-13, Agenda
Plan Schedule Management
Use Cases Discuss the what and how of use cases: Basics Benefits
Chapter 4 Defining the Project.
Project Management -- Defining the Project
Work Breakdown Structure
Defining Scope, Quality, Responsibility, and Activity Sequence
Information Technology Project Management – Fifth Edition
Create a project schedule
Defining the Project Chapter 4.
2018 CompTIA PK0-004 Study Guide Killtest
PMIS Initiating a Project Application of Project Management Processes Project Charter Stakeholder Analysis and Stakeholder Register 2. Planning.
MGMT 404 Education for Service-- tutorialrank.com
Where We Are Now. Where We Are Now Defining the Project (100) Step 1: Defining the Project Scope Step 2: Establishing Project Priorities Step 3: Creating.
Project Theory and Application
Created by Katy Koenen © Microsoft Corporation
Defining the Project Step 1: Defining the Project Scope
MGT 605: CH 04 Defining the Project.
CIS12-3 IT Project Management
CIS 210 Systems Analysis and Development
Welcome W 15 Introduction to Engineering Design II (IE 202)
Work Breakdown Structure
PMI-SVC Scheduling Forum
Work Breakdown Structure and Activity List Workshops
Project Scope Management
Project Scope Management
Creating robust project networks
Time Scheduling and Project management
Executive Project Kickoff
Project Kick-off <Customer Name> <Project Name>
Chapter 2 Managing the Information Systems Project
Information system analysis and design
Presentation transcript:

Work Breakdown Structure and Activity List Workshops

Today’s Agenda Converting Project Charters and Scope Statements into Work Plans Creating a Work Breakdown Structure – The “Nouns” Creating an Activity List – The “Verbs” Next Steps

Nouns & Verbs (or . . .converting project charter and scope statement into work plans)

Converting Charters into Work Plans From the project charter and scope statement, create a Work Breakdown Structure (WBS) From the WBS, identify the activities needing completion From the activity list, develop a network diagram, identifying the sequence of activity completion From the network diagram, develop a preliminary project schedule and assign resources Iterate the above with key stakeholders until acceptance (a set of baselines) is agreed upon. Our Focus Today You Your WBS Our Focus Next Week

Nouns & Verbs Nouns Verbs =

The Work Breakdown Structure (WBS) The WBS = your “Nouns” WBS = The things being delivered Hierarchical representation of work elements needing completion—deliverables themselves or deliverable components Single most important tool in scope definition, scope control, and communications “Divide and Conquer”

The Noun Workshop Goal Materials: Develop hierarchical definition of the project Materials: Sticky Notes Tape Wall Faith . . . that in lieu of a perfect project definition you, your teammates, and your customer will iterate the WBS to a satisfactory conclusion You’ve gone deep enough in the hierarchy when: Bottom level work—the work package level—requires ~ 8 to 80 total hours to complete

WBS Template

Tips for Creating the WBS Start with the major work of the project first (top down) This is level 1, then proceed downward; this level establishes the framework for the entire project so be smart here Figure out if the project is analogous to something else and cherry-pick the approach to the project Use the Internet or other available expertise If you’re tempted to think at the activity level (bottom up), that’s ok Find a common theme to multiple activities, then convert to one or more nouns Start an Open Items log now No “Gold Plating” Make sure to complete the work necessary to achieve the level of scope, quality, time and cost expected, no more and no less 100% Rule Child elements within a single parent element should represent 100% of the work envisioned in the parent Continually ask: “What work is missing”? All projects should include “Project Management” as a Level 1 work package

The Activity List Activities = your “Verbs” List of things to do to complete the work packages Feeds into activity sequencing (network diagrams), scheduling, and resourcing process Have durations, owners, and specified outputs An activity should not be performed within your project unless it is specified Note: Activities are defined only at the lowest level of the WBS

The Verb Workshop Goal Materials: = Goal Capture as many project activities as possible Materials: Stickies Tape Wall Faith . . . that in lieu of a perfect project definition you, your teammates, and your customer will iterate the WBS to a satisfactory conclusion Reminder: Activities should be placed only below the lowest level of your WBS

Activity Template (Work Package)

Tips for Activity Definition Look Out!! You will likely find a need for additional WBS elements through the activity definition process All activities must fit logically into the WBS Identify good opportunities to insert major milestones, which are defined as zero-duration activities Indicates that a major block of work has been completed. Milestones are also good status reporting mechanisms when talking to customers Consider strongly the role that quality and risk should play in activity definition Update your Open Item log with issues Exclude incidental or trivial activities

Next Steps Ensure that today’s WBS and activities have numbers assigned Scope Iterations Complete the first version of the WBS and Activity List as a team Share WBS and optionally the activity list with customer to confirm scope Re-define scope until complete Schedule Iterations As scope is progressively elaborated, continue to add appropriate activities Use activity definitions to sequence activities (network diagrams) Apply the concept of “critical paths” Keep an eye out for new WBS or activities that might crop up Assign dates and owners to activities Share schedule (milestone-level) w/customer Re-define until complete Lock down scope and schedule; manage risk, quality, and change aggressively