OpenUP/OpenUP_baseline_EN/exported_HTML_0_9/openup_basic/capabilitypatterns/transition_phase_iteration/content.html - epf/org.eclipse.epf.nl-libraries - Git at Google

 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
 <!-- VERSION rmc:7.1.0 -->
 <html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
 <!-- START NON-TRANSLATABLE -->
 <title>\openup_basic\capabilitypatterns\transition_phase_iteration\content.xmi</title>
 </head>
 <!-- WARNING: do not modify the generated comments in this file below this line.  They are used as markers for the import process. -->
 <body>
 Element Name: content.xmi<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: presentationName<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:presentationName,_0rQRgMlgEdmt3adZL5Dmdw CRC: 3311363436 -->Transition Phase Iteration<!-- END:presentationName,_0rQRgMlgEdmt3adZL5Dmdw -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: briefDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:briefDescription,_0rQRgMlgEdmt3adZL5Dmdw CRC: 1589840480 -->This iteration template defines the activities (and associated roles and work  products) performed in a typical iteration in the Transition phase. Each activity  and the related goals are described.<!-- END:briefDescription,_0rQRgMlgEdmt3adZL5Dmdw -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: mainDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:mainDescription,_mtb-__L5Edm6Nvont3uinw CRC: 875220565 --><h3> Introduction&nbsp; </h3>
 <p> In the Transition phase,
   most activities happen in parallel. The main objectives are to fine-tune functionality,
   performance, and overall quality of the beta product from
   the end of Construction phase. </p>
 <p> The activities performed in a typical iteration during
   the&nbsp;Transition phase are described below. </p>
 <h4> Manage iteration </h4>
 <p> This activity is performed throughout the lifecycle. The goal of this activity
   is to identify risks and issues early enough that they can be mitigated, to
   establish the goals for the iteration, and to support the development team in
   reaching these goals. </p>
 <p> Similar to other phases, this is an activity led by the <a class="elementlinkwithusertext" href="./../../openup_basic/roles/project_manager,_0a0o0MlgEdmt3adZL5Dmdw.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">project
   manager</a> (in collaboration with the team) to launch the iteration, to allocate
   work, to track status, and to handle risks and issues. It’s unlikely that risks
   of high impact will happen during the Transition, but it is recommended that
   the project manager and team identify any potential issues&nbsp;while delivering
   the product to the end users. </p>
 <p>If this is the last iteration of the project, the main goal is to achieve final
   acceptance of the system. At the end of the iteration, results are assessed
   against phase objectives<em>,</em> and <a class="elementlinkwithusertext" href="./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">stakeholders'</a>
   concurrence on the project objectives is obtained. The team conducts a retrospective
   review to capture lessons learned and make improvements to the process for subsequent
   <strong> </strong>projects. The project is then closed.</p>
 <h4>Ongoing tasks </h4>
 <p> Submission of change requests during the Transition phase <strong></strong>works&nbsp;differently
   than in other phases. New requirements will rarely be identified at late stages
   of the software development lifecycle in a way they can be implemented in the
   current release. If there are enhancement requests, though, they can be captured
   in the <a class="elementLinkWithUserText" href="./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">work
   items list</a> and allocated to a future release, when a new software development
   lifecycle begins. In that case, requirements will be outlined and detailed accordingly.
 </p>
 <p> However, defects are typically dealt with during the Transition phase,&nbsp;thus
   a stable release can be accepted by the user community. If there is general
   agreement from stakeholders, correction of low-priority defects can be postponed
   to subsequent evolutionary releases. </p>
 <h4> Develop solution for requirement within context</h4>
 <p> This activity is repeated multiple times, in parallel, for each development
   task planned for that iteration. The main goal of this activity is an executable
   system that provides the incremental quality and functionality for the specified
   requirements within the specified context. </p>
 <p> During the Transition phase, most requirements will have been already implemented
   and validated, which is the focus of the previous phase. Nevertheless, there
   may be a few low-priority requirements that could be accommodated in the release
   being developed. However, enhancement requests and defects found in previous
   iterations may need to be allocated to <a class="elementlinkwithusertext" href="./../../openup_basic/roles/developer,_0YDosMlgEdmt3adZL5Dmdw.html" guid="_0YDosMlgEdmt3adZL5Dmdw">developers</a>.
 </p>
 <h4> Validate build </h4>
 <p> This activity is repeated throughout the lifecycle. The main goal of this
   activity is to validate the current increment of the system against the requirements
   allocated to it. </p>
 <p> This activity happens in parallel with development of the
   solutions for enhancement requests and defects
   (and possibly remaining requirements), to make sure that
   a stable release can be presented to the user community. Users can be involved
   in performing <a class="elementLinkWithUserText" href="./../../openup_basic/capabilitypatterns/test,_0nz79clgEdmt3adZL5Dmdw.html" guid="_0nz79clgEdmt3adZL5Dmdw">tests</a>
   to accept the release. </p>
 <h4><!-- END:mainDescription,_mtb-__L5Edm6Nvont3uinw -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: presentationName<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:presentationName,_0q33AclgEdmt3adZL5Dmdw CRC: 1824416172 -->Plan and Manage Iteration<!-- END:presentationName,_0q33AclgEdmt3adZL5Dmdw -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: presentationName<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:presentationName,_0qrpwslgEdmt3adZL5Dmdw CRC: 79270194 -->Validate Build<!-- END:presentationName,_0qrpwslgEdmt3adZL5Dmdw -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: presentationName<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:presentationName,_0qxwYclgEdmt3adZL5Dmdw CRC: 642658025 -->Ongoing Tasks<!-- END:presentationName,_0qxwYclgEdmt3adZL5Dmdw -->
 </body>
 </html>
	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
	<!-- VERSION rmc:7.1.0 -->
	<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
	<!-- START NON-TRANSLATABLE -->
	<title>\openup_basic\capabilitypatterns\transition_phase_iteration\content.xmi</title>
	</head>
	<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
	<body>
	Element Name: content.xmi<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: presentationName<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:presentationName,_0rQRgMlgEdmt3adZL5Dmdw CRC: 3311363436 -->Transition Phase Iteration<!-- END:presentationName,_0rQRgMlgEdmt3adZL5Dmdw -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: briefDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:briefDescription,_0rQRgMlgEdmt3adZL5Dmdw CRC: 1589840480 -->This iteration template defines the activities (and associated roles and work products) performed in a typical iteration in the Transition phase. Each activity and the related goals are described.<!-- END:briefDescription,_0rQRgMlgEdmt3adZL5Dmdw -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: mainDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:mainDescription,_mtb-__L5Edm6Nvont3uinw CRC: 875220565 --><h3> Introduction  </h3>
	<p> In the Transition phase,
	most activities happen in parallel. The main objectives are to fine-tune functionality,
	performance, and overall quality of the beta product from
	the end of Construction phase. </p>
	<p> The activities performed in a typical iteration during
	the Transition phase are described below. </p>
	<h4> Manage iteration </h4>
	<p> This activity is performed throughout the lifecycle. The goal of this activity
	is to identify risks and issues early enough that they can be mitigated, to
	establish the goals for the iteration, and to support the development team in
	reaching these goals. </p>
	<p> Similar to other phases, this is an activity led by the <a class="elementlinkwithusertext" href="./../../openup_basic/roles/project_manager,_0a0o0MlgEdmt3adZL5Dmdw.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">project
	manager</a> (in collaboration with the team) to launch the iteration, to allocate
	work, to track status, and to handle risks and issues. It’s unlikely that risks
	of high impact will happen during the Transition, but it is recommended that
	the project manager and team identify any potential issues while delivering
	the product to the end users. </p>
	<p>If this is the last iteration of the project, the main goal is to achieve final
	acceptance of the system. At the end of the iteration, results are assessed
	against phase objectives<em>,</em> and <a class="elementlinkwithusertext" href="./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">stakeholders'</a>
	concurrence on the project objectives is obtained. The team conducts a retrospective
	review to capture lessons learned and make improvements to the process for subsequent
	<strong> </strong>projects. The project is then closed.</p>
	<h4>Ongoing tasks </h4>
	<p> Submission of change requests during the Transition phase <strong></strong>works differently
	than in other phases. New requirements will rarely be identified at late stages
	of the software development lifecycle in a way they can be implemented in the
	current release. If there are enhancement requests, though, they can be captured
	in the <a class="elementLinkWithUserText" href="./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">work
	items list</a> and allocated to a future release, when a new software development
	lifecycle begins. In that case, requirements will be outlined and detailed accordingly.
	</p>
	<p> However, defects are typically dealt with during the Transition phase, thus
	a stable release can be accepted by the user community. If there is general
	agreement from stakeholders, correction of low-priority defects can be postponed
	to subsequent evolutionary releases. </p>
	<h4> Develop solution for requirement within context</h4>
	<p> This activity is repeated multiple times, in parallel, for each development
	task planned for that iteration. The main goal of this activity is an executable
	system that provides the incremental quality and functionality for the specified
	requirements within the specified context. </p>
	<p> During the Transition phase, most requirements will have been already implemented
	and validated, which is the focus of the previous phase. Nevertheless, there
	may be a few low-priority requirements that could be accommodated in the release
	being developed. However, enhancement requests and defects found in previous
	iterations may need to be allocated to <a class="elementlinkwithusertext" href="./../../openup_basic/roles/developer,_0YDosMlgEdmt3adZL5Dmdw.html" guid="_0YDosMlgEdmt3adZL5Dmdw">developers</a>.
	</p>
	<h4> Validate build </h4>
	<p> This activity is repeated throughout the lifecycle. The main goal of this
	activity is to validate the current increment of the system against the requirements
	allocated to it. </p>
	<p> This activity happens in parallel with development of the
	solutions for enhancement requests and defects
	(and possibly remaining requirements), to make sure that
	a stable release can be presented to the user community. Users can be involved
	in performing <a class="elementLinkWithUserText" href="./../../openup_basic/capabilitypatterns/test,_0nz79clgEdmt3adZL5Dmdw.html" guid="_0nz79clgEdmt3adZL5Dmdw">tests</a>
	to accept the release. </p>
	<h4><!-- END:mainDescription,_mtb-__L5Edm6Nvont3uinw -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: presentationName<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:presentationName,_0q33AclgEdmt3adZL5Dmdw CRC: 1824416172 -->Plan and Manage Iteration<!-- END:presentationName,_0q33AclgEdmt3adZL5Dmdw -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: presentationName<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:presentationName,_0qrpwslgEdmt3adZL5Dmdw CRC: 79270194 -->Validate Build<!-- END:presentationName,_0qrpwslgEdmt3adZL5Dmdw -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: presentationName<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:presentationName,_0qxwYclgEdmt3adZL5Dmdw CRC: 642658025 -->Ongoing Tasks<!-- END:presentationName,_0qxwYclgEdmt3adZL5Dmdw -->
	</body>
	</html>