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.
Qlik Sense Desktop – Loading QVD
When using the Qlik Sense Desktop you can easily add Excel or CSV files to your new application by selecting them in the add data window. What I missed was the fact that this option also allows you to add a QVD easily as the source file. Just select "All Files" and...
Trifacta – Wrangling Dates (and yet another open data rant)
One of the pieces of data we use regularly is dates. Every data repository needs the ability to view the data by day, month, year, etc. There is often also a need to view data based on holidays. Funnily enough, you would think that a list of data containing the NZ...
Guided vs Discovery vs Blending Information Products
I have seen a massive change in the business intelligence, data and analytics tools our customers are buying and using over the last couple of years. The advent of data wrangling tools such as Trifacta, open-source analytics tools such as R and visual exploration...
AgileBI Delivery
As a BI Practitioner
I want to understand how to deliver in an AgileBI way
So that I can deliver faster and with less risk
AgileBI Team
As a BI Practitioner I want to understand what an AgileBI team is and isn't So that I know how to form and storm one Building a self organising team is one of the key factors required to deliver in an AgileBI way. Creating a team with T-Skills and helping...
AgileBI Discipline
As a BI Practitioner
I want to understand what AgileBI Disciplines are
So that I know what Disciplines to follow (and what Disciplines not to)
Evaluating BI tools – Don’t get left hanging
Evaluating BI tools used to be easy. You either took a stack approach and picked a vendor first, then selected the modules you wanted to use from their product catalog. Or you picked one thing you wanted to do extremely well and selected a best of breed product/vendor...
Hans Hultgren – The 2016 NZ Data Vault Certification Tour
As you may have worked out if you have been reading our blogs for a while, we are big fans of the Data Vault approach as a way of automating the Integration layer of a Data Warehouse (DW). In 2014, we sent a couple of our DW experts to Sydney to attend Hans...
The challenges and risks of being an Agile BI Manager
As a BI manager who decides to empower their team by introducing an AgileBI approach, there is a massive amount of risk in that simple action.