51

Click here to load reader

Agile Myths and Legends

Embed Size (px)

DESCRIPTION

Have you heard any of these statements? “As a manager I will have no control or visibility into my team’s activities with Agile!” “Agile practices are unstructured, everyone is a cowboy!” “An agile development team doesn’t work from requirements, and testing goes out the window!” and my personal favorite - “Agile means no documentation!” Ahhhhhhhhh, no wonder Agile is a scary word for managers and testers. If any of the above statements are true in your organization, then someone is doing it wrong. I am here to tell you from personal experience at a number of clients, both large and small, that none of these claims are true if you are truly following the tenets of Agile. Actually, these statements reflect a situation that is really the OPPOSITE of what can happen on a mature, well-functioning agile team. In this presentation, we will discuss what Agile really IS, and debunk some of the popular myths that make organizations hesitate from adopting Agile into their organization.

Citation preview

Page 1: Agile Myths and Legends

Agile: Myths and Legends

FEATURING: TFS AND VISUAL STUDIO 2012

Page 2: Agile Myths and Legends

Angela Dugan

Mobile Solutions

Project Leadership

.NET Solutions

Application Lifecycle Management

Page 3: Agile Myths and Legends

Obligatory Dilbert

Page 4: Agile Myths and Legends

Agile Tenets

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Page 5: Agile Myths and Legends

Quick review of Agile/Scrum

SCRUM = Agile Agile <> Scrum

Page 6: Agile Myths and Legends

My Top Agile Myths & Legends

1. Organizations are not succeeding with agile

2. Agile works better than traditional approaches (e.g. Waterfall)

3. Traditional (Waterfall) works better for distributed/offshore teams

4. Agile teams waste a lot of time testing that traditional teams don’t

5. Agile teams don’t produce documentation

6. Daily stand-ups are just glorified status meetings

7. Without detailed records, I don’t know that my people are really working all the time!

8. If we convert to Agile, that means we can “do more with less” right?

Page 7: Agile Myths and Legends

Myth #1

Organizations are not succeeding with agile

(a.k.a. “Agile is just a fad”)

Page 8: Agile Myths and Legends
Page 9: Agile Myths and Legends

Regarding that fad nonsense…

Agile has been around as a general methodology since as early as the 70s

Agile was introduced as an “official” flavor of software development processes in the early 90’s

The Agile Manifesto came into being in 2001

Page 10: Agile Myths and Legends

Myth #1

Organizations are not succeeding with agile

False: At least 86% are trying, and most are succeeding!

Page 11: Agile Myths and Legends

Myth #2

Agile generally works better than traditional approaches (e.g. Waterfall)

Page 12: Agile Myths and Legends

The Numbers Don’t Lie

Page 13: Agile Myths and Legends

But Agile Projects Still Fail!

Agile is more than 3 time LESS likely to fail than Waterfall.

Agile is 3 times MORE likely to succeed than Waterfall.

But…

Agile is not a guarantee of Success (“no silver bullet”)

Agile will never be perfect so long as imperfect people are executing it

Page 14: Agile Myths and Legends

Myth #2

Agile generally works better than traditional approaches (e.g. Waterfall)

True: Anybody can fail with Agile, but when done right I’ve yet to see a situation where adopting agile practices didn’t improve things

Page 15: Agile Myths and Legends

Myth #3

Traditional (Waterfall) works better for distributed/offshore teams

Page 16: Agile Myths and Legends

Challenges of Distributed TeamsCommunication and coordination can be hampered by time-zone differences

Self-management and communicating impediments is difficult for some cultures

Daily stand-ups may require additional technology to facilitate

Peer review and code quality/standards enforcement may require extra effort and diligence

Page 17: Agile Myths and Legends

TFS 2012 Team Dashboard

Page 18: Agile Myths and Legends

TFS 2012 Backlog Planner

Page 19: Agile Myths and Legends

VS 2012 Code Review Tool (requires VS Premium or better)

Page 20: Agile Myths and Legends

Distributed Agile StrategiesCoordinate schedules to ensure overlap in the work-day

Meet face to face to establish trust

Install web cameras, Skype, and/or on-line task boards to enable real-time communication

Establish continuous integration CI and target high test coverage across all teams

Keep iterations short

Page 21: Agile Myths and Legends

Myth #3

Traditional (Waterfall) works better for distributed/offshore teams

Sometimes: Agile can work for distributed teams, but takes work and it IS succeeding.

Page 22: Agile Myths and Legends

Myth #4

Agile teams waste a lot of time up front testing that traditional teams don’t

Page 23: Agile Myths and Legends

