Business Analysis in the

Agile Organization

Module 2
Module 2

Scrum Framework
Module 2

Learning Outcomes
Define and describe:
• What is Agile Development
• Scrum Roles
• Scrum Activities (Overview)
• Product Backlog
• Sprints

This slide presentation augments your Course and

Module Readings. Complete the module readings
before reading through this presentation.
Retrieved May 4, 2013,
http://www.modernanalyst.com/Resources/BusinessAnalystHumor/tab
id/218/Default.aspx?ArticleType=ArticleView&ArticleID=1077
Agile, an Approach
Agile Development has many meanings:

• Extreme Programming
• Feature Driven Development
• Kanban
• Scrum

Agile, an Introduction
Video - Agile, an approach
Agile is an iterative process, Waterfall is more of a
sequential process.

Video 1:37 min -- Waterfall vs Agile -- this short video

demonstrates the iterative nature of Agile
https://www.youtube.com/watch?v=CKD9nWVsDzc
Scrum
• Scrum is a framework based on:
• Values
• Principles
• Practices
Mostly used for software or web site development
• Agile (lots of change, you may not even know what the end
production is at the start)
• For high risk project
• VP’s don’t like it so much necessarily, at least initially
Scrum Roles
The Product Owner
• Responsible for features and functionality
(requirements)
• Communicates the vision of the product
• Responsibly for the overall success of the
product
• Ensure the most valuable work is done first
• Manages the product backlog
Scrum Roles
The Product Owner (PO)
• Works with business stakeholders to compile and
prioritize user stories
• Extracts and documents user acceptance criteria
from the stakeholders
• Attends the sprint planning, sprint review and product
backlog update meetings
• Answers or tracks down any requirements questions
in real time
Scrum Roles
The ScrumMaster
• NOT a project manager
• Coach
• Help the team resolve issues
• Remove roadblocks (let the development team work)
• Scrum process leader
• Protects the team
Scrum Roles
The ScrumMaster (SM)
• Co-located with the team in the team room
• Does not manage the team organizationally
• Facilitates all scrum meetings
• Facilitates removal of impediments
• Encourages team self-management
• Works directly with Product Manager to clarify
requirements when needed.
Scrum Roles
Development Team
• Diverse, cross-functional team
• Design, build and test the product
• Small team (5 to 9)
• Collocated
• Self forming
Scrum Roles
Development Team
• Self-manages and make decisions
collaboratively
• Collectively responsible for sprint delivery. (If
one team member is slacking the whole team
is accountable)
• Constantly collaborating in the team room to
solve problems and make progress
• Has fun together
Self-Forming Teams
 A group of
people working
together in
their own ways
There is the power of the
team, at least the power
in a self-forming team.
Retrieved June 18, 2013 https://www.scolab.com/
 Scrum Team and
the Business

The entire Scrum Team can

interact with business
owners and stakeholders,
although typically it’s the
Product Owner with the
ScrumMaster coming in 2nd

Retrieved June 18, 2013 http://agileatlas.org/commentaries/article/scrum-in-a-nutshell

Video – The Wrong Way to do Agile
Video -- The Wrong way to do Agile: Team Structure
0:53 min
https://www.youtube.com/watch?v=HsB0UZR7XvE

How many
“wrong” things can
you spot?
 Review the explanation

Scrum Framework of this diagram in the

textbook, p17

Retrieved June 18, 2013

http://www.informit.com/articles/article.aspx?p=1952809
Product Backlog
• Start with features – example “once the
customer inputs their first and last name the
address will be auto-populated by the system”
• Product Owner (PO) collaborates with
stakeholders to define the product backlog
items
Product Backlog
• The PO force ranks the product backlog
• High value items always to the top
• This document is a “living” document
(items can move up or down, added or
deleted)
• Items are estimated
 Product
Backlog

Retrieved June 18, 2013 More than just features

http://www.informit.com/articles/article.aspx? go into a backlog
p=1928232&seqNum=2
Planning Meeting(s)
• Facilitated by the ScrumMaster
• Break each user story into a set of smaller tasks (sticky
notes) with more accurate time estimates.
• Finalize commitment.
• Team volunteers for the tasks on the board . Any tasks
that have not been volunteered for must be assigned out
by the team
• Creates “burndown chart” in team room becomes the
status dashboard for everyone.
Daily Standup
• Facilitated by the ScrumMaster
• Team Members stand and answer questions:
- What did you do since the last standup?
- What will you do today?
- What is blocking you?
• Teams then work for the day in the team room
together. Strong preference for co-location in
the same room (not cubicles).
Sprint Review
• Facilitated by ScrumMaster
• Attended/supported by Product Owner
• Team demonstrates all vertical slices, stories,
to the product owner for approval
• Failed items go back to the product backlog
• Items that come up in the review may go into
the product backlog
Retrospective
•  Facilitated by the ScrumMaster
• Silent writing exercise
• What worked well
• What did not work well
• Can add items to the backlog
• The objective is selected improvement
 Scrum Framework Retrieved June 18, 2013
http://www.informit.com/articles/artic

Review, a Walk Through le.aspx?p=1952809

You should be able to

map last few slides to
this diagram
Other Module Activities
• Read chapter 2 (keep up with your readings)
End of Module
Parts of this document were sourced from:

Essential Scrum - A Practical Guide to the Most Popular Agile Process

Author: Kenneth S. Rubin
Publisher: Pearson Education, Inc