Velocity sprint planning 2022 Best
This assignment is about velocity sprint planning. Assume that you have completed the stories in your first sprint as you previously identified. Now assume that you have completed a 2nd sprint and after completion of the 2nd sprint you have completed the top 1/2 of your user stories in your backlog (take 1/2 the user stories, not 1/2 the story points).
Velocity sprint planning.
PART 2 ● Assume that you have completed the stories in your first sprint as you previously identified. Now assume that you have completed a 2nd sprint and after completion of the 2nd sprint you have completed the top 1/2 of your user stories in your backlog (take 1/2 the user stories, not 1/2 the story points). This includes completing the original set of sprint 1 user stories (that you previously identified) plus additional stories that would complete the top 1/2 of your backlog in your 2nd sprint. If you have an even number of stories in your backlog, then select the first ½ of them.
Velocity sprint planning.
For example, if you have a total of 10 user stories in your product backlog, you will select the top 5. If you have an odd number of stories in your backlog, you can select either one less or one more to reach a whole number. For example, if you have a total of 11 user stories in your backlog, choose either the top 5 or the top 6 user stories. Assume that you have used two sprints to complete the stories you just selected. Assume each sprint takes 5 days to complete. ○ Calculate your team’s velocity per sprint for this project (please show us your calculations). Velocity sprint planning
Velocity sprint planning.
Also, based on the velocity you just calculated for this project, calculate how many sprints it will take you to complete all of your user stories in your backlog. Share all your calculations in your submitted documentation. ○ Next, create a burn down chart (or burn up chart) for your project. Your chart should show ‘Time’ (in days or sprints) on the x axis (horizontal axis) to complete all the sprints necessary to complete your project (complete all user stories in your backlog). Continue to assume that each sprint is 5 days in length. Show the number of story points on the y axis (vertical axis).
Velocity sprint planning.
For the number of story points, you should use the total story points for your entire backlog. You will plot two lines: your ideal line based on past team performance, and your actual line based on team performance in this project. Plot your ideal burn down line based on your ‘historical team velocity’ from part 1 of the assignment. Next, plot your actual performance to date using the top ½ of your user stories in the backlog and their story point estimates. You can plot the number of story points finished at the end of sprints 1 and 2 for your actual burn down line. https://youtu.be/cgJAw15Vv5w
Velocity sprint planning.
Remember, that you started this exercise with a set of user stories you finished for sprint 1, then added to that user stories for sprint 2 that completed the top ½ of your backlog of stories at the end of 2 sprints. Plot only those story points completed in the first 2 sprints for your ‘actual’ line. For assistance with creating a burn down chart in excel, you can reference this video: (Will provide Link) ● Based on the chart you created, explain the progress of your project in detail over the first 2 sprints, current project status, and how many sprints in total are needed to complete all the work in your backlog.
Velocity sprint planning
Submit your PART 2 documents to the corresponding Assignments Dropbox. ● Submit a burn down or burn up chart for your project as well as the team’s velocity assuming that you have completed one half of your user stories. Submit a document that describes: ○ Based on your burn down or burn up chart – how would you describe the status of your project after 2 sprints are complete. Include your calculations used for your team velocity and your calculations for how many sprints would be needed to complete the entire backlog of stories.
Attached Files
|