Asif Gill Blogs

The adoption of agile software development practice and tools is challenging. It would be appropriate to gradually introduce and improve agile practices and tools into large and complex software intensive organizations . The Agility Adoption and Improvement Model first first developed and published in 2007 and then was updated in 2010 as "AAIM Version 2.0". AAIM V2.0 has been developed based on the intensive research in agile adoption @ a large scale. The AAIM can be used as a roadmap or guide for agile transformation. Organizations or teams can adopt and improve agile people, practices and tools environment in order to achieve specific agile level(s) (e.g. focus one level at a time). This article describes the six stages or levels of the AAIM V2.0.   The Agility Adoption and Improvement Model Version 2.0 (Copyright Asif Q. Gill) The AAIM is structured into white, green and black blocks and 6 levels (from 0 to le

Traditional waterfall software delivery approaches focus on detailed upfront planning, requirements analysis, architecture, design, development and deployment phases. Here, the assumption is that all the requirements are fixed or known or complete. Lot of time and resources are spent upfront for achieving this illusion of fixed or complete list of requirements without actually delivering a single piece of working software. On top of that by the time requirements are completely defined-signed off and developed ,business focus and market competition are already moved few steps further in response to changing business landscape.   Organisations need to innovate and transform their services in response to always changing new business demands. One way to do is applying agile principles and practices of agile software delivery for meeting the always changing business demands. Agile focuses on developing and delivering working software based on just-in-time isolated user stories in smal