Your SlideShare is downloading. ×
Agile Adoption: Does it Have to be All In or Fold?
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

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

834

Published on

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 …

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.

Published in: Technology, Sports
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
834
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
15
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Agile 2005 Experience Report
  • 2. Drawn from extreme programming and scrum
  • 3. Independent Implement Implement dev of lowPlanning UI features Designs Designs Developers code code DataGathering 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
  • 4. Time Open On-site customer workspace start Configuration Automated Mgmt BuildsCollective Automated CodingOwnership Tests Standards SCRUM Refact Meetings Planning oring Game Continuous Code Pair Integration Reviews Pgmming Incrementally added over 16 months

×