ProjectConnections Print View
888-722-5235
7am-5pm Pacific
Monday - Friday
We'd love to talk to you.
Learn more about ProjectConnections and who writes our content.
Site Help
| Content Levels | |
 | Register for free access to papers, case studies, and almost 50 templates. |
 | Subscribe for complete access: $14.95 monthly or $149/year |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Software Release Life Cycle - Phase 3: Planning and Negotiation
Quick Summary
Recommended deliverables for the planning and negotiation phase of a Software Release Life Cycle.
What this is
This document covers Phase 3 of a Software Release Life Cycle. It includes a one-to-two page description of recommended deliverables for this phase.
The Negotiation and Planning phase is focused on bringing a full release team together, based on the desired release scope defined in the Phase 2 preliminary plans. The team will continue to plan the release, bringing individual project information into a set of master plans that encompass the entire package of the release Scheduling of specific resources, time, equipment, money, etc. are all combined and various final trade-offs are made between scope, quality and time. Elements may be dropped from the release scope at this point by necessity.
The Release Vision document is created and iteratively updated during the phase to reflect final release scope decisions as tradeoffs are made. The Vision helps ensures the release will meet the needs of the customers and their quality expectations.
The SW architecture is completed to document what is required technically to meet the Release Vision, and is referenced by the entire team and by individual projects.
The detailed project plan is created, and the associated budget is formalized and approved.
Why it's useful
This phase provides the opportunity for all the various threads of development and production to come together under one master release plan. This plan includes the total budget, the total resource allocation, the high-level view of the total architecture, etc. The final release scope cannot be decided until some of the project-level work plans and estimates are available. This phase provides a construct for bringing that info together to make final decisions.
How to use it
Review the deliverables suggested in this document (See Checklist). Adjust for your particular organization, project type, or company.
Perform the activities described in those deliverables. See the Software Release Life Cycle Team Member Glossary if you have questions about the roles listed as Driver and Contributor for a deliverable.
At the end of this phase, you will be prepared for Phase 4, Release Plan Refinement. Phase 3 generates the initial detailed release plan for development work. During phase 4 the team will refine the testing aspects of the plan, as the individual projects get far enough along for that information to be available.
©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy