Usage of Agile methodologies such as Scrum, Scrum-XP, FDD, Crystal and methodologies has become increasingly large in IT Industry and also non IT industries. As the usage of agile methods becoming wide spread, the effectiveness of implementation of these agile practices in projects, organizations become more important for success of agile. Agile manifesto and 12 agile principles, acts as guiding principles and helps in the agile deployment. But when it comes to operational daily tasks, there is no method to ensure whether agile projects implement 4 values of manifesto. For traditional methods of software development we have standards such as CMMI,ISO etc. This paper makes an attempt to defining Maturity Model for agile projects.

Following maturity model has been defined after our experience in consulting and training agile methods.

Level

Categorized by

Guidelines for Description

Maturity Rating based on Focus Areas

1

Basic

1) Following traditional Water fall approach for delivery. 2) Agile practices used in pockets. 3) Requirements/Features (Product backlog items) are more at high-level or Epics levels

Any Focus area <= 50%. Overall Compliance <=50%

2

Managed

1) Product backlog items are broken from EPICs   into development user stories, product back log grooming is done 2) Basic metrics used and not very strong in prediction of the current performance, timeliness of deliverables 3) The Agile team delivers business value occasionally

All Focus Areas - 50% and 75%. Over-all compliance- 50-75%

3

Matured

1) Iteration Status , Agile Metrics in place using Agile Tasks Board 2) Usage of historic data such as velocity, story points committed v/s delivered for forecasting and estimation 3) Team reports the Iteration Effectiveness, Release Effectiveness to different levels of management like functional manager, Product Owner and Top management. 4) Team is skillfully using the Agile Engineering Practices in projects if not at Program Levels

All Focus Areas - >75% Overall compliance > 75%

To validate the maturity levels defined, an assessment of agile practices in projects are done and mapped into following focus areas.

 

Focus Areas

Development Practices/ Infrastructure

Iteration Planning/ Tracking

Product Ownership

Release Planning/ Tracking

Team Cohesiveness( Collaboration)

Agile Testing Practices

 

In order to rate the maturity levels for any project, the compliance of agile practices are mapped into above focus areas and Radar Chart is plotted to depict the compliance of each of these focus areas and are the agile mturity in projects.

 

 

 

 

 
1 favorite thumb_down thumb_up 10 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Outline:

  • Objective
  • current standards for assessment of  Tradtional Processes
  • How do we do in agile projects/processes
  • Agile Maurity Model framework
  • Focus Areas of  Agile Practices
  • Assesment  and Results

Learning Outcome

  1. To understand the effectiveness of agile practices in a project
  2. To define a road map for moving up the maturity in agile practices
  3. Calibration of current agile practices wrt Agile Manifesto and 12 Agile principles.
  4. To identify the gaps and improvement areas.
  5. Objective assement of agile practices for any interested to understand the agile practices

Target Audience

