Krishna: The Ultimate ScrumMaster chosen by Pandavas (The Team)

Krishna: The Ultimate ScrumMaster chosen by Pandavas (The Team)

As per Vedas, somewhere around 5000 years back, Mahabharat (Kurukshetra war) battle had been fought. There were so many sequential events which led to the circumstances where battle became inevitable. There were 2 sides Kauravas & Pandavas. Both the armies (teams) participated in the event. We all know this.

Have you ever analysed the role of “Krishna” in that battle (event)? What he did? What he thought and to what was he accountable? Let’s see!

1-      Krishna did not fight the battle himself.

2-      He aligned Pandavas to the goal (which is actually not winning the battle rather re-installing the ‘Dharma’ on the Earth).

3-      He facilitated all the discussion among Pandavas to find the solution of problem. He took Pandavas on the same page and let them take the collective decision what to do next.

4-      Only when Pandavas were not able to take any decision, he ‘suggested’ the action-items.

5-      When Arjuna put down his weapons, he asked Arjuna to fight not-to-win but for the goal which “re-installation of Dharma”. He re-installed the Commitment, Courage & Focus among the Pandavas (the team).

Krishna was accountable only for “re-installing the Dharma” and keeping team motivated towards this goal for which he made Pandavas:-

a)       Committed towards the goal

b)      Focused towards the goal

c)       Courageous enough to proceed towards the goal (Here, pandavas were courageous enough to fight but when Arjuna saw relatives other end, Krishna made him & other courageous enough to take step which are required to achieve goal which is re-installing Dharma.)  

d)      Open enough so that they can say/suggest what they think

e)      Respecting each other’s quality among them. (E.g. – Yudhishthir every time spoke truth which created tough situations to handle. But other Pandavas supported their eldest brother.)

This battle had been fought for 18 days and after each day’s fight, Krishna facilitated discussion for Pandavas to inspect the incident and adapt & prepare for next day. He instilled the quality of ‘Empiricism’ (learn from today’s experience and plan for tomorrow accordingly) among the members.

I could see this as the qualities of ScrumMaster. The 2 things:-

1-      Reveal - not resolve, and

2-      Actively doing nothing

are something on which facilitation is based. Krishna was truly a facilitator for Pandavas during the complete event by: -

-          keeping them focused towards the goal (again, not winning but to re-install the Dharma)

-          keeping away from external distraction

-          helping them to identify the blockers (like Bhishma, Karna) towards goal and removing them

Along with this, He made team (Pandavas) able to earn trust on each other. Everyone trusted each other. This was one of the main ingredient of their success.

If not completely, isn’t it mostly in line of ScrumMaster’s responsibility?

Krishna correctly proclaimed:

“It is not my duty to do your work (fighting the battle). I’ll show the correct path to you and set the environment in which you can fulfil your duty.”

Most importantly, he left Hastinapur when the re-installation of Dharma was achieved (the goal).

“And ScrumMaster is succeed only when team is in condition when ScrumMaster is not required.”

Learn From Google Map to Grow as SCRUM Team!

Learn From Google Map to Grow as SCRUM Team

Today, it is very common & easy to use google map navigation when you are going somewhere. Just enter your source & destination and start navigation. Right after this moment, google map will do below activities for you: -

1. Calculate Estimated Time of Arrival as per current traffic scenario;
2. Highlights the best possible path to reach destination;
3. It also mentions the other available paths in grey colour;
4. During the journey, if traffic scenarios changes on the way, google map will highlight the other best alternate route;
5. If you change the destination in middle of journey, it accepts the change and highlights the best possible route to reach changed destination;
6. Once you reach destination, it notifies the same to you;

Along with these standard steps, google-map also does: -

a)       Learn about newly created route on the way. (Eg. – On your way, one new underpass or alternative route was constructed by Govt. When you & other travellers follow that route, google-map learns that there is another route here and after significant learning, it will start suggesting this route in navigation);

b)      It keeps check on time-taken during the journey. If time-taken is more or lesser than the predicted one, it learns whether this route has some issue (like some construction is going on) or the route has been improved. Based on this learning, it adapts the new changes and provide predictions accordingly;

c)       It learns whether a path contains toll booth. Accordingly, it highlights the same thing so that you might know about other extra expenses before journey;

Apart from these, it also does number of things. However, let’s consider only these activities performed by google map.

Let’s give a thought on this, doesn’t it look like standard activities of a project (or journey of a product). During the product development, we do: -

1. Set the product vision (the destination)
2. Create plan as per available resources (people, tools, budget etc)
3. Based on the information in #1 & #2, define the roadmap and estimated time of delivery
4. Since, during the development nothing (vision, people, tools etc) will be fixed or prone to change, the teams need to adapt these changes and come out with the best possible plan in the scenario
5. Once product has significant features, it will be released to customers
6. According to the further requirements, the future development will go on
7. During the development, team learns & enhance skills which results into better & faster product delivery
8. Team can foresee the other challenges, roadblocks, extra-cost during the product development and notifies this to business.

What we have seen, is the quality of Scrum: -

Inspection, Adaption and Transparency!

Google map is the prefect example which Inspect or Retrospect the surroundings and improve its knowledge and learns from the experience (Empiricism). It Adapt the changes coming in the surroundings whether new construction, any roadblock or extra-cost requirement or the destination itself has been changed from the original destination. Having the quality of Inspection & Adaption, it truly satisfies the need of being Transparent. It is transparent to user and providing the most correct information. These are the exact virtues of Scrum Teams who learns from experience, retrospect themselves & adapt the changes, embraces the change requests coming during the product development and ensure transparency among themselves & to organization.  

Scrum Teams, if you want to learn, grow & develop as an Agile/Scrum team, analyse the activities of google map doing for you & learn from it