Releasing the project
The activities involved in a project depend on the software's complexity, the team's distribution, and the organization's processes. Smaller projects may simply involve building the software, updating the installation and user documentation, and then shipping it to the customer. Complex projects may involve iteratively building a multitude of components until approved by QA branching the code, creating the installation and user documentation, creating demo data for the users, tuning for performance based on deployment, and concluding with a discussion of lessons learned and best practices.
As we have already seen, Rational Team Concert allows us to create releases right from the build results. In our case, we are working on Sprint–2 and we can probably release the project once all the work items are closed on Sprint–1, Sprint–2, and Release Backlog. Notice that Sprint–1 and Sprint–2 are attached to the release plan Release–1. To do a quick reality check of the release...
