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.
21. Independent
Implement Implement
dev of low
Planning UI features Designs Designs Developers
code code
Data
Gathering
Cycle 0
Design for Test cycle 1 Test cycle 2
cycle 2 code code Interaction
Gather design Design for design Design for Designers
customer cycle 3 cycle 4
input for customer Gather input customer Gather input
data for cycle 4 data for cycle 5
cycle 3
Cycle 1 Cycle 2 Cycle 3
22.
23.
24. Time
Open
On-site
customer
workspace
start
Configuration Automated
Mgmt Builds
Collective Automated Coding
Ownership Tests Standards
SCRUM
Refact Meetings
Planning oring
Game
Continuous Code
Pair
Integration Reviews
Pgmming
Incrementally added over 16 months
