The three pillars of scrum

Most practitioners associate the tenets of the agile manifesto as the guiding principles in executing their scrum agendas. In this article, With the premise of Scrum optimized on empirical process control, I wanted to spend some time looking into the three pillars of Scrum theory: transparency, inspection and adaption and provide some annotation on what they really mean, and why these pillars should be the foundations of your practice.

Embracing the Agile manifesto

Something as a practicing program manager I tend to always use as tenets when guiding teams, is relying on the spiritual bible of contemporary project management, and that’s the Agile Manifesto. Products of the Agile Alliance, the premise of the Manifesto is to simplify the practice of project management through a lightweight framework to build software expeditiously with bias for customer validation over processes and documentation and red tape.

The two drivers behind the manifesto are iterative and incremental development, over pre-medicated and over planning, and creating higher quality software in shorter time, or more concisely, build more with less.

The one thing agile teams miss when WFM: Osmotic Learning

Overwhelmingly, tech companies have transitioned their sprint iterations from co-location to having teams work remotely, from home. The Covid-19 pandemic has forced teams to change how they interact with each other, perform agile rituals and deliver products. 

One thing that is missing, is osmotic communications, learning through accidentally overhearing.