<?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\inception_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,_0o3r4slgEdmt3adZL5Dmdw CRC: 1693890671 -->Inception Phase Iteration<!-- END:presentationName,_0o3r4slgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_0o3r4slgEdmt3adZL5Dmdw CRC: 3157703874 -->This iteration template defines the activities (and associated roles and work  products) performed in a typical iteration in the Inception phase. Each activity  and related goals are described.<!-- END:briefDescription,_0o3r4slgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: mainDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:mainDescription,_mtb-6_L5Edm6Nvont3uinw CRC: 1159950529 --><h3>
    Introduction
</h3>
<p>
    The project starts with the assumption that the business case has been created, the <a class="elementlinkwithusertext"
    href="./../../openup_basic/roles/project_manager,_0a0o0MlgEdmt3adZL5Dmdw.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">project
    manager</a> has been identified, the team (at least for the first iteration) has been defined, the development
    environment (including tools and infrastructure) is in place, and the process to be followed is the <a
    class="elementlinkwithusertext"
    href="./../../openup_basic/deliveryprocesses/openup_basic_process,_0uyGoMlgEdmt3adZL5Dmdw.html"
    guid="_0uyGoMlgEdmt3adZL5Dmdw">delivery process</a> suggested by OpenUP/Basic. The number and length of each Inception
    iteration will vary, depending upon the needs of the project.
</p>
<p>
    In the next sections we describe the activities performed in a typical iteration during Inception phase.
</p>
<h4>
    Initiate project
</h4>
<p>
    This activity takes place at the beginning of the first iteration, when the project starts. The goal of this activity
    is to establish the vision for the project and the project plan at a high level of granularity.
</p>
<p>
    The people in the roles involved at this time collaborate to perform this activity:
</p>
<ul>
    <li>
        <a class="elementlinkwithusertext" href="./../../openup_basic/roles/analyst,_0VxJsMlgEdmt3adZL5Dmdw.html"
        guid="_0VxJsMlgEdmt3adZL5Dmdw">Analyst</a> and <a class="elementlinkwithusertext"
        href="./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html"
        guid="_dTa6gMAYEdqX-s4mWhkyqQ">stakeholder</a> roles work together to define the <a class="elementLinkWithUserText"
        href="./../../openup_basic/workproducts/vision,_0WVxcMlgEdmt3adZL5Dmdw.html"
        guid="_0WVxcMlgEdmt3adZL5Dmdw">vision</a> for the project, capturing the customer needs and features for the system
        under development. Needs and features are captured to the extent required to reach agreement about the scope of the
        project.
    </li>
    <li>
        Project manager (with collaboration and agreement of team and stakeholders) proposes a high-level <a
        class="elementLinkWithUserText" href="./../../openup_basic/workproducts/project_plan,_0a6vcMlgEdmt3adZL5Dmdw.html"
        guid="_0a6vcMlgEdmt3adZL5Dmdw">project plan</a> that includes the <a class="elementLinkWithUserText"
        href="./../../openup_basic/guidances/concepts/milestones,_HNxbwMBJEdqSgKaj2SZBmg.html"
        guid="_HNxbwMBJEdqSgKaj2SZBmg">milestones</a> for the four phases and time-boxed iterations for each phase. This
        plan and the allocation of staff to the project evolve throughout the phases to reflect the project pace, as
        necessary.
    </li>
</ul>
<h4>
    Manage iteration
</h4>
<p>
    This activity is about the ongoing work performed by the project manager and the development team to initiate and
    conduct a given iteration. It consists of status reporting, handling of exceptions and problems, identifying risks, and
    reprioritizing work, as needed.
</p>
<p>
    At the end of the iteration, the project manager conducts a&nbsp;<a class="elementLinkWithUserText"
    href="./../../openup_basic/workproducts/status_assessment,_0bA2EMlgEdmt3adZL5Dmdw.html"
    guid="_0bA2EMlgEdmt3adZL5Dmdw">status assessment</a> with the development team and stakeholders.
