Please work through each problem and help me understand all steps All questions 1,2,3 and 4 please show math for each question Background All the questions in this homework are related to work at 2 Technology, Inc You are the project manager for the first (v1 0) release of 2 's latest product, ChordArc The software team that will be working on this product is the Avengers development team The Avengers operate using the Scrum model with 2 week sprints Each sprint includes 10 working days sprints start on a Monday and finish on the Friday of the second week The questions in this assignment are sequential and happen at specific dates Instructions Question 1 Product Release Estimation (December 1, 2023) Before starting coding on the project, the product manager worked with all their stakeholders to show a product backlog of the required user stories for v1 0 of ChordArc This included meeting with the lead engineer on the team to come up with t shirt size estimates for all of the user stories Product Estimates Rank User Story T Shirt Size 1 US1 M 2 US2 M 3 US3 L 4 US4 S 5 US5 XXL 6 US6 M 7 US7 M 8 US8 M 9 US9 S 10 US10 L 11 US11 M 12 US12 M 13 US13 XXL 14 US14 L 15 US15 L 16 US16 L 17 Accessibility Plan S 18 Prefs Dialog M 19 DB Table M 20 Tutorial M 21 Payment Pipeline XL 22 Installer M 23 US23 XS 24 US24 S 25 US25 XXL 26 US26 XL 27 US27 M The t shirt sizes were based on the following timetable T Shirt Sizes Shirt XS S M L XL XXL FTE estimate weeks week 1 week 2 weeks 3 weeks 4 weeks 6 weeks Based on the above data, what is the total FTE estimate weeks for the entire project The team plans to start working on the product on January 8, 2024 ( which is in the future) Your boss has asked for a date when you will release the product Why is the information up to this point not sufficient to provide a projected completion date Question 2 Team Burn down chart (February 26, 2024) Time has passed Coding on ChordArc started as planned on January 8, 2024 The team started their 4th sprint on February 19, 2024 At sprint planning, the team committed to 6 user stories which they broke into 44 tasks with initial bean estimates per task based on planning poker The team is currently exactly halfway through its fourth sprint To be specific, it is first thing Monday morning, just after the daily standup, and the team just provided the scrum master (you) with their updated progress about what they did on Friday In the following chart Tasks that were taken on by an engineer have initials in the owner column The first remaining effort estimate after an engineer started on a task is underlined All numbers after an engineer started on a task represent the engineer's updated estimate as of daily standup A zero means the task was completed The team bid the sprint based on a velocity of 420 beans for the sprint (42 beans per day) Sprint Table User Story Rank Task Owner Est D1 D2 D3 D4 D5 Accessibility Plan 6 Research 13 13 13 13 13 13 Accessibility Plan 6 Scoping 13 13 13 13 13 13 Accessibility Plan 6 Ranking 8 8 8 8 8 8 Accessibility Plan 6 User Story Creation 5 5 5 5 5 5 Prefs Dialog 3 Deep Design EE 21 15 19 5 0 0 Prefs Dialog 3 Dialog Layout EE 13 13 13 13 13 13 Prefs Dialog 3 Model Structure EE 13 13 13 13 13 3 Prefs Dialog 3 Tab Controls 3 3 3 3 3 3 Prefs Dialog 3 Data Validation 5 5 5 5 5 5 Prefs Dialog 3 Unit Tests 5 5 5 5 5 5 DB Table 1 Table Design CC 21 21 16 0 0 0 DB Table 1 Table Build CC 8 8 8 6 0 0 DB Table 1 Table APIs CC 5 5 5 5 2 0 DB Table 1 Input Filters CC 8 8 8 8 8 1 DB Table 1 Consistency Tests 8 8 8 8 8 8 DB Table 1 Speed Tests 8 8 8 8 8 8 DB Table 1 Unit Tests 8 8 8 8 8 8 DB Table 1 App integration 21 21 21 21 21 21 Tutorial 4 Screen 1 BB 5 0 0 0 0 0 Tutorial 4 Screen 2 BB 3 0 0 0 0 0 Tutorial 4 Screen 3 BB 13 13 4 0 0 0 Tutorial 4 Screen 4 BB 8 8 8 8 8 4 Tutorial 4 Screen 5 BB 21 21 21 15 5 0 Tutorial 4 Screen 6 2 2 2 2 2 2 Tutorial 4 Pathway Nav 5 5 5 5 5 5 Tutorial 4 Unit Tests 8 8 8 8 8 8 Payment Pipeline 2 Deep Design DD 21 9 0 0 0 0 Payment Pipeline 2 DB Fields APIs DD 13 13 12 3 0 0 Payment Pipeline 2 Fraud API Integ AA 8 8 8 8 8 8 Payment Pipeline 2 Address API Integ DD 5 5 5 5 0 0 Payment Pipeline 2 Processing API Integ DD 21 21 21 21 21 5 Payment Pipeline 2 Load Tests 13 13 13 13 13 13 Payment Pipeline 2 Address UX 8 8 8 8 8 8 Payment Pipeline 2 Pmt Method UX 8 8 8 8 8 8 Payment Pipeline 2 Confirmation UX 2 2 2 2 2 2 Payment Pipeline 2 Save CC Dialog 5 5 5 5 5 5 Payment Pipeline 2 Save Addr Dialog 5 5 5 5 5 5 Payment Pipeline 2 Unit Tests 21 21 21 21 21 21 Installer 5 Learn Install App AA 13 7 5 0 0 0 Installer 5 Flow design AA 8 8 8 1 0 0 Installer 5 Implementation AA 8 8 8 8 4 0 Installer 5 Happy Path Tests AA 2 2 2 2 2 0 Installer 5 Unhappy path tests AA 8 8 8 8 8 4 Your tasks Show a sprint table in Excel (by copying the above table) that you can use to calculate track daily progress You do not need to copy this to your Word PDF document In your Word PDF, document, how many beans did the team burn down on each of the first 5 days Show a sprint burndown graph (line chart) in Excel to track progress for the entire sprint Graph both the actual daily sprint progress (for days that have passed) and ideal burndown (for all days in the sprint) based on the team's predicted velocity Copy this to your Word PDF file Is the sprint on track, ahead, or behind How do you know Question 3 Team velocity (February 26, 2024) Here is the data from the first three completed sprints on this project Sprint 1 User Story Estimated Beans Finished Remaining Beans US1 75 Yes US2 48 Yes US3 133 Yes US4 21 Yes US5 164 Yes US6 99 No 99 Sprint 2 User Story Estimated Beans Finished Remaining Beans US6 99 Yes US7 51 Yes US8 95 Yes US9 57 No 57 US10 132 Yes US11 41 Yes Sprint 3 User Story Estimated Beans Finished Remaining Beans US9 57 Yes US12 81 Yes US13 198 No 51 US14 141 Yes US15 102 No 77 US16 119 Yes As mentioned above, the team thinks its velocity is 42 beans per day Using the data from the first 3 sprints, do you agree Explain Question 4 Product velocity(February 26, 2024) Using all of the data provided so far in this assignment Calculate the Avengers team's backlog velocity (in FTE estimate weeks per sprint) Use the task based model for calculating team velocity Show a product backlog burndown graph (line chart) in Excel to track progress for the entire project Show both per sprint progress (for the first three completed sprints) and ideal burndown (for sprints 4 and beyond) based on the team's velocity from (B) Using all of the data provided so far in this assignment, what date would you provide senior leadership for when the project will be complete Justify your answer

