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.
BI 2.0 Series – iBI where are you?
The world of computing for consumers has changed markedly over the last couple of years. We now google rather than search, we Facebook rather than face to face, and we constantly eye devices that begin with the letter i. But in the world of Business Intelligence I...
Gartner BI Platform Magic Quadrant for 2012
Gartner have just released their 2012 Magic Quadrant for Business Intelligence Platforms.
MobileBI Vendors
As we are researching our go to market for MobileBI in New Zealand, we are looking at all the product offerings available globally out there at the moment. So far we have found: EQ-technologies IBM Cognos Klipfolio MicroStrategy Oracle MobileBI PushBI QlikView...
Doco on Goldengate / Oracle Data Integrator integration
Looking for info on how to utilise Oracle Golden Gate and ODI together. Official doco is here: http://docs.oracle.com/cd/E14571_01/integrate.1111/e12644/ogg.htm This chapter describes how to work with Oracle GoldenGate in order to capture changes on source...
Sorting out SAS Addin and Pivot training for new users
Currently sorting out a resource to create training material for new users. A lot of the clients users are unfamiliar with both Excel and the EDW Content, not to mention SAS. So we are aiming for a simple user guide that shows users how to access Information Maps via...
Moving SAS Servers
Moving the SAS 9.2 environment from the old SAN based server to a new server with a dedicated disk array, to resolve some I/O issues under high load. Will be using shadow copy to automate the move across machines as it manages the swap out of drivers etc for the new...
BI/DW Architecture
Currently working on a developing a BI/DW technical architecture to define how we will manage an environment with multiple ETL and Reporting tools. Will feed into the Enterprise Information Management and Reporting Strategy we are working on.
Configuring SAS ROLAP – Solving Excel Pivot Size Issues
Had some issues with users using the SAS Addin for Microsoft Office against Info Maps where the size of the Excel file gets massive when you save it. It seems Excel must be caching the data somewhere. We are working on configuring SAS OLAP cubes in ROLAP mode as this...
Re-branding the Portal Theme
We are re-branding the project after the successful completion of decommissioning the old Data Warehouse environment at the end of the month. So we are currently changing the SAS Portal theme to match the new brand.