Introducing scrum Framework slides techxpla

27
Welcome to Agile Webinar Series Organized By: Computer Society of India Mumbai Chapter www.csimumbai.org www.techxpla.com For any question during the webinar you can tweet at #CSIMum

Transcript of Introducing scrum Framework slides techxpla

Welcome to Agile Webinar Series

Organized By:Computer Society of India

Mumbai Chapter

www.csimumbai.org

www.techxpla.com

For any question during the webinar you can tweet at

#CSIMum

Webinar Series on Agile and Digital Marketing

1. Introducing Agile Date: 12/03/2016 Time: 11 AM

2. Advanced Agile Date 19/03/2016 Time 11 AM

3. Scrum Framework Date 26/03/2016 Time 11 AM

4. How to start marketing with zero budget for B2B IT Business 16/03/2016 Time: 11 AM

5. Inbound marketing tips and tricks for B2B IT Technology Business 01/04/2016 Time: 3 PM

6. How to target account based marketing for IT industry 02/04/2016 Time: 11 AM

7. Social Media Marketing for IT industry B2B marketing 06/04/2016 Time: 11 AM

8. How to choose digital agency for IT industry 09/04/2016 Time: 11 AM

Upcoming Sessions

Classroom Sessions in Mumbai & Online Sessions on Agile & Digital Marketing.

Upcoming 2 days Workshop on Digital Marketing ; 1 day workshop on LinkedIN marketing.

Online 16 hours Online training in April/May on Digital Marketing

Today’s Speaker

Anushree VermaTechnical Delivery Manager/Agile Coach, Capgemini

Certified SCRUM Master(CSM)

Certified Trainer from PMI(PMI)

Certified Agile Professional Trained(PMI)

Distributed Agilist

PMP Trained

ITIL Certified

Latest Blog

www.techxpla.com

Agenda

• Introduction to ‘SCRUM’• Lifecycle of SCRUM• Principles of SCRUM• Components of SCRUM –

SCRUM TeamSCRUM ArtifactsSCRUM Events/Ceremonies

Different methodologies in Agile

9Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

SCRUM

10Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

Principles of SCRUM

• Every activity is time boxed. Every commitment is time boxed and every artifact maintained and followed is time boxed.

• Time boxing helps in adhering to commitment and schedule.Time boxed

• Teams are small, cross functional and preferably co-located.

• Small teams help in managing the teams and adhering to the commitments easy.

Small Teams

• A small deliverable is made at the end of iteration.

• Small deliverables keeps the deliverables flowing periodically and also makes administration simple and manageable.

Incremental Deliverables

11Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

Lifecycle of SCRUM

Sprint planning

Daily

ReviewSprint

Sprint Retrospective

12Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

Components of SCRUM - ROLES

PRODUCT OWNER

DEVELOPMENT TEAMSCRUM MASTER

13Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

PRODUCT

OWNER

Sets the VISION ; Responsible for maximizing the business value delivered by the team Eye on market Knowledgeable , empowered and engaged Accepts and rejects work

Managing the product BacklogCreation ManagementPrioritization Set clear expectation for acceptance

Represent the desire to stake holders Manages stakeholders and sponsor expectation

Motivates the team , celebrate success

Components of SCRUM - ROLES

14Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

Components of SCRUM - ROLES

15Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

Makes sure SCRUM is understood by team and enactedA servant-leaderFacilitating the scrum ceremoniesCoaching the team in self-organization and cross-functionalityRemoving impediments to the development team’s progressBringing in changes that increases the team productivityWorking with other Scrum masters in the for effective scrum in org Teaching the development team scrum

SCRUM

MASTE

R

Components of SCRUM - ROLES

16Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

Deliver high quality potentially shippable increments Cross functional and self-organizingConvert product backlogs into increments of working softwareOptimal size of development team 6(+/-) 3 Scrum recognizes no titles other than “Developer” Accomplish sprint goal

