Info

B. Post-mortem summary of lessons learned

Figure 6-7. Typical release description outline

Figure 6-7. Typical release description outline

Status Assessments

Status assessments provide periodic snapshots of project health and status, including the software project manager's risk assessment, quality indicators, and management indicators. Although the period may vary, the forcing function needs to persist. The paramount objective of a good management process is to ensure that the expectations of all stakeholders (contractor, customer, user, subcontractor) are synchronized and consistent. The periodic status assessment documents provide the critical mechanism for managing everyone's expectations throughout the life cycle; for addressing, communicating, and resolving management issues, technical issues, and project risks; and for capturing project history. They are the periodic heartbeat for management attention. Section 9.3 discusses status assessments in more detail. i

Typical status assessments should include a review of resources, personnel staffing, financial data (cost and revenue), top 10 risks, technical progress (metrics snapshots), major milestone plans and results, total project or product scope, action items, and follow-through. Continuous open communications with objective data derived directly from on-going activities and evolving product configurations are mandatory in any project.

Software Change Order Database

Managing change is one of the fundamental primitives of an iterative development process. With greater change freedom, a project can iterate more productively. This flexibility increases the content, quality, and number of iterations that a project can achieve within a given schedule. Change freedom has been achieved in practice through automation, and today's iterative development environments carry the burden of change management. Organizational processes that depend on manual change management techniques have encountered major inefficiencies. Consequently, the change management data have been elevated to a first-class management artifact that is described as a database to instill the concept of a need for automation. Once software is placed in a controlled baseline, all changes must be formally tracked and managed. By automating data entry and maintaining change records on-line, most of the change management bureaucracy and metrics collection and reporting activities can be automated. Software change orders are discussed in detail in Chapter 12.

Deployment

A deployment document can take many forms. Depending on the project, it could include several document subsets for transitioning the product into operational status. In big contractual efforts in which the system is delivered to a separate maintenance organization, deployment artifacts may include computer system operations manuals, software installation manuals, plans and procedures for cutover (from a legacy system), site surveys, and so forth. For commercial software products, deployment artifacts may include marketing plans, sales rollout kits, and training courses.

Environment

An important emphasis of a modern approach is to define the development and maintenance environment as a first-class artifact of the process. A robust, integrated development environment must support automation of the development process. This environment should include requirements management, visual modeling, document automation, host and target programming tools, automated regression testing, integrated change management, and defect tracking. A common theme from successful software projects is that they hire good people and provide them with good tools to accomplish their jobs. Automation of the software development process provides payback in quality, the ability to estimate costs and schedules, and overall productivity using a smaller team. By allowing the designers to traverse quickly among development artifacts and easily keep the artifacts up-to-date, integrated toolsets play an increasingly important role in incremental and iterative development.

Management Artifact Sequences

In each phase of the life cycle, new artifacts are produced and previously developed artifacts are updated to incorporate lessons learned and to capture further depth and breadth of the solution. Some artifacts are updated at each major milestone, others at each minor milestone. Figure 6-8 identifies a typical sequence of artifacts across the life-cycle phases.

A Informal version A Controlled baseline

Inception

Elaboration

Construction

Transition

Iteration 1

Iteration 2 | Iteration 3

Iteration 4 | Iteration 5 { Iteration 6

Iteration 7

Management Set

1. Work breakdown structure A

2. Business case A

3. Release specifications A

4. Software development plan A

5. Release descriptions A

6. Status assessments

7. Software change order data

8. Deployment documents

9. Environment

Requirements Set

1. Vision document A

2. Requirements model(s) A

Design Set

1. Design model(s) A

2. Test model A

3. Architecture description A

Implementation Set

1. Source code baselines

2. Associated compile-time files

3. Component executables

Deployment Set

1. Integrated product-executable baselines

2. Associated run-time files

3. User manual

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment