Workshop – How to Guide Agile Adoption Efforts
This workshop was presented by Ahmed Sidky and is based on the research he conducted as part of his PhD thesis. Ahmed has developed a methodology for agile adoption that is values-based and focuses on the creation of an agile adoption roadmap. The overall objective of the methodology is to avoid the deep canyon of employee negativity associated with making significant changes within an organization; using Ahmed’s methodology will help convert the deep canyon into a series of smaller ruts.
Within the methodology the agile practices have been categorized based on levels that correspond to basic agile values:
Each level includes a number of related agile practices, and one or two are considered to be discontinuing factors. For example, a customer who is not willing to free up staff to work with your development team means that it’s going to be very difficult to implement the collaborative practices within Level 1. In this case a no go decision may be warranted.
Coupled with the adoption levels is a 4 stage process that you can use to help to develop an overall roadmap:
- Determine level, go/no go decision
- Identify agile practices to adopt, project by project
- Organization assessment
What intrigued me about this workshop was the notion that there is such a thing as an adoption framework that is research based and is more sophisticated than “we’ll start by sneaking the technical practices in behind the scenes”. For example, for Level 1: Collaborative the agile practices listed included more than just customer on site; there were other practices that surprised me at first but made sense in terms of promoting collaboration.
Unfortunately I can’t go into greater detail here because the session was highly interactive so I don’t have good notes and Ahmed was careful reclaim his handouts to avoid folks from applying his methodology irresponsibly. Ahmed did leave an open invitation to e-mail him for more information, which I plan to do in the near future.
- Workshop Abstract