Agile Coach Online

Expert support on demand

Agile Coach Online Logo

Agile issues for everyone

To make good use of agile it is helpful to understand the key concepts and the reasons that they exist. This understanding is independent of any particular approach to agile and helps to assess the potential of agile to add value to your activities. This section covers these things concisely and should be read by everyone at all levels in an organisation to ensure there is the basis for setting common goals and using common language to ensure effective communication. It is best to read this before you move on to sections of the site which are more specific to your roles and interests.

All these articles are available as (fairly) short videos with additional content for registered clients.

  • Thinking Agile - basic concepts behind agile
  • Key ideas on a page - a short summary of what agile is about, independent of any methodology, framework or technique
  • Common misconceptions - most people who are anti-agile are reacting to what they think it is, not what it actually is. This covers some of the most frequently seen misconceptions about agile
  • Comparing Agile and traditional approaches - people with a more 'traditional' background are often concerned about the way that key features of their approaches are lost in agile. In fact, we do not lose any of the good stuff, just enhance it and make it better. This article shows the relationship between traditional and agile approaches and how to make use of your existing skills in an agile world
  • Software development caused Agile - Agile has its origins from many sources, but one of the most important is in software development. This is because what software is and how it is used has changed immensely over time. This article explores those changes and how they have affected the way we deliver solutions
  • Old roles to new - many organisations have clearly defined roles for people. At the opposite extreme, there is an agile approach where there are no roles. In truth, we all have 'specialisms', but should have more flexible boundaries around roles. This is a general discussion of what a 'role' means in Agile, as well as linkiing to articles on specific roles and how they have changed