• I4Agile

 

Software development is increasingly performed in an Agile way. There are less boundaries between different functions and people will perform different roles. Many organizations struggle to fit testing, development, analysis, and project management into the Agile way of working. The objective of I4Agile (Improvement for Agile) is therefore to make this easier. It provides insight in the maturity of software development activities in Agile context and it helps teams to grow to a higher maturity level. The approach is fit for organizations that just started applying Agile as well as for organizations with Agile experience.

I4Agile context

The I4Agile model has a strong relation to the Agile manifesto and its underlying principles. For the terms that are used in scrum, the definitions from the scrum guide are used. Since not everybody in the Agile world uses scrum, a suitable interpretation for other development methods needs to be made by the user of the model. As a result, the model is usable in different Agile contexts.

The I4Agile model

The architecture of the model is similar to many other improvement models. Key areas provide the necessary coverage of relevant aspects. Within each key area, growth is expressed by means of the levels FormingNorming and Performing. Each next level builds on the previous one (from left to right). Furthermore the model consists of checkpoints. A checkpoint describes a practice that reflects something of significant value to reach a particular level.

Flexibility and focus is provided by dividing the model in different modules all related to different aspects of development work. At the moment, the following modules are present:

  • General
  • Testing
  • Development
  • (Project) management (under development)

I4Agile levels

  • Forming: Set the basis and the first steps towards working in an Agile manner
  • Norming: Adopt a process that facilitates the Agile view on working
  • Performing: Continuously improve the way you work by living the Agile way

I4Agile key areas

Key areas – general Forming Norming Performing
1. Stakeholder commitment 1 2 3 4 1 2 3 4 1 2 3
2. Planning & Estimation 1 2 3 4 1 2 3 4 1 2 3 4
3. People 1 2 3 4 1 2 3 4 1 2 3
4. Interaction 1 2 3 4 1 2 3 4 1 2 3 4
5. Teamwork 1 2 3 1 2 3 4 1 2 3 4
6. Environments 1 2 3 1 2 3 1 2 3 4
Key areas – testing Forming Norming Performing
7. Test process 1 2 3 1 2 3 4 1 2 3
8. Test management 1 2 3 4 1 2 3 1 2 3
9. Test profession 1 2 3 4 1 2 3 4 1 2 3
10. Test automation 1 2 3 1 2 3 4 1 2 3
11. Regression & E2E testing 1 2 3 4 1 2 3 1 2 3 4
12. Defect management 1 2 3 1 2 3 4 1 2 3
Key areas – development Forming Norming Performing
13. Code quality 1 2 3 4 1 2 3 1 2 3 4
14. Software architecture 1 2 3 1 2 3 4 1 2 3
15. CI/CD 1 2 3 4 1 2 3 4 1 2 3 3
16. Development testing 1 2 3 4 1 2 3 4 1 2 3 4
17. Development profession 1 2 3 4 1 2 3 4 1 2 3
18. Metrics 1 2 3 4 1 2 3 1 2 3
Key areas – (project) management Forming Norming Performing
19. Demand – supply coordination 1 2 3 1 2 3 1 2 3
20. Planning 1 2 3 1 2 3 4 1 2 3
21. Reporting 1 2 3 4 1 2 3 4 1 2 3
22. Project management profession 1 2 3 1 2 3 4 1 2 3
23. Integration 1 2 3 4 1 2 3 4 1 2 3