Does the Agile community have recommended processes for a single Scrum Team managing tasks coming in from multiple backlogs?
Context and Problem
- One Scrum Team
- One Scrum Master
- Delivering value to an Enterprise Organisation (+10,000 employees, +$2billion revenue)
- Tasks come into the Team from each Business Function (Sales, Marketing, Customer Service, etc)
- 2 week sprints
- Senior Management (Steering Board) review Scrum effectiveness monthly
- Tasks will be ongoing for at least the next 3 years as part of a massive Change Management implementation enterprise-wide
- The Scrum Team has a developer from each Function which knows the Function intimately but not necessarily what they are going to request from the Scrum Team
- In addition to Functional Requests the Scrum Team also have other demands from ad-hoc Projects (which have a Project Manager but not a Product Owner)
- Scrum Team still has tribal mentality of "I am a Sales Developer and he is a Marketing Analyst. I put more points on the board than he did and he only worked on stories for his buddy in Marketing."
My current plan is for the following action to take place (but I am happy to have the process reviewed by the SE community)
- Each function present their requirements as part of a Function Backlog
- Each function is responsible for grooming their own backlog and having a Product Owner
- Function requirements must be in the form of User Stories (basic level)
- A member of each function attend the Sprint Plan to argue their prioritization over the other Functions (no more than 30 mins time)
- The most compelling business case wins (prize = approx 30-50% of the Sprint Plan)
- The remainder of the Sprint Plan is dedicated to any High Priority functional item from any Function with an even split between Functions (Any Sales, Customer Service or Marketing M or S user story on the MoSCoW scale can be included.)
I cannot imagine a fairer way of bringing together equal Functions with fluctuating Business cases from Sprint to Sprint.
Luckily, all of the requirements are based in the same development environment centered around SAP functionality so the development team (and testing) does not massively vary between user stories/function. What Marketing ask for is well within the sphere of what Customer Service will ask for; just a different end user.
All that changes is which stakeholder gets the value at the end of the Sprint, which department gets the asset added to their bottom line and who gets the bill for the Scrum Team.
Happy to accept any thoughts, white papers or guidance from the Community.
In addition, I have really tried to frame this question for SE so please drop a line if the format is useful including explanations etc.