30
Speaker: Rachel Davies www.agilexp.com S

Agile Mashups

Embed Size (px)

Citation preview

Page 1: Agile Mashups

Speaker: Rachel Davieswww.agilexp.com

S

Page 2: Agile Mashups

What’s this talk about?

• Understanding industrycontext that’s useful toknow when you areadopting agile.

• What Agile teams aredoing that might be hard towork out from the books.

Page 3: Agile Mashups

Why does it matter?

Because books, training and conferences talk aboutagile methods with labels like Scrum, XP, DSDM,etc.

I’ll be talking about the form of Agile which I seeteams actually do.

Page 4: Agile Mashups

My experience?

• XP practitioner since 2000.

• Consulting agile coach since 2003. Coachedteams at BBC, CODA, Egg, Lloyds TSB, Nokia,Orange, Roche, Screwfix, and many more.

• Agile community work includes Agile Allianceboard, Experience reports for Agile2007/2006,Agile2008 conference chair, Agile Businessconference, BCS SPA, RetrospectiveFacilitators Gathering, Scrum Gathering openspace facilitator, XPDays, XTC, etc.

Page 5: Agile Mashups

Your experience?

Page 6: Agile Mashups

Methodologists United!

“I kicked off "The LightweightProcess Summit" with a 10minute plea for a manifesto, andthen watched with awe and gleeas these people, with some deepphilosophical differences, foundthemselves in fundamentalagreement with the notion thatwhat we shared in common wasmore important than ourdifferences.”Bob Martin re: Agile Manifesto

Page 7: Agile Mashups

Method Camps remain

Crystal

DSDM

Scrum XP

LEAN

Page 8: Agile Mashups

Banging the Drum

Keeping a method simple makesit easy to transmit and easy tounderstand.

Agile methods can help you getstarted but you have to fill inthe gaps.

Page 9: Agile Mashups

What am I seeing teams do?

• I work with Scrum teams who use XP practiceslike Velocity, Test-Driven Development andUser Stories describe their Product Backlog.

• I work with XP teams who use Burndowncharts, Retrospectives and Daily Scrum format.

• I work with Lean teams who use a mix of theabove.

• It seems a generic Agile mashups are emerging.

Page 10: Agile Mashups

Sorry, No again! Work out new Agile practice gradually through Retrospectives

The 13th Practice?

Page 11: Agile Mashups

CorporateCulture

XP SCRUM

Mashup Zone

Teams create their own agile “mashups”

Agile Transition

Page 12: Agile Mashups

How XP are you?

Can you claim to be an XP team ..• if you don't use index cards?• if you don't write code test-first?• if you don't program in pairs?• if you don't sit together?• If you don’t have an onsite customer?It seems that some practices are more optional

than others

Page 13: Agile Mashups

How Scrum are you?Can you claim to be a Scrum team ..• if you don't have a Sprint Review?• if you don't deliver a Product Increment at the

end of each Sprint?• if you don't have a Sprint Retrospective?• if you don't have a visible Sprint Burndown?• if you don't have a defined Sprint Goal?• if your Product Backlog is not prioritized?Maybe there’s a good reason why you don’t?

Page 14: Agile Mashups

Typical Agile Practice List Daily Scrum/Standup Iterations/Sprints User Stories Release Plans Test-Driven Development Velocity Burndown Charts Team boards Retrospectives Continuous Integration

X Pair ProgrammingX Product IncrementX Sit Together

Page 15: Agile Mashups

Agile Roles

Page 16: Agile Mashups

Between 5 and 10 team members• Cross-functional including at least one tester• Self-organizing

The Team

Page 17: Agile Mashups

Split the Customer (ProductOwner) role

The Truth works with support ofcommittees, management,customers, sales people, but is theonly person that makes decisionsabout priorities

With a trusty sidekick …

The Truth

Page 18: Agile Mashups

The Voice of the Customer

The Voice of the Customeris typically an analyst whoworks closely with theteam to make sure thatuser stories andacceptance tests areconsistent, valuable anduseful.

Page 19: Agile Mashups

Agile Project Managerand Scrum Master

Responsible for:

• Facilitating meetings

• Reporting progress

• Shielding the team

• Working with the team to removeobstacles

• Preparing the road ahead

Page 20: Agile Mashups

Whole Team

Current Iteration Future Iterations

Page 21: Agile Mashups

Agile Cycle

Page 22: Agile Mashups

Start from

Ziffer (Zero Feature Iteration) -- Michael Hill

Projects start with an Iteration Zero

Page 23: Agile Mashups

Two Week Cycle

PLAN

DEVELOP

DEVELOP

DEVELOP

DEVELOP

DEVELOP

DEVELOP

DEVELOP

DEVELOP

DEMO

RETRO

Most teams set their iteration/sprint length at 2 weeks

DEV

Page 24: Agile Mashups

Start the Day around the Board• Teams start the day with a Daily Standup by their

Project Board using the Scrum question format.• The Project Board shows what the team are working

on today and how much is left.

Page 25: Agile Mashups

Release Cycle

Sprints/Iterations

Releases

INTERNAL

ZFR

POLISH

EXTERNAL

EXTERNAL

POLISH

Sprints/Iterations

Page 26: Agile Mashups

Conformity?• Scrum says “Inspect & Adapt”• Manifesto says “the team reflects on how to become

more effective, then tunes and adjusts its behavioraccordingly.”

• Your team will be different and that’s OK :-)

Page 27: Agile Mashups

Agile Books

• Use as source of ideas• Not “religious” texts• Read more than one!

Page 28: Agile Mashups

No, I’m not suggesting we need this.Project are too varied so we need loose Agile.The Agile Manifesto already serves the purpose

of a framework.

Unified Agile v2.0?

Page 29: Agile Mashups

Any Questions?

Page 30: Agile Mashups

Rachel Davies

[email protected]

http://www.agilexp.com/