© ABB AB, Corporate Research - 1 5/19/2015 abb Project Breakdown Structure Creation.

Slides:



Advertisements
Similar presentations
Project Management 6e..
Advertisements

Software Quality Assurance Plan
NEES Project Management Workshop June 16 June 18 1 Segment 3.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Project Scope Management
Degree and Graduation Seminar Scope Management
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Defining the Project CHAPTER FOUR Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
© ABB AB, Corporate Research - 1 6/1/2015 abb Work Breakdown Structure Creation.
Defining the Project Chapter 4.
McGraw-Hill/Irwin© 2008 The McGraw-Hill Companies, All Rights Reserved Defining the Project (modified for 2015) Chapter 4.
1 Samples The following slides are provided as samples and references for the Quarterly Reviews Additional slides will be added.
Project Scope Management
Software Project Transition Planning
Software Engineering General Project Management Software Requirements
OM480 Defining the Project Parameters – Work Breakdown Schedule (WBS) (With Material from the Text Authors)
Project Management Session 7
Chapter 3: The Project Management Process Groups
Chapter 2- Software Process Lecture 4. Software Engineering We have specified the problem domain – industrial strength software – Besides delivering the.
This work is licensed under a Creative Commons Attribution 3.0 Unported LicenseCreative Commons Attribution 3.0 Unported License (CC-BY). Project Management.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
Project Scope Management
Software Engineering Institute Capability Maturity Model (CMM)
How to integrate the parts of your project to achieve success.
Project Management Process Overview
Typical Software Documents with an emphasis on writing proposals.
Chapter 4 Defining the Project.
Defining the Project CHAPTER FOUR PowerPoint Presentation by Charlie Cook Copyright © 2014 McGraw-Hill Education. All Rights Reserved.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Software Quality Assurance Activities
1 Lecture 3.1: Project Planning: Work Breakdown Structure (WBS) [SEF Ch 9] Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Lecture 4 Title: The Scope Management Plan
McGraw-Hill/IrwinCopyright © 2008 by The McGraw-Hill Companies, Inc. All Rights Reserved. Defining the Project Chapter 4.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Week 2 Seminar: Project Scope Management
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Software Project Management By Deepika Chaudhary.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
Pre-Project Components
Develop Project Charter
Request for Proposal (RFP)
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
Validate Scope What we have: Requirement Traceability Matrix Verified Deliverables What we do: Inspection What we get: Accepted Deliverables.
Project Scope Management 1. 2 Learning Objectives Understand the elements that make good project scope management important. Explain the scope planning.
Project Management Basics
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
Requirements Management Overview NIGMS Software Development.
Recent trends in IT projects – Globalization, outsourcing, and virtual teams Project management process groups – Initiating, planning, executing, monitoring.
Timesheet training Version: Introduction Duration: 1.5 hours Purpose: Guide on how to use Timesheet.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Team-Based Development ISYS321 Managing the Information Systems Project.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
Slide 1 CS 310 Ch5: Project management What do you think is involved? Proposal writing Project costing Project planning and scheduling Project monitoring.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Project Scope Management Pantelis Ipsilandis- Dimitrios Tselios.
Information Technology Project Management, Seventh Edition.
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
Project Management 6e..
Project Management 6e..
Scope Planning.
Project Management -- Defining the Project
PROJECT SCOPE MANAGEMENT
Defining the Project Chapter 4.
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.
Defining the Project Step 1: Defining the Project Scope
PROJECT SCOPE MANAGEMENT
NOTICE! These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Our Process CMSC 345, Version 1/04.
Presentation transcript:

© ABB AB, Corporate Research - 1 5/19/2015 abb Project Breakdown Structure Creation

© ABB AB, Corporate Research - 2 abb Project Planning Course Overview Project Planning Overview Facilitating Processes Project Planning Pre-conditions Risk Management Work Breakdown Structure Project Breakdown Structure Estimation Resource Planning Logical Network Plan Budgeting Time Schedule Project Planning Result Product Anatomy Organic Integration Plan Integration Plan

© ABB AB, Corporate Research - 3 abb Purpose The Project Breakdown Structure (PBS) defines all Work Products, produced by a project. The purpose is to first focus on what the project shall produce, not the activities to perform.

© ABB AB, Corporate Research - 4 abb Input & Output INPUT Product Requirements Specification Project Breakdown Structure from earlier versions of the product and previous projects, if available Know-how from experienced personnel Architecture Organizational Demands OUTPUT Project Breakdown Structure including; Technical Product Breakdown Structure Management Product Breakdown Structure Quality Product Breakdown Structure The PBS is used as input when defining the Work Breakdown Structure later in the planning process.

© ABB AB, Corporate Research - 5 abb Work Products A project always delivers tangible things like documents, code, models, executables, plans etc. which all are Work Products. Some examples; Customer deliverables software on a CD-ROM, user documentation etc. Software components source code files, DLLs, executables etc. Development components design models, prototypes, tools etc. Management artifacts plans, budgets, progress reports etc. Quality assessment artifacts test results, inspection reports etc.

© ABB AB, Corporate Research - 6 abb Project Breakdown Structure The Project Breakdown Structure should identify all Work Products of the project and the final product. The highest level represents the total set of Work Products. At the lowest level every Work Product is either a Management Product, a Technical Product or a Quality Product.

© ABB AB, Corporate Research - 7 abb Requirement-Work Product traceability matrix X XX X XX X X X X X X Req 1 Req 2 Req 3 Req 4 Req 5 Req 6 Req 7 Req 8 Req 9 Req 10 WP 1 WP 2 WP 3 WP 4 WP 5 WP 6 WP 7 WP 8 WP 9 WP 10

© ABB AB, Corporate Research - 8 abb Management Work Products The Management Work Products are those that; Assist in project management and control issues Gives the answer to the business requirements Typical Management Work Products are; Requirement specifications Project plans Risk list Status reports Budget specification Project (gate) assessments Minutes of meetings

© ABB AB, Corporate Research - 9 abb Technical Work Products The Technical Work Products are; Project deliverables, i.e. the final product Intermediate products needed during development The answer to the technical requirements Typical Technical Work Products are; Hardware and Software User documentation Prototypes Design models Education products Testing products Executables

© ABB AB, Corporate Research - 10 abb Quality Work Products The Quality Work Products; Exists to define, assure, verify and record quality issues Gives the answer to the quality requirements Typical Quality Work Products are; Test records Inspection (review) records Error (problem) reports Follow-up reports

© ABB AB, Corporate Research - 11 abb Summary The Project Breakdown Structure is a tree structure reflecting the Work Products on all levels produced by a project. The Project Breakdown Structure should contain all the items included in the final product, needed to build the final product and needed to support the development of the final product. The Work Breakdown Structure is later identified by defining what activities are needed to produce the Work Products to the required quality.

abb

© ABB AB, Corporate Research - 13 abb Revisions Rev.New Slide (N) Slide (S) DescriptionDate Dept./Init. 04AllUpdate from Version C / Fredrik Ekdahl 05Page17Planning package should not include the work product… picture redrawn / Christer Persson

© ABB AB, Corporate Research - 14 abb Relation between PBS & WBS PBS WBS Work Product Activity Planning Package Planning Package Description What How