Professional Diploma in Agile Software Development: Mastering Scrum for Modern Teams

The T Agile Software Development: Mastering Scrum for Modern Teams course offered by Geneve Institute of Business Management offers a concentrated, practice-oriented programme that equips participants with the mindset, rituals and structural choices required to run productive Scrum teams. Over ten instructional units the syllabus lays out the Scrum framework, role responsibilities, backlog stewardship, sprint orchestration, scaling patterns and the organisational practices that sustain continuous delivery. Instruction focuses on clear, pragmatic guidance—how to form effective teams, craft valuable increments, measure progress with meaningful indicators, and evolve processes to reduce waste. Participants leave prepared to set up, coach, or improve Scrum implementations aligned with product goals and organisational constraints.

Target group

• Product owners and product managers responsible for defining priorities, maximizing value, and stewarding the backlog.

• Scrum masters and team facilitators aiming to guide ceremonies, remove impediments, and foster continuous improvement.

• Engineering managers and technical leads who coordinate capacity, technical debt reduction, and cross-team dependencies.

• Delivery managers and program leads tasked with aligning multiple teams, cadence and release planning across initiatives.

• Business stakeholders and domain experts seeking to collaborate effectively with delivery teams and sharpen acceptance criteria.

• Quality assurance leads and test engineers integrating quality practices into incremental delivery and sprint workflows.

Objectives

• Explain Scrum pillars, events, artefacts and role responsibilities so teams can operate with shared clarity.

• Run effective backlog refinement, prioritisation and sprint planning that focus work on highest-value outcomes.

• Facilitate productive sprint ceremonies—standups, reviews, retrospectives—and remove operational impediments.

• Measure delivery health with velocity, flow metrics and outcome-focused indicators rather than vanity counts.

• Design scaling approaches and cross-team coordination patterns that preserve feedback loops and autonomy.

• Embed continuous improvement, technical excellence and product thinking into everyday team routines.

Course Outline

• Scrum Framework Essentials:

  • Origins, core values and the three pillars that uphold effective Scrum practice.

  • Primary roles: responsibilities of product owner, Scrum master and development team.

  • Key artefacts: product backlog, sprint backlog and increment with acceptance expectations.

  • Ceremonies: purpose and structure of planning, daily, review and retrospective.

  Setting Up a Scrum Team:

  • Team composition, cross-functional skills and appropriate team sizing considerations.

  • Defining clear goals, working agreements and role accountability from day one.

  • Onboarding new members and maintaining shared domain knowledge over time.

  • Establishing communication norms, coordination channels and meeting hygiene.

• Product Backlog Stewardship:

  • Writing effective backlog items: clear descriptions, acceptance criteria and traceability.

  • Prioritisation techniques: MoSCoW, WSJF, risk/value and stakeholder alignment.

  • Refinement cadence: decomposing epics into deliverable slices and estimating effort.

  • Managing technical debt and non-functional requirements within backlog planning.

  Sprint Planning and Commitment:

  • Translating product goals into sprint objectives and selecting backlog items accordingly.

  • Capacity assessment, team forecasting and realistic commitment setting.

  • Defining done and exit criteria to avoid ambiguity at sprint closure.

  • Planning for dependencies, shared resources and integration tasks.

• Daily Flow and Task Management:

  • Structuring daily standups for information flow, not status reporting.

  • Visualising work with boards, WIP limits and explicit policies to manage flow.

  • Work splitting strategies and handling interruptions without derailing sprint goals.

  • Maintaining transparent work state, impediment logs and owner assignments.

  Sprint Review and Stakeholder Feedback:

  • Presenting increments focused on value delivered and measurable outcomes.

  • Collecting actionable feedback, validating assumptions and updating priorities.

  • Managing stakeholder expectations and negotiating scope versus schedule.

  • Recording learnings and decisions to inform subsequent planning cycles.

• Retrospective Practices and Continuous Improvement:

  • Structuring retrospectives to surface root causes and concrete improvement experiments.

  • Selecting and tracking improvement actions with ownership and success criteria.

  • Balancing quick wins with longer-term capability building and technical remediation.

  • Creating psychological safety to enable honest reflection and team growth.

  Quality and Engineering Excellence:

  • Integrating testing, code review and automation into the sprint workflow.

  • Establishing definition of done that includes quality gates and non-functional checks.

  • Reducing defects through shift-left practices and incremental validation.

  • Managing build pipelines, test suites and regression strategies for stable delivery.

