Imparting right scrum knowledge and skills to Project teams & Support to implement the concepts

Coaching & Support for Scrum teams

Objective

  • Impart the right scrum knowledge to the team as defined in the Scrum Guide by Ken Schwaber & Jeff Suherland, the founders of Scrum

  • Introduce the teams to other agile best practices which can be used effectively by Scrum teams

  • Support the team during;

      • Sprint readiness (before the first sprint) - User story readiness, team readiness

      • First sprint planning meeting

      • First day of sprint#1 (Daily scrum), Updation of burndown charts

      • Sprint review meeting of Sprint#1

      • Sprint retrospective meeting of Sprint#1

      • Velocity calculations

      • Sprint planning meeting of Sprint#2

1. Scrum team coaching

  1. Introduction

  • Understand the agile ecosystem

  • Agile family of frameworks

  • Origins of agile

  • Agile manifesto

  • Agile principles

  • Self-organizing teams

  • Assessment

  • Q&A

  1. Get an overall view of the scrum framework

  • A bird’s eye view of the scrum framework

  • Uses of scrum

  • Scrum theory

  • Scrum values

  • Assessment

  • Q&A

  1. Understand the roles within scrum and their responsibilities to other stakeholders

  • Roles and responsibilities of the product owner

  • Roles and responsibilities of the development team

  • Roles and responsibilities of the scrum master

  • Assessment

  • Q&A

  1. Get an in depth understanding of scrum events

  • Sprint planning

  • Daily scrum

  • Sprint review

  • Sprint retrospective

  • Assessment

  • Q&A

  1. Get an in depth understanding of the scrum artefacts

  • Product backlog

  • Sprint backlog

  • Increment

  • Definition of done

  • Assessment

  • Q&A

  1. Fitment of other agile best practices into scrum

  • Epics

  • User stories

  • Story point estimation (sizing) using poker

  • Tracking boards

  • Burn down charts

  • Release planning

  • Velocity calculation

  • Average velocity

  • Assessment

  • Q&A

  1. Tailoring scrum

  • For highly dynamic projects

  • Q&A

  1. Scaling scrum

  • Challenges of distributed development

  • Tool usage

  • Symptoms of good and bad implementations

  • Q&A


It will better to limit the number of participants to less than 15 for better effectiveness. The training and support will be done remotely (online) or onsite.

Duration of the traing - 14 hours


Request for a meeting



2. Scrum team support

Post training, we support the team prior to and during the first sprint by;

      • Checking the Sprint readiness (before the first sprint) - User story readiness, team readiness, tool readiness

      • Facilitating the first sprint planning meeting

      • Facilitating the first day of sprint#1 (Daily scrum), Updation of burndown charts

      • Facilitating Sprint review meeting of Sprint#1

      • Facilitating Sprint retrospective meeting of Sprint#1

      • Helping the scrum master with Velocity calculations

      • Observing Sprint planning meeting of Sprint#2