Who should attend steering committees?
As a BI Manager
I want to understand who should attend the steering committee
So that I know I have the best representation
So the first thing to note is that if you are operating under a construct that has a steering committee, you are probably not operating as an agile organisation and your delivery team will struggle to “be” agile. However “doing” an agile approach is still better than a waterfall approach when delivering Data, Analytics or Visualisations.
A steering committees role is to govern a project and be accountable for making sure the project delivers its agreed outcomes to the stakeholders.
In AgileBI approach:
- The agile team govern themselves, with the help of the Scrum Master to assist them to improve. They are accountable for delivering what they promise to deliver.
- The Product Owner governs the prioritisation of what is done, and will typically have a group of stakeholders who assist them with the prioritisation. The Product Owner is accountable to make sure the top priorities are delivered first.
- The financials are simple in an AgileBI approach, you take the cost of the Agile Team per day and multiply it by 15 working days for each delivery sprint. You add on the cost of the infrastructure, which is hopefully cloud-based and therefore has a known cost per day.
- The proof of success is shown each Prove it day and measured based on the acceptance criteria being met.
So the role typically is undertaken by the Steering Committee, of being accountable for delivery and making sure the project is on budget is taken care off, without the need to write endless monthly status reports to the steering committee or discussing in detail who is doing what with them.
As I have mentioned a Product Owner will often have a group of people that will assist with prioritisation. And this will often be done via a prioritisation ceremony. In fact, one of the most effective ways I have seen this happened is for stakeholders to “horsetrade” their deliverables to see who will define the vision statements for the next sprints. This ceremony is not a steering committee or a steering committee meeting!
If you are stuck in an organisation that is still undergoing the transition to becoming an agile organisation, and you are forced to operate under a steering committee construct, then it is crucial that the Product Owner attends and is the “voice” of the agile delivery outcomes.
No doubt if you are forced to have a Steering Committee you will also have one (or more) Project Managers. Their role should be to organise the Steering Committee meetings and produce the minutes (think Project Administration) not to be the voice of the delivery team.
And if you are operating under that model you probably also have a formal Project Management Office (PMO) in place as well, so the Project Manager can also add value by completing the myriad of reporting that the PMO will require. Leave them to manage the dross of low-value traditional reporting that waterfall requires.
Leave the agile team to deliver and the Product Owner to manage expectations. That after all is their roles in an AgileBI Approach.
StandupsOne of the many key things in deliverying in an AgileBI way is the use of daily standups to enable the Agile Team to have regular conversations on where they are at, where they are going any any current impediments. Who can AttendAnybody should be able to...
As a AgileBI Guru
I want some examples of things that can fail in AgileBI
So that I know what to watch out for
As a BI Manager 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
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)
As a scrum master
I want I want to understand how to make retrospectives fun
So that I can keep the sprint team engaged
There are a number of myths abound about the Agile approach. These include that idea that having a daily 15 minute standup is being Agile, to Agile doesn't deliver documentation. When I hear these myths I typically reply with "Agile is not Adhoc". So let's list the...
There is a myth that Agile is all about being adhoc and that there is no planning upfront involved. It's not true. In fact when undertaking a AgileBI approach the team will spend far more time in planning sessions than in a typical waterfall project. What is different...
There is a myth that Agile doesn't deliver documentation. It's not true. We always do the documentation that is required during a BI project, such as design and as built documents, what differs is the way we create them and when. A waterfall project is all about big...