Why Does Testing Early and Often Matter?

Page 24: Agile Myths and Legends

Agile Testing PracticesTDD

ATDD

Automated Unit Testing

Automated Regression Testing

Continuous Integration

Exploratory Testing

Again… tools are your friend!

Page 25: Agile Myths and Legends

VS 2012 Unit Test Frameworks

Page 26: Agile Myths and Legends

MTM 2012 Exploratory Testing

Page 27: Agile Myths and Legends

MTM 2012 Web UI

Page 28: Agile Myths and Legends

Myth #4

Agile teams waste a lot of time up front testing that traditional teams don’t

False: Agile teams do a LOT more *continual* testing than traditional Waterfall teams, but I wouldn’t say the time is wasted. Testing early and

often builds in quality, rather than tests in quality.

Page 29: Agile Myths and Legends

Myth #5

Agile teams don’t produce documentation

Page 30: Agile Myths and Legends

Agile Tenets

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Page 31: Agile Myths and Legends

VS 2012 Storyboards

Page 32: Agile Myths and Legends

Myth #5

Agile teams don’t produce documentation

False: Agile teams only produce as much documentation as necessary

Page 33: Agile Myths and Legends

Myth #6

Daily stand-ups are just glorified status meetings

Page 34: Agile Myths and Legends

Daily StandupsShould be 15 minutes or less

Limited to what you did, what you plan to do, impediments

Goal is coordination and collaboration

If it devolves into a status meeting you are DOING IT WRONG!

Page 35: Agile Myths and Legends

TFS 2012 Task Board

Page 36: Agile Myths and Legends

Myth #6

Daily stand-ups are just glorified status meetings

False: Standups are only about the entire software team collaborating on the next 24 hours of work.

Page 37: Agile Myths and Legends

Myth #7

Without detailed records, I don’t know that my people are really working all the time!

Page 38: Agile Myths and Legends

http://www.slideshare.net/willevans/kanban-forcreatives-slideshare

Page 39: Agile Myths and Legends

TFS 2012 Sprint Planning tool

Page 40: Agile Myths and Legends

TFS 2012 Remaining Work Report

F i n d an swers to th e se q u e st ions :

H ow fast i s th e te am b u r n ing d ow n re main ing wo rk?

I s wo r k b e i ng ad d ed d u r ing th e i te rat ion?

H ow mu c h p ro gress can th e te am make i n th e ava i l ab le t i me ?

A p p rox imate l y w h en can th e te am f i n i sh th e wo rk ?

I s to o mu c h wo rk i n p ro gres s?

I s th e f l ow o f wo r k b e i ng i mp eded o r b l o cked?

W h en w i l l th e te am f i n ish th e c u r rent i te rat i on?

Page 41: Agile Myths and Legends

TFS 2012 Cross-Team Reporting

Page 42: Agile Myths and Legends

Be Careful What You Measure

Time to rethink what you are measuring! ;)

Page 43: Agile Myths and Legends

Myth #7

Without detailed records, I don’t know that my people are really working all the time

With agile you are MORE likely to know EXACTLY what people are working on every day.

The better question might be, why are you focusing on the number of hours worked?

Page 44: Agile Myths and Legends

Myth #8

If we convert to Agile, that means we can “do more with less” right?

Page 45: Agile Myths and Legends

The Cost of Multi-Tasking

http://www.codinghorror.com/blog/2006/09/the-multi-tasking-myth.html

Page 46: Agile Myths and Legends

Do More With LessHumans are TERRIBLE at multi-tasking!

Multi-tasking includes meetings, answering email, one-off conversations, they are all distractions

You will get 6 – 7 hours of productive time a day out of people AT BEST, but only if you *leave them alone*

Agile is not magic, you won’t get more hours in a day, but you will deliver more VALUE in the same amount of time

Page 47: Agile Myths and Legends
Page 48: Agile Myths and Legends

Myth #8

If we convert to Agile, that means we can “do more with less” right?

Sort of: People will be allowed to focus, and you will see more value delivered with less bugs in

the same amount of time

Page 49: Agile Myths and Legends

Good reads

Drive: The Surprising Truth About What Motivates Us

Daniel H. Pink

$10 on Amazon

http://www.amazon.com/Drive-Surprising-Truth-About-Motivates/dp/1594484805

Page 50: Agile Myths and Legends

Visual Studio Team Foundation Server 2012:

Adopting Agile Software Practices

Sam Guckenheimer

Neno Loje

$30 on Amazon

Good readshttp://www.amazon.com/Visual-Studio-Team-Foundation-Server/dp/0321864875

Page 51: Agile Myths and Legends

Questions?