Retrospective – No Meetings

by Feb 20, 2016

As I outlined in my earlier blog AgileBI fundamentally changes the team’s traditional view of meetings.  It’s interesting watching how new teams adapt to this change.

An example from one of the teams I worked with recently is …


One interesting example that we often see is the use of meetings to help troubleshoot a problem or clarify an expectation.

Where possible the AgileBI team is always co-located to assist with collaboration and communication.  When a new team starts working together and strikes a problem, they will often book a meeting in everybody’s diary at sometime in the future to work through the issue.  The same is when they want to clarify the expectation for a user story with the product owner, a meeting is booked in the future.

When running three week iterations these delays can kill the successful delivery of the sprint.  Given the team are all dedicated to the sprints there is nothing stopping the team from getting together to discuss the issue when it arises, often by just swiveling their chairs around or by all immediately getting up and standing around a whiteboard.

It’s not until you point this out though that the team realise the latency that these future based meetings cause and change their behaviour.

As with all things Agile, constant collaboration is a major change in the way the team works and often simple behaviours that have been embedded for years need to be changed.

Start your AgileBI journey with us.

Other steps in the AgileBI Journey

And sometimes a sprint or a scrum.

Adding members to the Agile Team makes you go slower

As a Stakeholder or Product Owner I want I want to understand if constantly adding Agile Team members is a good idea So that I can have a valid conversation with my Product Owner and Scrum Master Initially at least! VelocityWhen building a new AgileBI delivery team,...

read more