DEVELOPMEN

T TEAM

Components of SCRUM - ROLES

17Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

• Ordered list of everything that might be needed in the product.

• Single source of requirements for any changes to be made

• Evolves over time

Product Backlog

• Subset of items from the Product Backlog selected for the Sprint plus a plan for delivering the increment.

• Forecast by the Development Team as to what will be in the next increment based on the Definition of Done

Sprint Backlog

• Sum of all the Product Backlog items completed during this and all previous Sprints.

• A potentially shippable product

• Must meet the Definition of Done

Increment

• A common understanding of what it means to complete a particular element for the Increment, including activities and workflow items necessary to move the element to the next state.

Definition of Done

Components of SCRUM - ARTIFACTS

18Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

• Inspect the Increment and adapt the Product Backlog if needed.Sprint Review

Meeting

Sprint Planning Meeting

• Develop the plan for transforming items from the Product Backlog into an Increment.

Daily Scrum Meeting

• Synchronize the activities of the Development Team.

• Opportunity for the Development Team to inspect itself.Sprint

Retrospective

Sprint• Heart of the Scrum process where a usable, “Done”, potentially

shippable product is developed.

Components of SCRUM - EVENTS

19Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

SPRINT BACKLOG

SPRINT PLANNING MEETING

PRODUCT BACKLOG

PR

IOR

ITY

Other interested stakehold

ers

PO, Scrum

Master , Dev Team

Attended By:

What PBIs can we commit to?

What is our sprint goal?

What tasks can we identify for each story?

How long do we think each will take?

Components of SCRUM - EVENTS

20Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

DAILY SCRUM MEETING

• Synchronize the activities of the Development Team by answering three questions

Purpose

• 15 minutes, same time, same place every dayDuration

• Development Team

• Scrum Master (if required)Attendees

• What did I do yesterday to help the development team meet Sprint Goal?

• What will I do today to help the Development team meet the Sprint Goal?

• What impediments do I or the development team have to meet the Sprint Goal?

Structure

• Shared knowledge of the Development Team’s activitiesOutputs

Components of SCRUM - EVENTS

21Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

DAILY SCRUM MEETING

• Update on activity done the previous day

• Update on activities planned for today

• Impediments

• Any new risks identified

• “Solutioning” – solving technical or project problems during the Daily Scrum

• Late arrivals

• Changing meeting’s time and / or location

Components of SCRUM - EVENTS

22Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

SPRINT REVIEW MEETING

• Inspect the Increment and adapt the Product Backlog if needed Purpose

• 4 hours for a 1 month Sprint and proportionately less for smaller sprints, at the conclusion of the SprintDuration

• Product Owner

• Stakeholders

• Development Team

• Scrum Master

Attendees

• Development team demonstrates what has been “Done” based on the PBIs and obtains agreement from the Product Owner

• Obtain feedback from the StakeholdersStructure

• Revised Product Backlog for the next SprintOutputs

Components of SCRUM - EVENTS

23Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

SPRINT RETROSPECTIVE

MEETING

• Opportunity for the Scrum Team to inspect itself and adapt processesPurpose

• 3 hours for a 1 month Sprint and proportionately less for smaller sprints, immediately following the Sprint Review meetingDuration

• Development Team

• Scrum Master

• Product Owner

Attendees

• Inspect the Sprint with regards to people, processes and tools

• Identify what went well and what needs to be improved

• Create a plan for implementing improvements

Structure

• Improvements to the team to increase quality and productivityOutputs

Components of SCRUM - EVENTS

24Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

Components of SCRUM - EVENTS

TWO WEEK SCRUM CYCLE

25Copyright © Capgemini 2013. All Rights Reserved

Principles of Agile

SCRUM BOARD

Thanks!

Any Questions?

You can find me at : [email protected]

+91 9890109427

Thank You

www.csimumbai.org

www.techxpla.com

For any question during the webinar you can tweet at

#CSIMum