Getting Agile - AAIR · Team Waterfall Team Agile ... Culture eats strategy for breakfast...

Preview:

Citation preview

Doing what the customer wants, when they want it

Getting Agile

Rob HaleUniversity of New England, Armidale

AAIR Data Warehousing SIG Forum

27th August 2009

1Wednesday, 16 September 2009

Exercise: Build a Lego Car for a Customer

Team Waterfall Team Agile

•Scope•Requirements Doc•Delivery Schedule•Resource Allocation•Budget

•Sprint Planning

•Development•Development

Construct a car using the provided Lego resources. A prioritised feature list is provided

2Wednesday, 16 September 2009

Problem

Universities are operating in a competitive environment. The insight from BI/DW capability is vital to inform strategy and guide the enterprise

As BI professionals we are under pressure to give our customers what they want and to do this fast

3Wednesday, 16 September 2009

Complexity

Pressure to DeliverDesire to Deliver

Organisational CultureIT Development Tradition

Budget Process

Requirements AnalysisDocumentationResource PlanningDelivery ScheduleApproval to Start

4Wednesday, 16 September 2009

People change their minds, businesses change direction, markets

move, requirements aren’t fixed Re-DesignRe-Document

Re-PlanRe-ScheduleRe-Budget

Re-Communicate(Re-Peatedly)

BI projects are notoriously difficult to plan because clients rarely know what is possible until they see it

5Wednesday, 16 September 2009

Project Update

6Wednesday, 16 September 2009

Business runs on commitments

Do you:

Go ahead and build what

you think they need?

Someone committed us to deliver So far we haven’t Pressure mounts

7Wednesday, 16 September 2009

Business runs on commitments

Do you:

Is there a better way?or

Go ahead and build what

you think they need?

Someone committed us to deliver So far we haven’t Pressure mounts

8Wednesday, 16 September 2009

Explained by the Customer

Understood by the Manager

Designed by the Architect

Written by the Developer

What the Customer Wanted

Why is this stuff

still funny?

Culture eats strategy for breakfast9Wednesday, 16 September 2009

Know what you don’t know

Ask, do, ask some more

Try new things

Apply Understanding

Do things the ‘right way’

Approach based on experience

Rigid

Proven

Limited

Confident

Best Practice

Collaborative

Innovative

Learning

Flexible

Open

10Wednesday, 16 September 2009

11Wednesday, 16 September 2009

Complication:

Resolution:

Example:

Prototyping with customer

proto-typenouna full-scale, operational model, used for demonstration or testing, that incorporates a new design or features

Compressed TimelineClient Involvement High MomentumHigh EnergyEconomicalMotivating

12Wednesday, 16 September 2009

Project Update

13Wednesday, 16 September 2009

Original Requirement

Revision 1

Revision 2

What is really needed

Team Waterfall

Team Agile

14Wednesday, 16 September 2009

At the heart of every large projectthere is a small project trying to get out

We are going to try something called agile development.

Scrum

15Wednesday, 16 September 2009

Leadership Culture ShiftBusiness Value DeliveryExposed DysfunctionTeam Commitment Team ResponsibilitySelf-ManagementProduct BacklogSprint BacklogRetrospectiveDaily ScrumMotivationTimebox

We are going to try something called agile development.

Scrum is...

16Wednesday, 16 September 2009

17Wednesday, 16 September 2009

Product Backlog and Sprint Backlog

Drag Stories between Backlog and Sprint

Status of Story

Backlog

Current Sprint

Committed Story Points

18Wednesday, 16 September 2009

Sprint Taskboard

Tasks within each StoryTo Do WIP Solved Done

Developers Drag Stories Across

19Wednesday, 16 September 2009

Impediment

Went Wrong Here

The Sprint Burndown Chart and the See-Through Toaster

We can’t fix the problems we can’t see

Smooth Sprint

2-week duration

20Wednesday, 16 September 2009

Planning Poker

Fibonacci-ish Sequence

0 1/2 1 2 3

5 8 13 4020

100 ? ∞

Team EstimatesTeam Commits

21Wednesday, 16 September 2009

Watch out for Muscle Memory

Scrum is about teams

Do not change Scrum

22Wednesday, 16 September 2009

Agile Manifesto - http://agilemanifesto.org

Play Planning Poker Online - www.planningpoker.com

Mountain Goat Software - www.mountaingoatsoftware.com

Rob’s Higher Education BI Blog - http://blog.une.edu.au/robbi

23Wednesday, 16 September 2009

What next?

“...adopting Scrum in an enterprise is like looking into the abyss, girding

oneself for an epic journey and then making the plunge.

...it is taking a hard look in the mirror every day, every month and doing

something about what one sees.

Ken Schwaber 2007

The goal is for you and everyone in your enterprise to wake up looking

forward to coming to work, and for your competitors to wish they had

never woken up.”

24Wednesday, 16 September 2009

Recommended