Service share
Each team sets a guide for the share of a sprint that service requests and small changes take: 25% unless the team chooses another. It is a guide, not a limit. DelPulse tracks each sprint’s actual share and the average for each month of the year, so teams can adjust their load and plan for busy times such as year-end or a seasonal peak. The Pulse Cycle forecast keeps each team’s own guide.
Why it matters
Run-the-service work never stops, and it is rarely the same every month. A guide the team owns, checked against what really happened, keeps the roadmap honest.
- Owner
- Product Owner
Led or owned by
The rest of this page is for subscribers
Subscribe to read the other 4 sections of this page:
- How to run it
- Rules
- In the DelPulse workspace
- If you use Jira or Azure DevOps