<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="https://www.ibm.com/us-en/marketplace/rational-method-composer" rmc:version="7.5.1" xmi:id="-FiM8KERcn7kdBMMTlVVBHw" name="new_concept,_TUbH0K4FEeKOp7iC96firQ" guid="-FiM8KERcn7kdBMMTlVVBHw" changeDate="2014-01-09T14:59:03.103-0800" version="7.5.1">
  <mainDescription>&lt;h3>&#xD;
    Scrum Defined&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Scrum is&amp;nbsp;a framework within which people can address complex adaptive problems, while productively and creatively&#xD;
    delivering products of the highest possible value.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Scrum is:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        lightweight&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        easy to understand, but very hard to master&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        focused on delivering the highest business value in the shortest time&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        enables rapid and repeated inspection of actual working software&lt;br />&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    Most of all Scrum is…&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    A project management approach for iterative and incremental development superimposed on your:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        engineering practices&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        development methods&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        standards and compliance needs&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Produces a working software increment in 30 days&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    Scrum Theory&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Scrum is based upon empirical process control theory:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Knowledge comes from experience&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Make decisions based upon what is known now&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Three (3) pillars of empiricism:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                Transparency&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Inspection&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Adaption&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Four (4) formal opportunities for inspection and adaptation:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;>&#xD;
        &lt;ul>&#xD;
            &lt;li>&#xD;
                Daily scrum meeting&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Sprint planning&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Sprint review&#xD;
            &lt;/li>&#xD;
            &lt;li>&#xD;
                Sprint retrospective&#xD;
            &lt;/li>&#xD;
        &lt;/ul>&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    Scrum Values&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    The Scrum values are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Commitment&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Courage&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Focus&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Openness&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Respect&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    Supplemental Guidelines for Getting Started with Scrum&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    To get started with Scrum, you need a product vision and an ordered product backlog with enough items for at least one&#xD;
    Sprint. However, you may need to do the following tasks if you team is new to Scrum and/or you are working on a new&#xD;
    initiative:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Get your team or teams formed and organized&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Identify the high level scope and vision for the project&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Gain Stakeholder agreement around the vision&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Identify initial risks, constraints and assumptions&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Develop a high level project or release schedule with best guess velocity&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Estimated budget and project approval&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Technical requirements and high level architecture overview&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Technical setup and team work environment&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Be sure that you allow for sufficient time during the first Sprint to get the team organized,&amp;nbsp;refine the product&#xD;
    backlog, agree on story points and set up the technical environment. The first Sprint goal may be to get the technical&#xD;
    environment ready and prove it out by producing a potentially consumable product increment with a minimal number of&#xD;
    features to enable the team to gel.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    For more about Scrum, see &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../practice.mgmt.scrum.base-ibm/guidances/supportingmaterials/scrum_resources_99BF3E6C.html&quot;&#xD;
    guid=&quot;_oE6VAq3VEeKOp7iC96firQ&quot;>Scrum Resources&lt;/a>.&lt;br />&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;br />&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
