Chapter Creating the Work Breakdown Structure

If you've got a project charter and an excited customer, why go to the trouble to build a work breakdown structure After all, aren't you a software engineering professional The work breakdown structure (WBS) is the heart of a project plan, as most of the other parts of a project are built from it. The WBS is the tool used to document all the work that must be done to develop and deliver the software in a satisfactory manner. Although it may seem that the information that it contains is...

Brainstorming Dependencies and Activities

In Chapter 9 we looked at identification of the activities and tasks that might be needed in a software development project. Specifically, we saw how the 65 activities from 17 software engineering processes described in IEEE 1074 could be arranged according to a specific life cycle model to form a usable work breakdown structure. We could use those IEEE 1074 activities because the project we wanted to do fit an existing life cycle model closely enough to reuse most of the activities. But what...

Establishing Reporting Relationships

When the staffing management plan has been started and assignment of people to roles has been done, the project manager can then define the reporting relationships expected to carry out the project's activities. Organizations get depicted for a software development project in many ways. The first and most obvious representation of reporting relationships is the classic organization chart. In large project organizations, these can get messy-looking if taken to the lowest levels of the...

Where People Management Skills Are Addressed

We now turn to a brief explanation of the people management skills, competencies 23 through 34. Each competency will be introduced here to serve as a roadmap and as a review guide. The chapters in this handbook that more fully describe each competency are forward referenced in Table 1-5. We want to emphasize the competencies necessary to select and build a project team, infuse the team members with enthusiasm, encourage them through difficult issues, and help each member plan a career to ensure...

Setting Boundary Conditions

It is usually easier for a project team to identify what the software project should include than what it should of include. The goal and objectives statements describe what is to be part of the final project scope. What is often harder to describe is what it will not include, but this is absolutely necessary to help define the edges of the project scope. Later, preparation of the SRS will detail the contents of what is included more finely. Use the Is Is Not technique to help draw crisp...

Brief Description of People Management Skills

People competencies 23 through 34 are briefly described in the following sections. People Competency 23 Appraising Performance Evaluating Teams to Enhance Performance How do you know if your team is performing well as a team and not just as a group of individuals In addition to constant project tracking to ensure the team is meeting milestones and delivering project artifacts, it is important to ask them how they think they are doing. When a team is in the performing stage, players should have...

The WBSDecomposing a Project into Tasks

Creating the Work Breakdown Structure, that a WBS is a description of the work to be performed, broken downinto key elements or tasks. A task may be managerial, administrative, integral, or developmental. By partitioning the project into these manageable pieces, each element, or task, may be sized and its effort (expressed in person hours, weeks, months, etc.) may be estimated. The WBS identifies tasks at a level useful in locating available staff with the proper skills....

PHklEci Humeeme Nt

Shafer, Linda I. Safer Publisher Prentice Hall PTR Pub Date January 24, 2002 ISBN 0-13-091297-2 Pages 1677 Drawing on best practices identified at the Software Quality Institute and embodied in bodies of knowledge from the Project Management Institute, the American Society of Quality, IEEE, and the Software Engineering Institute, Quality Software Project Management teaches 34 critical skills that allow any manager to minimize costs, risks, and time-to-market....

Goal of Sei Cmm Level Key Process Area KPA Software Project Planning PP

Software estimates are documented for use in planning and tracking the software project. Ability to Perform, associated with KPA PP, Goal 1 Ability 4. The software managers, software engineers, and other individuals involved in the software project planning attained in the software estimating and planning procedures applicable to their areas of responsibility. Activity 10. Estimates for the software project's effort and costs are derived according to a documented procedure. This procedure...

Developing the Project Staffing Management Plan

As resource assignments that consider job and team fit, career plans, and project needs are made to activities in the WBS, a project-staffing plan takes shape. Typically, this information is entered into a project management scheduling tool, such as Microsoft Project or an equivalent, and a staffing plan can start to be generated. Ultimately, this information becomes part of the software project management plan (SPMP), discussed elsewhere. The staffing plan will show how many of each role the...

Project Competency Building a Work Breakdown Structure Building a WBS for a Project

The backbone of any project is the work breakdown structure (WBS). It describes the steps necessary to carry out the project and their relationship to each other. Not as straightforward as it first appears, there is an art to creating a good WBS that is useful and usable. Chapter 8, Creating the Work Breakdown Structure, andChapter 9, Identifying the Tasks and Activities, describe the project management skill of creating a WBS. The material in Chapter 4, Selecting Software Development Life...

Adapting Life Cycle Activities for Common Situations

IEEE 1074 provides a set of 17 processes and 65 activities that software projects may need to carry out the work of software engineering organized by where they fit in the basic product development life cycle that serves as our map (Figure 4-1). These are shown inTable 9-1. which is a tabular form of Figure 4-1, with activities added. The 34 competencies that every software project manager should know directly relate to the 65 software development project activities shown, and they are...

The Waterfall Software Development Life Cycle Model

The classic waterfall model, despite recent bad press, has served the software engineering community well for many years. Understanding its strengths and flaws improves the ability to assess other, often more effective life cycle models that are based on the original. In the earliest days of software development, code was written and then debugged. It was common to forego planning altogether and, starting with a general idea of the product, informally design, code, debug, and test until the...

IEEE Process Map for Software Life Cycle Process

IEEE 1074 provides a process for creating a software life cycle process (SLCP). The SLCP is defined as the project-specific description of the process that is based on a project's software life cycle (SLC) and the integral and project management processes used by the organization. These integral processes include configuration management, metrics, quality assurance, risk reduction, and the acts of estimating, planning, and training. It is primarily the responsibility of the project manager and...