• Estimation and Predictability:

  • Choosing estimation techniques: story points, t-shirt sizing, and relative forecasting.

  • Using velocity and throughput as planning tools with awareness of variability.

  • Handling uncertainty with spikes, prototypes and time-boxed exploration.

  • Communicating delivery forecasts and confidence intervals to stakeholders.

  Risk Management and Dependency Handling:

  • Identifying technical, organisational and external risks early in planning cycles.

  • Creating mitigation plans, contingency items and fallback options within sprints.

  • Coordinating cross-team dependencies via synchronization points and shared cadences.

  • Escalation paths and rapid decision protocols to unblock critical impediments.

• Scaling Scrum and Cross-Team Coordination:

  • Principles for scaling: alignment, autonomy, modularity and minimizing coordination tax.

  • Multi-team patterns: tribes, squads, value streams and feature teams trade-offs.

  • Integration cadence: release trains, shared backlogs and synchronized planning sessions.

  • Governance approaches that balance standardization with team-level flexibility.

  Portfolio and Release Management:

  • Aligning product strategy with program increments and release windows.

  • Roadmapping techniques that allow iterative delivery and market feedback loops.

  • Release readiness checklists, cutover plans and stakeholder communications.

  • Measuring release success through adoption, performance and business metrics.

• Metrics, Reporting and Outcome Focus:

  • Selecting metrics that reflect outcomes: cycle time, lead time and customer value.

  • Visualising flow metrics and using them to guide improvement experiments.

  • Avoiding anti-patterns: misuse of velocity and incentives that distort behaviour.

  • Building reporting that supports decisions without micromanaging teams.

  Product Discovery and Lean Practices:

  • Continuous discovery techniques for validating hypotheses before committing build effort.

  • Experimentation pipelines: A/B tests, prototypes and gated rollouts to learn quickly.

  • Incorporating user research, analytics and feedback into backlog prioritisation.

  • Reducing waste by aligning teams to validated customer problems and desired outcomes.

• Coaching, Facilitation and Conflict Resolution:

  • Active facilitation techniques to surface contribution and keep meetings productive.

  • Coaching teams through norms, accountability and evolving maturity levels.

  • Conflict resolution patterns that preserve trust and focus on shared goals.

  • Developing servant-leadership behaviours that enable team autonomy and ownership.

  Organisational Change and Adoption:

  • Phasing Scrum adoption, pilot teams and measures for incremental roll-out.

  • Addressing cultural barriers, legacy processes and stakeholder resistance.

  • Building capability through training, mentorship and role-specific coaching.

  • Monitoring adoption health and iterating the transformation approach.

• Tools and Automation for Effective Delivery:

  • Choosing tooling that supports backlog management, CI/CD and traceability needs.

  • Automating routine checks: linting, builds, tests and deployment gates.

  • Integrating toolchains to reduce manual handoffs and streamline feedback loops.

  • Safeguarding data and access controls within tooling ecosystems.

  Legal, Compliance and Contractual Considerations:

  • Embedding compliance activities into delivery cycles without becoming bottlenecks.

  • Contract models and their impact on sprint cadence and scope flexibility.

  • Managing third-party vendor deliverables and change controls in agile contexts.

  • Audit trails, documentation and evidence collection aligned with regulatory needs.

• Sustaining Momentum and Long-Term Improvement:

  • Establishing cadence for capability reviews, community of practice and knowledge sharing.

  • Funding technical improvements, refactors and infrastructure work through explicit backlog items.

  • Rotations and role diversification to reduce single points of expertise.

  • Celebrating outcomes, learning from failures and institutionalising improvements.

  Advanced Topics and Contemporary Trends:

  • Hybrid models combining Scrum with Kanban, Scrumban and flow-based practices.

  • Impact of remote and distributed teams on ceremony design and engagement.

  • Evolving patterns for product-centric organisations and outcome-based roadmaps.

  • Emerging tools and practices that reshape team collaboration and delivery.