AssignmentPart 1The product backlog is made up of three epics and a total of 18 user stories. Plan the release in a hybrid manner using thatproduct backlog by first assigning stories to sprints....

1 answer below »
read the questions and do what it ask for. for example, 1c, you need to create a release/plan map. you can ignore 3b.


Assignment Part 1 The product backlog is made up of three epics and a total of 18 user stories. Plan the release in a hybrid manner using that product backlog by first assigning stories to sprints. Use the following premises: (1) Up to ten ideal developer days of work can be completed by the team in a sprint. (2) EPIC2 is given top priority, followed by EPIC1 and EPIC3. (3) Make sure the MH stories are written first in an epic, followed by SH, then NH. (4) "Promote" the lower priority narrative if it is necessary for the creation of the MH tale but has a lower priority than the MH story. A) Fill in the numbers of the planned sprints for each story: (1, 2, 3, etc.) in the column labeled "Sprint" that is currently empty B) Indicate how many ideal days are expected to be completed for each sprint. C) Create a flight or agile release plan. D) If all stories are finished, how many sprints will be needed to finish this product backlog? E) In how many sprints will this product backlog be finished if just the MH stories are finished? Part 2 A busy university campus cafeteria that offers university dining services would like to improve its service and help customers who want to buy meals online or through a mobile app so they don't have to stand in line while their food is made. The app will be used by dining service customers on their own. It applies to the cafeteria's sushi, grilled meals, sandwiches, and salad stations. After placing her order, the customer is supposed to be able to pick up her lunch from the cafeteria at a specific time without having to wait. The feasting administration needs to utilize the framework to upgrade client assistance and make the most ideal client experience. As a result, there are a lot of aspects of the food service process that the application could improve. A) Create a "casual" use case story for this circumstance. B) The informal use case narrative from A) should be transformed into a "fully dressed" use case narrative with at least three extensions that are in line with your description. Make use of the fully dressed Larman use case. C) There are undoubtedly a variety of other goals that the university cafeteria service system might assist. The technology may make it feasible to administer a payment system unique to the institution, control client preferences, provide management and staff with feedback, promote special offers, particularly for loyal customers, provide dietary advice, and other things. Make a use case diagram that shows how the system as a whole is related to the use case narrative that was produced in stages A) and B). Feel free to utilize your imagination and add whatever additional functionality you believe would be valuable to such a framework. Part 3 The class textbook's system-sequence diagram from figure 5 A) Define the distinction between a design sequence diagram and a system sequence diagram in less than 100 words. B) Make the design sequence diagram "initiatePickUp(orderNbr)" for the message in figure 5. Show the system's reaction when an order is not yet prepared. Determine the display layer, the business logic layer, and the data layer in your diagram. C) Make a design sequence diagram for the "enterQty(qty)" message in Figure 5 that starts with the current subtotal response. Add all classes in this message and use your understanding of loops to show how the system reacts when the quantity entered exceeds the upccode's quantity threshold. The classes that make up the display layer, business logic layer, and data layer should all be indicated on your diagram. Part 4 A UML class diagram for an online restaurant ordering system A) When overlaying packages on the class diagram, choose classes that are logically connected to one another. Choose the amount of packages that interact with one another the least. B) Create a UML package diagram that describes the online restaurant ordering system using the packets you found in A). C) Decide which package the "Customer" class is in. The relational database table classes for this package should be drawn, with each table's necessary properties clearly indicated. Make that the required characteristics are included in the abstract classes. D) Now, in your diagram from C, add the data access and manipulation (DAM) classes to the relational database table classes.
Answered Same DayMar 18, 2023

Answer To: AssignmentPart 1The product backlog is made up of three epics and a total of 18 user stories....

Amar Kumar answered on Mar 19 2023
31 Votes
EPIC
    Story ID
    MoSCow Priority
    Dependencies
    Ideal Days Estimate
    Sprint
    
    Epic 1.1
    SH
    
    2
    1
    
    Epic 1.2
    MH
    Epic 1.1
    3
    1
    
    Epic 1.3
    NH
    Epic 1.2
    3
    1
    
    Epic 1.4
    SH
    Epic 1.3
    1
    2
    
    Epic 1.5
    MH
    Epic 1.4
    2
    2
    
    Epic 1.6
    NH
    Epic 1.5
    1
    2
    
