Professional Diploma in Agile Software Development: Mastering Scrum for High-Performance Teams

The Agile Software Development: Mastering Scrum for High-Performance Teams course offered by Geneve Institute of Business Management presents a compact, practice-oriented programme that concentrates on the mechanics, discipline and leadership behaviours required to run Scrum effectively in real organisations. Over ten instructional units participants gain a clear mental model of Scrum’s pillars and events, learn how to structure teams for continuous delivery, and acquire practical habits for backlog management, forecasting and quality assurance. The syllabus emphasises decision-focused learning: when to apply specific patterns, how to measure outcomes, and how to align delivery cadence with stakeholder expectations so teams become predictable, adaptable and capable of sustaining higher throughput without sacrificing quality.

Target group

• Scrum Masters and delivery leads aiming to raise team throughput while preserving sustainable pace and quality.

• Product owners and product managers responsible for backlog clarity, stakeholder alignment and value prioritisation.

• Engineering managers and tech leads designing team structures, interfaces and delivery contracts across squads.

• Project managers and programme coordinators transitioning from plan-driven approaches to iterative, value-driven delivery.

• Quality assurance leads and test managers integrating continuous quality into sprint workflows and release gates.

• Business stakeholders and change agents who need to evaluate delivery performance and support organisational agility.

Objectives

• Explain Scrum principles, roles, ceremonies and artefacts so teams can adopt consistent delivery rhythms.

• Structure product backlogs, write effective user stories and apply prioritisation techniques that maximise stakeholder value.

• Facilitate planning, review and retrospective events to produce realistic forecasts and continuous improvement actions.

• Design team composition, definition of done, and workflow policies that reduce handoffs and increase ownership.

• Implement metrics and inspections—velocity, cycle time, WIP limits and quality signals—to guide evidence-based decisions.

• Establish release and scaling strategies that preserve incremental delivery while managing architectural and organisational constraints.

Course Outline

• Scrum Foundations and Mindset:

  • Origins of Scrum, empirical process control and the inspect-and-adapt cycle.

  • Scrum roles: responsibilities of Product Owner, Scrum Master and Development Team.

  • The three pillars: transparency, inspection and adaptation and their practical implications.

  • Values and behaviours that support collaboration, focus and respectful accountability.

  Product Backlog Crafting:

  • Writing clear product backlog items: outcomes, acceptance criteria and testable statements.

  • Prioritisation techniques: MoSCoW, WSJF, cost of delay and stakeholder mapping.

  • Backlog refinement cadence, size limits and maintaining backlog health.

  • Managing dependencies, non-functional requirements and technical debt within the backlog.

• Sprint Planning and Forecasting:

  • Breaking work into sprint-sized increments and selecting a realistic sprint scope.

  • Capacity calculation, team availability and balancing new work with maintenance.

  • Sprint goal formulation and aligning scope to a single coherent objective.

  • Commitment versus forecast mindset and communicating uncertainty effectively.

  Daily Scrum and Team Flow:

  • Purpose of the Daily Scrum and structuring brief, value-focused stand-ups.

  • Visualising flow: boards, WIP limits and identifying blockers quickly.

  • Team cadence, focus windows and protecting the sprint goal from interruptions.

  • Escalation paths, impediment removal and empowering teams to resolve constraints.

• Sprint Review and Value Delivery:

  • Preparing tangible increments for review and demonstrating verified outcomes.

  • Engaging stakeholders to gather feedback and adapt priorities promptly.

  • Acceptance criteria, demo discipline and collecting usable insights from reviews.

  • Using review outcomes to inform roadmap adjustments and release decisions.

  Sprint Retrospective and Continuous Improvement:

  • Structuring retrospectives: gather data, generate insights, decide on actionable experiments.

  • Lightweight improvement experiments, hypothesis-driven changes and measuring impact.

  • Creating psychological safety to surface real issues and experiment openly.

  • Tracking improvements over time and integrating successful changes into team norms.

• Definition of Done and Quality Practices:

  • Creating a shared, explicit Definition of Done that covers testing and non-functional checks.

  • Continuous integration, automated testing and build hygiene as part of the sprint.

  • Acceptance criteria, QA-in-sprint practices and pairing to reduce defects.

  • Managing technical debt: visibility, prioritisation and preventing quality erosion.

  Backlog Estimation and Sizing Techniques:

  • Relative estimation: story points, affinity mapping and calibration across teams.

  • Estimating uncertainty: risk buffers, confidence bands and probabilistic forecasting.

  • Breaking large items into smaller, deliverable slices to reduce risk.

  • Using historical velocity and cycle time to improve future forecasts.

