AGILE DEVELOPMENT WITH SCRUM

Gloria StoilovaScrum Product Owner

BA, GfK Sofia

OUTLINEWhat is Scrum?The Scrum TeamScrum EventsScrum ArtifactsUX & TestingOrganizational Impacts

WHAT IS SCRUM?

Scrum is an iterative and incremental agile software development methodology for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal", challenges assumptions of the "traditional, sequential approach" to product development, and enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines in the project.

- Please don’t go there. There are obstacles waiting.

- But, why? I won’t let them waiting.

SCRUM FRAMEWORK

Founded on empirical process control theoryIntentionally incompleteIterative & incrementalOutwardly facing & transparentRequires a definition of “done”Adapts to changing requirements

THE SCRUM TEAM

Product

Owner

Scrum Maste

r

Business owner

Stakeholders

Scrum Team

BADSO

PRODUCT OWNERManages the Product Backlog and ensures business value of the Team’s work

Represents stakeholder interests to the team

Plans product releases and maintains product roadmap

ONE person, not a committee

Ultimately responsible for product’s success

SCRUM MASTERServes as coach, fixer, and gatekeeperA leadership role rather than managerialPlans individual Sprints with Team membersFacilitates all of the Scrum eventsManages relationship between Product Owner and rest of team

THE DEVELOPMENT (SCRUM) TEAM

Cross-functional group of 4 to 7 peopleSelf-organizing & continuously improvingTeam determines how to transform Product Backlog into shippable functionalityAccountability belongs to Team as a wholeNo domain-specific sub-teams

SCRUM EVENTS

SPRINTS

Consistent duration throughout projectTeam composition and quality goals remain constantNo changes made that affect Sprint GoalScope can be clarified or re-negotiated as more is learnedRisk is limited to cost of one sprint

SPRINTS

24 Hours

Expanded tasks

Daily Scrum meeting

Sprint Backlog

Product Backlog

Potentially shippable

product increment

14 Days

SPRINT PLANNING MEETING

Time-boxed meeting to determine work to be done in a Sprint First event of every SprintAnswers “What will be delivered in this Sprint?”Answers “How will the work be achieved?”

DAILY SCRUM (STAND UP)

Daily 15 minute (max) meeting

Each team member answers three questions: - What has been accomplished since last

meeting? - What will be done before the next meeting? - What obstacles are in the way?

NOT a status meeting

Only Development Team can participate

SPRINT REVIEW (DEMO)

Development Team demonstrates work done in the SprintProduct Owner determines what has been “Done” or not “Done”Results in a revised Product BacklogInforms planning for the next Sprint

SPRINT RETROSPECTIVE

Final activity of every SprintTeam reflects on the Sprint in terms of people, relationships, process, and toolsIdentify what went well and where improvements are needed. Team plans how to implement improvements

SCRUM ARTIFACTS

Product Owner

SCRUM Master

1st. Level

Support

PRODUCT BACKLOG

Single source of requirements and changes to the product

Ordered by unique priority

Never complete

Dynamic and changes as needed responding to changing business needs

Anyone involved can contribute to it

PRODUCT BACKLOG

Highest priority items have the most detail

Detail on lower priority items deferred until it’s needed

SPRINT BACKLOG

Set of Backlog items that the Team commits to delivering in the SprintServes as a real-time picture of how work is progressingBelongs solely to the Development Team

DEFINITION OF “DONE”

A shared understanding of what it means when work is considered done

Defined at the beginning of the project

Applies globally to the project

Might include things such as: - Unit & functional tests - Documentation

USER EXPERIENCE & TESTING

All explained in details Agile_Testing presentation

USER EXPERIENCE TASKS

UX tasks happen slightly ahead of programming tasks

UX expertise stays involved

No big handoffs

TESTING

No distinct testing phase

Features are tested as they are completed during the Sprint they are developed in.

Either developers or dedicated Testers create Unitest

ORGANIZATIONAL IMPACTS

ORGANIZATIONAL IMPACTS

Transitioning to Scrum isn’t always easy.Traditional roles change.Cultural changes.Commitment to continuous improvement.

WHO USES SCRUM?

QUESTIONS?

THANK YOU!

RESOURCES

Scrum.org - http://www.scrum.org/

Scrum Alliance - http://www.scrumalliance.org/

All Things Product Owner - http://www.romanpichler.com/blog/

Agile Project Management with Scrum by Ken Schwaber

Succeeding with Agile: Software Development Using Scrum by Mike Cohn

A Practical Guide to Distributed Scrum by Elizabeth Woodward