{"id":1927,"date":"2016-06-16T17:22:27","date_gmt":"2016-06-16T16:22:27","guid":{"rendered":"https:\/\/yanado.com\/blog\/?p=1927"},"modified":"2016-06-28T17:59:14","modified_gmt":"2016-06-28T16:59:14","slug":"how-to-use-yanado-for-scrum-project-management-framework","status":"publish","type":"post","link":"https:\/\/yanado.com\/blog\/how-to-use-yanado-for-scrum-project-management-framework\/","title":{"rendered":"How To Use Yanado For Scrum Project Management Framework"},"content":{"rendered":"<p style=\"text-align: center;\"><em>This article is part of our <a href=\"https:\/\/yanado.com\/blog\/how-to-use-yanado\/\">How To Use Yanado<\/a> series<\/em><\/p>\n<p>In our <a href=\"https:\/\/yanado.com\/blog\/ultimate-guide-to-scrum-project-management-framework\/\">Ultimate\u00a0Guide\u00a0to Scrum\u00a0Project Management Framework<\/a>, \u00a0we tackled the essentials of Scrum as one of the most popular agile frameworks used by software development teams.<\/p>\n<p>For Scrum to be performed successfully, you need a collaborative environment, where Scrum team members are actively communicating and reviewing their work against what they commit to accomplish during the iterations\/sprints.<\/p>\n<p>To make this possible, team members need to understand the big picture.<\/p>\n<p>This means they must have a clear understanding of Sprint goals and the work required to achieve them.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1933 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/giphy-1.gif\" alt=\"big-picture\" width=\"480\" height=\"270\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>If team members don\u2019t understand how their work fits into the team as a whole, it stifles collaboration and cross communication, leaving no room for improvement.<\/p>\n<p>For better teamwork, a collaboration space is needed. This is where a project management tool comes as a support. The simpler and easier to use, the better.<\/p>\n<p>There are tons of project management tools out there to run your software projects using Scrum framework. And they all get the job done (more or less).<\/p>\n<p>But a project management tool can quickly manage you. Sometimes, it can feel like you spend more time working the tool, instead of getting work done.<\/p>\n<p>All you need is a simple way to visualize and track the work being done during the Sprints in order for team members to stay aligned.<\/p>\n<blockquote><p><i><span style=\"font-weight: 400;\">\u201cThe effectiveness of any tool is the discipline [enterprise-wide] to use it well.\u201d &#8211;\u00a0<a href=\"https:\/\/twitter.com\/agilescout\">Peter Saddington<\/a><\/span><\/i><\/p><\/blockquote>\n<p>So let\u2019s see how to make this possible with Yanado.<\/p>\n<p>&nbsp;<\/p>\n<h2>Step #1 Setting Up A Collaborative Space for Better Teamwork<\/h2>\n<p>First, your Scrum process needs to be visualized and tracked in one place, accessible to everyone on the team.<\/p>\n<p>To make one in Yanado, start with creating a separate <em>List<\/em> naming it <em>Sprints<\/em>, as an example.<\/p>\n<p>Invite users to the <em>List<\/em> to put everyone on the Scrum team (<a href=\"https:\/\/yanado.com\/blog\/ultimate-guide-to-scrum-project-management-framework\/#client\">Product Owner<\/a>, <a href=\"https:\/\/yanado.com\/blog\/ultimate-guide-to-scrum-project-management-framework\/#master\">Scrum Master<\/a>, <a href=\"https:\/\/yanado.com\/blog\/ultimate-guide-to-scrum-project-management-framework\/#devteam\">Development team<\/a>).<\/p>\n<p>Next, you need a well structured process to fit into the Scrum framework.<\/p>\n<p>To do this in Yanado, we suggest you create the following <em>Statuses<\/em> inside the <em>Sprints List<\/em>:<\/p>\n<ul>\n<li><strong>Product Backlog<\/strong> &#8211; list of items representing all product features that will be prioritized, estimated and planned for upcoming sprints.<\/li>\n<li><strong>Sprint Backlog<\/strong> &#8211; list of items team will work on in the next sprint based on the priority.<\/li>\n<li><strong>In Progress<\/strong> &#8211; list of items team is currently working on in the sprint.<\/li>\n<li><strong>Dev Completed<\/strong> &#8211; list of items developers are finished with but are still being collected and prepared for testing.<\/li>\n<li><strong>Ready for Test<\/strong> &#8211; list of items that are ready for testing.<\/li>\n<li><strong>Test In Progress<\/strong> &#8211; list of items that are being tested.<\/li>\n<li><strong>Done<\/strong> &#8211; list of items that are fully completed during the sprint.<\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-1977\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/1_statuses-1.png\" alt=\"1_statuses-1\" width=\"690\" height=\"264\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Step #2 Managing The Product Backlog<\/h2>\n<p><strong>Status:<\/strong> <em>Product Backlog<\/em><\/p>\n<p>This is where you start. A separate column status in Yanado for your <a href=\"https:\/\/yanado.com\/blog\/ultimate-guide-to-scrum-project-management-framework\/#productbacklog\">Product Backlog<\/a> makes it possible for your Scrum team to have a place to put items it will be working on in the upcoming sprints.<\/p>\n<p>Your Product Owner is responsible for the Product Backlog, as he will be re-prioritizing the items inside of it based on the strategic and the tactical decisions.<\/p>\n<p>To learn how Product Owner can do that, check out Roman Pichler&#8217;s advice on the relation between\u00a0<a href=\"http:\/\/www.romanpichler.com\/blog\/product-roadmap-product-backlog\/\">The Product Roadmap and the Product Backlog<\/a><\/p>\n<p>Essentially the Product Backlog should serve as the connection between the Product Owner and the Development team.<\/p>\n<p>Now, what goes into the <strong><em>Product Backlog<\/em><\/strong> column?<\/p>\n<p>Simply: all work items should be included here. This is important because it ensures everyone&#8217;s work items are included in the overall discussion for each sprint. Team members can then make trade-offs with the product owner before starting a sprint to be clear with everything to be done. It helps to know these items are all of a particular type.<\/p>\n<p>Here are some of them:<\/p>\n<ul>\n<li>Product features<\/li>\n<li>Bugs<\/li>\n<li>Technical work<\/li>\n<li>Customer requests<\/li>\n<li>Action items from the retrospective, etc.<\/li>\n<li>Miscellaneous tasks that enable the team to perform the other work.<\/li>\n<\/ul>\n<p>To better understand the types of Product Backlog items, check out how <a href=\"http:\/\/www.innolution.com\/blog\/demystifying-product-backlog-concepts\">Ken Rubin describes the concepts behind them.<\/a><\/p>\n<p>To start creating these items in Yanado, go to the column<strong><em> Product Backlog<\/em><\/strong> and <em>Add a new Task<\/em>, writing it\u2019s title in the form of a User Story.<\/p>\n<p>To pick some good advice on how to write your tasks as User Stories, read\u00a0<a href=\"https:\/\/yanado.com\/blog\/how-to-write-project-task-description\/\">our article<\/a>. And if this doesn&#8217;t help, you might also want to check out these\u00a0<a href=\"http:\/\/www.romanpichler.com\/blog\/10-tips-writing-good-user-stories\/\">10 Tips for Writing Good User Stories<\/a>, by Roman Pichler.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1978 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/2-new-task.png\" alt=\"2 new-task\" width=\"470\" height=\"312\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>To emphasize the type of the <em>Items<\/em>, use <em>Tags<\/em> as you write the title (for example: <em>#feature<\/em>, <em>#bug<\/em>, <em>#improvement<\/em>, <em>#technical work<\/em>\u2026).<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1979 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/3-TAG.png\" alt=\"3 TAG\" width=\"471\" height=\"290\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>As a Product Owner you will be prioritizing the Product Backlog items.<\/p>\n<p>In Yanado, the priority is determined by the order of the items\u00a0in the column. To move or change the priority drag the items up or down.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1939 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/drag-priority.gif\" alt=\"drag priority\" width=\"256\" height=\"392\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Items shown at the top of the column are most important, and the team should start work on those first. Items at the bottom are to be tackled in future sprints. These items may be more vague, while items near the top should be the most defined for your team to easily implement.<\/p>\n<p>Prioritizing the Product Backlog properly means the Product Owner will seek the inputs and feedback from customers and the development team to optimize everyone&#8217;s workload and the product delivery.<\/p>\n<p>At this point, the most important input the development team needs to provide is a high-level initial <a href=\"https:\/\/yanado.com\/blog\/ultimate-guide-to-scrum-project-management-framework\/#estimation\">estimate<\/a>, in order to get an idea of the effort required for Product Backlog items.<\/p>\n<p>This helps to inform a Product Owner\u2019s decision about priorities.<\/p>\n<p>To include the estimates in your Product Backlog items in Yanado, simply write them next to the items title.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1980 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/4-ESTIMATE.png\" alt=\"4 ESTIMATE\" width=\"472\" height=\"312\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>With these rough estimates, a Product Owner will be able to take another quick look at priorities and change the order of items.<\/p>\n<p>The Product Backlog also serves as the foundation for sprint planning, as the highest priority items are the ones that the team will deliver in next sprint.<\/p>\n<p>To be able to start work, make sure you provide enough detail to each item.<\/p>\n<p>These details are commonly called the Acceptance Criteria. This is what helps the team to have a common understanding of what completes a particular Item.<\/p>\n<p>To write these acceptance criteria in Yanado, you simply open the items\u00a0from the top of the Product Backlog column and <em>Add Task Description<\/em>. You can also turn this details\/acceptance criteria in a checklist and use it later during the testing.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1981 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/5-acceptance-criteria-1.png\" alt=\"5 acceptance-criteria-1\" width=\"472\" height=\"445\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Take note the Product Owner should regularly maintain the Product Backlog column, reviewing it before each sprint planning meeting to ensure new priorities are assessed and inputs from the last sprint are also incorporated. This is the part of the product backlog grooming, which also includes adding new items\u00a0and discarding irrelevant tasks.<\/p>\n<p>For items\u00a0you want to remove, use the <em>Archive<\/em> or <em>Delete<\/em> option.<\/p>\n<p>So it&#8217;s important that Product Owner gets the Product Backlog items in shape before the team starts working on them. To learn more about how to do that, check out Roman Pichler&#8217;s <a href=\"http:\/\/www.romanpichler.com\/blog\/the-product-backlog-grooming-steps\/\">five-step backlog grooming process<\/a>.<\/p>\n<p>Having top priority items\u00a0in the Product Backlog column drawn up, detailed and estimated is what makes you ready for the next step &#8211; <strong>sprint planning<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<h2>Step #3 Sprint Planning<\/h2>\n<p><strong>Statuses:<\/strong> <em>Product Backlog<\/em>, <em>Sprint Backlog<\/em><\/p>\n<p>When in the <a href=\"https:\/\/yanado.com\/blog\/ultimate-guide-to-scrum-project-management-framework\/#sprintplan\">sprint planning meeting<\/a>, the whole team with Product Owner is looking at the top items\u00a0from the <em><strong>Product Backlog<\/strong> column<\/em> in order to decide what would be possible to deliver in the next sprint.<\/p>\n<p>To learn more about the sprint planning meeting, <a href=\"http:\/\/www.agileprojectmanagementtraining.com\/running-an-effective-sprint-planning-meeting\/\" target=\"_blank\">check out this article by\u00a0Dan Tousignant<\/a>.<\/p>\n<p>The Product Owner presents each item and explains how it should work from a functional perspective. The whole team discusses the item in detail and asks questions about the item in order to establish what it should do and how it should work.<\/p>\n<p>Eventually, the development team will decide how much they are able to achieve in the next sprint as they pick a section of items\u00a0from the top of the <em><strong>Product<\/strong> <strong>Backlog<\/strong> column<\/em>.<\/p>\n<p>As the Items are picked from the Product Backlog, make sure you drag them into <em><strong>Sprint Backlog<\/strong> column<\/em>.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1942 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/drag-to-sprint-backlog.gif\" alt=\"drag to sprint backlog\" width=\"545\" height=\"370\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>At this point the team will be focused on planning the work associated with items they have decided to deliver in the next sprint.<\/p>\n<p>This is where you <em>Assign<\/em> each item to a particular team member.<\/p>\n<p>NOTE: We suggest one team member is responsible for each item\u00a0so you can have a clear understanding of individual responsibilities. This is possible if you break the item making it small and specific enough so that one person on the team can take the responsibility to implement it.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1982 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/6-ASSIGN.png\" alt=\"6 ASSIGN\" width=\"472\" height=\"538\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Team members will likely want to split items\u00a0up into constituent subtasks, representing small pieces of work required to be done for the items to be finished. In Yanado, simply open the items and <em>add Subtasks<\/em>.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1983 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/7-SUBTASKS.png\" alt=\"7 SUBTASKS\" width=\"470\" height=\"536\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Once you have all the items\u00a0set in the <em><strong>Sprint Backlog<\/strong> column<\/em> your team is ready for the next step &#8211; <strong>sprint!<\/strong><\/p>\n<p>&nbsp;<\/p>\n<h2>Step #4 Tracking the Sprint<\/h2>\n<p><strong>Statuses:<\/strong> <em>In progress<\/em>, <em>Dev Completed<\/em>, <em>Ready for Test<\/em>, <em>Test In progress<\/em>, <em>Done<\/em><\/p>\n<p>Once team members begin working on the items\u00a0they are assigned to, they will drag them into the <em><strong>In Progress<\/strong> column.<\/em><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1946 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/DRAG-TO-IN-PROGRESS.gif\" alt=\"DRAG TO IN PROGRESS\" width=\"542\" height=\"365\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>While they work on the items, they will be using the <em>Subtasks<\/em> they created to easily guide themselves<a href=\"https:\/\/yanado.com\/blog\/ultimate-guide-to-scrum-project-management-framework\/#standup\"> through the progress.<\/a> Since these <em>Subtasks<\/em> in Yanado are in the form of a checklist, this makes a good visual indication of the amount of work associated with the item\u00a0as it is completed.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1947 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/CHKECKLIST-SUBTASKS.gif\" alt=\"CHKECKLIST SUBTASKS\" width=\"469\" height=\"535\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>For items\u00a0developers are finished with, but decide to leave in one place before sending to testing, consider dragging them into the status <em>column <strong>Dev Completed<\/strong><\/em>. It is good to have this status column because developers may decide to have more finished items to send for testing in a batch process, rather than losing time sending them one by one.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1948 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/DRAG-TO-DEV-COMPLETED.gif\" alt=\"DRAG TO DEV COMPLETED\" width=\"543\" height=\"344\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Once developers finish all their work on the items they will drag them into the <em><strong>Ready for Test<\/strong> column<\/em>, thus making it ready for testing.<\/p>\n<p>Make sure you <em>Assign<\/em> the items to the team member responsible for the testing.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1949 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/DRAG-TO-TEST-READY-ASSIGN.gif\" alt=\"DRAG TO TEST READY + ASSIGN\" width=\"543\" height=\"366\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>As Testers start working on the items, they will move it in the <em><strong>Test In Progress<\/strong> column<\/em>.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1950 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/DRAG-TO-TEST-IN-PROGRESS.gif\" alt=\"DRAG TO TEST IN PROGRESS\" width=\"542\" height=\"327\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Achieving completeness is a process as well. To make sure the items are really done before moving on, testing must be integrated throughout the lifecycle. This means testing should be done feature by feature, rather than a group of at the very end of the sprint.<\/p>\n<p>This is how you make it possible for certain issues to be noticed early, leaving time to fix them until the end of the sprint.<\/p>\n<p>So once a certain issue in a particular item is noticed during the testing, make sure you address it properly.<\/p>\n<p>You can do this by adding a specific <em>Tag<\/em> in the item\u00a0title in order to emphasize the items with issues or bugs. An example would be <em>#TestFailed<\/em><\/p>\n<p>It is also important to provide details about the issue in the <em>Comments section<\/em> to make it possible to understand how it should be tackled.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1984 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/8-TEST-FAILED.png\" alt=\"8 TEST-FAILED\" width=\"472\" height=\"538\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Make sure you <em>Assign<\/em> the item with issues to a developer or team member so he can work on fixing it while still in the sprint.<\/p>\n<p>Or, you can move this item back to the <em><strong>Product Backlog<\/strong> column<\/em> and replan it for the next sprint.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1985 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/9-FROM-TEST-FAILED-TO-PRODUCT-BACKLOG-1.png\" alt=\"9 FROM-TEST-FAILED-TO-PRODUCT-BACKLOG-1\" width=\"471\" height=\"441\" \/><\/p>\n<p>&nbsp;<\/p>\n<p>Once the items have passed the testing and the acceptance criteria are met, they are considered to be done.<\/p>\n<p>Take note the definition of done is what needs to be a common understanding among all team members. To learn more about how to bring team members on the same page when it comes to the &#8220;definition of done&#8221;, check out <a href=\"http:\/\/www.ronjeffries.com\/articles\/2015-04-24-done\/\">this advice from Ron Jeffries. \u00a0<\/a><\/p>\n<p>In order to make the status of these items\u00a0visible for everyone on the team, make sure you drag them into the <em><strong>Done<\/strong> column.<\/em><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1955 aligncenter\" src=\"https:\/\/yanado.com\/blog\/wp-content\/uploads\/2016\/06\/DRAG-TO-DONE-1.gif\" alt=\"DRAG TO DONE\" width=\"547\" height=\"224\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Step #5 Closing the Sprint<\/h2>\n<p>So you came to the end of the sprint.<\/p>\n<p>Items in the <em><strong>Done<\/strong> column<\/em> are those that will be discussed and reviewed with the whole team in the<a href=\"https:\/\/yanado.com\/blog\/ultimate-guide-to-scrum-project-management-framework\/#review\"> sprint review meeting.<\/a><\/p>\n<p>Items that have not been completed, or have not met the acceptance criteria will be moved back to the Product Backlog column to be re-planned for the future sprints.<\/p>\n<h2>Conclusion<\/h2>\n<p>So this was a demonstration of how you can use Yanado for a &#8220;Sunny Day Scenario&#8221; Scrum Process.<\/p>\n<p>It may not be a one size fits all solution, but is a good base to start your Scrum Process with.<\/p>\n<p>Overall, the tool should not a be burden. This means you should adapt the tool to your process and the people, making the tool work for you.<\/p>\n<p>Try it and let us know if you like it.<\/p>\n<p><div class=\"swp_social_panel swp_horizontal_panel swp_flat_fresh  swp_default_full_color swp_individual_full_color swp_other_full_color scale-100  scale-\" data-min-width=\"1100\" data-float-color=\"#ffffff\" data-float=\"bottom\" data-float-mobile=\"none\" data-transition=\"slide\" data-post-id=\"1927\" ><div class=\"nc_tweetContainer swp_share_button swp_facebook\" data-network=\"facebook\"><a class=\"nc_tweet swp_share_link\" rel=\"nofollow noreferrer noopener\" target=\"_blank\" href=\"https:\/\/www.facebook.com\/share.php?u=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F\" data-link=\"https:\/\/www.facebook.com\/share.php?u=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F\"><span class=\"swp_count swp_hide\"><span class=\"iconFiller\"><span class=\"spaceManWilly\"><i class=\"sw swp_facebook_icon\"><\/i><span class=\"swp_share\">Share<\/span><\/span><\/span><\/span><\/a><\/div><div class=\"nc_tweetContainer swp_share_button swp_twitter\" data-network=\"twitter\"><a class=\"nc_tweet swp_share_link\" rel=\"nofollow noreferrer noopener\" target=\"_blank\" href=\"https:\/\/twitter.com\/intent\/tweet?text=How+To+Use+Yanado+For+Scrum+Project+Management+Framework+%23agile+%23scrum+%23projectmanagement&url=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F&via=YanadoTool\" data-link=\"https:\/\/twitter.com\/intent\/tweet?text=How+To+Use+Yanado+For+Scrum+Project+Management+Framework+%23agile+%23scrum+%23projectmanagement&url=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F&via=YanadoTool\"><span class=\"iconFiller\"><span class=\"spaceManWilly\"><i class=\"sw swp_twitter_icon\"><\/i><span class=\"swp_share\">Tweet<\/span><\/span><\/span><span class=\"swp_count\">14<\/span><\/a><\/div><div class=\"nc_tweetContainer swp_share_button swp_linkedin\" data-network=\"linkedin\"><a class=\"nc_tweet swp_share_link\" rel=\"nofollow noreferrer noopener\" target=\"_blank\" href=\"https:\/\/www.linkedin.com\/cws\/share?url=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F\" data-link=\"https:\/\/www.linkedin.com\/cws\/share?url=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F\"><span class=\"iconFiller\"><span class=\"spaceManWilly\"><i class=\"sw swp_linkedin_icon\"><\/i><span class=\"swp_share\">Share<\/span><\/span><\/span><span class=\"swp_count\">14<\/span><\/a><\/div><div class=\"nc_tweetContainer swp_share_button total_shares total_sharesalt\" ><span class=\"swp_count \">14 <span class=\"swp_label\">Shares<\/span><\/span><\/div><\/div><br \/>\n\r\n    <div class=\"subscribe\">\r\n        <div class=\"subscribe_content\">\r\n        <h1>Learn More About Project Management<\/h1>\r\n        <!--<h3>Reviews of the productivity tools every business needs<\/h3>-->\r\n            <div class=\"widget-content clearfix\">\r\n                <form action=\"https:\/\/netdokumenti.us2.list-manage.com\/subscribe\/post?u=04f16884b0ed8c0e274b55443&amp;id=a514f42814\" method=\"post\" class=\"mc-embedded-subscribe-form\" name=\"mc-embedded-subscribe-form\" class=\"validate\" target=\"_blank\" novalidate>\r\n\r\n                    <div class=\"input-group\">\r\n                        <input type=\"email\" value=\"\" name=\"EMAIL\" class=\"form-control\" placeholder=\"Enter your email address\">\r\n                                  <span class=\"input-group-btn\">\r\n                                    <input type=\"submit\" value=\"Send Me More About Project Management\" name=\"subscribe\"\r\n                                           class=\"btn btn-orange btn-sidebar-subscribe\">\r\n                                  <\/span>\r\n                    <\/div>\r\n                     <!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups-->\r\n                    <div style=\"position: absolute; left: -5000px;\"><input type=\"text\" name=\"b_04f16884b0ed8c0e274b55443_7c89eb2054\" tabindex=\"-1\" value=\"\"><\/div>\r\n                <\/form>\r\n                <!-- <\/div> -->\r\n                 <!--<script type='text\/javascript' src='\/\/s3.amazonaws.com\/downloads.mailchimp.com\/js\/mc-validate.js'><\/script><script type='text\/javascript'>(function($) {window.fnames = new Array(); window.ftypes = new Array();fnames[0]='EMAIL';ftypes[0]='email';fnames[1]='FNAME';ftypes[1]='text';fnames[2]='LNAME';ftypes[2]='text';}(jQuery));var  = jQuery.noConflict(true);<\/script>-->\r\n            <\/div>\r\n        <\/div>\r\n    <\/div>\r\n<\/p>\n<div class=\"swp-hidden-panel-wrap\" style=\"display: none; visibility: collapse; opacity: 0\"><div class=\"swp_social_panel swp_horizontal_panel swp_flat_fresh  swp_default_full_color swp_individual_full_color swp_other_full_color scale-100  scale-\" data-min-width=\"1100\" data-float-color=\"#ffffff\" data-float=\"bottom\" data-float-mobile=\"none\" data-transition=\"slide\" data-post-id=\"1927\" ><div class=\"nc_tweetContainer swp_share_button swp_facebook\" data-network=\"facebook\"><a class=\"nc_tweet swp_share_link\" rel=\"nofollow noreferrer noopener\" target=\"_blank\" href=\"https:\/\/www.facebook.com\/share.php?u=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F\" data-link=\"https:\/\/www.facebook.com\/share.php?u=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F\"><span class=\"swp_count swp_hide\"><span class=\"iconFiller\"><span class=\"spaceManWilly\"><i class=\"sw swp_facebook_icon\"><\/i><span class=\"swp_share\">Share<\/span><\/span><\/span><\/span><\/a><\/div><div class=\"nc_tweetContainer swp_share_button swp_twitter\" data-network=\"twitter\"><a class=\"nc_tweet swp_share_link\" rel=\"nofollow noreferrer noopener\" target=\"_blank\" href=\"https:\/\/twitter.com\/intent\/tweet?text=How+To+Use+Yanado+For+Scrum+Project+Management+Framework+%23agile+%23scrum+%23projectmanagement&url=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F&via=YanadoTool\" data-link=\"https:\/\/twitter.com\/intent\/tweet?text=How+To+Use+Yanado+For+Scrum+Project+Management+Framework+%23agile+%23scrum+%23projectmanagement&url=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F&via=YanadoTool\"><span class=\"iconFiller\"><span class=\"spaceManWilly\"><i class=\"sw swp_twitter_icon\"><\/i><span class=\"swp_share\">Tweet<\/span><\/span><\/span><span class=\"swp_count\">14<\/span><\/a><\/div><div class=\"nc_tweetContainer swp_share_button swp_linkedin\" data-network=\"linkedin\"><a class=\"nc_tweet swp_share_link\" rel=\"nofollow noreferrer noopener\" target=\"_blank\" href=\"https:\/\/www.linkedin.com\/cws\/share?url=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F\" data-link=\"https:\/\/www.linkedin.com\/cws\/share?url=https%3A%2F%2Fyanado.com%2Fblog%2Fhow-to-use-yanado-for-scrum-project-management-framework%2F\"><span class=\"iconFiller\"><span class=\"spaceManWilly\"><i class=\"sw swp_linkedin_icon\"><\/i><span class=\"swp_share\">Share<\/span><\/span><\/span><span class=\"swp_count\">14<\/span><\/a><\/div><div class=\"nc_tweetContainer swp_share_button total_shares total_sharesalt\" ><span class=\"swp_count \">14 <span class=\"swp_label\">Shares<\/span><\/span><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>This article is part of our How To Use Yanado series In our Ultimate\u00a0Guide\u00a0to Scrum\u00a0Project Management Framework, \u00a0we tackled the essentials of Scrum as one of the most popular agile frameworks used by software development teams. For Scrum to be performed successfully, you need a collaborative environment, where Scrum team members are actively communicating and&#8230;<\/p>\n","protected":false},"author":9,"featured_media":1928,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[96],"tags":[134,136,130],"class_list":["post-1927","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-how-to-use-yanado","tag-project-management","tag-scrum","tag-agile","show-featured-img","hd-red"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/posts\/1927","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/comments?post=1927"}],"version-history":[{"count":22,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/posts\/1927\/revisions"}],"predecessor-version":[{"id":2007,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/posts\/1927\/revisions\/2007"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/media\/1928"}],"wp:attachment":[{"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/media?parent=1927"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/categories?post=1927"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yanado.com\/blog\/wp-json\/wp\/v2\/tags?post=1927"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}