The information you provide here will be shown on the wizard completion certificate which you can download at the end of this wizard and then upload it to your Trim folder.
Does your release change business processes involving external agencies?
Do the required man-hours needed for the release exceed the minimum Type 1 release threshold?
Does the release cover any new requirements or does it cover changes made to any existing requirements?
This SDLC track covers Type 1 releases which depending on the business area could cover specific release sizes and labels (i.e. in Information and Technologies and Human Resources Branches, it is mapped to Major releases and in Finance Branch, it is mapped to Projects as “Table 6 - release sizes and size mappings for different areas of the organization” illustrates).
This track starts from the Needs stage and ends at the Deployment stage and accordingly, such releases will require the artefacts and controls highlighted in all the included stages.
NOTE: For Type 1 releases, it’s mandatory to go through the Transition Process and the Validation Process in the Deployment stage to ensure the benefits of the solution are fully realized.
This SDLC track covers Type 2 releases which depending on the business area could cover specific release sizes and labels (i.e. in Information and Technologies and Human Resources Branches, it is mapped to Minor releases and in Finance Branch, it is mapped to Major/Significant releases as “Table 6 - release sizes and size mappings for different areas of the organization” illustrates).
This track starts from the Requirements stage and ends at the Deployment stage and accordingly, such releases will require the artefacts and controls highlighted in all the included stages.
This SDLC track covers Type 3 releases which depending on the business area could cover specific release sizes and labels (i.e. in Information and Technologies and Human Resources Branches, it is mapped to Maintenance/Big Fix releases and in Finance Branch, it is mapped to Minor, Emergency, Adhoc releases as “Table 6 - release sizes and size mappings for different areas of the organization” illustrates).
This track starts from the Analysis and Design Stage and ends at the Deployment stage and accordingly, such releases will require the artefacts and controls highlighted in all the included stages.
NOTE: The important aspect of Type 3 releases is that with them, the requirements do not change. The goal of such releases is to fix issues and problems and ensure the requirements are fulfilled properly, rather than implementing new requirements.
NOTE: In majority of cases, practically, the work to fix bugs and/or do maintenance work starts from the Implementation stage, however, there are also cases where in order to fix a persistence issue, the design should be changed accordingly. That’s why a more inclusive scenario has been selected for this release type. Obviously, if the design is not changed, then some of the processes in this stage can be skipped even though processes like “System Analysis Process” and “Iteration Planning Process” may still be applicable.
Figure 10 – SDLC Stages in a Type 3 Release Track
The lesser of...
Select most appropriate consequence sub-category:
Check if any risk factors are applicable (optional)
Check if any of these are applicable to your situation:
Please verify your information below.
