Lesson 3 Hands-On10 pointsDirectionsIn this Hands-On Project, we will revisit the previous exercise with a Scrum twist. You will be required to create a Scrum Backlog and plan your first sprint....

trello.com


Lesson 3 Hands-On10 points Directions In this Hands-On Project, we will revisit the previous exercise with a Scrum twist. You will be required to create a Scrum Backlog and plan your first sprint. Our focus in this exercise will be to give you a brief experience as both the Product Owner and a Scrum Development Team. Through this activity, you will come to understand some of the different processes of a Scrum team. This Hands-On will be graded, so be sure you complete all requirements. To turn in this project, please take screenshots of each requirement and add it to a Word document. Then, you will be able to turn in every requirement at once. Caution! Do not submit your project until you have completed all requirements! You will not be able to resubmit. Additional Info! Before starting this assignment, watch this workshop: Scrum Project. --- Requirements Leveraging what you've learned about the Scrum method, you will be required to Populate a Product Backlog with User Stories. This exercise will give you practice with authoring User Stories and expose you to the challenges of the Product Owner. You will then plan your first sprint, an exercise that the Scrum Master would facilitate. Through the planning process, you will be required to provide Story Points for each of the User Stories that you have created. Meet the below requirements: · Create a Trello Project: Log into your Trello account and click Create new Board. Select a project title of your choosing. Select "none" for the team and change the board setting from private to public. · Create a Scrum Board: Add 4 Lists: · Product Backlog · To-Do · In-Progress · Done · Create a Product Backlog: Populate your Product Backlog by adding a minimum of 20 Cards. Each Card should represent a user story, and should follow the standard user story format: "As a ____, I need ____ to ____." · Groom your Backlog: Reorder the stories by priority with the most urgent stories up top. Consider the value to the customer, and ensure that the most valuable stories are at the top. · Add Story Points: Once you have your 20 User stories written, you will need to switch gears from Product Owner to Development Team. Go back through each story and prepend the story point value to the title like this: "[8] As a ____, I need ____ to ____". Be sure to follow the Fibonacci sequence when pointing your stories, and if a story ends up larger than a 13, break it down into smaller stories. · Plan a Sprint: Lastly, assume your scrum team has a historical velocity of 36 points per sprint. Plan out your next sprint by moving the appropriate cards into the To-Do list. Your To-Do list should contain stories that are designed as Potentially Shippable Increments(PSI). Example Project: Feel free to plan any project you like; however, if you need inspiration for a project to design, you may use the following: · Your client is asking you to plan a project to develop a web application which will allow students to connect with like-minded students for projects. · They would like a student to be able to log into a web application and either post an idea for a project, or search other student's ideas to find something they are interested in working on. · The students will need the ability to connect with each other and discuss working together. Any options to make the application more social would be valued. · The client values quality and innovative solution over something that is quick to market. They are looking to you and your team to help define some features that would motivate students to engage in using this platform to connect and build better communication.