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.
The business model for BI is changing
Anybody who knows me knows that I am a big fan of Seth Godin. I find his logic enlightening, his insight well-reasoned, his writing innovative and when added together he is just cool! (Pity I didn't think of this way to see Seth cheap, like Victoria's friend) Seths...
SAS Visual Analytics Short Online Demo
Quick overview on SAS Visual Analytics from the SAS Software Youtube channel below. Excuse the number of times they say daaaattaaaa and the word Billion (and no thats not the price 😉 Interesting bits I picked up: It automatically picks the most suitable...
SAS Inno”VA”tion
SAS has been around for a long time and you have to admit it has been a very successful company announcing USD $2.8 billion in revenue lately, while remaining privately owned and focussed on delivering Analytics and related Business Intelligence software. But it's...
Google insight – is this the future of Analytics?
I found an interesting article here: http://www.buzzfeed.com/justinesharrock/a-glimpse-into-googles-brain-hidden-in-a-spreadsheet-app It outlines how if you open a google docs spreadsheet and create two cells of related text (say two different brand of beers) then...
Gartner (meta) BI Definitions – Definitions about Definitions
When reading the latest 2013 Gartner BI and Analytics Magic Quadrant I noticed that they have included some definitions of the various capabilities in each of the BI categories. I wil no doubt end up cutting and pasting them into a few BI Strategy documents this...
Gartner Magic Quadrant Business Intelligence and Analytics Platforms 2013
Gartner released their latest Magic Quadrant for BI last month. My thoughts as I when reading through the document: Microsoft has shot right up and given the massive disparity in pricing between them and the old Mega BI Vendors club (Oracle, IBM, SAS, SAP) and the...
Innovation Innovation where for art thou
I was sitting at the SUNZ conference last week listening to Evan Stubbs talk about Innovation and Analytics and how over the next 3-5 years there will be a marked shortage in Analytical bods, as the demand for these skills will far outweigh the supply. One of the examples of Innovation Evan gave was that old favourite […]
Meetings, Meetings, Meetings and not an outcome to drink
It would be fair to say that when working with customers defining or implementing BI strategies or architectures, I spend a bit of time in meetings with them. Meetings are always booked for at least an hour often two. (as compared to workshops that are normally 1/2 a...
Apple Retail Stores are a competitive advantage, goes against conventional wisdom or does it?
Interesting article on how Apple are closing down 20 retail stores so they can move them to alternative locations that allow them to be bigger: http://techcrunch.com/2013/02/12/apple-closing-20-retail-stores-in-order-expand/ Interesting as of course the conventional wisdom for retailers for the last few years has been to from “bricks and mortar” to an eChannel strategy. However there has been a lot of noise around people […]