Abhishek KumarB.Tech. 3rd Year

Computer Science and EngineeringHindustan Institute of Technology and Management,

Agra

Seminar on

Introduction History of Scrum Introduction to Agile Scrum Framework

Scrum Roles Events Scrum Artifacts

Applications of Scrum Advantages/Disadvantages Conclusion

Index

Scrum is an iterative and incremental Agile software Development Framework for managing product development.

Scrum is a management and control process that cuts through complexity to focus on building software that meets business needs.

Scrum adopts an empirical approach—accepting that the problem cannot be fully understood or defined, focusing instead on maximizing the team's ability to deliver quickly, to respond to emerging requirements and to adapt to evolving technologies and changes in market conditions.

Introduction

1995 Design of a new method: Scrum by Jeff Sutherland & Ken Schwaber Enhancement of Scrum by Mike Beedle & combination of Scrum with

XP

1996 Introduction of Scrum at OOPSLA conference

2001 Publication “Agile Software Development with Scrum” by Ken

Schwaber & Mike Beedle

2005 Scrum and XP were the most popular Agile frameworks implemented

2009 Scrum is the single most popular Agile implementation. With popularity there is criticism or frustration of failure in some

cases

History of Scrum

Agile is SDLC model, a combination of iterative and incremental process models with focus on process adaptability and customer satisfaction by rapid delivery of working software product.

In agile the tasks are divided to time boxes (small time frames) to deliver specific features for a release.

The most popular agile methods include:Rational Unified Process (1994), Scrum (1995), Crystal

Clear, Extreme Programming (XP) (1996), Adaptive Software Development(ASD), Dynamic Systems Development Method (DSDM) (1995)

What is Agile ?

Agile Model

The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules.

Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.

Sprint The heart of Scrum is a Sprint, a time-box of two weeks or

one month during which a potentially releasable product increment is created.

A new Sprint starts immediately after the conclusion of the previous Sprint.

In product development, a sprint is a set period of time during which specific work has to be completed and made ready for review.

Scrum Framework

Roles Product owner Scrum Master The Team

Events Sprint planning Sprint review Sprint retrospective Daily scrum meeting

Artifacts Product backlog Sprint backlog

Scrum Framework

Roles Product owner

The product owner defines what to do and in what order to do it.

Product owners decide which features and functionality to build and the order in which to build them. 

The Product Owner is responsible for maximizing the value of the product and the work of the Team.

Scrum Framework

RolesScrumMaster

ScrumMasters act as coaches and facilitators to Scrum teams, ensuring that the team and the rest of the organization obtain optimum results from the Scrum process. 

The ScrumMaster is the keeper of the scrum process. He/she is responsible for: making the process run smoothly removing obstacles that impact productivity organizing and facilitating the critical

meetings

Scrum Framework

Roles The Team

The Team is self-organizing and cross-functional. That means the team comprises of analysts, designers, developers, testers, etc. as appropriate and as relevant to the project.

Scrum Framework

Scrum Process Framework

Product Backlog

The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases.

Scrum Process Framework

Grooming

Product backlog grooming is made up of the activities of writing and refining, estimating, and prioritizing product backlog items.

Scrum Process Framework

Sprint Planning

During sprint planning, a sprint backlog is produced to help the team acquire confidence that it can deliver the committed product backlog items.

Scrum Process Framework

Sprint Backlog

A prioritized list of tasks that the team needs to complete during the sprint.

The sprint backlog is a list of stories the sprint team members have agreed to complete for a sprint.

Scrum Process Framework

Sprint Execution

The period of time during which the development team performs the tasks necessary to complete the features selected during sprint planning.

Scrum Process Framework

Daily Scrum

The Daily Scrum Meeting is a 15-minute meeting for the Team, conducted daily to quickly understand the work since the last Daily Scrum Meeting and create a plan for the next 24 hours.

Scrum Process Framework

Potentially Shippable Product

It means completed to a high degree of confidence and being of such quality that the work could be shipped to end customers at the end of a sprint.

Potentially Shippable = state of confidence.

Potentially Shippable = Validated learning

Potentially Shippable ≠ Shipped

Scrum Process Framework

Sprint Review

At the end of a sprint the team demonstrates the functionality added during the sprint.

During the Sprint Review, a presentation of the increment that is getting released is reviewed.

Scrum Process Framework

Sprint Retrospective

At the end of each sprint the team participates in a retrospective meeting to reflect on the sprint that is ending and identify opportunities to improve in the new sprint.

The scrum master and team members discuss the work completed and demonstrate the completed work to the product owner.

Scrum Process Framework

Commercial software

In-house development

Contract development

Financial applications

ISO 9001-certified applications

Embedded systems

Video game development

Applications of ScrumWebsites

Satellite-control software

Handheld software

Mobile phones

Network switching applications

ISV applications

AdvantagesIt provides customer

satisfaction by optimizing turn around time and responsiveness to requests

Increase the quality Provide better estimates

while spending less time creating them

Scrum is fast, quick and can adapt changes easily

Never changes the schedule, or Sprint

Work estimates are much easier

Work proceeds and completes more logically

Advantages/Disadvantages of Scrum Disadvantages

It’s hard!Documentation is very lessTeam members dedication is

very importantTeam work is highly

essentialIf team members does not

cooperate well, the project will face failure

Scrum doesn’t fix anything: the team has to do it

Bad products will be delivered sooner, and doomed projects will fail faster

Scrum Tools

Agile and Scrum are not the same.Scrum is advised to teams with experienced team

members as the Framework requires great collaboration and self-organization as well.

If the Scrum rules are not followed strictly, a project can lead to failure. Hence, it is necessary to have a proper understanding of Scrum concepts among the entire team.

Evidence shows that scrum has gained popularity and will continue in the many years to come.

Conclusion

http://www.innolution.com

https://www.scrumalliance.org

http://wiki.servicenow.com

http://www.ijetae.com/(ISSN 2250-2459, ISO 9001:2008 Certified Journal, Volume 3, Issue 6, June 2013)

https://en.wikipedia.org/

http://www.tutorialspoint.com

References

“ Thank you”Any Queries???