The Answer is in the image, click to view ...

Answered step by step

Verified Expert Solution

Link Copied!

Question

1 Approved Answer

Posted on Jul 03, 2024

Please work through each problem and help me understand all steps All questions 1,2,3 and 4. please show math for each question. Background All the

Please work through each problem and help me understand all steps

All questions 1,2,3 and 4. please show math for each question.

Background

All the questions in this homework are related to work at ²Technology, Inc. You are the project manager for the first (v1.0) release of ²'s latest product, ChordArc.

The software team that will be working on this product is the "Avengers" development team. The Avengers operate using the Scrum model with 2-week sprints. Each sprint includes 10 working days; sprints start on a Monday and finish on the Friday of the second week.

The questions in this assignment are sequential and happen at specific dates.

Instructions

Question 1: Product Release Estimation (December 1, 2023)

Before starting coding on the project, the product manager worked with all their stakeholders to show a product backlog of the required user stories for v1.0 of ChordArc. This included meeting with the lead engineer on the team to come up with t-shirt size estimates for all of the user stories.

Product Estimates:

Rank	User Story	T-Shirt Size
1	US1	M
2	US2	M
3	US3	L
4	US4	S
5	US5	XXL
6	US6	M
7	US7	M
8	US8	M
9	US9	S
10	US10	L
11	US11	M
12	US12	M
13	US13	XXL
14	US14	L
15	US15	L
16	US16	L
17	Accessibility Plan	S
18	Prefs Dialog	M
19	DB Table	M
20	Tutorial	M
21	Payment Pipeline	XL
22	Installer	M
23	US23	XS
24	US24	S
25	US25	XXL
26	US26	XL
27	US27	M

