AgileBI Culture Change – No Meetings

by Feb 13, 2016

A Massive Change

One of the biggest challenges of using Agile methods to deliver BI projects, is the massive change in the way the team has to work.

Everything from the way they plan, their level of accountability, the way they interact with their team, interact with other teams and stakeholders, and the tools and techniques they use are all different to what they are used to.

Meetings, Meetings, Meetings but not an outcome to find

One of the interesting changes is moving the team from their concept of meetings.  To the team a meeting is something that:

  • is planned in the future
  • often has unclear goals
  • a raft of people are invited to, often even if they are not required to achieve those goals
  • is always for at least an hour in duration
  • is often seen as a waste of everybody’s time

Unless its an AgileBI “Meeting”

When undertaking an Agile project, we actually see a massive increase in the amount of time the team spend together collaborating, from attending sprint planning, backlog grooming, retrospectives through to constant group sessions to nut out the many problems they strike.

Initially though we will often see the usual disparaging attitude to these collaboration sessions as they are perceived as the meetings of old.

Planning has massive value

Once the team gets to experience the value that sprint planning delivers in helping them work through the steps that they will undertake in the upcoming sprint, they will typically embrace them with open arms.  The same can be said for backlog grooming, once the team experience how constantly refining the user stories in advance helps reduce the time required for sprint planning, as well as ensuring that every new requirement is captured weekly,  they see the value in these planning sessions.

Meetings are DEAD, long live Collaboration

In our AgileBI projects we ban the use of the word “Meeting”.

All pre-planned events that require the team to get together are scheduled at the beginning of the sprint and have an outcome.  Those events are named after that outcome (e.g backlog grooming).  Any other requirement for the team to collaborate are a result of the user stories being delivered and the team should immediately get together to ensure there is no delay in removing the road blocks for that user story.

In a three week sprint every day counts.

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