• Author / Uploaded
• piyu_kotrashetti

Citation preview

SMC Case Study Document v4.0

©2014 SCRUMstudy.com

1

Role-play: Mock Product Development In this role-play, we will develop an Online Sales Channel for a fictional company. We will go through a simulated but complete Scrum project, practicing all meetings prescribed by Scrum and using the related artifacts. Each step of the role-play will use the output/results of preceding steps. For practical purposes, for this role-play we will focus solely on the Web pages needed for an Online Sales Channel and assume that any necessary infrastructure (databases, server-interfaces, etc.), back-office functionality, human, and other resources already exist. Since we can’t develop real Web pages during a two-day class, we will develop them on paper using a technique called “Paper Prototyping” (for more information, see www.paperprototyping.com or “Paper Prototyping: The Fast and Easy Way to Design and Refine User Interfaces” by Carolyn Snyder; Morgan Kaufmann Publishers; 2003; ISBN-13: 978-1-55860-870-2).

©2014 SCRUMstudy.com

2

Product Vision Meeting Case Study VMfoods is a 10-year-old, nationwide grocery chain with about 100 outlets. Lately, the management team at VMfoods has observed that their customers are leading a fast-paced lifestyle and do not travel long distances to do their grocery shopping. They also feel that because grocery shopping is not a highly involved process (and because VMfoods always provides high-quality products), the best way to increase market share would be to deliver groceries to the customer’s residence. In this regard, a representative has approached your team on behalf of VMfoods to create a website for customers to prepare their online delivery order and make payments. The vision and generic requirements are given to you by a company representative (the faculty) in a Product Vision meeting.

©2014 SCRUMstudy.com

3

Role-play: Create an Initial Product Backlog With your team, create an initial Product Backlog (containing high-level user stories, also called “Epics”) for the given Product Vision. Some Epics have already been defined for your reference. Create additional Product Backlog items (another 7–10). Item # 1

2

3

User Story Description As a Customer, I want to access the VMfoods online grocery system so that I can see information and services specific to me As an online grocery shopper, I want to be able to have multiple payment gateway options so that I can purchase groceries/services As an online grocery shopper, I want to be able to browse for groceries and add products to a shopping cart so that I can select items to buy

©2014 SCRUMstudy.com

Initial Estimate 4

Revised Estimate

5

5

4

Issues with creating a Product Backlog 1. Team members disagreeing with the Product Owner regarding priorities

2. Product Backlog Item not well defined:

©2014 SCRUMstudy.com

5

Role-play: Release Planning Meeting The Product Owner from each team will now conduct a Release Planning Meeting to explain the project requirements to the team, decide on the length of the Sprint, and discuss deadlines and the Product Backlog.

©2014 SCRUMstudy.com

6

Issues with the Release Planning Meeting 1. Product Owner trying to convince the team to take on more than they want to:

2. Product Owner not agreeing with activity estimates:

3. All Product Owners don't have input/consensus:

©2014 SCRUMstudy.com

7

Sprint Planning Meeting Using the existing Prioritized Product Backlog (initially provided by the Product Owner and refined by you during Release Planning), plan your next Sprint with the faculty as your Product Owner, commit to the scope of your next Sprint, and create a Sprint Backlog. List all the tasks related to each user story and estimate them. Create an initial Burndown chart. Item #

User Story Description

Story 1

As a Customer, I want to access the VMfoods online grocery system so that I can see information and services specific to me As a Customer, I would like the website to have a feature through which the visitor can create a unique login for themselves, so that VMfoods can maintain a database of their visitors. As a Web developer, I would like to track user data through their unique login, so that the client can make use of this data to customize offerings to the visitors. As a Product Owner, I want to ensure that the customer is able to log in as a guest, if he or she does not want to log in. The Login feature should be placed on the top right section of all pages. The first-time login should collect information like Name, e-mail id, delivery address, age (optional), gender (optional), and family size (optional).

1.1

1.2

1.3

1.4

©2014 SCRUMstudy.com

Initial Estimate

Revised Estimate

4

8

The requirements are discussed below in detail, including tasks description. Requirements: 1. Login feature:  As a Customer, I would like the website to have a feature through which the visitor can create a unique login for themselves, so that VMfoods can maintain a database of their visitors.  As a Web developer, I would like to track user data through their unique login, so that the client can make use of this data to customize offerings to the visitors.  As a Product Owner, I want to ensure that the customer is able to log in as a guest, if he or she does not want to log in.  The Login feature should be placed on the top right section of all pages. The first-time login should collect information like Name, e-mail id, delivery address, age (optional), gender (optional), and family size (optional).  Customers are allowed to create a unique password for themselves. 2. Payment mechanism:  The website should also have accessibility to various payment gateways in order to enable payment after the shopping.  The page should be redirected to the payment gateway when the customer clicks the “proceed button” after they finishing shopping.  The gateway should return back to the payment success page on the website, which should have links to any loyalty discounts or referral discounts that we provide. 3. Generic browsing and shopping Cart:  Users should be able to, at a cursory glance, get an idea about the products in the VMfoods portfolio. It should include a downloadable magazine including all products at VMfoods.  Users should have a shopping cart facility to track the products they’ve added.  If the user has not completed the transaction in a given visit, the cart should feature it in the next visit as pending items.  There should be a mechanism wherein the customer can alter products on the cart (increase quantity, change the brand, etc.) without having to delete the product and go back to buy it. 4. Category tabs:  Categories should be featured as tabs on the landing page, leading to separate category pages when clicked.  The tabs should be present on the top half of the landing page as a line where the users can click and proceed to the relevant pages. 5. Top-selling products:  Individual category tabs on the main page should have drop-down menus featuring the top 5 selling products in that category.  A user should be able to go to the individual product page upon clicking the respective tab. 6. The website is to be prepared using the house colors: green for headings, blue for subheadings, and black for text. 7. Featured products should be featured on the side of the main page. 8. Contact us, terms and conditions, about us, etc., pages are to be filled out and present at the bottom of the page.

©2014 SCRUMstudy.com

9

Issues with Developing the Sprint Backlog 1. An outlier that will not change their mind:

2.

One person dominates the planning session and doesn't give others the opportunity to share their ideas:

3. Team arguing with the Product Owner about priority of User Stories

©2014 SCRUMstudy.com

10

Implementation We do a mock product development using the technique of paper product development. The technique will be explained to you by your faculty member. You will use it to develop the features committed to in the Sprint Planning Meeting. In this role-play, the duration of a simulated workday will be time-boxed to 5 minutes. A Sprint will consist of 3 working days of 7 minutes (2 minutes Daily Standup, 5 minutes development).

©2014 SCRUMstudy.com

11

Daily Standup Meeting Perform a Daily Standup Meeting. Based upon the previously simulated workday, each team member answers three relevant questions:   

What did I complete yesterday? What will I complete today? Are there any impediments?

Possible Issues 1. Executive management trying to interfere:

2. Problem solving occurring:

©2014 SCRUMstudy.com

12

Sprint Review Sprint Review Meetings are a part of the Demonstrate and Validate Process. At the end of the Sprint, demonstrate the items your team has completed in the preceding Sprint to the Product Owner (represented by the faculty or a member from another team).

Issues in Sprint Review 1. Team member refuses to accept when Product Owner rejects a Product Backlog Item:

2. Team members blame each other for failure to complete Sprint goals:

©2014 SCRUMstudy.com

13

Retrospect Sprint Meeting Discuss what went well and what did not. Identify improvement opportunities

©2014 SCRUMstudy.com

14