EPIC 1 Ideal Days
    11
    
    
    Epic 2.1
    MH
    
    3
    2
    
    Epic 2.2
    MH
    
    2
    2
    
    Epic 2.3
    MH
    
    2
    3
    
    Epic 2.4
    SH
    
    1
    3
    
    Epic 2.5
    SH
    
    2
    3
     EPIC 1 Ideal Days
    10
    
    
    Epic 3.1
    MH
    
    1
    3
    
    Epic 3.2
    SH
    Epic 3.1
    2
    3
    
    Epic 3.3
    MH
    Epic 3.2
    3
    3
    
    Epic 3.4
    SH
    Epic 3.3
    2
    4
    
    Epic 3.5
    MH
    Epic 3.4
    1
    4
    
    Epic 3.6
    SH
    
    1
    4
    
    Epic 3.7
    NH
    
    2
    4
     EPIC 1 Ideal Days
    12
    
     Product Backlog Ideal Days:
    33
    
Que 1(a):
Que 1(b):
Based on the table with the planned sprints for each story, the expected number of ideal days to be completed for each sprint are:
· Sprint 1: 7 ideal days (EPIC 1: 7 ideal days)
· Sprint 2: 6 ideal days (EPIC 1: 4 ideal days, EPIC 2: 2 ideal days)
· Sprint 3: 10 ideal days (EPIC 2: 8 ideal days, EPIC 3: 2 ideal days)
· Sprint 4: 10 ideal days (EPIC 3: 10 ideal days)
Que 1(c):
Based on the table with the planned sprints for each story, we can create an Agile release plan as follows:
Release 1:
· Sprint 1: EPIC 1.1 (2 ideal days) and EPIC 1.2 (3 ideal days) - Total 5 ideal days
· Sprint 2: EPIC 1.3 (2 ideal days), EPIC 1.4 (1 ideal day), and EPIC 1.5 (2 ideal days) - Total 5 ideal days
· Sprint 3: EPIC 1.6 (1 ideal day), EPIC 2.1 (3 ideal days), and EPIC 2.2 (2 ideal days) - Total 6 ideal days
· Sprint 4: EPIC 2.3 (2 ideal days), and EPIC 2.4 (1 ideal day) - Total 3 ideal days
Release 2:
· Sprint 1: EPIC 2.5 (2 ideal days), and EPIC 3.1 (2 ideal days) - Total 4 ideal days
· Sprint 2: EPIC 3.2 (2 ideal days), and EPIC 3.3 (3 ideal days) - Total 5 ideal days
· Sprint 3: EPIC 3.4 (2 ideal days), and EPIC 3.5 (1 ideal day) - Total 3 ideal days
· Sprint 4: EPIC 3.6 (1 ideal day), and EPIC 3.7 (2 ideal days) - Total 3 ideal days
In this release plan, we have divided the backlog into two releases based on the priorities of the epics. EPIC 2 has the highest priority, followed by EPIC 1 and EPIC 3. Within each release, we have scheduled the sprints based on the dependencies of the stories and the priority of the narratives (MH, SH, and NH).
The total ideal days for Release 1 is 18, and for Release 2 is 15, which sum up to the total ideal day’s estimate for the product backlog, 33. Each release has four sprints with a total ideal day’s estimate of 10 for each sprint, which is the maximum capacity of the team.
Que 1(d):
If all stories are finished, then the total ideal days required to complete the product backlog will be 36 (11 + 10 + 15). Since the team can complete up to 10 ideal developer days of work in a sprint, the number of sprints needed to finish the product backlog will be 4 (36/10 = 3.6, which rounds up to 4).
Que 1 (e):
To determine how many sprints will be needed to finish just the MH stories, we need to identify the total number of ideal days required for the MH stories in the product backlog.
From the product backlog provided earlier, we can see that the total number of ideal days required for the MH stories is 14 (3+2+2+2+2+3).
Since the team can complete up to 10...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here