To successfully transition a diverse group—including both project-focused and operational departments—into Agile and Scrum, the approach must emphasize mindset, adaptability, and practical application tailored to each department’s context.
Start with shared understanding: All participants, regardless of background, should learn the Agile mindset—valuing collaboration, adaptability, and continuous improvement over rigid processes.
Pilot teams and coaching: Launch Agile with pilot teams that include members from different departments. Provide coaching and support, especially early on, to help teams internalize Scrum practices and adapt them to their work.
Customize ceremonies and artifacts: Scrum ceremonies (like daily stand-ups, sprint planning, reviews, and retrospectives) and artifacts (like backlogs) should be adapted to fit both project and operational workflows.
Foster cross-functional collaboration: Encourage departments to break silos, share knowledge, and focus on delivering value together, not just completing tasks.
Embrace change: Agile thrives on responding to change rather than resisting it.
Respect and collaboration: Value every team member’s input, foster psychological safety, and work as a unified team.
Continuous learning: Treat every sprint as an opportunity to improve, experiment, and adapt.
Customer focus: Prioritize delivering value to internal or external customers, not just meeting internal metrics.
Below are examples of how each department can practice Scrum, with both project and operational work in mind:
Project Management Office - Facilitate Scrum training, coach teams, and help set up sprint cycles for both projects and recurring improvement initiatives.
Design & Engineering - Use sprints to deliver design packages or engineering solutions incrementally, review progress in sprint reviews.
Legal - Break large legal assignments (e.g., contract reviews) into sprint-sized tasks, review deliverables, and adapt priorities.
Finance - Organize cyclical financial tasks (monthly closings, audits) into sprints; use backlogs for ad hoc requests.
Government Relations & Docs - Manage permitting or compliance deliverables in sprints, with backlog items for each required document or stakeholder meeting.
Power - Plan and execute maintenance or installation projects in sprints; review outcomes and adapt schedules as needed.
Commercial - Use sprints to launch new offers or campaigns, review sales performance, and refine strategies based on feedback.
HR & Admin - Run recruitment drives or policy updates in sprints, using retrospectives to improve onboarding or admin processes.
Procurement & Supply Chain - Manage procurement cycles or supplier onboarding in sprints, track progress via Scrum boards, and adapt based on feedback.
SAQ & Permitting - Break down site acquisition tasks into sprint backlogs, review completed permits, and adjust for regulatory changes.
Roll-out - Plan deployment phases in sprints, regularly review site progress, and resolve blockers in daily stand-ups.
Transitioning to Agile and Scrum requires everyone—regardless of project or operational focus—to adopt a mindset of collaboration, flexibility, and learning. Each department can tailor Scrum practices to their context, using sprints, backlogs, and regular reviews to improve both project delivery and day-to-day operations.