Software Project Management Show
a. top-down b. mind mapping c. bottom-up d. Analogy Answer: B
➔Free 30-day WBS Software Trial Breaking work into smaller tasks is a common productivity technique used to make the work more manageable and approachable. For projects, the Work Breakdown Structure (WBS) is the tool that utilizes this technique and is one of the most important project management documents. It singlehandedly integrates scope, cost and schedule baselines ensuring that project plans are in alignment. The Project Management Institute (PMI) Project Management Book of Knowledge (PMBOK) defines the Work Breakdown Structure as a “deliverable oriented hierarchical decomposition of the work to be executed by the project team.” There are two types of WBS: 1) Deliverable-Based and 2) Phase-Based. The most common and preferred approach is the Deliverable-Based approach. The main difference between the two approaches are the Elements identified in the first Level of the WBS. Deliverable-Based Work Breakdown StructureA Deliverable-Based Work Breakdown Structure clearly demonstrates the relationship between the project deliverables (i.e., products, services or results) and the scope (i.e., work to be executed). Figure 1 is an example of a Deliverable-Based WBS for building a house. Figure 2 is an example of a Phase-Based WBS for the same project. Figure 1 – Deliverable Based Work Breakdown Structure In Figure 1, the Level 1 Elements are summary deliverable descriptions. The Level 2 Elements in each Leg of the WBS are all the unique deliverables required to create the respective Level 1 deliverable. Phase-Based Work Breakdown StructureIn Figure 2, a Phase-Based WBS, the Level 1 has five Elements. Each of these Elements are typical phases of a project. The Level 2 Elements are the unique deliverables in each phase. Regardless of the type of WBS, the lower Level Elements are all deliverables. Notice that Elements in different Legs have the same name. A Phase-Based WBS requires work associated with multiple elements be divided into the work unique to each Level 1 Element. A WBS Dictionary is created to describe the work in each Element. Figure 2 - Phase Based Work Breakdown Structure A good WBS is simply one that makes the project more manageable. Every project is different; every project manager is different and every WBS is different. So, the right WBS is the one that best answers the question, “What structure makes the project more manageable?”. How to Make a Work Breakdown StructureA good Work Breakdown Structure is created using an iterative process by following these steps and meeting these guidelines:
Caution: It is possible to break the work down too much. How much is too much? Since cost and schedule data collection, analysis and reporting are connected to the WBS, a very detailed WBS could require a significant amount of unnecessary effort to manage. There are many WBS software tools available. Some of them are based on mind mapping and others are drawing tools. You can read about these tools in this WBS software review. Here is an example of how to make a WBS with MindView: How to Use a Work Breakdown StructureThe Work Breakdown Structure is used for many different things. Initially, it serves as a planning tool to help the project team plan, define and organize scope with deliverables. The WBS is also used as the primary source of schedule and cost estimate activities. But, its biggest contributions to a project are is use as a description all of the work and as a monitoring and controlling tool. Work Packages Planning Packages Figure 3 – WBS Work Packages and Control Accounts Control Accounts Create a WBS with the MindView software free trial. Check it out.Related Links:Software Project Management a. top-down b. mind mapping c. bottom-up d. Analogy Answer: B Which of the following is not a suggestion for improving user input? a. Develop a good project selection process for IT projects. b. Have users on the project team. c. Co-locate users with developers. d. Only have meetings as needed, not on a regular basis.
Which of the following is not a suggestion for improving user input? a. Develop a good project selection process for IT projects. b. Have users on the project team. c. Co-locate users with developers. d. Only have meetings as needed, not on a regular basis. |