Suggested deliverables (with 1-2 page descriptions of each) for the Development Tracking phase of a software release.
What this is
Suggested deliverables for the Development Tracking phase of a software release -- each with a 1-2 page deliverable description. This phase is focused on monitoring, controlling, and tracking at the release level. It is also a phase where test activities are reviewed, updated and finalized for movement of the various projects, components, sub-projects, modules, etc. into the formal Integration Phase.
Why it's useful
Things change during the development phase as the individual project teams in the release discover new information, risks are actualized and contingency plans implemented, personnel are reassigned, the market changes, etc.
Tracking these changes and integrating the new information into the release documentation will prepare the Release and the Release Team to move as smoothly as possible into the Integration Phase. Integration of large software systems can be arduous, unpredictable, influenced by many factors, and bring disaster to a projects and companies. Keeping up to date documentation and plans significantly lowers the possibilities of negative events and wasted time and lost effort in the upcoming Integration phase.
How to use it
Review the phase deliverables suggested in this document. Adjust for your particular organization, project type, or company.
Perform the activities described in the documentation for this phase. See the Checklist for documents included in this phase. NOTE: See the Software Release Life Cycle Team Member Glossary if you have questions about the roles listed as Driver and Contributor for a deliverable.
As the phase begins, allocate a certain amount of your time to monitoring all the parallel and concurrent activities on the various projects in the release. Get a feeling as to their likelihood of success.
As each project begins to move to the project teams testing their own work, the release team will need to ensure integration preparation is done in earnest. While the teams are developing their components, get much of the administration activities done early, like ensuring the integration lab has machines, software, etc.
As the phase evolves, time will become more critical and the pre-Integration reviews, plans, resources allocations, etc. will occupy much of the Release Team and Software Release Project Manager's time.
See the ProjectConnections "Checklist: Software Integration Phase Planning & Execution" for additional hints about the Integration phase that will help you understand some of the issues in the next phase.
©Copyright 2000-2017 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail email@example.com