Scrum Ch 4 Initiate--Develop Epic(s)

What are the two mandatory inputs required for the Develop Epic(s) process?

Scrum Core Team Project Vision Statement

Which is a mandatory tool for the Develop Epic(s) process?

User Group Meetings

How does the Develop Epic(s) process help in managing Change in projects?

Approved Change Requests and Unapproved Change Requests are used to manage Change in Scrum Projects and they are non-mandatory inputs to the Develop Epic(s) process. Approved Change Requests: Approved Change Requests originating from the program or portfolio areINPUTS to be added to the list of approved project changes for implementation in future Sprints. Each change can require its own Epic or User Story and could become an input to the Develop Epic(s) process. Approved Change Requests to this process could also result from other Scrum processes. Unapproved Change Requests: Request for changes are usually submitted as Change Requests and remain in an unapproved status until they are formally approved. Unapproved Change Requests to Develop Epic(s) process could come from Create Deliverables, Conduct Daily Standup and other processes.

Can you create one or more Epic(s) for this case study?

Epics are unrefined User Stories e.g. one Epic in the case study could be 'As Michele I want to be able to create a user profile so that I save time doing future purchases and can spend more time with my family.' Other Epics could relate to the following functionality: Running Promotional Offers on the website. Ability to show multiple images for each product. Enabling creation of an e-kart to buy multiple products in one transaction. Social Media Integration. Integrating Payment Gateway. Delivery Time Scheduling. Giving customers the option to give reviews and ratings. Back Office - Enabling VMfoods operations personnel to upload product information and availability. Mobile app. Loyalty Program [It is important to note that there are times when an Epic might not be related to any one person, then the Epic can be generic e.g. "As an user I want ...." but when things are created to point out certain desires then the story should use the major persona involved.]

What are the two mandatory outputs of the Develop Epic(s) process?

Epics; Personas

Can you determine what would be all the possible inputs, tools and outputs for the Develop Epic(s) process?

Inputs 1. Scrum Core T eam* 2. Project Vision Statement* 3. Stakeholder(s) 4. Program Product Backlog 5. Approved Change Requests 6. Unapproved Change Requests 7. Program and Portfolio Risks 8. Laws and Regulations 9. Applicable Contracts 10. Previous Project Information 11. Scrum Guidance Body Recommendations Tools 1. User Group Meetings* 2. User Story Workshops 3. Focus Group Meetings 4. User or Customer Interviews 5. Questionnaires 6. Risk Identification Techniques 7. Scrum Guidance Body Expertise Outputs 1. Epic(s)* 2. Personas* 3. Approved Changes 4. Identified Risks

What is the basis for developing Epics?

Project Vision Statement serves as the basis for developing Epics.

Create two Personas for this case study.

Persona 1: Employed Single Male Andy is a 28 year old bachelor living in San Francisco.He is an investment bank and works 12-14 hours every day. He loves shopping but due to lack of time he prefers doing it online.This is true of his grocery shopping as well. Persona 2: Housewife Michele is a 39 year old housewife and mother of 2 living in New York, with a husband that works for a multi-national organization.They used to shop together in a physical store but that only happens on weekends now.She currently prefers making her purchases online and not having the restriction of waiting until the weekend.This makes her feel more independent.