Introduction to Scrum training course is a one-day workshop which helps anyone understand how Scrum works.
The active, workshop-style approach ensures everyone participates and so that they explore the opportunity to improve ways of working for themselves and their team.
Consequently, delegates leave the course more confident in five key areas:
- The intention behind agile and Scrum practices.
- Scrum roles and interactions.
- Scrum events, artefacts and tools.
- Managing and refining a product backlog with user stories.
- Putting Scrum into action.
For a private, on-site course for your team get in touch now!
The Introduction to Scrum training course takes the scrum framework apart, hence allows delegates to examine each role, event and artefact and then put it back together as a practical product delivery tool. Delegates use this case study to explore backlog refinement, estimation, value, planning, forecasting and agile retrospectives.
Scrum is a framework for delivering software products in an agile way, therefore we begin by understanding the benefits agility can bring to an organisation. Building software products is a complex problem with a large number of variables and Scrum is designed to manage effectively this type of work, which is described at a high level.
The intent of Scrum is not to deliver a project on-time and on-budget, but to maximise the business value and outcomes for a software product. We discuss the implications of this, therefore the differences between Scrum and plan-driven project management techniques.
Introduction to Scrum Roles
Especially relevant are the three Scrum roles and how they bring simplicity of decision-making through clear accountabilities:
- Product Owner: Maximising the value of the product
- Development Team: Delivering a high-quality product
- Scrum Master: Maximising the organisation’s ability to deliver
A product is introduced including artefacts such as a business scenario, a product vision, and an initial backlog of features. As a result, delegates form into teams to turn the product backlog into a delivery plan, taking on Scrum roles they have just learned.
Introduction to Scrum Artefacts
The three core Scrum artefacts are introduced as the expression of requirements at different points in time:
- Product backlog: requirements to be delivered.
- Sprint Backlog: the current, active working plan.
- Increment: the current state of the product, representing the progress made so far.
Delegates explore the wide range of techniques available to manage this information and take part in practical exercises to explore, such as:
- User stories.
- Estimating software development with story points.
- Value and return on investment.
- Sprint planning.
- Acceptance criteria with behaviour driven development (BDD).
- Sprint burn-down charts for tracking progress within a single sprint.
- Product burn-up charts for tracking progress over multiple sprints.
- Release forecasting.
Introduction to Scrum Events
Given that Scrum seeks to maximise the value delivered to the business rather than stick to the plan, we need opportunities to inspect and adapt the plan and the process. Delegates are also able to experience the intent of the events as a means of:
- Creating an effective tactical plan: sprint planning.
- Maximising productivity over a single day: daily scrum.
- Creating a culture of continuous improvement and whole-team accountability: sprint retrospective.
- Capitalising on strategic information and new opportunities while collaborating with stakeholders to adjust long-term plans: sprint review.
Scrum as a delivery tool
Most of all, we show how Scrum is a tool to help organisations deliver better products. Therefore, we discus the fact that Scrum has rules, and how to use these effectively rather than dogmatically. Delegates also gain practical experience in all of the Scrum elements, and a shared understanding of the intent underlying this technique.