The first two-week sprint during the sprint review meeting


At the end of the first two-week sprint, during the sprint review meeting, you show interested stakeholders the questionnaire you distributed to students (about membership fees and how to store materials) and discuss the findings. Students indicated that they did not want advertisements cluttering the app, so you remove the Establish advertising requirement from the product backlog. Arwin considers the acceptance criteria for the questionnaire and declares that PBI done. You also demonstrate the Create Membership feature of the Android app. Because changes were made to this PBI that are not reflected in its current operation, Arwin does not declare it done, but rather moves it to the top of the product backlog, so that it will be included in the next sprint.

In your second sprint, you finish the Create Membership works on Android requirement and fulfill the Credit card processing requirement. Both are declared done by Arwin. At the end of the sprint review meeting for Sprint 2, you discuss your velocity and show your burndown chart. In your first sprint, you completed one small task (questionnaire) worth 2 story points, added PBIs (Web app works on MacBook, Web app works on PC, App works on iOS) worth 16 total story points, and deleted a PBI (establish advertising) worth 6 story points. In your second sprint, you completed one medium task (Create Membership works on Android) worth 4 story points and one large task (Credit card processing) worth 8 story points. Your average velocity, based on actual effort, at this point is (2 story points in first sprint + 12 story points in second sprint) / 2 sprints = 7 story points per sprint.

The top of your current burndown chart looks like this.

In the starter Excel spreadsheet provided, create a tab called Burndown. Input the table on the left. Note that initially in Sprint 0, you begin with 62 story points, none are done, and none have been added. The remaining story points should be calculated using this formula.

Remaining current sprint = Remaining prior sprint - Done current sprint + Added current sprint

For example, in Sprint 1, 70 = 62 - 8 + 16. Create a formula in Excel to do the calculations in the Remaining Story Points column. The items in the current product backlog (see below) have been assigned to sprints based on an average current velocity of 7.

Use this information to complete the table and Release Burndown chart started above. You may assume at this point that no other story points will be added. (If they are added in the future, you can adjust the table and chart appropriately at that time. Also, as you complete more sprints, your velocity estimate will improve and may warrant additional adjustments to the table and chart.) See Figure 27-3 on page 470 for an example of a burndown chart.

The current product backlog contains the following items.

On the tab called Product Backlog in the Excel spreadsheet, you will find some of the information above. Your spreadsheet should contain the following qualities.

The Sprint Number should be selected from a list of values in the range [1,10].

The Sprint Start and End dates should be set automatically using Excel's VLOOKUP function.

The Status should be selected from a list of values in the set (Approved, Deleted, In Progress, Done).

The format of the elements in a row should change based on the Status selected for that row. Use conditional formatting as follows.

Done - font color is gray

Deleted - font color is gray and text has a strike through it

In Progress - font is bold and dark green

Solution Preview :

Prepared by a verified Expert
HR Management: The first two-week sprint during the sprint review meeting
Reference No:- TGS01725256

Now Priced at $120 (50% Discount)

Recommended (94%)

Rated (4.6/5)