how we use scrum @ bluegrass digital

www.bluegrassdigital.com

What

SCRUM?is


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).

Why

SCRUM?


Why have we chosen SCRUM?

= a Mess!


Why have we chosen SCRUM? (cont.)

Agile development is now accepted globally as the best way to develop, maintain, and support software systems 01Scrum is designed to add energy, focus, clarity, and transparency to project planning and implementation 02Scrum will increase the speed of development by detecting & removing anything that gets in the way 03

Scrum will align internal Bluegrass and Client objectives 04Scrum will achieve stable and consistent communication of performance at all levels 05

Empowers everyone involved to feel good about their job 06We always miss project deadlines. Scrum will ensure that we meet our deadlines! 07


SCRUM vs Traditional Processes

Self-ManagedSCRUM Teams

Traditional Organization

Customer driven

Multi-skilled teams

Information is widely shared

Few levels of management

Shared goals

Seemingly chaotic

Purpose achievement emphasis

Continuous improvements

Self driven & controlled

Values / principles based

Management driven

Isolated specialists

Limited information sharing

Many levels of management

Segregated goals

Seemingly organized

Problem solving emphasis

Incremental improvements

Management controlled

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 Determined during planning Set during the project

Completion date Determined during planning Set during the project

Responsivenessto 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

How

SCRUM?we


SCRUM Team

PM

Scrum Master

BA

DEV Team


SCRUM Roles

Project Managers

Business Analyst

Development Team

Scrum Master

01Define the project features & requirements

02Prioritize project features & functionality

03Adjust features & priorities when they change

04Defines clients timelines

05Accepts or rejects work results

01Define the project features & requirements

02Analyse & defines the project scope & vision

03BA & Senior Dev works together to define tasks

04Defines specification documentation

05Identifying and reporting on bugs

06Accepts or rejects work results

01Works in pairs on projects, with weekly reviews of each others work

02BA & Senior Dev works together to define tasks

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

04Demos work results to PM’s & BA

05Senior Dev signs off Done

01Ensures the team is fully functional & productive

02Enable close cooperation across all roles and functions

03Removes barriers

04Shield the team from external interferences

05Ensures that the Scrum process is followed


SCRUM Process & Phases

Vision & Planning Solution

Daily Scrum

Develop

TestingSprint Review

Prioritise

PLANNING(Phase 1 - Pregame)

SPRINT(Phase 2 - Game)

CLOSURE(Phase 3 - Postgame)

UAT Testing

Go Live

PM

BA

Team

Team


Daily Scrum ‘Standup’

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?

OVERVIEW

Moderator :The Scrum Master

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

Duration:15 minutes @ 09h30

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.

“This is the team’s opportunity to report to itself on progress and obstacles.”


Sprint Review

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

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

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

5. The Project Manager has the final say here

OVERVIEW

Moderator:Project Manager

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

Duration:10 minutes to ~

“This is when the Team demos what they’ve built during the Sprint phase.”


Definition of‘DONE’

For THE TEAM For SCRUM

Code has or is:

Meets the functional requirements defined

Corresponds to development & coding standards

Deployed to staging environment Committed into source control Tested & reviewed by Senior Dev

Individual tasks are ‘Done’: 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

Contact

Us


LondonUnit C7, Commodore House Battersea ReachJuniper Drive SW18 1TW

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

Cape Town3rd Floor, Sunclare Building 21 Dreyer Street Claremont7708

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

Johannesburg1st Floor82 Maude StSandton2146

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

[email protected]

how we use scrum @ bluegrass digital

Technology