</p>
<p>
    If the iteration end coincides with the phase end, meeting the objectives for that phase should be used as success
    criteria for leaving the iteration. The iteration assessment should verify that the objectives&nbsp;for
    the&nbsp;Iteration phase&nbsp;have been achieved, including agreement on the key functionalities and at least one
    possible solution for the system under development, as well as a reasonable understanding of cost, schedule and risks
    associated with the project.
</p>
<p>
    Based on demonstration of key functionalities and architectural feasibility during the assessment, it becomes clear
    that either the project can proceed at the given pace or that a reprioritization of work needs to happen. As a
    consequence, the project manager may need to refine the project scope and duration.
</p>
<h4>
    Manage requirements
</h4>
<p>
    This activity is first performed in the first iteration, and repeated throughout the lifecycle.&nbsp; The goal of this
    activity is to understand and prioritize stakeholder needs, and associated requirements for the system, and capture
    these in a form that will support effective communications and collaboration between the stakeholders and development
    team.
</p>
<p>
    As the project is initiated, the&nbsp;<a class="elementlinkwithusertext"
    href="./../../openup_basic/roles/analyst,_0VxJsMlgEdmt3adZL5Dmdw.html" guid="_0VxJsMlgEdmt3adZL5Dmdw">analyst</a>
    gathers <a class="elementLinkWithUserText"
    href="./../../openup_basic/guidances/concepts/requirements,_0Wh-sMlgEdmt3adZL5Dmdw.html"
    guid="_0Wh-sMlgEdmt3adZL5Dmdw">requirements</a> from&nbsp;stakeholders and captures associated&nbsp;work items&nbsp;for
    development in the <a class="elementLinkWithUserText"
    href="./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html"
    guid="_rGNWsCbSEdqh1LYUOGRh2A">work items list</a>&nbsp;to facilitate prioritization and planning. As needed,
    requirements are outlined and detailed in&nbsp;<a class="elementLinkWithUserText"
    href="./../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html"
    guid="_0VGbUMlgEdmt3adZL5Dmdw">use-case</a> specifications and <a class="elementLinkWithUserText"
    href="./../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html"
    guid="_BVh9cL-CEdqb7N6KIeDL8Q">supporting requirements</a>&nbsp;to the extent needed to provide information for the <a
    class="elementLinkWithUserText" href="./../../openup_basic/roles/architect,_0X9iEMlgEdmt3adZL5Dmdw.html"
    guid="_0X9iEMlgEdmt3adZL5Dmdw">architect</a> to create a prototype of the architecture and for the project manager to
    scope and plan the next iteration.
</p>
<h4>
    Determine architectural feasibility
</h4>
<p>
    This activity is initiated in the Inception phase and completed in the Elaboration phase. The goal of this activity is
    to establish an architecture for the system that provides the high-level design that maximizes&nbsp;stakeholder
    benefit, while respecting the constraints placed on the system and the development team.
</p>
<p>
    Based on requirements being captured and detailed in parallel with this activity, the architect analyzes the
    architectural constraints and leverages the available assets and technology to propose an architectural
    proof-of-concept. This early architectural prototype is used both to demonstrate the feasibility of the project, by
    using the selected candidate architecture, and to mitigate one or more architecturally significant <a
    class="elementLinkWithUserText" href="./../../openup_basic/guidances/concepts/risk,_0bsLgMlgEdmt3adZL5Dmdw.html"
    guid="_0bsLgMlgEdmt3adZL5Dmdw">risks</a>.
</p><!-- END:mainDescription,_mtb-6_L5Edm6Nvont3uinw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_0oSdE8lgEdmt3adZL5Dmdw CRC: 2715165358 -->Initiate Project<!-- END:presentationName,_0oSdE8lgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_0okw8clgEdmt3adZL5Dmdw CRC: 2084512818 -->Manage Requirements<!-- END:presentationName,_0okw8clgEdmt3adZL5Dmdw -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_0oreoclgEdmt3adZL5Dmdw CRC: 3175277106 -->Determine Architectural Feasibility<!-- END:presentationName,_0oreoclgEdmt3adZL5Dmdw -->
</body>
</html>