blob: 9968f640a74c8bdf8fffaa9b6517fcb205aa987f [file] [log] [blame]
<?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>\Scrum\tasks\Plan sprint 2.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: Plan sprint 2.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_4LOggPpaEdqsc-f87sBK8A CRC: 3345244880 -->
Sprint plan<!-- END:presentationName,_4LOggPpaEdqsc-f87sBK8A -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_4LOggPpaEdqsc-f87sBK8A CRC: 3073388689 -->
Short-term planning<!-- END:briefDescription,_4LOggPpaEdqsc-f87sBK8A -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: keyConsiderations<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:keyConsiderations,-NRwwk6YGAtu25V3Lc04G6w CRC: 4228366794 -->
<p>The sprint planning meeting is a work in group.</p>
<p>It is limited in time:</p>
<ul>
<li>max. length: up to 4 hours</li>
<li>avg length: 2 hours</li>
</ul><!-- END:keyConsiderations,-NRwwk6YGAtu25V3Lc04G6w -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: purpose<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:purpose,-NRwwk6YGAtu25V3Lc04G6w CRC: 3319225101 -->
The goal is to plan the starting sprint..<!-- END:purpose,-NRwwk6YGAtu25V3Lc04G6w -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_TJNsUP--Edqtbrr0B1TG-A CRC: 84701924 -->
Defining the sprint's goal<!-- END:name,_TJNsUP--Edqtbrr0B1TG-A -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_TJNsUP--Edqtbrr0B1TG-A CRC: 568426307 -->
<p>At the beginning of the first sprints of the first release of a product, the goal is usually to show the feasability on the potential architecture.</p>
<p>Then, once the architecture is validated, the goal of a sprint is proposed by the <a class="elementLink"
href="./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html" guid="_ICJyYPpaEdqsc-f87sBK8A">Product Owner</a> and discussed with the team. It oftenly focuses on a given functional theme.</p><!-- END:sectionDescription,_TJNsUP--Edqtbrr0B1TG-A -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_xvy5UAPKEdubhrgDuRb4fA CRC: 3619794437 -->
Selecting the items<!-- END:name,_xvy5UAPKEdubhrgDuRb4fA -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_xvy5UAPKEdubhrgDuRb4fA CRC: 1436541147 -->
<p>It is about defining the scope of this sprint. This is done by associating <a class="elementLink"
href="./../../Scrum/workproducts/Product Backlog Item,_-D85cIGIEduKE9hnyImx1Q.html"
guid="_-D85cIGIEduKE9hnyImx1Q">Product Backlog Item</a>s one by one &nbsp;to the sprint, and balancing with the team velocity.</p>
<p>If a <a class="elementLink" href="./../../Scrum/guidances/reports/Release Planning,_Z2NzkIGWEduKE9hnyImx1Q.html"
guid="_Z2NzkIGWEduKE9hnyImx1Q">Release Planning</a>&nbsp;has been done, this step is only about collectively validating the forecasted backlog subset for the sprint.</p><!-- END:sectionDescription,_xvy5UAPKEdubhrgDuRb4fA -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_p4C0sP--Edqtbrr0B1TG-A CRC: 382414914 -->
Identifying tasks from items<!-- END:name,_p4C0sP--Edqtbrr0B1TG-A -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_p4C0sP--Edqtbrr0B1TG-A CRC: 3752350718 -->
<p>The 2nd part of the meeting is about defining how the team is gonna achieve the sprint objectives.<br /> To do that, each selected <a class="elementLink"
href="./../../Scrum/workproducts/Product Backlog Item,_-D85cIGIEduKE9hnyImx1Q.html"
guid="_-D85cIGIEduKE9hnyImx1Q">Product Backlog Item</a>&nbsp;is decomposed into tasks. This enables the team to discuss and figure solutions aspects towards this item, asking the procut owner, if necessary, precisions on the product behavior.<br />
</p>
<p>Normaly, all the lifecycle activities are rolled out during a sprint:<br />
</p>
<ul>
<li>Selected requirements are specified</li>
<li>Architecture is modified if necessary</li>
<li>Classes and subsystems are designed, implemented and tested</li>
<li>The different components are integrated and tested</li>
<li>Product is packaged</li>
<li>Acceptance tests are passed.<br />
</li>
</ul>
<p>The given importance to these activities depends on the position of the sprint within the release.<br /> <br /> The planned work in a previous sprint that couldn't be done because of objectives reduction, becomes the priority for next sprint.</p><!-- END:sectionDescription,_p4C0sP--Edqtbrr0B1TG-A -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_DxNQUAPLEdubhrgDuRb4fA CRC: 1795174630 -->
Estimating tasks<!-- END:name,_DxNQUAPLEdubhrgDuRb4fA -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_DxNQUAPLEdubhrgDuRb4fA CRC: 3162440086 -->
<p>Tasks are estimated in hours. Tasks should be thin enough to take less than 16 hours.</p>
<p>Estimation is collectively made by the team. During this discussion, technical aspects are reviewed.</p><!-- END:sectionDescription,_DxNQUAPLEdubhrgDuRb4fA -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_worbAP--Edqtbrr0B1TG-A CRC: 3283188657 -->
Assigning tasks<!-- END:name,_worbAP--Edqtbrr0B1TG-A -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_worbAP--Edqtbrr0B1TG-A CRC: 2941712191 -->
Once sprint activities are defined, they will be assigned to team members. Activities can be done by one or many persons. All the activities must be taken in to account, including work meetings (non Scrum meetings as well), code or document reviews.<br /> It is preferable to delay assignement of certain activities, which will be assigned during the sprint in accordance with team members availability.<!-- END:sectionDescription,_worbAP--Edqtbrr0B1TG-A -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: name<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:name,_Iq14wAPLEdubhrgDuRb4fA CRC: 2825760581 -->
Getting team commitment<!-- END:name,_Iq14wAPLEdubhrgDuRb4fA -->
<!-- START NON-TRANSLATABLE -->
<br/><br/><br/>
Attribute: sectionDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:sectionDescription,_Iq14wAPLEdubhrgDuRb4fA CRC: 1541491738 -->
<p>Team should collectively commit to the sprint backlog, that is on backlog items it estimates being able to implement within the sprint.</p><!-- END:sectionDescription,_Iq14wAPLEdubhrgDuRb4fA -->
</body>
</html>