The t-shirt sizes were based on the following timetable:

T Shirt Sizes:

Shirt	XS	S	M	L	XL	XXL
FTE-estimate-weeks	week	1 week	2 weeks	3 weeks	4 weeks	6 weeks

Based on the above data, what is the total FTE-estimate-weeks for the entire project?
The team plans to start working on the product on January 8, 2024 (which is in the future). Your boss has asked for a date when you will release the product. Why is the information up to this point not sufficient to provide a projected completion date?

Question 2:Team Burn down chart (February 26, 2024)

Time has passed:

Coding on ChordArc started as planned on January 8, 2024.
The team started their 4th sprint on February 19, 2024. At sprint planning, the team committed to 6 user stories which they broke into 44 tasks with initial bean estimates per task based on planning poker.
The team is currently exactly halfway through its fourth sprint. To be specific, it is first thing Monday morning, just after the daily standup, and the team just provided the scrum master (you) with their updated progress about what they did on Friday.

In the following chart:

Tasks that were taken on by an engineer have initials in the owner column.
The first remaining effort estimate after an engineer started on a task is underlined.
All numbers after an engineer started on a task represent the engineer's updated estimate as of daily standup.
A zero means the task was completed.
The team bid the sprint based on a velocity of 420 beans for the sprint (42 beans per day).

Sprint Table:

