18
Agile Scrum Methodology Prateek Aggarwal Android Team -India

Agile Scrum Methodologies

Embed Size (px)

Citation preview

Page 1: Agile Scrum Methodologies

Agile Scrum Methodology

Prateek AggarwalAndroid Team -India

Page 2: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 2

Published on February 2001 by 17 Software Developers to

develop a Software in better way .

They came up with these Statement of values :

• Individuals & Interactions over processes and tools

• Working Software over comprehensive documentation

• Customer collaboration over contract negotiation

• Responding to change over following a plan

Agile ManifestoAgile Manifesto

Page 3: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 3

• Scrum

• Extreme Programming (XP)

• Adaptive Software Development (ASD)

• Dynamic System Development Method (DSDM)

• Agile Modeling

• Agile Unified Process (AUP)

Agile Alliance (www.agilealliance.org)A non-profit organization promotes agile development

Agile Methods

Page 4: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 4

Page 5: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 5

Why Market Research ?

It becomes before Approving the project.

Benefits of doing market research :

• For Setting the Realistic targets – Growth / Sales

• Can propose more solutions to Client for increasing sale

• Identifying potential of customer

• Understand existing customers of similar requirements

• Identifying new business opportunities

Page 6: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 6

• Define the features of the product

Decide on release date and content

• Be responsible for the profitability of the product (ROI)

• Prioritize User Stories

• Adjust features and priority every iteration, as needed

• Accept or reject work results

Product Owner

Page 7: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 7

• Be a Team Player

• Radiate information

• Support the Product Owner

• Improve the team’s engineering practices and tools as

needed

Six attributes of the Good Scrum Master :

Responsible, Humble, Collaborative, Committed

Influential, Knowledgeable

Scrum Master

Page 8: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 8

• Cross-functional Teams : QA, Programmers , UI

Designers etc.

• Typically 5-10 people and It varies project to project

• Membership can change only between sprints

• Teams are self-organizing

Team

Page 9: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 9

• Ordered list of requirements and It’s written in story format

• It contains rough estimates of both business value and

development effort

• Product owner can gauge this timeline & reorder the backlog

items in Release Backlog

• estimated effort to complete each backlog item is decided by

Development Team

Product Backlog

Page 10: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 10

Release Backlog

• Release Backlog is a set of User Stories taken from the

Product Backlog

• Prioritize User Stories according to estimation

• Add only finalized User Stories in project

• It again breaks into Sprint Backlog

Page 11: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 11

• A subset of Release Backlog Items, which define the

work for a Sprint

• Should be updated everyday

• No more than 300 tasks in the list

• If a task requires more than 16 hours, it should be

broken down

• Team adds new tasks whenever they need to in order to

meet the Sprint Goal

• Estimates are updated whenever there’s new

information

• Team can remove unnecessary tasks

Sprint Backlog

Page 12: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 12

Parameters:• Daily 15-minutes Stand-up• Not for problem solving

Three questions:• What did you do yesterday?• What will you do today?• What obstacles are in your way?

Why Required ?• In this meeting team members make

commitments to each other and to the Scrum Master

• It’s a good way for a Scrum Master to track the progress of the Team

Daily Scrum

Page 13: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 13

Sprint PlanningMeeting

Product Backlog

Team Capabilities

Management

Business Conditions

Product

Owner

Scrum

Team

Customers

Sprint Goal

Sprint Backlog

Sprint Planning Meeting

Page 14: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 14

User Story

• A user story is a very high-level definition of a

requirement

• Contains enough information so that the developers

can produce a reasonable estimate of the effort to

implement it

Page 15: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 15

• Review the work that was completed and not completed

• Present the completed work to the stakeholders

• Incomplete work cannot be demonstrated

Participants

• Customers

• Management

• Product Owner

• Other engineers

Sprint Review

Page 16: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 16

• Two main questions are asked in the sprint

retrospective:

• What went well during the sprint?

• What could be improved in the next sprint?

• Feedback meeting

• Scrum Team Only

• Three-hour time limit

Sprint Retrospective

Page 17: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 17

Sprint Burn Down Chart

• shows remaining hours in current sprint.

• Ideally should burn down to zero at the end of the Sprint

• Helps to increase velocity for completing the sprint on time

Sprint Burn Down chart

• Will the release be done on right time?

• X-axis: No of days

• Y-axis: amount of hours remaining

It’s a “big picture” view of project’s progress (all the

releases)

Burn Down Chart

Page 18: Agile Scrum Methodologies

2/8/2015 Mutual Mobile India 18

THANK YOU