{"id":745,"date":"2019-04-25T18:47:15","date_gmt":"2019-04-25T18:47:15","guid":{"rendered":"http:\/\/www.smart-bricks.net\/?p=745"},"modified":"2019-04-28T22:23:35","modified_gmt":"2019-04-28T22:23:35","slug":"how-to-implement-scrum-in-7-steps-and-not-die-trying","status":"publish","type":"post","link":"http:\/\/www.smart-bricks.net\/index.php\/2019\/04\/25\/how-to-implement-scrum-in-7-steps-and-not-die-trying\/","title":{"rendered":"How to implement Scrum in 7 steps and not die trying"},"content":{"rendered":"\n<p><em>Let\u2019s discover the 7 steps to follow that tell you<strong> how to implement Scrum<\/strong> in your projects without dying during the attempt.<\/em><\/p>\n\n\n\n<p><strong>Scrum can be used in practically all types of projects<\/strong>: software development, sales, marketing for the launch of a new product, or in the organization of an event, among many others.<\/p>\n\n\n\n<p>What is the common denominator? It is that <strong>multidisciplinary teams function as a unit<\/strong> in order to generate partial and regular deliveries of a product within a dynamic and changing environment.<\/p>\n\n\n\n<p>But <strong>how do we implement Scrum in our own projects?<\/strong> The Scrum model supposes a high level of interaction, which positions communication in a very significant place and across to all processes in every moment of the process. With this in mind, I wanted to concentrate on the<strong> 7 steps to follow to successfully implement this methodology within your project<\/strong> without dying during the attempt.<\/p>\n\n\n\n<h2>1.&nbsp;Defining the Scrum elements<\/h2>\n\n\n\n<p><strong>How to implement Scrum correctly i<\/strong>n any project mostly depends on not neglecting any of the factors that make Scrum what it is:<\/p>\n\n\n\n<ul><li><strong>Product Owner or the one responsible for the product<\/strong><br>\nIt is the person who has a clear vision of what is needed, what is going\n to be done or manufactured, and the objectives to be met. The Product \nOwner <strong>is who will take into account the risks<\/strong>, as well \nas what is feasible. Having a clear understanding of who meets the \nnecessary conditions to perform these functions will be critical to the \nsuccessful implementation of Scrum.<\/li><li><strong>Work team<\/strong><br>\nIt is necessary to form a team between 4 and 9 people, which is expected\n to be multidisciplinary and self-organized to perform the analysis, \nimplementation, design, testing, and other tasks. When it comes to \nlarger and more complex teams, the best thing to do is <a href=\"https:\/\/www.agilealliance.org\/glossary\/scrum-of-scrums\/#q=~(filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_experience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'scrum*20of*20scrums))~searchTerm~'~sort~false~sortDirection~'asc~page~1)\" target=\"_blank\" rel=\"noreferrer noopener\">Scrum of Scrums<\/a> and split the team.<\/li><\/ul>\n\n\n\n<p>As a whole, the team is responsible for delivering products in due \ntime and in correct form at the end of each Sprint and incrementally.<\/p>\n\n\n\n<ul><li><strong>Scrum Master<\/strong><br>\nThe Scrum Master is the one who guarantees that the team is effective \nand progressive, removing all those obstacles that block satisfactory \nprogress. Their role does not imply dictating what the team will do or \nfollow, in an excessive way, to the smallest detail. Their main function\n is to lead the team through the Scrum work system.<\/li><li><strong>Sprint duration<\/strong><br>\nIt is necessary to define a window of time, known as a Sprint, which is \ngenerally between 1 and 4 weeks and maintains that duration throughout \nthe entire project. In case you do not know how much time is the most \nappropriate, it is advisable to start with 2 weeks and then find the \nbest timing.<\/li><\/ul>\n\n\n\n<h2>2.&nbsp;Prioritize a list of objectives or Backlog<\/h2>\n\n\n\n<p>The pending work to make the product a reality is what we call a \nBacklog. It is a list of tasks that evolves as the reality of the \nproject, the juncture, impediments, and possibilities become better \nknown.<\/p>\n\n\n\n<p>Given this nature, <strong>the Backlog is often considered the roadmap of the product<\/strong>: a single list with all the functionalities, pending activities, and the priority that each of them has assigned.<\/p>\n\n\n\n<p>Usually, a priority list contains <strong>3 types of work items<\/strong>:<\/p>\n\n\n\n<ul><li><strong>Epic:<\/strong> High level requirements that give an idea of the work and that possibly are then split into different User Stories.<\/li><li><strong>User Stories:<\/strong> Refined and more detailed requirements on what needs to be done.<\/li><li><strong>Tasks:<\/strong> The User Stories are divided again into tasks that will be included in the Sprint to start working on the desired product.<\/li><\/ul>\n\n\n\n<p>It is important to have an idea of the amount of time the project will take, which is why it is absolutely necessary to <strong>make an estimation of the next tasks to be performed and understand if there is any crucial information that is not available<\/strong> and that could radically modify the times.<\/p>\n\n\n\n<p>Many times, there will be a lack of information for an accurate \nestimation, but it is good to know, at least, the dimension of these \ntasks using methods such as the succession of Fibonacci.<\/p>\n\n\n\n<h2>3.&nbsp;Plan the Sprint<\/h2>\n\n\n\n<p>In this first meeting, <strong>the details of the tasks to be carried out will be refined<\/strong> so that the whole team has the necessary information to get the final product.<\/p>\n\n\n\n<p>At this stage of the process, <strong>estimations are made, and commitments are established for the performance of a certain number of tasks and stories<\/strong>,\n always in accordance with the defined work time. To do this, a joint \nplanning will be made, but if you have already worked some Sprint, the \nspeed of the team is taken into account in order to make a more \nrealistic estimation. The Scrum Master and the team itself will make \nsure to optimize this speed without losing the objective of fulfilling a\n realistic plan.<\/p>\n\n\n\n<h2>4.&nbsp;Make work and daily meetings visible<\/h2>\n\n\n\n<p>During the course of the Sprint, it is necessary to <strong>make the progress of the team visible. <\/strong>Therefore,\n it is advisable to use tools such as TFS, Trello, or use a Burndown \ndiagram or a physical whiteboard to record the status of each item. This\n helps to <strong>measure the <em>temperature<\/em> of the progress of the tasks <\/strong>and to identify possible delays.<\/p>\n\n\n\n<p>Likewise, every day at the same time, and for a maximum of 15 \nminutes, the team and the Scrum Master participate in the Daily, where 3\n key questions are answered:<\/p>\n\n\n\n<ul><li><strong>What did I do yesterday to help<\/strong> the team finish the Sprint?<\/li><li><strong>What am I going to do tomorrow to help the team<\/strong> finish the Sprint?<\/li><li><strong>What obstacles do I have <\/strong>in my path or in the team\u2019s path?<\/li><\/ul>\n\n\n\n<p>The Scrum Master is the one who looks after the elimination of \nobstacles and has a general vision of the fulfillment of the objective \ndefined for the Sprint.<\/p>\n\n\n\n<h2>5.&nbsp;Sprint Review or Demonstration<\/h2>\n\n\n\n<p>Once the work time has been completed, it is essential to show real progress on the product. <strong>Scrum\u2019s\n own iterative methodology requires visualizing the progress in the \nproduct and making decisions in those cases where reality is not in line\n with expectation<\/strong>. To do this, a review\/demo is carried out in \nwhich everyone involved in the development takes part: Product Owner, \nScrum Master, and the rest of the team, as well as any other interested \nparty.<\/p>\n\n\n\n<p>In this open meeting, the team shows <strong>only what is <em>finished<\/em> and can be shown.<\/strong> It may not be a 100% finished product, but it should be a product that is ready to work.<\/p>\n\n\n\n<h2>6.&nbsp;Retrospective of the Sprint<\/h2>\n\n\n\n<p>Once the iteration is complete, the team reunites to reflect on <strong>what went well, what could be done better, and what could be perfected for the next Sprint<\/strong>.<\/p>\n\n\n\n<p>The main thing here is to<strong> allow everyone to suggest improvements<\/strong>.\n In this way, the team takes responsibility for its process and outcome,\n thus analyzing the options to improve in a constructive way.<\/p>\n\n\n\n<p>At the end of this meeting, <strong>the team and the Scrum Master should agree on at least one improvement to the process<\/strong>,\n which will be incorporated in the following Sprint. That improvement \nshould be documented and considered at the moment of making the next \nretrospective meeting, always allowing any member of the team easy and \nfree access to it.<\/p>\n\n\n\n<h2>7.&nbsp;Immediately start the next cycle of Sprints<\/h2>\n\n\n\n<p>Taking into account the previous experience of the team, with obstacles and the incorporation of improvements, <strong>the process begins again<\/strong>, and the changes will start to become visible.<\/p>\n\n\n\n<h3>The last advice<\/h3>\n\n\n\n<p><strong>The improvement of the team will only be achieved with practice<\/strong>.\n It may not be well understood how to use Scrum until you start and \ncommit to the process, but once you do, it will radically change the way\n in which your team interacts and collaborates.<\/p>\n\n\n\n<p>Before leaving us, I invite you to learn the myths about Scrum we all must avoid. Now that you are aware of the steps to follow, are you still uncertain about how to implement Scrum? <strong>What are you waiting for?<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Let\u2019s discover the 7 steps to follow that tell you how to implement Scrum in your projects without dying during the attempt. Scrum can be used in practically all types of projects: software development, sales, marketing for the launch of a new product, or in the organization of an event, among many others. What is&hellip;&nbsp;<a href=\"http:\/\/www.smart-bricks.net\/index.php\/2019\/04\/25\/how-to-implement-scrum-in-7-steps-and-not-die-trying\/\" class=\"\" rel=\"bookmark\">Read More &raquo;<span class=\"screen-reader-text\">How to implement Scrum in 7 steps and not die trying<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[9,14],"_links":{"self":[{"href":"http:\/\/www.smart-bricks.net\/index.php\/wp-json\/wp\/v2\/posts\/745"}],"collection":[{"href":"http:\/\/www.smart-bricks.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.smart-bricks.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.smart-bricks.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.smart-bricks.net\/index.php\/wp-json\/wp\/v2\/comments?post=745"}],"version-history":[{"count":1,"href":"http:\/\/www.smart-bricks.net\/index.php\/wp-json\/wp\/v2\/posts\/745\/revisions"}],"predecessor-version":[{"id":746,"href":"http:\/\/www.smart-bricks.net\/index.php\/wp-json\/wp\/v2\/posts\/745\/revisions\/746"}],"wp:attachment":[{"href":"http:\/\/www.smart-bricks.net\/index.php\/wp-json\/wp\/v2\/media?parent=745"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.smart-bricks.net\/index.php\/wp-json\/wp\/v2\/categories?post=745"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.smart-bricks.net\/index.php\/wp-json\/wp\/v2\/tags?post=745"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}