A “Team” is generally defined as a group of people. Who work together towards a shared goal. In my experience, effective interaction forms the bedrock of such a ‘team’ – a factor often taken for granted. All the more true in an agile environment, where one sees high levels of ambiguity, uncertainty and diversity.

How do we better utilize our time attending an insane number of meetings? Coaches get this asked a lot. While little can be done about the number of meetings just like driving in bumper to bumper traffic, we can surely improve the in-car time utilization!

In Scrum framework, retrospective is the last event of each sprint and has also been one of the most rushed events in our experience. This has meant that the event has failed in helping the team, consequently failing in its purpose and has thus been considered mostly as an helpless event.

Scrum Alliance has published seven versions of Scrum Guide in a decade since the first version was published in 2010. Each version has been a reflection of the changing landscape of software development processes.