About this task
After your team has coded the majority of the application and you have completed code freeze, you will be ready to perform selective builds. These builds will no longer include every completed task; you will want to include only specific tasks in the build.
Workflow for small and large teams
If your team is small and your application is part of a larger application, you might be the only person to determine which tasks are allowed in a build. The workflow would be similar to the following:
- Code freeze is over and the developers and testers are using the application. They find a problem that needs to be fixed in developer Joe’s area.
- Joe creates a task and assigns it to himself. He makes the fix and completes the task.
- Joe notifies Bob, his build manager, that this task needs to be included and why. Bob approves the change and manually adds it to the next scheduled build.
If your team is big and your application is a deliverable, you might work as part of a change control board to determine which tasks are necessary to deliver a quality product that meets the requirements. The flow would be similar to the following:
- Code freeze is over and SQE is testing the application. They find several problems and submit them using Rational Change.
- The program manager gives each change control board member a list of change requests from SQE, and the team decides which will be fixed.
- The build manager assigns the tasks to be fixed to his team members, and informs them of the next build date.
- When the developers have completed their assigned tasks, they notify the build manager, and the build manager manually adds the completed tasks to the build.
At this point, the build manager can add the tasks to the build in the following way.