Menu Close

Agile People Framework IT™- Learn More …

The Agile People Framework IT has come from a number of years working in IT, HR, and between the two – and realising the crucial role that HR needs to play in supporting and facilitating an Agile transformation.

Agile Adoption
“Doing Agile”
Agile Transformation
“Being Agile”
Speed of Change Quick Slow
Planning Timeframe Short-term Long-term
Productivity Gain 20% – 100% 300%
Organisation Structure Change Little Significant
Culture Change Localised Widespread

Source: Vitality

There is a difference between Agile Adoption, or “Doing Agile”, and Agile Transformation, or “Being Agile”.  For long-term sustainability, the latter is preferable.  The main differences between the two are:

  1. Agile Adoption can be very quick.  Train a few teams, set up new processes and off you go – with some Agile Coaching to keep the teams in line with Agile.  Agile Transformation, on the other hand, takes time.  It’s about creating the Mindset and Culture that makes Agile sustainable, it’s about bringing all stakeholders – yes, even customers – along for the ride.  It’s about taking the time to make sure that Agility seeps through the very essence of the organisation.
  2. The timeframe for Agile Adoption vs Agile Transformation is different.  Agile Adoption is generally a shorter timeframe with focus on one or more projects.  Project offices manage both Agile and Waterfall projects, and people are moved between them.  With Agile Transformation, the focus is on Products, Customers or Applications set up around long-standing, stable Agile teams.
  3. Productivity generally increases with both Agile Adoption and Agile Transformation.  However, the productivity increase in Agile Adoption has been measured at between 20% and 100%, whereas the productivity increase in Agile Transformation is closer to 300%.
  4. With Agile Adoption, the traditional organisational siloes are, largely, maintained – especially at senior level in the organisation.  The Build and Delivery areas of the organisation are formed into Agile teams for the purpose of delivering work faster.  With Agile Transformation, the inefficiencies of organisational siloes are virtually eliminated by replacing functional siloes with groups of teams aligned with
    customers or internal products.
  5. In Agile Adoption, the teams may feel that they’ve changed.  They may feel more empowered and, hopefully, supported to self-organise. Agile team members may also strive to live to the Agile Values and principles.  In Agile Transformation, it is the culture that is being transformed. Agile is not the goal.  Agile is the vehicle to achieve the goal of cultural and business model transformation.

As you can tell, an Agile Transformation is a significant program of change in an organisation.  And we can help!

If you feel ready to really start learning about it, you can attend our Agile People Framework IT™ (APFIT™) Training Program.   Click the button below for all the details of our Agile People Framework IT™ (APFIT™) and attend Lesson 1 for a taste of what we cover in the program.

If you would prefer to talk to us, or have questions or need support, please click here to set up a time to talk to us, or click here to email us now.

Click the button below to learn more about our Agile People Framework IT™ (APFIT™) Training Program.