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.
SFT – The art of Innovation – break it and then fix it
Innovation is a popular word these days in business. Good old Wikipedia defines it as "Innovation is the application of better solutions that meet new requirements, inarticulated needs, or existing market needs." But being innovative is not simple. And often the...
Day 1 – Overview, Vision, Scope and Accountability
So day one is down and it was a day of setting the vision and starting the definition of the scope (the Dev team were off sick, so it was only a 1/2 a day) The Process The day started with a quick whiteboard overview of the entire Agile Scrum Framework and this...
I’m getting flexible – a week of Agile ahead
I love learning new stuff! The six months I spent at Xero has probably been my most intensive learning experience I have had, and in retrospect it was due to the fact it was total immersion, completely focussed on delivery (having Rod Drury walking the floor behind...
Dynamic Data Driven Urls coming in SAS VA 6.3
Kathryn has just spent part of last week mentoring a SAS VA customer in Australia. We love this type of work because we help out customers help themselves (rather than black boxing delivery and forcing them to pay us for every change) and because we always learn new...
SFT – Watch the end of the runway
Often in a project we focus on the wrong things. Lets look at a project with the goal of building a plane that will take off. The challenge is that while we are building the plane it is slowly moving towards the end of the runway. Once we run out of runway the...
SFT – What is cloud computing?
Cloud computing is the latest buzz word and in true IT style, we have invented a raft of TLA's to explain what it is (and isn't) as well as a myriad of versions to confuse people even more. PaaS, IaaS, SaaS, DaaS, public cloud, private cloud, hybrid cloud, BIaaS, How...
SFT – Don’t complain, suggest something better
When you find something you don't like a natural reaction is to complain. The people you complain to will often listen politely, but they won't typically do anything about it. (Unless you have something they really want, that they will lose if they don't rectify what...
SFT – Its not the idea, its the execution
Your idea probably isn't unique. But then again you probably haven't found anybody that has done it the way you plan to do it. So don't spend your time asking people to sign NDA's or telling them half of the story. Just go execute on it. If you not sure, or need help,...
Deloitte Fast50 2013 – Infographic
So have you heard that the Deloitte Fast50 for 2013 has been announced and we came 22nd 😉 Check out our Badge Well one of the cool things about the Fast50 is that there are a myriad of different companies, doing different things and all at different stages of their...