![\"\"](\"https:\/\/www.59secondsagile.com\/wp-content\/uploads\/2020\/04\/Scrum-Master-Banner-Introductory-Offer-1536x450-1-1024x300.gif\")
<\/a>Creating Tasks and User Stories is a critical element in the extraction of User Requirements in any Scrum Project. User Stories define a specific component that is needed as part of the whole Product Deliverable. It is described in language that is clear to the Business User. The technical specifications that underlie this small User statement are not described. They need to be Documented as briefly and concisely as possible. This is achieved by breaking down each User Story into a set of Tasks<\/strong>. The Tasks are then the building blocks of the Sprint. <\/p>\n\n\n\n Team members complete User Stories by taking one or more Tasks, developing the functionality and demonstrating it during a Sprint Review<\/a> meeting at the end of the iteration. The Daily Stand-Up Meeting is utilized to report on the Tasks completed the previous day and the Tasks to be Done today. Tasks can have interdependencies, which gives a pattern to how they are constructed. They are not taken on arbitrarily, but constantly viewed as part of the whole.<\/p>\n\n\n\n When all of the User Stories have been created, they are added into the Product Backlog in priority order. The Stories with the highest priority are put forward for inclusion in the next Sprint. Throughout the Sprint Planning Meeting, the Scrum Team (Agile Scrum Master<\/a>, Scrum Product Owner and Scrum Development Team<\/a>) discuss the number of Stories they can commit to completing in the next Sprint. An agreement is reached and a set of User Stories are moved into the Sprint Backlog for execution. These Stories can now be divided into Tasks during the Sprint Planning<\/a> Meeting.<\/p>\n\n\n\nCreating Tasks: Getting to Task Discovery<\/h2>\n\n\n\n