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.
Is it a plane, a dinosaur or a ducks foot, dont ignore the cultural differences
It is well-known that when you enter a new market or country there is often a number of cultural differences that you need to be aware of and if you don't then you have a large risk of either confusing that market or alienating them. As part of taking OptimalBI into...
Visualising your Linked in Network
I attended a 1/2 day seminar last week all about visualisation, presented by Neil Fraser from Macquarie University. Great session with lots of tit bits that were both interesting and informative. One of the areas he talked about was the visualisation of linkedin...
BI Platform in 3 months – Lesson #2 – Use IaaS you cant afford time to get servers
Following on from my first tip BI Platform in 3 months - Lesson #1 - Change your business owners engagement frequency the next area I wanted to cover is the challenge that is getting a hardware platform up and running. Lesson #2 - Use IaaS you cant afford time to get...
An Innovative thought – Shared data across all my mobile devices
Sometimes I wonder if the big incumbent companies don't innovate as much as they should because they are consciously defending their legacy revenue streams? It must be hard to say let's go down this route because it makes sense and blow the fact that we will initially...
How do you make something you have done reusable to somebody else?
Ok I managed to not put it in the title but it comes back to the old give a man a fish vs teach a man to fish concept. I have been struggling to work out what the best options are to impart knowledge to others in a way they can consume it, but more importantly in a...
SUNZ preso’s have been popular
A few years ago when I first left SAS and started up OptimalBI, I took on the role of chairperson for the SAS New Zealand User group. As part of that role I started uploading the excellent presentations from each years SUNZ conference to slideshare. I had forgotten...
What is a good culture? (apart from blue cheese of course)
Thinking back to all the places I have worked before I started OptimalBI, a lot of my memories are rose tinted (enhanced) or dark grey (clouded) by the culture that I perceived was endemic at the company at that time. Often the smaller team I was part of exhibited a...
BI Platform in 3 months – Lesson #1 – Change your business owners engagement frequency
We have just finished a 3 month sprint working with a customer to deliver a BI Platform from woe to go in 3 elapsed months. This is the first time I have been involved in delivering something from scratch to production in such a short amount of time. Yes we have done...
Some Innovations are big, some are small, some make the boat go faster
When looking at what value your company provides to its customers it can often be classified into the 3 E's Efficiency You provide something faster or cheaper than the customer doing it themselves. Experience You have done something a number of times before and its...