• Release Planning and Incremental Delivery:

  • Release strategies: feature toggles, phased rollouts and incremental value delivery.

  • Aligning release cadence with business rhythm and regulatory constraints.

  • Minimum viable increments and defining release readiness criteria.

  • Rollback, mitigation and post-release monitoring to reduce customer impact.

  Scaling Scrum Within Organisations:

  • Patterns for coordinating multiple teams: alignment, dependencies and cross-team cadence.

  • Lightweight coordination constructs: communities of practice, syncs and cross-team backlog grooming.

  • Choosing a scaling approach that fits organisational context and domain boundaries.

  • Balancing autonomy with predictable delivery through standard interfaces and APIs.

• Metrics and Evidence-Based Management:

  • Selecting meaningful metrics: lead time, cycle time, throughput and quality indicators.

  • Avoiding metric gaming and combining quantitative signals with qualitative feedback.

  • Using metrics to detect trends, plan capacity and justify investments.

  • Reporting formats that help stakeholders make pragmatic trade-offs.

  Managing Risk and Technical Constraints:

  • Identifying architectural and operational risks early and making them visible in the backlog.

  • Mitigation strategies: spikes, prototyping and incremental architecture validation.

  • Policies for branching, release windows and emergency fixes that limit disruption.

  • Coordinating cross-cutting concerns like security, compliance and performance within sprints.

• Leadership and Servant-Mastery:

  • Scrum Master behaviours that enable teams: coaching, facilitation and organisational influence.

  • Product leadership: stakeholder negotiation, outcome focus and roadmap stewardship.

  • Building trust, mentoring and fostering continuous learning cultures.

  • Conflict resolution models and effective decision facilitation techniques.

  Coaching Teams Toward High Performance:

  • Assessing team health and interventions to unblock flow and capability gaps.

  • Designing learning paths, pairing and rotating responsibilities to build redundancy.

  • Conducting effective feedback cycles and embedding improvement routines.

  • Scaling coaching efforts through lightweight frameworks and trained internal coaches.

• Tools and Automation for Agile Delivery:

  • Selecting and configuring boards, filters and workflows to reflect team process.

  • Automating pipelines: CI, automated checks and deployment gating aligned with sprints.

  • Integrating tools for visibility: dashboards, alerts and release tracking.

  • Maintaining tool hygiene, data governance and permissions as teams grow.

  Contracts, Budgeting and Procurement in Agile:

  • Agile-friendly contracting models: outcome-based, time-and-material with clear collaboration clauses.

  • Iterative budgeting and forecasting aligned with incremental delivery milestones.

  • Vendor collaboration patterns that preserve agility and delivery cadence.

  • Procuring services with acceptance criteria, SLAs and shared accountability.

• Organisational Change and Adoption Strategy:

  • Rolling out Scrum across teams: pilot selection, sponsorship and measurable success criteria.

  • Addressing cultural friction points and aligning HR and performance systems to new ways.

  • Communications, training pathways and leadership involvement to sustain adoption.

  • Institutionalising retrospection and celebrating iterative wins to reinforce behaviour change.

  Legal, Compliance and Governance Considerations:

  • Mapping regulatory requirements into backlog items and definition of done checks.

  • Audit trails, traceability and documentation practices compatible with iterative delivery.

  • Data governance, privacy and retention integrated into sprint workflows.

  • Governance thresholds for cross-team decisions and escalation paths for critical issues.

• Continuous Improvement at Scale:

  • Scaling retrospectives, improvement backlogs and cross-team experiments for systemic change.

  • Feedback loops between product, engineering and operations to reduce lead time.

  • Institutional mechanisms to capture lessons learned and propagate effective patterns.

  • Measuring cultural change and adapting organisational levers to embed agility.

  Career Paths and Professional Development:

  • Roles enabled: Scrum Master, Product Owner, Agile Coach, and Delivery Lead.

  • Developing credentials, mentoring paths and evidence-based portfolios of improvements.

  • Building communities of practice and sustaining knowledge flows across the organisation.

  • Roadmaps for progressing from team-level to organisational agile leadership.