Agile Adoption: Does it Have to be All In or Fold?

Preview:

DESCRIPTION

Adopting Agile approaches can have a huge impact on software development teams. Agile practices can help teams yield more accurate assessments of project progress, better ensure that what gets delivered will be useful, and lead to higher quality products that are more maintainable.Yet it can be difficult to successfully transition to an Agile approach. Taking an all-or-nothing approach to adopting recognized Agile practices rarely succeeds. As a result, the pragmatic Agile change agent learns to adapt Agile practices to their organization’s unique context. This requires courage, convictions, and experimentation. Successful Agile adopters need to know when to push for changes to the “standard way we do things” and when to adapt or discard ill-fitting Agile practices. This talk will share lessons learned from experiences of those who’ve successfully adapted Agile practices presented by experience reporters that Rebecca Wirfs-Brock shepherded at past Agile conferences. Not willing to leave it at that, Rebecca concludes by challenging you to examine what it will take for you to succeed with Agile adoption.

Citation preview

Agile 2005 Experience Report

Drawn from extreme programming and scrum

Planning Data

Gathering

Design for cycle 2 Gather

customer input for cycle 3

Independent dev of low UI features

Test cycle 1 code

Design for cycle 3

Gather input for cycle 4

Implement Designs

Implement Designs

Test cycle 2 code

Design for cycle 4

Gather input for cycle 5

Cycle 0

Cycle 1 Cycle 2 Cycle 3

Developers

Interaction Designers

code code

design design

customer data

customer data

On-site customer

Open workspace

Configuration Mgmt

Automated Builds

Coding Standards

Automated Tests

Collective Ownership

Planning Game

SCRUM Meetings

Continuous Integration

Pair Pgmming

Code Reviews

Refactoring

Incrementally added over 16 months

Time

start

Recommended