{"id":2980,"date":"2016-03-15T14:32:16","date_gmt":"2016-03-15T14:32:16","guid":{"rendered":"https:\/\/www.storm-consulting.com\/?p=2980"},"modified":"2017-12-08T00:59:41","modified_gmt":"2017-12-08T00:59:41","slug":"scrum-planning-meetings-agile-delivery","status":"publish","type":"post","link":"https:\/\/www.storm-consulting.com\/scrum-planning-meetings-agile-delivery\/","title":{"rendered":"Use Scrum Planning Meetings for Agile Delivery"},"content":{"rendered":"<p><a href=\"https:\/\/www.storm-consulting.com\/wp-content\/uploads\/Fotolia-98774152-XS.jpg\"><img decoding=\"async\" loading=\"lazy\" class=\"aligncenter size-medium wp-image-2982\" src=\"https:\/\/www.storm-consulting.com\/wp-content\/uploads\/Fotolia-98774152-XS-300x200.jpg\" alt=\"Agile Delivery\" width=\"300\" height=\"200\" srcset=\"https:\/\/www.storm-consulting.com\/wp-content\/uploads\/Fotolia-98774152-XS-300x200.jpg 300w, https:\/\/www.storm-consulting.com\/wp-content\/uploads\/Fotolia-98774152-XS-100x67.jpg 100w, https:\/\/www.storm-consulting.com\/wp-content\/uploads\/Fotolia-98774152-XS-53x35.jpg 53w, https:\/\/www.storm-consulting.com\/wp-content\/uploads\/Fotolia-98774152-XS.jpg 424w\" sizes=\"(max-width: 300px) 100vw, 300px\" \/><\/a><br \/>\nThere are three regular planning events in Scrum, and although each has a different objective and audience they form the basic mechanism for <strong>Agile delivery<\/strong> and risk-management.<\/p>\n<p><em>Managers that understand the purpose of these three meetings will be able to gain the benefits Agile Delivery in a wide range of business situations, not just in IT and whether or not they follow Scrum.<\/em><\/p>\n<p>In overview, the regular planning meetings are:<\/p>\n<ul>\n<li><strong>Sprint Planning meeting<\/strong>: a collaboration to agree WHAT can be delivered in the time available and HOW will it be achieved<\/li>\n<li><strong>Sprint Review meeting<\/strong>: another collaboration to review the DELIVERY achieves and to prioritise the next delivery increment with that knowledge<\/li>\n<li><strong>Daily Scrum meeting<\/strong>: to allow the team to stay focused on reaching their agreed goal<\/li>\n<\/ul>\n<h2>Sprint Planning<\/h2>\n<p>The input for Sprint Planning meeting is the Product Backlog &#8211; a list of requirements, plus the knowledge of what the team actually achieved in the last Sprint. It takes place immediately before the Sprint commences and involves the whole team with the Product Owner, who must prioritise the Backlog and decide what will be included now and what left for later.<\/p>\n<p>For many team members, the planning meeting will be the first time they have encountered a particular requirement. Since they will be asked to make a commitment to deliver it by the end of the Sprint, they must fully understand the customer&#8217;s requirement; the acceptance criteria; and the team&#8217;s approach to dong the work. This is no time for holding back on questions in the hope that somebody else will ask, or to assume that all will be clear once you get started on the job itself &#8211; the purpose of this meeting is to drive-out all such unknowns.<\/p>\n<p>The output for this part of planning is an agreed Backlog of requirements to be delivered and defines the goal of the Sprint.<\/p>\n<p>For each selected requirement, the team also answers the question HOW will the chosen work be accomplished.<\/p>\n<p>This is usually done by breaking the work down into actual tasks. These are quite detailed, often specifying details of people that need to be interviewed, documents to research, names of classes and functions, diagram types and scopes, etc.<br \/>\nTasks are sometimes given a time estimate in hours, so the Scrum Master can track the day to day progress of each requirement.<\/p>\n<h2>Sprint Review<\/h2>\n<p>At the end of the Sprint, the Team demonstrates to the business everything that has been completed at the Sprint Review. This may be the delivery, or delivery may have taken place in which case the Team usually presents the status and provides performance information.<\/p>\n<p>Based on the delivery, and with their knowledge of the latest activities in the wider business, stakeholders review what they have learned with the Team and together they discuss the opportunities arising for the forthcoming Sprint.<\/p>\n<h2>Daily Scrum<\/h2>\n<p>The 15 minute Daily Scrum meeting is perhaps most famous because of the name and a clue to the sporting analogy that runs through Scrum.<\/p>\n<p>It\u2019s also the simplest planning meeting with just three questions to answer:<\/p>\n<ul>\n<li>What did you do yesterday that helped the team reach the Sprint Goal? (Review);<\/li>\n<li>what do you intend to do today to help the team reach its Sprint Goal? (Plan);<\/li>\n<li>Is anything holding us back from meeting the Sprint Goal? (Check).<\/li>\n<\/ul>\n<p>The daily Scrum allows the team to plan their day according to everyone\u2019s output on the previous day. More importantly it focuses the whole team on their objective &#8211; reaching the Sprint Goal.<\/p>\n<h2>The Secret of Agile Delivery is Regular Planning<\/h2>\n<p>At its heart, Agile simply prioritises delivery and encourages behaviours that lead to collaboration.<\/p>\n<p>Managers that admire Scrum&#8217;s ability to deliver value incrementally and reliably need only lead three regular meetings that focus relentlessly on <strong>Agile Delivery<\/strong> to start removing the blockers to Organisational Agility.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There are three regular planning events in Scrum, and although each has a different objective and audience they form the basic mechanism for Agile delivery and risk-management. Managers that understand the purpose of these&#46;&#46;&#46;<\/p>\n","protected":false},"author":5,"featured_media":2982,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9,52],"tags":[36,64,86],"_links":{"self":[{"href":"https:\/\/www.storm-consulting.com\/wp-json\/wp\/v2\/posts\/2980"}],"collection":[{"href":"https:\/\/www.storm-consulting.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.storm-consulting.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.storm-consulting.com\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.storm-consulting.com\/wp-json\/wp\/v2\/comments?post=2980"}],"version-history":[{"count":0,"href":"https:\/\/www.storm-consulting.com\/wp-json\/wp\/v2\/posts\/2980\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.storm-consulting.com\/wp-json\/wp\/v2\/media\/2982"}],"wp:attachment":[{"href":"https:\/\/www.storm-consulting.com\/wp-json\/wp\/v2\/media?parent=2980"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.storm-consulting.com\/wp-json\/wp\/v2\/categories?post=2980"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.storm-consulting.com\/wp-json\/wp\/v2\/tags?post=2980"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}