A handy guide to help you navigate the wonderful world of agile practices, principles and values.

I was wondering how I could enable the teams that I work with to make the best decisions on which agile methodologies they utilise. I thought it could be helpful to create a map detailing some of the principal agile practices for teams to check their approach against.

I decided to create a map that would link agile practices and principles with Scrum values within the context of the agile manifesto. Linking all these elements to the values of my team, department and company could help to improve day to day communications, which is vital for effective teams. This map can be used in retrospectives and meetings to provide a focal point and stimulate useful debate.

The map represents the relationship between a practice, a principle, a value and an element of the agile manifesto. Each practice connects with more than one principle, value and element, which can be quite complex, so I simplified it as much as possible.

Note: The principles are colour-coded to connect them to corresponding agile principles and manifesto elements. The practices are positioned alongside related principles. I have made the principles of ‘technical excellence’ and ‘business and developers daily collaboration’ larger than the others to show their weight and importance.

I’d love to hear any suggestions you have to improve the map.

It could also be used in team exercises, eg the team could decide how to connect the elements on a black and white version of the map. This could promote discussions on values and principles, and how to put them into practice. You can also pick a practice, describe it to the team and then have an open discussion about which principles, values and topics within the agile manifesto relate to this practice. This works best with a black and white version of the map so people can draw their own conclusions about the connections.

Last but not least, this document contains a list of agile practices, principles, values and manifesto. It shows the relationship between these and includes interesting links describing each point.

If you use it, we’d love to hear your team's experiences.