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.
RapidMiner – Unsupported major.minor version 51.0
If you ever try and install RapidMiner on a mac, you might get this little error when starting its engines: Exception in thread "main" java.lang.UnsupportedClassVersionError: com/rapid_i/LauncherJVMOptionBuilder : Unsupported major.minor version 51.0 To get this error...
Webstock – I was blown away!
Webstock is one of those events I have always wanted to attend, ever since it started when I was at Xero. But for some reason or other I never managed to make it. This year I finally sorted my shit and made it and I was blown away! (and now regret not find the time to […]
Constantly providing something for free, its not normal (until now)
When you get offered something for free do you start feeling uncomfortable, looking for the fishhook? For me it depends, if its a Software as a Service app, there are so many that are offered for free these days, its a new norm, so i'm happy to take it (understanding...
It’s ok to fail, just don’t
constantly fail doing the same thing and expecting a different outcome. There is a whole philosophy at the moment around fail fast and fail often. The idea being that by working out what doesn't work, you'll find what does work quicker. And that finding out quickly...
OptimalOrange
Its often not what you do, its how you do it
The other day I redeemed a reward from Flybuys (whoot freebie!) and went into Noel Lemming to pick it up. Flybuys (Loyalty NZ) have made it so easy these days, no more waiting for a piece of paper to arrive via snail mail (sorry NZ Post yet another nail), you just...
OptimalOrange
SFT – Keeping yourself honest, customers will like the experience.
One of our 3 values is "Don't be dodgy". Its a value we don't have plastered on our walls anywhere, we don't have it framed as a picture, but we do use it to test things against when we decide to do them. In the world of Search Engine Optimisation there are ways of...
Mentoring as a Service Experiment
As part of the Agile week at BoostAgile, they gave me a copy of the lean startup book to read. I liked it One of the things I really liked was the concept of creating experiments to prove or disprove an idea or concept. Its one of the things we have been doing...