Waterfall planning and production work without explicit WIP limits.
Sprint and flow discipline: full Scrum cycle for software teams, Kanban with WIP limits for production, and sprint-based planning for creative production.
Better flow and more predictable delivery, with five coordinators running delivery independently.
- Backlog
- Sprint planning
- Scrum / Kanban flow
- Review & retrospective
- Improve
At Reality Premedia Services I worked across BFSI and healthcare software projects and creative production work for clients, first as Project Coordinator, then as Lead Project Coordinator.
Creative production ran on waterfall planning, and production teams worked without explicit limits on work in progress.
Unpredictable delivery was showing up as client escalations, missed dates, rework and quality issues.
I facilitated Scrum for software teams of 8–12, partnered with product owners, coordinated UAT, and led five project coordinators.
The two kinds of work behave differently. Software could be broken into small, time-boxed sprints that each end in a working increment. Production work arrives as a continuous stream of tasks, so it needed a visual board, limits on work in progress and steady flow rather than fixed sprints.
Full Scrum cycle for software teams: sprint planning, backlog refinement, reviews, retrospectives and Scrum of Scrums. Kanban with WIP limits for production teams. Velocity and sprint-goal completion reported through Jira and Confluence dashboards.
Introduced Kanban workflows with WIP limits in production teams and helped move creative production from waterfall to sprint-based planning.
People: led five project coordinators and mentored them into independent delivery roles. Product owners and clients: backlog grooming, user story mapping, sprint goals and UAT coordination.
Better flow and more predictable delivery in production teams, and five coordinators running delivery independently. Recognised with the Outstanding Achievement Award (2019).
A delivery method works when it fits the work, and when the team can run it without you.