How we use SCRUM @ Bluegrass Digital

What is SCRUM?
“Scrum is an Agile methodology that delivers software to
customers and end users faster, better, and cooler...”
1. The name ‘SCRUM’, is taken from Rugby – where whole team works
together to move the ball down field. This analogy in development is
for teams to work together to develop quality software.
2. Scrum is a simple framework used to organize teams; create a
balance between chaos & order; which gets work done more
productively with higher quality.
3. Designed to adapt to constantly changing requirements, and allows
teams to prioritize requirements and adapt in real time.
4. Scrum therefore provides what the customer wants (improving
customer satisfaction), while eliminating waste (work that is not highly
valued by the customer).
www.bluegrassdigital.com

Why have we chosen SCRUM?

= a Mess!


Why have we chosen SCRUM? (cont.)

01

Agile development is now accepted globally as the best way
to develop, maintain, and support software systems

02

Scrum is designed to add energy, focus, clarity, and
transparency to project planning and implementation

03

Scrum will increase the speed of development by detecting &

04

Scrum will align internal Bluegrass and Client objectives

05

Scrum will achieve stable and consistent communication of
performance at all levels

06

Empowers everyone involved to feel good about their job

removing anything that gets in the way

We always miss project deadlines. Scrum will ensure that we
meet our deadlines!

07

SCRUM vs Traditional Processes
Self-Managed
SCRUM Teams

Traditional Organization

Customer driven

Management driven

Multi-skilled teams

Isolated specialists

Information is widely shared

Limited information sharing

Few levels of management

Many levels of management

Shared goals

Segregated goals

Seemingly chaotic

Seemingly organized

Purpose achievement emphasis

Problem solving emphasis

Continuous improvements

Incremental improvements

Self driven & controlled

Management controlled

Values / principles based

Policy / procedure based


Methodologies Comparison
Waterfall (current)

Scrum

Defined processes

Required for each step

Planning & Closure phases only

Final product

Determined during planning

Set during the project

Project cost



Completion date



Responsiveness
to environment

Planning phase only

Throughout

Team flexibility, creativity

Limited – cookbook approach

Unlimited during iterations

Knowledge transfer

Training prior to project

Teamwork during project

Probability of success

Low

High

SCRUM Team
Scrum
Master

BA

PM

DEV
Team

SCRUM Roles
Project
Managers

Business
Analyst

Development Scrum
Team
Master

01

01

01

Define the project features
& requirements

Define the project features Works in pairs on projects,
& requirements
with weekly reviews of
each others work
02

02
Prioritize project features
& functionality

Analyse & defines the
project scope & vision

03

03

BA & Senior Dev works
together to define tasks

Adjust features & priorities
when they change

04

04
Defines clients timelines

05
Accepts or rejects work
results

Defines specification
documentation

05
Identifying and reporting
on bugs

06
Accepts or rejects work
results

01
Ensures the team is fully
functional & productive

02

02

BA & Senior Dev works
together to define tasks

Enable close cooperation
across all roles and
functions

03
Has right to do everything
within project boundaries
to reach deadline

03
Removes barriers

04
Demos work results to
PM’s & BA

05

04
Shield the team from
external interferences

Senior Dev signs off Done

05
Ensures that the Scrum
process is followed

SCRUM Process & Phases
SPRINT

(Phase 2 - Game)

PLANNING

Daily
Scrum

(Phase 1 - Pregame)

Vision &
Planning

Solution

CLOSURE

Prioritise

(Phase 3 - Postgame)

Develop

UAT
Testing

Go
Live

Team
Sprint
Review

Testing

PM
BA

Team

Daily Scrum ‘Standup’
“This is the team’s opportunity to report to itself
on progress and obstacles.”
OVERVIEW
Moderator :
The Scrum Master

Participators:
The Team (active)
Scrum Master (passive)
PM / BA (passive)

Duration:
15 minutes @ 09h30

One by one, each member of the team reports just
3 things to the other members of the team:

1. What did you get done since the last standup?
2. What blocks or obstacles got in the way of
completing this work?
3. What are you aiming to get done by the next
standup?
 The ScrumMaster takes note of these blocks, and then helps team
members to resolve them after the standup.
 No discussion happens during the Daily Scrum Standup, just the
reporting of the 3 key pieces of information.
 If discussion is required, it takes place right after the standup.


Sprint Review
“This is when the Team demos what they’ve
built during the Sprint phase.”
OVERVIEW
Moderator:
Project Manager

Participators:

1. Anyone interested in the project can be present
at this meeting.
2. It can last 10 minutes, or it can last 4 hours –
whatever it takes to show what’s been built and
to get feedback

The Team (active)
Scrum Master (passive)
Management (active)
Stakeholders (active)

3. Surprises are reported and anything can be
changed, work added, removed or re-prioritized.

Duration:

4. Project Manager accepts/rejects the work
according to the definition of DONE

10 minutes to ~

5. The Project Manager has the final say here

Definition of‘DONE’
For THE TEAM

For SCRUM

Code has or is:

Individual tasks are ‘Done’:

 Meets the functional requirements
defined
 Corresponds to development &
coding standards
 Deployed to staging environment
 Committed into source control
 Tested & reviewed by Senior Dev

 When the Team has reached its level
of ‘Done’

Sprints are ‘Done’ when:
 All items/tasks are ‘Done’
 When the Sprint reaches its goal
 Meets the functional requirements
defined

UAT is ‘Done’ when:
 Meets clients expectations

Go-Live is ‘Done’ :
 Released to Production environment

London

Cape Town

Johannesburg

Unit C7, Commodore House
Battersea Reach
Juniper Drive
SW18 1TW

3rd Floor, Sunclare Building
21 Dreyer Street
Claremont
7708

1st Floor
82 Maude St
Sandton
2146

Tel: +44 (0)20 3326 1580
Fax: +44 (0)84 5688 3362

Tel: +27 (0)21 671 1966
Fax: +27 (0)21 671 6337

Tel: +27 (0)10 003 0250
Fax: +27 (0)11 783 4383

hello@bluegrassdigital.com

How we use SCRUM @ Bluegrass Digital

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à How we use SCRUM @ Bluegrass Digital

Similaire à How we use SCRUM @ Bluegrass Digital (20)

Dernier

Dernier (20)

How we use SCRUM @ Bluegrass Digital