Inputs to Create WBS PDF

Preview

Summary

Download Inputs to Create WBS PDF

Description

5/1/2020

Skillsoft Course Transcript

Inputs to Create WBS Learning Objective After completing this topic, you should be able to identify inputs to the Create WBS process

1. [Topic title: Inputs to Create WBS] To create a well-designed work breakdown structure, you first need to analyze a range of inputs. Remember, processes completed during a project build on each other, so outputs from the initiating and planning processes become inputs for the create WBS process. [Project Scope Statement.] The first input is the detailed project scope statement, which contains six elements. The product scope description, which details all the features and functions a product must have. The project deliverables, which details all the work that needs to be done to complete the project. The product acceptance criteria, which outline the requirements the project must meet before stakeholders accept the final product or service. Project constraints, which specify the limitations and restrictions the project faces. Project assumptions, or the factors that are considered to be true about a project. And project exclusions, which clearly stipulate what is not included in the project. I'll give an example of a hospital management information system project, to illustrate how each one is used to create the WBS. [Product Scope Description.] By making it clear what attributes a product or service must have, the product scope description helps identify what work must go into creating project deliverables. This guides the process of breaking down deliverables in the WBS. [Project Deliverables.] The list of work that needs to be done for completion of project deliverables assists in identifying what tasks must be included in the WBS. In this case, each individual deliverable will then be broken down into smaller tasks in the WBS. For example, the deliverable of the functional requirements document could be subdivided into analyze current system, change recommendations, and write document. [Product Acceptance Criteria.] Product acceptance criteria assist in defining what goals must be met by the project before the stakeholders will give the project deliverables the stamp of approval. It also indicates what tasks must be included in the WBS to achieve these goals. In this example, when the system is able to handle these concurrent connections, transactions, and availability requirements, the stakeholders will consider the project complete. [Constraints.] Project constraints, such as imposed budgets or time limitations, will influence how you structure your WBS. For example, to ensure that the system can run over the correct speed for the modem connection, the project manager may choose to include a testing phase to ensure that the system meets this minimum standard. [Assumptions.] The WBS will be structured in accordance with project assumptions. This will, in turn, lead to certain tasks being included and excluded from the WBS. For example, if the existing infrastructure is unable to support it, the new system will be completely flawed, and thus useless. It is therefore imperative to continually reassess project assumptions to ensure their validity. [Exclusions.] Project exclusions assist in stipulating what tasks to include and exclude from the project. In this example, the points that require the system are all stationary, and therefore the manager does not have to focus on any form of system mobility. [Requirements Documentation.] The second input for the create WBS process is requirements documentation. [The new drug diagram is displayed as an example on the screen. It is divided into four https://library.skillport.com/courseware/Content/cca/apj 03 a02 bs enus/output/html/course transcript.html

7/29

5/1/2020

Skillsoft Course Transcript

quarters: Quarter 1, Quarter 2, Quarter 3, and Quarter 4. These quarters are further divided into phases. The Quarter 1 includes Research Phase which further includes Lab Work, Clinical Trials, and Market Research. The Quarter 2 includes Design Phase which further includes Package Insert, Marketing Strategy, and Factory Planning. The Quarter 3 includes Production Phase which further includes Raw Chemicals, Factory Construction, and Packaging. The Quarter 4 includes Roll Out Phase which further includes Advertising, Distribution, and Production.] This input is important because all requirements must map to specific deliverables in the WBS. [Lab Work, Package Insert, Factory Construction, and Production is highlighted under Quarter 1, 2, 3, and 4 respectively.] The more accurate the input is [All the phases are highlighted.] the more accurate the WBS will be in ensuring all requirements are met. Requirements documentation can also identify the priority of each requirement. [Research phase is at priority 1, Design phase is at priority 2, Production phase is at priority 3, and Roll Out phase is at priority 4.] This can affect how you structure the WBS. For example it may determine the order in which work on deliverables should be carried out during project execution [Again, all the phases are highlighted.] so that higher priority deliverables are completed first. You use requirements documentation to ensure that the WBS reflects stakeholder expectations for the project and its deliverables. [Scope Management Plan.] The next input to the create WBS process is the scope management plan. It provides guidance on how to create the WBS, and identifies how the WBS will be approved and maintained. Enterprise environmental factors and organizational process assets are also inputs to this process. The external factor most relevant to creating a WBS would be any industry or government standard that must be taken into account while scoping the work. [Organizational Process Assets.] Some OPAs that may provide input include existing policies and procedures, which often contain guidance for handling various aspects of projects. Existing WBS templates, which you may be able to use as is or with minor modifications. Project files and documents from previous projects, such as time schedules, costing sheets, and process guides. Which can often be reused or serve as guidelines, and may shed light on the actual complexity of activities for scheduling purposes. And lessons learned from previous similar projects, which can help project managers avoid mistakes, thereby saving time and money. In summary, the five inputs to the create WBS process are the project scope statement, requirements documentation, the scope management plan, enterprise environmental factors and organizational process assets.

https://library.skillport.com/courseware/Content/cca/apj 03 a02 bs enus/output/html/course transcript.html

8/29...