In India every March they celebrate the festival of color. The festival recites the legend of a good overcoming evil even in the midst of a flaming fire emerging in a festival of beautiful colors rather than a mere cloud of smoke.

In Scrum, the festival of color is sparked by the customer being priority one and the desire of the Scrum Team to deliver the first-hand valuable product increment to the customer. Every sprint the Scrum team is given a fresh canvas on which to collaborate all their diverse tones of color to create their festivals of colors.

Let’s look at the festival of color that lives within a Scrum Team.

The three roles of Scrum

The ScrumMaster, the Development teams, and the Product Owner. The ScrumMaster comes pigmented with the values of Scrum and pure motives. The pure motives are like a white spectrum of light that projects through the servant leadership of the ScrumMasters character.

Each team member is pigmented with the strength that comes from the skills they bring to the table. The tester skills come with their fluorescent colors of quality like bright oranges that reflect the brilliance of the sun when it is in full. The teams are testing skills crescendo when they have to look at code and functionality to ensure the finalized a view that the customer will have will be the deepest color of a high-quality product increment. The developer brings the grounding prime colors to the table and we know without the prime color palate there can be no innovation. The fabulous shades of pink and lavenders hue demand core colors as their base. Principles of from engineer practices bring those prime colors to the table. When developers refactor their code and pair program in the manner suggested by Extreme Programming affectionately known as XP. Developers can bring strong high quality pigmented base colors to the table.

Then we have the Product Owner who Scrum has designed to be the brightest color. Not because any color is better than another, but the Product owner has the responsibility of leading the way, navigating the ship even in the darkest day. When value and Return On Investment are not clear the requirements that are presented as product backlog items elicit too many questions if left unanswered could create potential shading on the canvas that does not meet the customer’s vision of complete.

The ScrumMaster continues to support the Scrum Team throughout the creative process by helping to keep the environment clear of clutter of outside distractions. However the ScrumMaster cannot give direction on how the Development team execute their festivals of color, so when the development team allows itself to go into the zone of interpretive art waste can emerge along with conflict. Everyone know creative teams are hot colored from time to time.

To ensure the right amount of every color is created and used in every stroke, a definition of done has to be very carefully defined, because without it the brush stroke of a particular color maybe too heavy.

Allow your sprint review to be a gallery of the festivals of color merged into a perfect painting that will demonstrate the beauty of constant collaboration and skills of a focused, committed, courageous team that ultimately respect the art of Scrum.
The sprint retrospective allows the team to get into their painting gallery, clean up and reflect on the art piece they created. Ultimately it helps them to refine their individual techniques of mixing the shades of the palette they bring to the table because each team is nothing without each palette of color that every individual brings. The next canvas will need every color to bring the right texture and stroke and pigments to truly demonstrate the festival of color that is a high functioning Scrum Team.