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.
What motivates the team behind a company
I have worked for enough "big" companies that pay lip service to motivation, especially when it comes to renumeration. As part of the sales team for these organisations it was often a see saw between a big carrot and an even bigger stick (especially at fiscal year...
Articles on Setting up CDC for SSIS 2012
I am doing some work at the moment working out options to enable Change Data Capture (CDC) within Microsoft SQL Server 2012. As always there are a number of blogs, articles etc on the web that give you a head start. As I find the ones that are useful I will add them...
Using the Art of Visualisation to tell a story
This is a great example of using visualisation to tell a story by Hans Rosling's. Its from the The Joy of Stats which was a show on BBC Four it seems, wonder if it was ever on NZ TV?
Do you want to be a Data Scientist?
So if you had a choice between being a Data Scientist: or another visualisation of the term based on somebody who goes out and explores the unknown (and while maybe a little unconventional, is still well qualified and effective ): So which one would you be? And what...
Some things are just so ……
Cool! A Kathryn Masterpiece
The 3 W’s of Project Success
My role at OptimalBI has three areas I concentrate on: Solution Delivery As the founder and part owner of OptimalBI, when I make a promise to a customer on what we will do to add value to their business, I am ultimately responsible for making sure we deliver (of...
Cool Visualisation – WebGL – Book Shelf
I have been doing some research on cool and advanced ways of visualising large volumes of data and content. Stumbled across a Technology called WebGL and a few interesting examples. Check out: http://workshop.chromeexperiments.com/bookcase/ Once you have finished...
Execution is more important than the idea
I am obsessed with the idea of visualising Metadata. But more on that later.... Reading this article prompted some thoughts.... I often talk to people about cool or Innovative business ideas they (or myself) have had. Everynow and again I meet somebody who mentions...
Simplicity = Change and Focus, My favs to follow at the moment
Steve Jobs always displayed the essence of simplicity in everything he did. Sometimes he took it a little to far, for example when it came to furnishing his house. There are 3 people I blog stalk at the moment, that take the status quo, and via a combination of...