This represents ongoing project management activities, including the following workflow details:

• Manage the Iteration
• Monitor and Control Project

On this small project, the Project Manager is also the Test Manager, so this task also includes:

• Achieve Acceptable Mission (activities: Assess and Advocate Quality, Assess and Improve Test Effort)
  

The principal output artifacts are:

• Review Records
• Iteration Assessment
• Status Assessment

Next Iteration Planning

This includes workflow details:

• Plan for Next Iteration
• Develop Software Development Plan (optional, depending on scope of change)
• Define Evaluation Mission (Test Manager related activities)

The principal output artifacts are:

• Iteration Plan - updated based on what new functionality is to be added during the new iteration, factoring in the current level of product maturity, lessons learned from the previous iterations, and any risks that need to be mitigated in the upcoming iteration)
• Software Development Plan - all subplans updated as required to reflect changes in scope and risk. The Risk List in particular must be revisited if there are significant remaining risks
• Test Plan - updated to reflect the mission for the next iteration's testing.

The results of status assessments and iteration assessments should be considered in determining if any changes to process and tools are necessary.

Manage Changing Requirements

Requirements discovery and refinement is shown as complete at this stage, the remaining effort relating entirely to the management of change.

Refine the Architecture

The Software Architect has an ongoing task, which lessens as the project matures, to make any necessary changes to the software architecture.

The relevant workflow detail is Refine the Architecture.

Integration and Test Support

Maintaining the build environment, selecting and running regression tests on builds, is an ongoing task.

The relevant workflow details are:

• Validate Build Stability
• Manage Baselines and Releases

Develop Components/Features

• Component/Feature A
• and so on

• Design Components (or Design the Database)
• Implement Component
• Integrate the System
• Test and Evaluate
• Improve Test Assets

Other tasks may design and implement components that then support multiple features, use cases, or scenarios.

Large tasks (more than a couple of weeks) may be divided into subtasks of incremental functionality. Other large tasks may be subdivided by the principal activity being performed. For example, into:

• Design - may include some prototyping
• Implement - includes (in this small project) all unit testing
• Integrate and Test - including fixing bugs found in the new code during integration. (Bugs in existing code are covered by the Defect Fixing task).

This is the workflow detail Plan Deployment.

This task may alternatively be merged into the iteration planning that occurs at the end of the previous iteration.

The principal output artifact is an updated Software Development Plan (Deployment Plan section).

This is the workflow detail Develop Support Material.

The principal output artifact is End-User Support Material.

This is the workflow detail Manage Acceptance Test (At Development Site).

The principal output artifact is an installed and tested Product.

This is the workflow detail Produce Deployment Unit.

The principal output artifacts are:

• Installation Artifacts
• Release Notes
• Deployment Units.

This is the workflow detail Manage Acceptance Test (At Installation Site).

For this sample, the software is deployed at a customer site. Other forms of deployment are discussed as part of the Discipline: Deployment.

The principal output artifact is a Product installed and tested at the customer site.