User Story	Rank	Task	Owner	Est	D1	D2	D3	D4	D5
Accessibility Plan	6	Research		13	13	13	13	13	13
Accessibility Plan	6	Scoping		13	13	13	13	13	13
Accessibility Plan	6	Ranking		8	8	8	8	8	8
Accessibility Plan	6	User Story Creation		5	5	5	5	5	5
Prefs Dialog	3	Deep Design	EE	21	15	19	5	0	0
Prefs Dialog	3	Dialog Layout	EE	13	13	13	13	13	13
Prefs Dialog	3	Model Structure	EE	13	13	13	13	13	3
Prefs Dialog	3	Tab Controls		3	3	3	3	3	3
Prefs Dialog	3	Data Validation		5	5	5	5	5	5
Prefs Dialog	3	Unit Tests		5	5	5	5	5	5
DB Table	1	Table Design	CC	21	21	16	0	0	0
DB Table	1	Table Build	CC	8	8	8	6	0	0
DB Table	1	Table APIs	CC	5	5	5	5	2	0
DB Table	1	Input Filters	CC	8	8	8	8	8	1
DB Table	1	Consistency Tests		8	8	8	8	8	8
DB Table	1	Speed Tests		8	8	8	8	8	8
DB Table	1	Unit Tests		8	8	8	8	8	8
DB Table	1	App integration		21	21	21	21	21	21
Tutorial	4	Screen 1	BB	5	0	0	0	0	0
Tutorial	4	Screen 2	BB	3	0	0	0	0	0
Tutorial	4	Screen 3	BB	13	13	4	0	0	0
Tutorial	4	Screen 4	BB	8	8	8	8	8	4
Tutorial	4	Screen 5	BB	21	21	21	15	5	0
Tutorial	4	Screen 6		2	2	2	2	2	2
Tutorial	4	Pathway Nav.		5	5	5	5	5	5
Tutorial	4	Unit Tests		8	8	8	8	8	8
Payment Pipeline	2	Deep Design	DD	21	9	0	0	0	0
Payment Pipeline	2	DB Fields/APIs	DD	13	13	12	3	0	0
Payment Pipeline	2	Fraud API Integ.	AA	8	8	8	8	8	8
Payment Pipeline	2	Address API Integ.	DD	5	5	5	5	0	0
Payment Pipeline	2	Processing API Integ.	DD	21	21	21	21	21	5
Payment Pipeline	2	Load Tests		13	13	13	13	13	13
Payment Pipeline	2	Address UX		8	8	8	8	8	8
Payment Pipeline	2	Pmt. Method UX		8	8	8	8	8	8
Payment Pipeline	2	Confirmation UX		2	2	2	2	2	2
Payment Pipeline	2	Save CC Dialog		5	5	5	5	5	5
Payment Pipeline	2	Save Addr. Dialog		5	5	5	5	5	5
Payment Pipeline	2	Unit Tests		21	21	21	21	21	21
Installer	5	Learn Install App	AA	13	7	5	0	0	0
Installer	5	Flow design	AA	8	8	8	1	0	0
Installer	5	Implementation	AA	8	8	8	8	4	0
Installer	5	Happy Path Tests	AA	2	2	2	2	2	0
Installer	5	Unhappy path tests	AA	8	8	8	8	8	4

Your tasks:

Show a sprint table in Excel (by copying the above table) that you can use to calculate & track daily progress. You do not need to copy this to your Word/PDF document.
In your Word/PDF, document, how many beans did the team burn down on each of the first 5 days?
Show a sprint burndown graph (line chart) in Excel to track progress for the entire sprint. Graph both the actual daily sprint progress (for days that have passed) and ideal burndown (for all days in the sprint) based on the team's predicted velocity. Copy this to your Word/PDF file.
Is the sprint on track, ahead, or behind? How do you know?

Question 3: Team velocity (February 26, 2024)

Here is the data from the first three completed sprints on this project:

Sprint 1:

User Story	Estimated Beans	Finished?	Remaining Beans
US1	75	Yes
US2	48	Yes
US3	133	Yes
US4	21	Yes
US5	164	Yes
US6	99	No	99

Sprint 2:

User Story	Estimated Beans	Finished?	Remaining Beans
US6	99	Yes
US7	51	Yes
US8	95	Yes
US9	57	No	57
US10	132	Yes
US11	41	Yes

Sprint 3:

User Story	Estimated Beans	Finished?	Remaining Beans
US9	57	Yes
US12	81	Yes
US13	198	No	51
US14	141	Yes
US15	102	No	77
US16	119	Yes

As mentioned above, the team thinks its velocity is 42 beans per day. Using the data from the first 3 sprints, do you agree? Explain.

Question 4: Product velocity(February 26, 2024)

Using all of the data provided so far in this assignment:

Calculate the Avengers team's backlog velocity (in FTE-estimate-weeks per sprint). Use the task-based model for calculating team velocity.
Show a product backlog burndown graph (line chart) in Excel to track progress for the entire project. Show both per-sprint progress (for the first three completed sprints) and ideal burndown (for sprints 4 and beyond) based on the team's velocity from (B).
Using all of the data provided so far in this assignment, what date would you provide senior leadership for when the project will be complete? Justify your answer.