How to organize Cloud Infrastructure team in Scrum?

Hi there,

I faced the same problem before and worked with a Scrum Team that handles both BAU and project tasks.

The key points here are the prioritization and communication.

As for prioritization, PO should work closely with the development team and stakeholder to give the most appropriate priority for all items. Considering the urgency (from the view of the stakeholder/PO) and effort (from the view of Development Team) for each task is very important. Don't hesitate to move out items in Sprint Backlog if there is a more urgent item in BAU.

Regarding communication, the PO should work closely with stakeholder as the schedule will much likely to be changed, depended on the number of new BAU tasks. If anything is going to be late, announce it immediately and take feedback from the stakeholder. The PO then can give proper order for the Product Backlog.

One more point is your Development Team spirit. In my case, most BAU tasks are from the production environment, which usually require hot fix and the deployment often happens after business hours. If they have to work late/ overtime, I have to monitor closely and even have to stay with them until they leave. Just don't let them feel alone if any impediment rises and you can gain their trust too.

Hope this will help.

Quang Bui

Regardless of work being project or BAU, are the Development Team able to agree a Sprint Goal with the Product Owner, commit to it, and focus on achieving it without interruption?

In my opinion, BAU would be technical debt and be handled just like any other item in the Product Backlog.  It should be understood by the PO so that it can be properly ordered along with all of the new feature work being done.  The Scrum team should treat technical debt and new feature work equally.  

As for urgent production issues, they would be discussed by the Scrum Team (Dev, PO, SM) and a decision made on whether it needs to be addressed in the current sprint.  That same discussion will include the topic of "if we pull this in, does something need to come out?" and "if we pull it in does it endanger the Sprint Goal?".  Based on those discussions and decisions, you will have the appropriate way to handle the urgent issue. 

As with all things Scrum, as Scrum Master for the team, you should facilitate a discussion on how the Scrum Team feels they should work.  It isn't your job to come up with the solution.  It is the team's job to come up with the solution.