This curriculum spans the design and operation of cross-functional agile teams with the granularity of a multi-workshop organizational rollout, addressing coordination challenges seen in enterprise agile transformations, governance integration, and sustained change management across product, engineering, and non-technical functions.
Module 1: Defining Team Structure and Role Clarity
- Selecting between T-shaped skill alignment and dedicated functional roles based on project velocity and domain complexity.
- Mapping RACI matrices across product, engineering, design, and QA to resolve overlapping ownership in backlog refinement.
- Deciding on embedded versus shared specialists (e.g., UX researcher) based on sprint dependency frequency.
- Establishing escalation paths when functional managers and product owners disagree on resource allocation.
- Documenting role expectations for non-traditional contributors such as compliance officers in regulated sprints.
- Adjusting team size during scaling events (e.g., SAFe ART integration) without violating Scrum’s 3–9 person guideline.
Module 2: Integrating Agile Frameworks Across Functions
- Aligning sprint cycles between product teams using Scrum and operations teams using Kanban.
- Configuring PI planning events to include marketing and customer support with limited agile exposure.
- Resolving mismatched cadences when finance teams operate on monthly cycles and dev teams on two-week sprints.
- Choosing between Nexus and LeSS frameworks when integrating three or more cross-functional squads.
- Customizing Jira workflows to reflect legal review gates without creating bottlenecks in deployment pipelines.
- Implementing definition of done (DoD) criteria that include non-engineering deliverables such as training documentation.
Module 3: Communication Protocols and Collaboration Tools
- Selecting collaboration platforms (e.g., Microsoft Teams vs. Slack) based on enterprise security policies and integration needs.
- Setting up automated notifications for backlog changes without overwhelming non-technical stakeholders.
- Establishing meeting hygiene rules for stand-ups involving remote team members across four time zones.
- Creating shared documentation repositories with version control accessible to legal, product, and engineering.
- Defining escalation SLAs for production incidents involving multiple functional teams.
- Implementing asynchronous decision logs to reduce dependency on real-time meetings for global teams.
Module 4: Conflict Resolution and Decision-Making Authority
- Applying consent-based decision-making (sociocracy) when product and engineering disagree on scope reduction.
- Mediating disputes over technical debt allocation between delivery leads and product managers.
- Designing escalation protocols for cases where UX design is blocked by backend API delays.
- Facilitating trade-off discussions when QA capacity limits release frequency despite dev team output.
- Documenting and socializing final decisions after cross-functional disagreements to prevent re-litigation.
- Assigning decision rights for go/no-go release calls involving compliance, security, and product.
Module 5: Performance Measurement and Accountability
- Defining shared KPIs (e.g., time-to-market) that hold product, engineering, and operations jointly accountable.
- Tracking cycle time across functional handoffs to identify bottlenecks in the value stream.
- Adjusting individual performance reviews to reflect team-based agile outcomes without diluting accountability.
- Using outcome-based metrics (e.g., feature adoption) instead of output metrics (story points) in stakeholder reporting.
- Implementing team health checks that include psychological safety and cross-functional trust indicators.
- Aligning bonus structures with cross-team objectives without creating perverse incentives.
Module 6: Governance and Compliance Integration
- Embedding regulatory checkpoints (e.g., SOX, HIPAA) into sprint planning without disrupting flow.
- Documenting audit trails for user story changes involving legal or compliance input.
- Coordinating with internal audit teams to validate agile artifacts as evidence for control frameworks.
- Managing change advisory board (CAB) approvals in high-velocity environments with weekly releases.
- Ensuring data privacy requirements are translated into actionable acceptance criteria for developers.
- Creating compliance playbooks for common scenarios (e.g., data subject access requests) integrated into backlog.
Module 7: Scaling and Organizational Change Management
- Rolling out agile practices to legacy departments (e.g., finance, legal) with process-heavy cultures.
- Managing resistance from functional leaders losing direct control over team members in matrix structures.
- Designing communities of practice to maintain technical standards across decentralized teams.
- Transitioning from project-based funding to product team funding models aligned with agile cadences.
- Integrating vendor teams into cross-functional squads while maintaining IP and security controls.
- Conducting retrospective-based interventions when team performance degrades after organizational restructuring.
Module 8: Continuous Improvement and Feedback Loops
- Facilitating cross-functional retrospectives that produce actionable improvements across team boundaries.
- Implementing customer feedback loops into sprint planning for non-customer-facing teams (e.g., platform).
- Using value stream mapping to identify and eliminate handoff delays between functions.
- Rotating team members across functions (e.g., dev to support) to build empathy and reduce silos.
- Integrating production incident root cause analysis into backlog refinement for systemic fixes.
- Adjusting team composition quarterly based on retrospective outcomes and skill gap analysis.
