Scrum in a Business as Usual (BAU) Team

ZXM had been working on a project with a client using Scrum to help them set up an Intranet redevelopment project. The transparency and collaboration that the manager saw emerging out of the intranet project was very appealing to him. He decided that it might be adaptable to his BAU team.
The BAU team  always seemed to have a “backlog” of work that never got done. The main issues were:

  • No collective process for them to process business user requests
  • New work coming constantly coming in from the business
  • Team not sure of which work was important, urgent or ranked higher
  • No collective processes to handle BAU as well as project work
  • Small team but working in three streams of activity
As a result, they started a bit of each project but never quite got anything finished.
Using a psychology based learning model of competency, within three months we were able to take the team from Unconscious Incompetence to Unconscious Competence.
Why was this approach success for the BAU team?
  • Scrum gave the team radical visibility of what was coming up from conversations in standups and backlog refinement.
  • The traceability of stories to themes and Epics gave the team a sense of where their work fitted into the bigger picture.
  • Knew to refine the backlog with the Product Owner in order to work together to establish the definition of done (DOD), estimations and tasks
  • Able to better understand and estimate BAU velocity and project velocity
  • Now had a process to deal with business requests and how to determine order/priority of work in context of the product backlog
As a result the Team asked t0 be involved in work across old silos and the product owner was comfortable to move to only stating the WHAT and not the HOW to his team.
  • Better understanding of commitment to take on a product/story in a Sprint
  • Collaboration and pairing across old silos occurred to complete tasks
  • Not silos of 3 streams — a single team with a single, shared vision of how to get their work done

Leave a Reply

Related Posts:

“Netiquette” for online meetings for remote and distributed teams

As with face-2-face meetings, online meetings also have an etiquette (“Netiquette”) to make them effective. One of the 12 principles of the agile manifesto suggests face-to-face is the best option but in today’s world of social distancing and WFH, it is no longer an option.

Here are the guidelines we have found useful for having for online meetings with distributed


22 Stances of a Scrum Master

The Scrum Master doesn’t remove impediments from the team. Their job encompasses 22 wider stances for supporting the team to self-organise to remove impediments themselves, coaching the Product Owner and coaching the wider organisation.


Does agility go out the window when we work remotely?

Many organisations are making guidance on what tools to use for remote teams in response to COVID-19. The situation isn’t a tools problem. This is a people problem – how can people, who are social creatures, successfully work remotely without physical interaction?


Copyright © Zen Ex Machina® and ™ (2019) All rights reserved. ABN 93 153 194 220

search previous next tag category expand menu location phone mail time cart zoom edit close