Agile Practitioners, Scrum Masters, Product Owners, Process Experts

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • steve ropa
    By steve ropa  ~  3 years ago
    reply Reply

    Hi Niranjan,

    This is a very challenging topic to be sure.  I noticed in your bio that you have presented at other conferences before.  Do you have any links to presentations or maybe even videos of you presenting these topics?  It might be nice to see a little more detail about the presentation itself.

    Thanks

    Steve

    • Niranjan N V
      By Niranjan N V  ~  3 years ago
      reply Reply

      Hi Steve,

      Yes, I also feel this is a challenging topic to discuss. These maturity levels or guideines ahave been evolved over a period of time from our consulitng and training experience in agile. we have created an assessment tool that will compute the percentage adherence on following agile focus areas/ practices   Development Practices/ Infrastructure,Iteration Planning/ Tracking,Product Ownership, Release Planning/ Tracking, Team cohesiveness(collaboration) ,Agile Testing Practices.

      All these areas has certain set of questions created from our experience. This  subjext provides some yardstick to measure how much agile practices have been implemented around these areas, which ultimately point to agile manifesto and 12 agile principles. These scores are depicted in the form of radar chart with an individual score and Over all Score. I dont have any deck or slides at present.  In case you need, probably I can create a rough overview next week and send it. Do let me know. Thanks once again for the comments. If necessary I can think of changing the title maturity model to simple words. Kindly provide any suggestions.

  • Ram Srinivasan
    By Ram Srinivasan  ~  3 years ago
    reply Reply

    Hi Niranjan - 

    Thanks for your proposal, I have a few questions. 

    What is the business value in this? WHy should business care? If you look at programs like CMMI, the levels mean nothing to business, it just shows that the company was able to demonstrate few processes to the auditors. Does not necessarily mean that it adds business value.

    How are you measuring culture? I see that the ultimate measure of success is RoI and employee/team happiness. And sometimes, it takes a long time to really see the RoI.  How does your proposal address these things?

    Thanks,
    Ram

    • Niranjan N V
      By Niranjan N V  ~  3 years ago
      reply Reply

      Hi Ram,

      Yes, i do agree with mere  levels measurement without Buiness impact does not  not add value. Here we are trying to usage of agile practices to  meet agile manifesto (4 values) and 12 agile principles, the practices will be rated based on these as a guiding principles. The thinking here is, if we can follow these properly the outcome of agile is almost certain. Offcoure our model does not measure directly the outcome, we are tryng to take care of practices , such that outcome  becomes reality.

       

      Answerig to your other questions, like culture. We measure culture in terms of eavulating practices like  colloboration, working as one uinit, are they using silos based approach or team culture for planning, execution, estiamtion etc.

       

      Hope this answers your questions?

       

  • Sachin goel
    By Sachin goel  ~  3 years ago
    reply Reply

    Hi

    thanks for the submissio. Its inetresting in a way that we are aiming to measure how agile we are? Are there any standard f/w you have come across? How different is this from Retro?

    thanks - sachin

    • Niranjan N V
      By Niranjan N V  ~  3 years ago
      reply Reply

      Hi Sachin,

      This helps objective way of assessing agile practices and the ratings will be given for practices wrt following focus areas

       

      Focus Areas

      Development Practices/ Infrastructure

      Iteration Planning/ Tracking

      Product Ownership

      Release Planning/ Tracking  

      Team Cohesiveness( Collaboration)

      Agile Testing Practices

      The percentage of score is computed after rating is given for the focus areas above and then maturity of agile practices is decided as per the maturity level defined below based on the percentage of score in all these areas and overall score.

       

       

      Level

      Categorized by

      Guidelines for Description

      Maturity Rating  based on Focus Areas

      1

      Basic

      1) Following traditional Water fall approach for delivery.
      2) Agile practices used in pockets.
      3) Requirements/Features (Product backlog items) are more at high-level or Epics levels

      Any Focus area <= 50%.
      Overall Compliance <=50%

      2

      Managed

      1) Product backlog items are broken from EPICs  into development user stories, product back log grooming is  done
      2) Basic metrics used and not  very strong in prediction of the current performance, timeliness of deliverables
      3) The Agile team delivers business value  occasionally

      All Focus Areas - 50% and 75%.
      Over-all compliance- 50-75%

      3

      Matured

      1) Iteration Status , Agile Metrics in place using Agile Tasks Board
      2) Usage of historic data  such as velocity, story points committed v/s delivered for forecasting and estimation
      3) Team reports the Iteration Effectiveness, Release Effectiveness to  different levels of management like functional manager, Product Owner and Top management.
      4) Team is skillfully using the Agile Engineering Practices in projects if not at Program Levels

      All Focus Areas - >75%
      Overall compliance > 75%

      The retrospective is subjective wasy identiying the improvements areas only, Here with the help of our assessment tool and maturity level guidelines, we can rate the maturity of agile practices in a project obectively.

      example

       

       

      • Sachin goel
        By Sachin goel  ~  3 years ago
        reply Reply

        thanks - i was curious to know if Focus Areas / Ratings are defined by yourself based on your experience or there are industry standards around same?

        • Niranjan N V
          By Niranjan N V  ~  3 years ago
          reply Reply

          Hi Sachin,

          These ratings and focuse areas are evolved out of our own  experience and best of our agile knowledge.

  • Sonik Chopra
    By Sonik Chopra  ~  3 years ago
    reply Reply

    Hi Niranjan

    It is very difficult to measure Agile projects with a single scale. The main measure is success of project and time to market. Lot of these items mentioned will not apply if I am using Lean or sustenance projects. So this model will show them very low but they're actually very successful.

    • Niranjan N V
      By Niranjan N V  ~  3 years ago
      reply Reply

      Hi Sonik,

      Thanks. Let me clarify you certain things.

      Here we are taking following focus areas of apllicability.

       

      1.     Development Practices/ Infrastructure

       

      2.     Iteration Planning/ Tracking

       

      3.     Product Ownership

       

      4.     Release Planning/ Tracking

       

      5.     Team cohesiveness(collaboration)

      Agile Testing Practices

      We are measuring how much percentage of thes practice are implmented individually and overall and ratings given accordingly.  Hence for sustennace projects or any otherprojects  where certain practices are not applicable, those practices will not be considered for rating (individual and overall). The overalll rating will not get affected and get adjusted accordingly.( It is based on basics)

      This mechanism is to measure the agile pracitices implemented only, to compare them against 4 vlaues in the manifesto and 12 agile principles. Anyone inetersted to measure the sucess of the project, other measures like time to market, business value realises, quality (defet rates) have to be used.