No Meetings
As a Product Owner or Scrum Master
I want to understand how to deal with ‘meetings’ in an AgileBI project
So that I can change the team’s negative view on collaboration
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 used are all different to what they are familiar with.
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.
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.
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 roadblocks for that user story.
In a three-week sprint, every day counts.
Adding members to the Agile Team makes you slower
The Issue: As a Stakeholder or Product Owner 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. My Answer: Adding members makes you slower. Initially, at least....
The Agile Team member should know what they are working on and why
As a AgileBI Coach
I want I want to understand how to determine if the AgileBI Team are in a healthy state
So that I can keep the sprint team engaged
Standups should be open not closed
As a Stakeholder or Product Owner I want I want to understand who can attend a standup So that I can ensure we are following an Agile approach Standups One of the many key things in deliverying in an AgileBI way is the use of daily standups to...
Who should attend Steering Committees?
As a Stakeholder or Product Owner
I want to understand who should attend the steering committee
So that I know I have the best representation
Remote Scrum Masters
As a Stakeholder or Product Owner
I want some examples of things that can fail in AgileBI
So that I know what to watch out for
AgileBI Discipline
As a BI Practitioner
I want to understand what AgileBI Disciplines are
So that I know what Disciplines to follow (and what Disciplines not to)
Making Retrospectives Fun
As a scrum master
I want I want to understand how to make retrospectives fun
So that I can keep the sprint team engaged
It’s Agile not Adhoc
There are a number of myths abound about the Agile approach. These include that idea that having a daily 15 minute standup is being Agile, to Agile doesn't deliver documentation. When I hear these myths I typically reply with "Agile is not Adhoc". So let's list the...
Agile Discipline – Planning
There is a myth that Agile is all about being adhoc and that there is no planning upfront involved. It's not true. In fact when undertaking a AgileBI approach the team will spend far more time in planning sessions than in a typical waterfall project. What is different...