Module 1: Initiate a project release

When a new release or project starts, the team collaborates to define the scope, the technical vision, and the high-level release plan.

As part of the project initiation, the team must also set up the environment to support the work through the different development sprints. For efficient collaboration, team members and stakeholders must share the project resources, including design information.

Al is the owner of the JKE solution architecture. He is leading and coordinating the technical design of the system and is responsible for the major technical decisions for the software architecture.

[CLM scenario] The self-paced training focuses on collaborative design activities. Other roles and activities are involved in collaborative lifecycle management (CLM.) A requirements collection defines what to develop. A release plan defines when it will be developed. A test plan verifies the implementation and validates that the delivery meets the requirements.

Jazz.net icon Money that Matters Lifecycle Scenario on Jazz.net

Jazz.net icon Money that Matters Lifecycle Scenario roles

At the beginning of the release, Al the architect works with the product owner to prioritize the release backlog. Stories are moved up in the priority list if the team anticipates an impact on the architecture or technical uncertainties. Such planning helps to mitigate technical risk early.


Feedback