A tailored course, built for your situation
Pragmatic Agile-at-Scale Implementation for Public-Sector Programs
A structured, implementation-grade path to scaling agile practices across complex public-sector environments
The situation this course is for
Public-sector initiatives face unique pressures: layered governance, fixed budgets, and accountability to diverse stakeholders. Traditional agile training rarely addresses how to maintain agility without violating compliance or procurement rules. Teams end up either rigidly waterfall or chaotically 'agile', neither of which delivers on time or within scope.
Who this is for
Business and technology professionals in public-sector or public-facing programs who lead or influence delivery at scale, program managers, delivery leads, product owners, and IT directors working across multiple teams and compliance boundaries.
Who this is not for
Individual contributors focused only on team-level Scrum, or professionals working exclusively in unregulated, private-sector startups with no governance overhead.
What you walk away with
- Apply agile frameworks that comply with public-sector procurement and audit requirements
- Coordinate backlogs across 5+ interdependent teams without central bottlenecks
- Design governance checkpoints that enable speed instead of slowing it down
- Facilitate stakeholder alignment across political, technical, and operational domains
- Deploy a repeatable playbook for agile-at-scale rollout in regulated environments
The 12 modules (with all 144 chapters)
- Defining agile at scale in public-sector contexts
- Balancing speed with transparency and oversight
- Mapping agile workflows to procurement cycles
- Regulatory touchpoints in iterative delivery
- Risk-based sprint planning
- Stakeholder communication cadence design
- Documentation that supports agility
- Version control for policy and process
- Audit readiness in continuous delivery
- Change management within fixed budgets
- Cross-department alignment models
- Scaling readiness self-assessment
- Team topology design for public programs
- Defining interface contracts between teams
- Shared backlog prioritization techniques
- Synchronizing sprint cycles across units
- Dependency mapping and resolution
- Cross-team refinement sessions
- Scaling Scrum-of-Scrums effectively
- Managing handoffs with minimal latency
- Conflict resolution in distributed backlogs
- Common metrics without micromanagement
- Tooling integration across platforms
- Scaling coordination without bureaucracy
- Integrating regulatory checks into sprint zero
- Privacy-by-design in user story formulation
- Security acceptance criteria templates
- Policy compliance as a Definition of Done
- Handling classified or sensitive data in sprints
- Audit trail generation per iteration
- Third-party vendor sprint inclusion
- Ethics review integration points
- Accessibility compliance in agile workflows
- Public consultation cycles and sprints
- Handling legislative changes mid-backlog
- Compliance debt tracking and resolution
- Strategic theme definition for public missions
- Backlog slicing across policy objectives
- Funding cycle alignment with release planning
- Prioritization using public value scoring
- Managing political vs. technical dependencies
- Balancing maintenance and innovation work
- Scenario planning for budget volatility
- Backlog transparency for oversight bodies
- Multi-year roadmap visualization
- Stakeholder-driven backlog grooming
- Managing sunset initiatives alongside new ones
- Portfolio-level Definition of Ready
- Identifying power and influence stakeholders
- Designing feedback loops for non-technical users
- Translating agile progress for executive briefings
- Citizen co-design in sprint reviews
- Managing media and public expectations
- Oversight committee reporting cadence
- Handling stakeholder churn during elections
- Facilitating inter-agency consensus
- Conflict mediation between stakeholder groups
- Public demo planning and risk mitigation
- Feedback integration without scope creep
- Engagement maturity self-assessment
- Reframing governance as a service
- Lightweight approval workflows for sprints
- Fast-track pathways for urgent initiatives
- Escalation protocols for blocked teams
- Decision logging for transparency
- Empowering teams within guardrails
- Governance dashboard design
- Balancing autonomy and accountability
- Handling exceptions without precedent
- Audit preparation as a continuous activity
- Governance role definitions at scale
- Review cycle optimization
- Zero-based budgeting for agile portfolios
- Staffing models for cross-functional teams
- Contracting for outcomes vs. outputs
- Managing union or HR constraints in agile roles
- Blended FTE and contractor team design
- Capacity planning across shifting priorities
- Carry-forward budget rules and agile pacing
- Resource leveling across programs
- Cost transparency dashboards
- Funding reallocation protocols
- Managing vacancies in agile teams
- Budget storytelling for non-technical leaders
- Assessing agile readiness across departments
- Identifying early adopters and influencers
- Pilot program design and measurement
- Communicating change without jargon
- Training pathways for different roles
- Managing fear of obsolescence
- Celebrating small wins publicly
- Feedback mechanisms for continuous adjustment
- Scaling success stories across units
- Addressing union or HR policy concerns
- Sustaining momentum beyond launch
- Change saturation monitoring
- Selecting outcome-based KPIs
- Balancing velocity with public value
- Translating sprint metrics for executives
- Avoiding metric gaming in public programs
- Public reporting of agile progress
- Burn-down charts with compliance overlays
- Lead time and cycle time in regulated flows
- Team health metrics in government settings
- Benchmarking against peer agencies
- Data integrity in distributed tracking
- Visualizing progress for non-technical audiences
- Metrics review and refinement cycles
- Evaluating Jira, Azure DevOps, and open-source options
- Configuring workflows for auditability
- Integrating with legacy case management systems
- Single sign-on and access control setup
- Cross-tool reporting and dashboards
- Data export for public transparency requests
- Managing tool sprawl across teams
- Training teams on shared tool conventions
- Backup and disaster recovery for agile data
- Vendor lock-in risk mitigation
- API strategies for system integration
- Tooling cost-benefit analysis
- Time-zone-aware sprint planning
- Asynchronous refinement techniques
- Cultural considerations in team interactions
- Localizing user stories for regional needs
- Central vs. decentralized backlog ownership
- Managing language and translation challenges
- Remote-first ceremony design
- Building trust without in-person meetings
- Holiday and local event awareness
- Security implications of remote work
- Collaboration tool standards across locations
- Distributed team onboarding
- Conducting agile maturity assessments
- Refresh cycles for frameworks and tools
- Handling leadership transitions
- Updating policies to reflect agile norms
- Scaling lessons learned across agencies
- Preventing burnout in high-pressure programs
- Rotating roles to build resilience
- Continuous feedback loop design
- Adapting to new regulations and technologies
- Building internal agile coaching capacity
- Knowledge transfer between teams
- Creating a legacy of adaptive delivery
How this maps to your situation
- You're launching a multi-agency digital transformation
- You're managing a program with overlapping compliance requirements
- You're introducing agile to a traditionally waterfall organization
- You're accountable for delivery across geographically dispersed teams
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 60-70 hours of total engagement, designed for completion over 8-12 weeks with flexible pacing.
How this compares to the alternatives
Unlike generic agile certifications or vendor-specific training, this course provides a public-sector-specific, implementation-grade curriculum that bridges policy, technology, and delivery, without requiring live sessions or video content.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.