Scrum Methodology well elucidated

37
Scrum Agile For Everyone OMSATS C V ehari

Transcript of Scrum Methodology well elucidated

Page 1: Scrum Methodology well elucidated

ScrumAgile For Everyone

OMSATSC Vehari

Page 2: Scrum Methodology well elucidated

What Is Scrum?

Scrum (the name is derived from an activity that occurs during a rugby match

Page 3: Scrum Methodology well elucidated

By Jeff Sutherland and his development team.

Scrum is a subset of Agile. It is a lightweight process framework for agile development, and the most widely-used one.

Agile is a time boxed, iterative approach to software delivery that built software incrementally.

Introduction:

What Is Agile?

Page 4: Scrum Methodology well elucidated

Some Agile Methodologies are:

Agile Methodologies

KanBanDSDM

Xp Crystal

Scrum

Page 5: Scrum Methodology well elucidated

Productivity and efficiency:

87% said their 93% Said adopting team were Agile helped them more productive improve speed to using agile market

Page 6: Scrum Methodology well elucidated

Scrum Is Used By

Scrum has been used by:

Page 7: Scrum Methodology well elucidated

Scrum Is Used For

Commercial software

Fixed-price projects

Contract development

WebsitesVideo game developmentEmbedded

systems

Page 8: Scrum Methodology well elucidated

To manage complex software's

Increases productivity and reduces time

Adjust smoothly to rapidly-changing requirements

Build Quality in

Why to Use Scrum?

Provide better estimates while spending less time creating them

Page 9: Scrum Methodology well elucidated

Scrum benefits for business

Quicker ROI

Lower Total Cost

Reduce Risk

Page 10: Scrum Methodology well elucidated

Scrum benefits for Developer

Teaming

Quality Work

Sense Of Done

Visible Progress

Page 11: Scrum Methodology well elucidated

Cycle Of Scrum

Page 12: Scrum Methodology well elucidated

Change

No changes during a sprint:

Page 13: Scrum Methodology well elucidated

Scrum Process

Sprint View

Sprint .Retrospective

Update . product backlog

Sprint Planning . Meeting

Daily Cycle

Product Increment

Page 14: Scrum Methodology well elucidated

Sprint Planning Meeting

Scrum Process

Sprint View

Sprint .Retrospective

Update . product backlog

Sprint Planning . Meeting

Daily Cycle

Product Increment

The first meeting to kick off the sprint.

Attended by : Scrum Master, Development Team, the Product Owner invited stakeholders.

Product owner describes the highest priority features to the team.

At the end team developed the Sprint Backlog

Page 15: Scrum Methodology well elucidated

Daily Cycle

Scrum Process

Sprint View

Sprint .Retrospective

Update . product backlog

Sprint Planning . Meeting

Daily Cycle

Product Increment

It is 15 minute meeting held every day.

In daily Scrum Meeting , Scrum Master Ask the Three Questions:

What have you done since the last meeting? Are there any obstacles in the way of meeting your goal? What will you do before the next meeting?

Page 16: Scrum Methodology well elucidated

Product Increment

Scrum Process

Sprint View

Sprint .Retrospective

Update . product backlog

Sprint Planning . Meeting

Daily Cycle

Product Increment

The sum of all the product backlog Items completed during a sprint and all previous sprints.

At the end of a sprint, the increment must be complete.

Page 17: Scrum Methodology well elucidated

Sprint View

Scrum Process

Sprint View

Sprint .Retrospective

Update . product backlog

Sprint Planning . Meeting

Daily Cycle

Product Increment

It is like the demo of new product.

Page 18: Scrum Methodology well elucidated

Sprint Retrospective

Scrum Process

Sprint View

Sprint .Retrospective

Update . product backlog

Sprint Planning . Meeting

Daily Cycle

Product Increment

Usually done after sprint and also after sprint review. The meeting is facilitated by the Scrum Master and the product owner.

Page 19: Scrum Methodology well elucidated

Update Product Backlog

Scrum Process

Sprint View

Sprint .Retrospective

Update . product backlog

Sprint Planning . Meeting

Daily Cycle

Product Increment

After each sprint is given to owner

he may update their requirements.

Page 20: Scrum Methodology well elucidated
Page 21: Scrum Methodology well elucidated

Vs.

ScrumWaterfall

Vs.

Scrum XP Comparison

Page 22: Scrum Methodology well elucidated

Do not allow changes

Work in the sequence

Validation at sprint Review

Does not prescribe any engineering practices

Team allow changes

Work in a strict priority order

Validation All time

Prescribe engineering practices

Scrum Xp.

Page 23: Scrum Methodology well elucidated

Scrum Vs.

Waterfall

Iterative

Requirement will change

Unknown Steps

Daily meeting

Not Iterative

Requirement will not Change

Known Steps

Not Daily MeetingsScrum

Water

Fall

Page 24: Scrum Methodology well elucidated

Scrum Framework

Roles

Ceremonies Artifacts

Page 25: Scrum Methodology well elucidated

Roles

Product Owner

Team

ScrumMaster

Page 26: Scrum Methodology well elucidated

Ceremonies

Sprint Planning

Sprint Review

Daily Scrum Meeting

Page 27: Scrum Methodology well elucidated

Artifacts

Product Backlog

Sprint Backlog

Page 28: Scrum Methodology well elucidated

•Define the features of the product•Prioritize features according to market value

Product Owner

Roles

Product Owner

Scrum Master

Team

Page 29: Scrum Methodology well elucidated

•Represents management to the project•Removes impediments •Ensure that the team is fully functional and productive

Scrum Master

Roles

Product Owner

Scrum Master

Team

Page 30: Scrum Methodology well elucidated

•Define the features of the product•Prioritize features according to market value

Team

Roles

Product Owner

Team Scrum Master

Page 31: Scrum Methodology well elucidated

•A collaborative meeting in the beginning of each Sprint.•Takes 8 hours and consists of 2 parts

Sprint Planning

Ceremonies

Sprint Planning

Sprint Review

Daily ScrumMeeting

Page 32: Scrum Methodology well elucidated

•Is a meeting in which team members make commitments to each other and to the Scrum Master

Daily Scrum Meeting

Ceremonies

Sprint Planning

Sprint Review

Daily ScrumMeeting

Page 33: Scrum Methodology well elucidated

•Is held at the end of each Sprint•Team presents what it accomplished during the sprint

Sprint Review

Ceremonies

Sprint Planning

Sprint Review

Daily ScrumMeeting

Page 34: Scrum Methodology well elucidated

•Requirements for a system, expressed as a prioritized list of Backlog Items•Usually is created during the Sprint Planning Meeting•Is managed and owned by a Product Owner

Product Backlog

ArtifactsProduct

Backlog

SprintBacklog

Page 35: Scrum Methodology well elucidated

•A subset of Product Backlog Items, which define the work for a Sprint.

•Estimates are updated whenever there’s new information.

•Changes

Sprint Backlog

ArtifactsProduct

Backlog

SprintBacklog

Page 36: Scrum Methodology well elucidated

Advantage:

Agile scrum helps the company in saving time and money.

Cutting edge developments can be quickly coded and tested using this method.

Mistake can be easily corrected.

It is easier to deliver a quality product in a scheduled time.

Disadvantage:

Team members leave during a development. (Huge Effect)

This methodology needs experienced team members only.

Difficult for the Scrum master to plan, structure and organize a project that lacks a clear definition.

Page 37: Scrum Methodology well elucidated

Improvement:

Allow the team to determine their Sprint capacity.

Work is not added during the Sprint.

The team has permission to add work to the Sprint to make improvements.