Scrum Values meet Agile Principles
Part I of this Evidence-Based Management (EBM) blog post series covered a general introduction to show how evidence-based management can be a powerful instrument when being used in agile transformations. In particular we linked the 12 agile principles using EBM to drive impact in an agile transformation.
In part II, we are taking a look at the Scrum Values and see how focus, openness, courage, commitment and respect can influence the culture of an organization during a transformation. The following free learnings aids might also be helpful. Don't forget to check out our free agile poster series, below you see the Scrum and Agile Manifesto posters with the iconized Scrum Values and 12 principles of the Agile Manifesto.
Crowd-sourcing, self-organization, teams, collaboration, communication, facilitation…are all frequently used terms within organizations striving for more agility. What they all have in common is the link to soft skills. Agile culture, and the ability to learn and react swiftly, is a common desire and motivation to start agile transformations in the first place. Whenever I hear “culture”, it means to be sum of all individuals within an eco-system. For example, I am sure you have visited a company before and you learned a lot about a particular culture by meeting simply the front desk receptionist or security guard.
Being courageous, to pick one of the Scrum values as an example, is not something that would be limited to a specific Scrum team. Let’s say a team faces an impediment that the product vision is not clear or non existent. It takes courage for a team to raise this topic among colleagues and to facilitate it in a respectful manner. But even if this particular team can work through this issue in a successful manner, it requires courage to work through organizational change to revisit the in-take process, the collaboration with stakeholders, customers or business people. Questions like “Is it really our highest priority to satisfy the customer?” Or “Are business people and developers work together daily?” May require courage also only a transformational level.
Focus, just to pick one more Scrum value, is important on a team level for example to be focused on a Scrum Goal, the Scrum framework as a whole, or focusing on the ordering of the product backlog. In terms of agile transformations, and linking the Scrum Value to the 12 principles could mean a focus on “Working software is the primary measure of progress” or a focus on “Simplicity - the art of maximizing the amount of work not done — is essential.”
Using the 5 Scrum values to inspire agile transformations or vice versa driving Scrum implementation using the 12 agile principles might give every agile coach or scrum master a new angle on how they influence each other.
We are also taking a deeper dive into evidence based management during our agile leadership (PAL-E) and agile transformation course + Open Space conference during the Agile Power Week in NYC in NYC in March.