Work Breakdown Structure, Statement Of Work And Project Charter-Introduction to Software Engineering-Lecture Slides, Slides of Software Engineering

Download Work Breakdown Structure, Statement Of Work And Project Charter-Introduction to Software Engineering-Lecture Slides and more Slides Software Engineering in PDF only on Docsity! Work Breakdown Structure (WBS), Statement Of Work (SOW), & Project Charter docsity.com Planning, Estimating, Scheduling  What’s the difference?  Plan: Identify activities. No specific start and end dates.  Estimating: Determining the size & duration of activities.  Schedule: Adds specific start and end dates, relationships, and resources. docsity.com WBS  A deliverable-oriented grouping of project elements that organizes and defines the total scope of the project work.  Work not in the WBS is not in scope of the project.  Each descending level represents an increasingly detailed description of the project elements.  Often used to develop or confirm a common understanding of project scope.  It provides a framework for the rest of your project planning  It helps ensure that all project work is included in the plan  It promotes accurate estimation and objective measurement  You can apply past experience by comparing new and old WBSs docsity.com Project Planning Tasks Related to the WBS Modify the Software Management Plan/ Product Plan Identify deliverables and dependencies Identify development and/or acquisition strategy Define management and technical approaches Estimate product size, effort, and cost Develop the work schedule Develop the Work Breakdown Structure (WBS) Define the organization and resources needed Develop management strategies (e.g., Risk, DM, M&A, Training, and Stakeholders Write the Software Management Plan/Product Plan* Iterate on these steps The blue boxes contribute to your WBS docsity.com Work Breakdown Structure: WBS  Hierarchical list of project’s work activities  2 Formats  Outline (indented format)  Graphical Tree (Organizational Chart)  Uses a decimal numbering system  Ex: 3.1.5  0 is typically top level  Includes  Development, Mgmt., and project support tasks  Shows “is contained in” relationships  Does not show dependencies or durations docsity.com Partitioning Your Project  You need to decompose your project into manageable chunks  ALL projects need this step  Divide & Conquer  Two main causes of project failure  Forgetting something critical  Ballpark estimates become targets  How does partitioning help this? docsity.com WBS  List of Activities, not Things  List of items can come from many sources  SOW, Proposal, brainstorming, stakeholders, team  Describe activities using “bullet language”  Meaningful but short labels  All WBS paths do not have to go to the same level  Do not plan more detail than you can manage docsity.com Work Packages  Generic term for discrete tasks with definable end results  Typically the “leaves” on the tree  The “one-to-two” rule  Often at: 1 or 2 persons for 1 or 2 weeks  Basis for monitoring and reporting progress  Can be tied to budget items (charge numbers)  Resources (personnel) assigned  Ideally shorter rather than longer  Longer makes in-progress estimates needed  These are more subjective than “done”  2-3 weeks maximum for software projects  1 day minimum (occasionally a half day)  Not so small as to micro-manage docsity.com PBS WBS OBS Product Breakdown Structure Work Breakdown Structure Organizational Breakdown Structure WHAT? HOW? WHO? Breakdown Structures docsity.com Steering Fuel Odometers Wipers Lights • • Fenders Roof Hoods Doors Windows • • Front Seats Back Seats Radio • CAR EngineFrame Interior Controls Carburetor Cylinders Piston Cam • • • Example - PBS/What? docsity.com Project DesignRqmts Build DeliverManage Plan Execute Control Close • • Assess Determine Analyze Propose • • Engineer Specify • • • Construct Test Validate Integrate • • • Install Train • • • Example - WBS/How? docsity.com WBS Types  Process WBS  Activity-oriented  Ex: Requirements, Analysis, Design, Testing  Typically used by PM  Product WBS  Entity-oriented  Ex: Financial engine, Interface system, DB  Typically used by engineering manager  Hybrid WBS: both above  This is not unusual  Ex: Lifecycle phases at high level with component or feature-specifics within phases  Rationale: processes produce products docsity.com Product WBS Intranet oasaaeeannaenaans | Web Site Design Home Page Design _ Marketing Pages Sales Pages . Site Map _ Graphic Design Programs . Hyperlinks Hyperlinks Hyperlinks docsity.com  Intranet Level 0 - Entire Project Project Web Site Web Site Concept Design Development Roll Out Support Evaluate Define Define Define Develop Brief Web Development Current Requirements Specific Risks & Risk project Plan Team Leveli2 Systems Functionality Management Approach Define Server Owner Requirements Define User Define Content Define System Requirements Requirements Requirements WBS Outline Example 0.0 Retail Web Site 1.0 Project Management 2.0 Requirements Gathering 3.0 Analysis & Design 4.0 Site Software Development 4.1 HTML Design and Creation 4.2 Backend Software 4.2.1 Database Implementation 4.2.2 Middleware Development 4.2.3 Security Subsystems 4.2.4 Catalog Engine 4.2.5 Transaction Processing 4.3 Graphics and Interface 4.4 Content Creation 5.0 Testing and Production docsity.com Wea otro mets iad 2) Ble Edt View Insert Format Tools Project Window Help SHE GRY SOAS 9 OO H% HO OCH weer Task Name rer_| January _| February March | _—_Aprit__| j2t Jas] 4 [1a [isosy 1 [8 [1s]22[ 4 [8 [is]22yos[s [i2tis]2613 rH =| Concept —_——v Evaluate curren ns B > Define Requirements oy ia ih Define user requireme Define content require S em requirements b er owner requirer nents i Define specific functionality i Define risk S ana 1ent approach 6b 1 2 3 4 5 6 7 8 9 aa As f Ie A188 i a p : | ‘ Web Site Design —v * Web Site Development * Roll Out * Support Benefits of the WBS WBS Estimates Schedule Project Plan Risk and Contingency Plans Progress Reports Activity List Risk Control Project Control Change Control Communication Control docsity.com WBS Techniques  Analogy  Base WBS upon that of a “similar” project  Use a template  Analogy also can be estimation basis  Pros  Based on past actual experience  Cons  Needs comparable project docsity.com WBS Techniques  Brainstorming  Generate all activities you can think of that need to be done  Group them into categories  Both Top-down and Brainstorming can be used on the same WBS  Remember to get the people who will be doing the work involved (buy-in matters!) docsity.com Brainstorming all work to be done and then grouping into a hierarchy. Bottom Up Using a general-to- specific structure to progressively detail the work. Top Down Common Approaches docsity.com Bottom Up 18 Step 1 - TIPS  Sit down and participate as a peer.  Have someone else write on the board.  Encourage starting with a verb.  Don’t correct or worry about wording.  Capture all phrases, thoughts.  Explanation not required. docsity.com Bottom Up 19E - 2  Assessment  Review, Research, Collect, Analyze, Assess, Determine, Identify  Requirements  Define, Describe, Design, Develop work activities, Choose, Obtain, Prepare, Approve  Construction  Construct, Build, Write, Obtain, Create  Validation  Validate, Pilot, Check, Test  Implementation  Implement, Move, Train, Replace, Evaluate Useful Brainstorming Verbs docsity.com Bottom Up 20 2. Organize the “to-do” list.  Back at a desk have someone organize the list.  Take very detailed, but related steps and group them into tasks. Name the task.  Take related tasks and group them into activities. Name the activity.  Group activities into phases. docsity.com Bottom Up 22 Step 3 - TIPS  Constrain Level of Detail  Lowest level should be completed in approximately 1-3 weeks.  Lowest level should contain a definition that includes the detailed steps. docsity.com Bottom Up 23 4. Verify Correctness /Completeness At the lowest level you should be able to:  Name all the work packages;  e.g. scope definition document,  code specification #1,  painted exterior.  Indicate Dependencies.  Apply approximate duration.  Assign a resource role;  e.g. carpenter, tester. docsity.com Bottom Up 24 4. Common Obstacles  Discussing or setting requirements.  Talking about solutions rather than the work.  Wanting to sequence and assign resources too early.  Level of detail issues.  Other issues. docsity.com =-5> OF A\QeeHadlse E eetoanel System Development Life Cycle (SDLC) provides a common framework of life cycle management practices, It structures the IT application acquisition, enhancement, and development processes. Provides a road map to follow and to assure that all the needed elements are addressed. It This graphic document demonstrates how the Life Cycle Phases are aligned with and overlap Project Management Phases, SDLC PMO Graphic 04-10-2006 SDLC Framework 03-2006 This document provides a System Development Life Cycle (SDLC) frarnework to be used for IT application acquisition, enhancement, and development. Life Cycle Models Life Cycle Model Templates WBS Schedule Life Cycle Templates Templates Templates Application Acquisition Life Cycle 11-1-2005 Excel MS Project MS _ Word Feasibility Study Life Cycle 11-1-2005 Excel MS Project oO Word po Application Development 11-1-2005 _ fel | betes Project MS Word ae System Maintenance Life Cycle 11-1-2005 Excel MS Project MS Word Traditional New Development 11-1-2005 Excel MS Project MS Word Examples thd ¥ docsity.com Top Down Start at the top of a model - Deliverables 28  Verify deliverables represent the major phases of your project,  Verify purpose/need of each major deliverable or phase,  Determine if a previous project completed a major deliverable, e.g. Feasibility.  Choose to: eliminate or modify deliverable after review of previous completed work 2. Verify highest level phases/deliverables docsity.com Note* This step’s question means - different levels of decomposition are appropriate for each of the major deliverables/phases. Top Down “Yes” Decisions Guidelines 29 3. Can adequate estimates be made at this level?  Can it be completed within a 2 – 3 week period?  Adequate may change over the course of the project.  Estimating a major work package that will be produced 6 – 12 months out may not be possible. docsity.com Top Down • Requires more up front discussion. • Terminology & structure can get in the way. • Decreases participation. • Slower to start. Lesson Learned Bottom Up • Easy to start. • No terminology issues. • Higher participation. • What do we do with this? docsity.com What’s Next?  Briefly describe each item  Reference by number  List associated activities  List milestones  List other information needed to facilitate work Further decomposition into a WBS Dictionary docsity.com WBS – Basis of Many Things  Network scheduling  Costing  Risk analysis  Organizational structure  Control  Measurement docsity.com Closing The greatest benefit of developing a work breakdown structure is providing a common understanding of all the work required to deliver the product or service. docsity.com Reading Task docsity.com Statement of Work (SOW)  A description of the work required for the project  Sets the “boundary conditions”  SOW vs. CSOW (Contract SOW)  Latter: uses legal language as part of a competitive bidding scenario  Can be used in the final contract – be careful, be specific, be clear docsity.com Project Charter  A high-level project description:  Business need, product, assumptions  Often precedes SOW  Often 2-4 pages (can be longer) docsity.com Project Charter  Typical outline  Overview  Business need  Objectives  Method or approach  General scope of work  Rough schedule & budget  Roles & responsibilities  Assumptions docsity.com Homework Assignment Write a Project Charter for your project Combines elements of an SOW 2-3 pages Use format of your choice but outlined as below Graded on content, not format docsity.com Charter Examples Primary Stakeholders (following examples are not of one set)  Sponsor: VP of Marketing  Sponsor: Five Star Brokerage Consortium  Sponsor: Bill Smith, CEO  Users: Call center operators  Users: Our partner banks  Customers: Attorneys from small-to-mid size law firms  Customers: Males 30-45 earning $75K or more docsity.com Charter Examples Deliverables  Retail Web Site  Full catalog  Shopping-cart system  Search engine  User registration system  Trading System  Equities order entry system  Portfolio management  Order execution engine  Integration with X legacy systems  Security infrastructure docsity.com Charter Examples Deliverables  Corporate Application  Network and hardware  Web-based HR portal  Connectivity for VPN  “Asset Management Viewport” application  Customized Reporting Engine  Allowing users to Peruses data mart  Delivery into HTML and Excel  User manuals docsity.com