1130-1215 - cheryl downes - mythbusters - tues - cm3 downes - mythbusters... · 2013-11-04 ·...

Mythbusters7 Agile Myths Busted, Plausible or Confirmed

Why this Topic?

Busted, Plausible or Confirmed

Myth 1: We Don’t Need …

Architects

Project Managers

TestersTesters

Myth 1: We Don’t Need Architects

• BDUF

• NUFD• NUFD

• RUFD

Myth 1: We Don’t Need PMs

Myth 1: We Don’t Need …

Myth 1: We Don’t Need

Focus on tasks not roles

Myth 2: No Documentation

Comprehensive documentation does not documentation does not

guarantee project

success!

High Level Test Strategy

Must Have Should have Consider

SystemName

Notes Tools Environ

•Testing is done on a

Un

it

Inte

gra

tio

n

Syste

m

Reg

ressio

n

UA

T

Perf

orm

ance

Explo

rato

ry

Data

Valid

ation

Security

DR

P

Deplo

y /

Rollb

ack

Failo

ver

/

Rollb

ack

1)List the systems that are either directly or indirectly impacted

2)Highlight the testing types that are in scope for the project

3)List any assumptions or comments about why a testing phase might either be required or out of scope.

A M M M M M NR M NR NR NR ? ?

•Testing is done on a UAT setup•Security and Performance for I/90 and Easy CCI were already done and is used in Live environment.

BA

MM M M M NR M NR NR ? ? ?

•Security and Performance for I/90 and Easy CCI were already done and is used in Live environment.

Project Team

Project Team

Testing of this system is required and is the

responsibility of the project team

Testing of this system is required but is the

responsibility of an external team

Testing Responsibility

AutomatedA

TESTING TYPE

M Manual

A

M

Both Manual

and

Automated

NR

SCOPE

?

Not Required

Unknown

Myth 2: No Documentation

Myth 2: No Documentation

Myth 2: No Documentation

Document what needs to be

documented because it adds value

Myth 3: Small Web development ONLY

• The larger a project’s scope, the greater the probability of failure!

• It is not a methodology specific issue.

Myth 3: Small Web development ONLY

Agile

• Only suitable in some parts of the business

• Works well in web

• Won’t work in core banking, hard transaction • Won’t work in core banking, hard transaction

processing or batch

Susan Kidd, NAB

Myth 3: Small Web Development ONLY

Agile

• Implement across the board

• Necessary to put it where it doesn’t fit to drive cultural

changechange

• If you don’t ... Cultural change necessary for modern

technology will fail

Andy Weir, Bankwest

Myth 3: Small Web Development ONLY

People are used to having a nice wall. Business on one side, IT on the otherEasy to say Business got it wrong or IT got it wrong.

Agile brings a lot more accountability.

Aman NarainStandard Chartered Bank

Myth 3: Small Web Development ONLY

• Accepts that larger projects are harder

• Reduce things to smaller more manageable chunks.

• The key is integrating often.

Myth 4: Undisciplined & Lacks Process

2010 World Cup Final

Dutch fined over 9,000 pounds for

bad discipline

• 8 yellow cards

• 1 player sent off• 1 player sent off

Spanish fined over 6,000 pounds

for bad discipline

• 5 yellow cards

New record for most cards in a

World Cup Final

Spain won 1-0

Myth 4: Undisciplined & Lacks Process

• Continuous Integration

• Refactoring

• Continuous delivery of

working software to

production

• Tested continuously • Tested continuously

• Definitely a

characteristic of

discipline

Myth 4: Undisciplined and Lacks Process

Discipline is bottom up

Myth 5: Cheaper

Minimising wastage is cheaper

Failing early is cheaper

Agile project teams are:

• 37% faster to market

• 16% more productive

• Able to maintain quality even with

compressed schedules.

Myth 5: Cheaper

Testing costs could be higher

Myth 6: Doesn’t Plan

Origin of the myth?

Perhaps it comes from

not planning everything in

too much detail up front

Planning is done

throughout rather

than in a dedicated

phase up fronttoo much detail up front

when it’s wastefulphase up front

Myth 6: Doesn’t Plan

Myth 6: Doesn’t Plan

Just in time

Minimise wastage and the impact of change

Myth 7: Is a Silver Bullet

Myth 7: Is a Silver Bullet

Done well, both agile and

waterfall can deliver great

outcomes for the customer

The key lies in how well the

team follows the practices team follows the practices

and the talent of your team

... And which path you would

like to take

Myth 7: Is a Silver Bullet

Leading causes of

failed agile projects

• Lack of experience

with agile methods

• Company

• External pressure to follow

traditional waterfall

practices

• Lack of cultural transition

• Lack of management • Company

philosophy/culture at

odds with core agile

values

• Lack of management

support

• Unwillingness

• Insufficient training

Myth 7: Is a Silver Bullet

7 Principles of software development

(Mary Poppendieck)

– Eliminate waste

– Build quality in

– Defer commitment– Defer commitment

– Deliver fast

– Improve relentlessly

– Respect people

– Appreciate the system

Agile Smells

Agile Smells

More Agile Myths

• Mike Griffiths - Leading Answers

Leadership and Agile Project Management Ideas, Observations and Links

http://leadinganswers.typepad.com/leading_answers/2011/01/i-like-

myths-and-have-written-on-leadership-myths-previoulsy-for-our-next-

calgary-apln-meeting-we-are-hosting-an-agile-myth.html