Agile Adoption Stratagies

From AgileOpenNorthwest

Introductions - name, company, time adopting agile and scope of adoption.

Group consists of mix of experience between 0 and 4 years and 0 to many teams.

Scope of adoption: Individual (agreed to skip this) Team Org. With Customers Environmental factors

Team:

• C.I. Practice
• Team Adoption
• Team resistance changes to team empowerment
• Resistance to change is a factor
• Hand picked team for the first one
• First team has warm up sessions
• Subsequent teams do not have as much support
• Second Adopeter Syndrome

Organizational Adoption:

• Pilot Project
• Second Adopter Syndrome
• Management buy-in
• Culture matching agile values
• Org. Impediments can be avoided in first team implementation but not later
• Org Change Management
  • issues exist
  • Human element
  • corporate culture has momentum
  • cynacisim about management inititatives
• Change is not necessarily resistenace but fear of loss
• lack of safty net for failure
• collective ownership
• integrating tesers really helped people "get it"
• having a good decision making practice is important

Transformation - Kaikaku

• Scared the crap out of people
• people left
• some teams thrived some did not
• a lot of rapid progress
• a lot of variance in erformancce and practices
• requires local experience

Timeframe:

• 3-4 itereations familiarity
• 6mo - 2 years fluency

Gradual adopton - Kaizen

• hurts for a long time
• always introducting change
• need to suspend disbelief because practices do not always work by themselves
• started with scrum for product/project (not xp practices)
• Started with TDD
• Agile values helped

Timeframe: Familiarity ~3 itereations Fluency - ???