4
Happy New year, Tutors. I need some assistance with the items listed below. Please read thoroughly before accepting bid. I have attached how part 2 of it should be done. Thank you for your assistance.
Part 1:
User Story Points and Team Velocity
User story points are critical for estimating the schedule and cost of a SCRUM project. For this discussion:
- Define what user story points are, and explain how they are determined.
- Provide at least four examples of user stories (these can come from your weekly SCRUM Project). Estimate the points of each example, and explain why you provided the estimate you did.
- Describe how team velocity is estimated.
- Explain how user story points are used in project management, and how they relate to the team’s velocity.
Explain the advantages of using this approach for project scheduling (rather than the more traditional approach of scheduling around the estimation of hours).
Must be a minimum of 300 words.
Part 2:
SCRUM Project, Part 4: Release Planning with Priority
Prior to beginning work on this assignment, read Chapters 6 and 7 in your textbook, and watch the
Managing Schedule, Release Planning, and Cost with Visual Studio Online (VSO) (Links to an external site.)
video. This video will demonstrate how VSO can be used to setup the schedule for your SCRUM project.
Last week, you developed a product backlog for your SCRUM project. This week, you will estimate the schedule of your project in VSO. Follow the steps below to estimate the schedule of your project:
- Determine the cadence of your iterations.
- Revisit each work item in your VSO backlog and estimate the level of effort that is required to implement it.
- Determine the velocity of your team.
- Calculate the number of iterations that are needed to complete the project.
Assume that you have only 1 SCRUM development team made of three developers. Also assume that the business owners mandated three release dates that the development team must commit to.
Your project schedule must span at least 4 sprints
Once you have estimated your project schedule in VSO, take a screenshot of it to submit for your assignment. Set up the starting dates of your iterations based on either regular work schedule or business mandated dates or both.
In addition to your screenshot, include a 750- to 1250-word (3-5 page) paper with the following:
- Summary of the relative level of effort for the items in your product backlog and your team velocity
- Explanation of your approach to completing this assignment and the decisions you made
- Summary of personal reflection and lessons learned in completing this assignment
The assignment
- Must be 750-1250 words (3-5 pages) in length (not including title and references pages, or the screenshot of your product backlog) and formatted according to APA style as outlined in the Writing Center.
- Must include a separate title page with the following:
Title of paper
Student’s name
Course name and number
Instructor’s name
Date submitted - Must use at least 1 credible source in addition to the course text.
- Must document all sources in APA style as outlined in the Writing Center.
- Must include a separate references page that is formatted according to APA style as outlined in the Writing Center.
>W _ Initial Set Up 1 2 3 4 5 2 Course Records
2
3
Initial Set Up
ID Number
Feature/Backlog Item
Priority
1
Student Records
1.1
Student Add
1.2
Student Modify
6
1.3
Student Delete
11
2
Course Records
2.1
Course Add
2.2
Course Modify
7
2.3
Course Delete
12
3
Class Records
3.1
Class Add
3.2
Class Modify
8
3.3
Class Delete
13
4
Registration
4.1
Registration Add
4.2
Registration Drop
9
5
Mobile Access
5.1
Mobile Add
5.2
Mobile Delete
10
Notes
1. Save a new MS Excel file
2. In Cells A1, B1, and C1 set up titles
3. Indicate the features with ID numbers 1, 2, 3, 4, and 5
4. Insert enough rows for the backlog items or user stories under each feature.
5. Under each feature insert the backlog items and assign an ID number that ties it to the feature.
For example student add would be ID 1.1, Student Modify would be 1.2, and Student delete
would be 1.3.
6. Set priorities for each backlog item. I arbitrarily set the priorities shown above.
Sort Backlog Items by Priroty
ID Number Feature/Backlog Item Priority
Estimated Work Level
1.1 Student Add 1 3
2.1 Course Add 2 3
3.1 Class Add 3 3
4.1 Registration Add 4 3
5.1 Mobile Add 5 3
1.2 Student Modify 6 2
2.2 Course Modify 7 2
3.2 Class Modify 8 2
4.2 Registration Drop 9 2
5.2 Mobile Delete 10 1
1.3 Student Delete 11 1
2.3 Course Delete 12 1
3.3 Class Delete 13 1
1 Student Records
27
Total Effort
Units
3 Class Records
4 Registration
5 Mobile Access
Notes:
1
Go to tab data
2
Within tab data go to sort
3
Cover all cells with data in them
You should see gray area. Note this may happen
automatically if you go to step 4 first.
4
Click on sort
5
Select ‘sort by’ priority
6
The result is that all of the backlog items are now shown in priority order.
Note 2:
You can also resort by feature by sorting again but this time select ‘sort by’
W4_Proj.
| Plan Item | Amount | Derivation | ||||||
| Project Cadence | weeks | |||||||
| User Story | 26 | user story effort units | From +D23 | |||||
| Velocity Estimate | ||||||||
| Number of Fixed Length Iterations | Sprints | User Story Estimate/Velocity Estimate rounded up | ||||||
| User Story Effort Units | ||||||||
| Initial Priority | Revised Priority | |||||||
| Sprint Identification | Start | End | Sprint User Story Effort Units | |||||
| Sprint 01 | 1/6/20 | 1/17/20 | ||||||
| Sprint 02 | 1/20/20 | 1/31/20 | ||||||
| Sprint 03 | 2/3/20 | 2/14/20 | ||||||
| Sprint 04 | 2/17/20 | 2/28/20 | ||||||
| Sprint 05 | 3/2/20 | 3/13/20 | ||||||
| Sprint 06 | 3/16/20 | 3/27/20 | ||||||
| Sprint 07 | 3/30/20 | 4/10/20 | ||||||
| Sprint 08 | 4/13/20 | 4/24/20 | ||||||
| Sprint 09 | 4/27/20 | 5/8/20 | ||||||
| Double Check >> | ||||||||
| Release Plan | ||||||||
| User Story Work Plan by Sprint | Release Details | |||||||
| WBS ID | Release Date | Released Effort Units | ||||||