Chronicles of a Scrum master #13 : Empiricism and its 3 Pillars (Transparency, Inspection, Adaptation)

What is Empiricism in the agile scrum context ? One thing it is not is about building empires in your product roadmap 🙂

According to the official Scrum guide , “Empiricism asserts that knowledge comes from experience and making decisions based on what is observed”.

In other words, empiricism is about fact-based, experience and evidence oriented approach typically done in iterations (or experiments). From these iterations, we can gather observations, market findings and feedback from others.

Towards this end, this is where the 3 pillars of empiricism comes in.

Source : https://www.scrum.org/resources/blog/three-pillars-empiricism-scrum

1. Transparency
One of the most common elements necessary in a scrum team is an agreed Communication channel and language, roles and responsibilities. Most commonly practiced via the scrum ceremonies such as daily scrums (otherwise known as stand ups), sprint planning, sprint retrospective and sprint review.

In daily scrums, there are no right or wrong questions and the team try to keep away from any negative info from business users, introduce Scrum roles.

The most important is trust between team members. The key transparency point is that everyone in the team should be able to collaborate with each other and share concerns, impediments, challenges and ultimately any solutions.

Another important element is the Definition of Done (which I will explain more in my next article so stay tuned).

2. Inspection – this pillar is not about auditing but rather more on seeking feedback on aspects of the product encompassing system, processes, people, practices, continuous enhancements, culture and collaboration. One such example is the demonstration of features built to users during the sprint demo and review session.

3. Adaptation – this pillar about continuous improvements on aspects described above. Without further actions and improvements on those identified aspects, the product may not be able to grow beyond the current scope and enhancing its value over time.

At the end of the day (or sprint), what this 3 pillars aim to promote is the team spirit of togetherness and ability to work and ensure that product improves over time with more iterations and experiments.

Agile Scrum master

Chronicles of a Scrum master #14 : 5 Values – Courage, Focus, Commitment, Respect, Openness

This has been a post which I wanted to write for some time but struggled till now to find the right words. Its not that its hard to describe but in an agile environment, there are turbulence and winds of change as well as sometimes thunderstorms, hurricanes and typhoons. To maintain the standards of the […]

Read More
Agile Scrum master

Chronicles of a Scrum master #12 : Planning ahead, sprint goals, and tracking stories

Planning ahead Planning the stories and roadmap is usually prepared by the product owner and presented to the team to prep everyone on coming deliverables. Planning ahead means being able to anticipate some of the coming overheads such as holidays and company events that may affect the deliverable timeline. Hence, having a roadmap of features […]

Read More
Agile Scrum master

Chronicles of a Scrum master #11 : What I learnt from certification training

This month marks the second month after I attended training and certified in PSM1. Hence, just wanted to share some of the knowledge which I have learnt from the training and hope this is of use to anyone preparing for the certification examination. Three roles, five events, and three artifacts (3-5-3) Scrum team – product […]

Read More