Agile Anti-Patterns. Yes your agile projects can and will fail too.

Agile Anti-Patterns Yes your agile projects can and will fail too Sander HoogendoornPrincipal Technology Officer & Global Agile Thoughtleader Capgemini @aahoogendoorn 1

Sander HoogendoornCapgeminiPrincipal technology officerGlobal agile thought leaderChief architect Accelerated Delivery Platform (ADP)OtherAuthor books on UML, agileAuthor +200 articles, columnsSpeaker +100 international conferencesMicrosoft Partner Advisory Council .NETEditorial boards & Advisory boardsCapping IT Off BlogWebwww.sanderhoogendoorn.comsander.hoogendoorn@capgemini.com@aahoogendoorn

Why waterfall won’t work• Why waterfall won’t work

Waterfall?

Agile! 7

You would believe …because waterfall doesn’t work, right?

So the methodology doesn’t work @aahoogendoorn They should never have used waterfall. @aahoogendoorn Does the name of the project coincidently start with a C?

But how would you feel if …

@aahoogendoorn They didn’t apply Scrum right. @aahoogendoorn This project likely did ScrumBut, not Scrum.So it’s not the methodology, right?

Jack states that we have over 300 resources who are trained as SCRUMmaster. As it happens I’m meeting him this afternoon. I’ll ask him. 15

Scrumman 16

Dogmagile

Crusader Agile

 Scrumdamentalism 

Stand up meetings

Sit down meetings…

Scrumdamentalism 

Scrumdamentalism  

Agilists against ZenifyingJust write down small things on small papers. It’s your kaizen.

Agilists against ZenifyingDon’t just write down small things on small papers. Write code. It’s your job.

The Bob-the-Builder-Syndrome Can we build it? Yes, we can!

There is no so thing asone-size-fits-all agile

Teams and roles 28

Customer, Coach, Developer

Product owner, Scrum master, Team

Customer, User, Domain ExpertProject Manager, Coach, Developer, Tester Create Stabilize project software proposalPropose Scope Realize Realize Realize Realize Finalize Manage Write Deliver Maintain project working software plan software

Multiple roles

Teams? 33

What is the keyto being successful as a team? 34

Collaboration 35

But what happens to the old roles? 36

An example team Product owner Responsible for gatheringall business requirements No ‘real’ business owner Scrum team Business analyst /2 Information analyst /2 SAP CRM /1 SAP XI/ BPM /2 SAP ABAP /1 UI developer /1 .NET developer /1 Test /2 Scrum master /1 Agile coach /1 37

The backlogWhere does it come from?

And on theseventh day Kencreated thebacklog

The automagical backlog

Preliminary iterations

Preliminary iterations Create Stabilize project software proposalPropose Scope Realize Realize Realize Realize Finalize Manage Write Deliver Maintain project working software plan software

Documentation Frenzy

Documentation Frenzy  

But if your IT landscape looks like this …

Index cards might just not do the trick

User stories are merely meant to get the conversation going?

So what about documentation?

The agile manifesto doesn’t sayno documentation (or modeling)

Eventually your software will go into maintenance (hopefully)

Will you document to maintain? 

Guesstimation 54

Apples Team 1 55

Apples and oranges Team 1 Team 2 56

Apples and apples Team 1 Team 2 57

Distributed Apples Off shoreTeam 1 Team 2 Team 3 Team 58

Mandatory burn down chart?Bad smell: note howthe same example isused in everyone’spresentations. Don’t trust a vendor’s presentation if it has this example of a burndown chart in it.

We have our ups and downs

Lightweight agile can be to enterprise projects What Monopoly isto solving the financial crisis

Agile is a sliding scale 62

Assembling Agile

Static versus Dynamic Agile 64

Project Approachpublic interface IApproach{ List<ITeam> Teams { get; set; } IDashBoard Board { get; set; } IUnitOfWork Unit { get; set; }}public abstract class Approach : IApproach{ public List<ITeam> Teams { get; set; } public IDashBoard Board { get; set; } public IUnitOfWork Unit { get; set; }} 65

Static Approachpublic class Scrum : Approach{ public Scrum() { Teams = new List<ITeam> {new LocalTeam()}; Board = new TaskBoard(); Unit = new UserStory(); }}public class ScrumProject{ public Scrum Approach = new Scrum();} 66

Dynamic Approachpublic class Project{ public IApproach Approach { get; set; }}public class MyProject : Project{ public MyProject() { Approach = new Smart(); Approach.Board = new KanbanBoard(); Approach.Teams.Add(new LocalTeam()); Approach.Teams.Add(new LocalTeam()); Approach.Teams.Add(new IndianTeam()); Approach.Unit = new Feature(); }} 67

Assembling Agile – The basics of agile Short Collaborative Small Iterations Teams Unit of Work Continuous Deliver Simplify Planning Early & Often Communication

Lightweight Agile

Assembling Agile – Light Short Collaborative Small Iterations Teams Unit of WorkContinuous Deliver Simplify Planning Early & Often Communication

Enterprise Agile

Assembling Agile – Enterprise Short Collaborative Small Iterations Teams Unit of Work Continuous Deliver Simplify Planning Early & Often Communication

Institutionalizing agile 73

Freedom and flexibility 74

Institutionalizing agile 75

In retrospective

Agile is no religionSo don’t be a zealot

Agile is a sliding scale 78

Assembling Agile

Value is foundIn all agile approaces (and yes, even in waterfall)

And please can we cut the crap And go back to work?

Sander Hoogendoornwww.sanderhoogendoorn.com @aahoogendoorn 83

http://sanderhoogendoorn.com	2007
http://adf.accelerateddeliveryplatform.com	8
http://www.sanderhoogendoorn.com	6
http://translate.googleusercontent.com	3
http://paper.li	2
https://twitter.com	2
http://www.linkedin.com	2
http://sanderhoogendoorn.org	2

Agile Anti-Patterns. Yes your agile projects can and will fail too.

by Sander Hoogendoorn

Accessibility

Categories

Upload Details

Usage Rights

8 Embeds 2,032

Statistics