Introduction to Scrum

About Scrum Key Values Scrum Framework Roles Processes Artifacts

Agile Manifesto

• Individuals and interactions over processes and tools

• Working software over comprehensive documentation

• Customer collaboration over contract negotiation

• Responding to change over following a plan

12 principles1. Our highest priority is to satisfy the customer

through early and continuous delivery of valuable software.

2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

4. Business people and developers must work together daily throughout the project.

12 Princilpes1. Build projects around motivated individuals. Give

them the environment and support they need, and trust them to get the job done.

2. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

3. Working software is the primary measure of progress.

4. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

12 Principles

• Continuous attention to technical excellence and good design enhances agility.

• Simplicity--the art of maximizing the amount of work not done--is essential.

• The best architectures, requirements, and designs emerge from self-organizing teams.

• At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

What is Scrum?

o Agile way of Project Managemento A team based- collaborative approacho Iterative & Incremental developmento Focus to deliver “business value”

More about Scrum

•Scrum is an agile process that allows to focus on delivering the highest business value in the shortest time. •It allows to rapidly and repeatedly inspect actual working

software (every two weeks to one month).•The business sets the priorities. Teams self-organize to

determine the best way to deliver the highest priority features. •Every two weeks to a month anyone can see real working

software and decide to release it as is or continue to enhance it for another sprint.

Key Values

oSimplicity is Essential (the power of less)

oSelf-organizing teamsoCommunication is the keyoDeliver Frequently

Scrum Framework• Roles

-Product owner-Project Manager/ Scrum Master-Team

• Ceremonies-Sprint Planning -Sprint Review

-Sprint Retrospective-Daily Scrum meeting

• Artifacts-product backlog

-sprint backlog-burn-down charts

Roles

•Product owner•Project Manager/ Scrum

Master•Team

Product Owner

o Define the features of the producto Decide on release date and contento Be responsible for the profitability of the

product (ROI)o Prioritize features according to market value o Adjust features and priority every iteration, as

needed o Accept or reject work results

Project Manager ( Scrum Master)

o Represents management to the projecto Responsible for enacting Scrum values and

practiceso Removes impediments o Ensure that the team is fully functional and

productiveo Enable close cooperation across all roles and

functionso Shield the team from external interferences

The Team

• Typically 3-9 people• Cross-functional:•Programmers, testers, user experience

designers, etc.• Members should be full-time

•May be exceptions (e.g., database administrator)

Sprint retrospectiveCEREMONIES

•Sprint planning•Sprint review•Sprint retrospective•Daily scrum meeting

Sprint planningo Team selects items from the product

backlog they can commit to completingo Sprint backlog is createdo Tasks are identified and each is estimated

(1-16 hours)o Collaboratively, not done alone by the

PMo High-level design is considered

Print Retrospectiveso Periodically take a look at what is and is not

workingo Typically 15–30 minuteso Done after every sprinto Whole team participateso Project Managero Product ownero Teamo Possibly customers and others

The Daily Scrumo Parameterso Dailyo 15-minuteso Stand-up

o Not for problem solvingo Whole world is invitedo Only team members, project manager, product

owner, can talko Helps avoid other unnecessary meetings

The Sprint Reviewo Team presents what it accomplished during the

sprinto Typically takes the form of a demo of new

features or underlying architectureo Informalo 2-hour prep time ruleo No slides

o Whole team participateso Invite the world

Artifacts

•Product backlog•Sprint backlog•Burn-down charts

Product Backlog

o The requirementso A list of all desired work on the projecto Ideally expressed such that each item has

value to the users or customers of the product

o Prioritized by the product ownero Reprioritized at the start of each sprint

Burn-down Chart example

Recourses:

http://www.scrumguides.org/

http://www.allaboutagile.com/

https://www.scrumalliance.org/

https://www.burndownfortrello.com/#

https://ru.atlassian.com/agile/scrum

Nora Papazyan for E-Worksnora@e-works.am