Sorry for this very late post, I was going through my backlog and found some missed articles.
There are many different ways of approaching agile in business and architecture, as a result I am always on the look out for different perspectives and views. This is why I went to the talk on "Business Requirements Analysis - How to do Requirements Analysis in Complex Integrated Agile and Waterfall Development Environments" back on the 23rd May 2013, hosted by the ACS Business Analysts Special Interest Group (BRASIG), as I do work in a mixed project environment where I may be on both agile and waterfall projects at the same time. The presenter for the evening was Dr Asif Q. Gill from the University of Technology Sydney (UTS). Dr, Gill is an experienced enterprise architect and after many years in industry now focuses on both teaching and researching enterprise architecture.
There are many different ways of approaching agile in business and architecture, as a result I am always on the look out for different perspectives and views. This is why I went to the talk on "Business Requirements Analysis - How to do Requirements Analysis in Complex Integrated Agile and Waterfall Development Environments" back on the 23rd May 2013, hosted by the ACS Business Analysts Special Interest Group (BRASIG), as I do work in a mixed project environment where I may be on both agile and waterfall projects at the same time. The presenter for the evening was Dr Asif Q. Gill from the University of Technology Sydney (UTS). Dr, Gill is an experienced enterprise architect and after many years in industry now focuses on both teaching and researching enterprise architecture.
The main focus of the presentation was on how and when to utilise the multitude of processes out there to manage from inception to realisation business requirements. It was an interesting presentation and he does put forward a good case for 'adaptive' processes. Rather then offering a hack-it-up as you go approach he offers a framework which allows for the inclusion of different agile process elements where appropriate for a business.
As he noted, agile is easy to explain but can be hard to adopt. This is the first time ive seen a maturity model for agile presented. Gill has the Agility Adoption and Improvement Model (AAIM) which represents the various stages which a business progresses through as it adopts agile. It is in the slide pack but here is the stages of maturity he offers.
 |
| Figure 1 - The Gill Framework Agility Adoption and Improvement Model (AAIM) |
I think the adoption model has value, to track the process. The feedback I have had from different companies doing agile all assume that once they have a process that is under the Agile Umbrella, then the goal is reached. I doubt this is the case.
References
No comments:
Post a Comment