Order ID:89JHGSJE83839 | Style:APA/MLA/Harvard/Chicago | Pages:5-10 |
Instructions:
ITSCM770 Product Backlog Functional System Prototype Term Paper
Learning Goal: I’m working on a business case study and need an explanation and answer to help me learn.
Refine the product backlog for the project and select the user stories to include in sprint 2 (2 points)
Note: An item not completed in Sprint 1 must be returned to the Product Backlog, “re-sized”, and prioritized so that the item may be considered for inclusion in Sprint 2. Because an item was not completed in Sprint 1 does not mean that it must or should be included in Sprint 2. If an item that was not completed in Sprint 1 is included in Sprint 2, the item tasks that had a status of “done” from Sprint 1 must not be included in the Sprint 2 Backlog.
Create the sprint 2 backlog based on the decisions made in #1. Explain the changes. (2 points)
Assume day 1 of sprint 2 is complete; create both a Task Board and Burndown chart for sprint 2. (4 points)
Make a recommendation regarding whether to release the product at the end of sprint 2 and what next steps should be for the project team after the completion of sprint 2. (2 points)
Case Study
Wisconsin weather has become surprisingly unpredictable and volatile in the last few years.
In the past year alone, some areas of Wisconsin had experienced unusually heavy rainfall (resulting in severe flooding), life-threatening wind-chill temperatures, heavy snowfalls, high winds and other extreme weather.
During these times, often local business – including restaurants – would close. This made it difficult for company workers to find places to order lunch during the day
. Local inhabitants and some off-campus college students also found themselves facing a lack of food or shopping options. Particularly for these types of residents, transportation in inclement weather could be an issue, since many walked or biked to their destinations.
During a particularly long stretch of dangerous wind chill weather, a group of young entrepreneurs attending a workshop wanted to go out for lunch.
After walking to two restaurants that were close by (in -35-degree wind chill weather!), they returned to the workshop without lunch because both restaurants were closed due to the weather.
Irritable and hungry, the group members thought of the idea to have a local resource available to help people find businesses that would be open during extreme weather emergencies.
They quickly formed a small startup company and Scrum team to create an online system for this purpose.
Their vision was for this online system to initially provide information only to attract site visitors and awareness, which would ultimately lead to potential revenue to be generated through ads, business sign ups, and other marketing and promotional services.
Product Backlog
After evaluating the weather reports for the upcoming month, then looking back over the past two years, the team decided it would be worthwhile to produce such a system.
They agreed to identify the initial priorities for the system based on the local college population (living off campus, without meal plans) and downtown area (young professionals living in the area and/or at work), since those potential customers were most likely to eat out often and to be looking for last minute dining options during inclement weather.
The Product Owner (PO) came up with the following Product Backlog for the project. After meeting with the ScrumMaster (SM) and Development Team (DT) members, the project team decided that this system could be fully developed within 2 month
3 attachments
ITSCM770 Product Backlog Functional System Prototype Term Paper
RUBRIC |
||||||
Excellent Quality 95-100%
|
Introduction
45-41 points The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned. |
Literature Support 91-84 points The background and significance of the problem and a clear statement of the research purpose is provided. The search history is mentioned. |
Methodology 58-53 points Content is well-organized with headings for each slide and bulleted lists to group related material as needed. Use of font, color, graphics, effects, etc. to enhance readability and presentation content is excellent. Length requirements of 10 slides/pages or less is met. |
|||
Average Score 50-85% |
40-38 points More depth/detail for the background and significance is needed, or the research detail is not clear. No search history information is provided. |
83-76 points Review of relevant theoretical literature is evident, but there is little integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are included. Summary of information presented is included. Conclusion may not contain a biblical integration. |
52-49 points Content is somewhat organized, but no structure is apparent. The use of font, color, graphics, effects, etc. is occasionally detracting to the presentation content. Length requirements may not be met. |
|||
Poor Quality 0-45% |
37-1 points The background and/or significance are missing. No search history information is provided. |
75-1 points Review of relevant theoretical literature is evident, but there is no integration of studies into concepts related to problem. Review is partially focused and organized. Supporting and opposing research are not included in the summary of information presented. Conclusion does not contain a biblical integration. |
48-1 points There is no clear or logical organizational structure. No logical sequence is apparent. The use of font, color, graphics, effects etc. is often detracting to the presentation content. Length requirements may not be met |
|||
You Can Also Place the Order at www.collegepaper.us/orders/ordernow or www.crucialessay.com/orders/ordernow
ITSCM770 Product Backlog Functional System Prototype Term Paper |
ITSCM770 Product Backlog Functional System Prototype Term Paper