This course is designed to leave delegates more confident in five key areas:
1. The fundamentals of Scrum theory and principles.
2. The Scrum framework.
3. Cross functional self-organising teams.
4. Generating and refining a product backlog.
5. Putting Scrum into action.
Audience, Pre-requisites and Assumed Knowledge
The Professional Scrum Foundations training course is appropriate for anyone working on or with a Scrum Team. The course is especially well suited to teams and individuals investigating Scrum, those who are currently struggling with Scrum, or those beginning to utilise Scrum in their development environment. Typical attendees include:
- Traditional engineering teams of software engineers, analysts and testers, who are planning to start using Scrum.
- Established Scrum teams that are worried they’re not doing “proper scrum”, or want a refresher on the principles behind what they’re doing.
- Project managers seeking to adapt to agile roles such as scrum master, product owner, or subject matter expert.
- Established or prospective product owners and product managers.
- Stakeholders or users of products who need a good working relationship with agile teams.
The Scrum simulation used throughout the course requires access to computers and the internet. It is not necessary to have any technical skills in order to participate: uncertainty in solving problems is all part of the exercise.
We are a friendly team of practitioners and we like to provide a personal level of support, before, during and after the class:
- Pre-course reading designed to expose questions so that they can be explored in class.
- Contact details allowing delegates to ask questions to the trainer before and after the class.
- Access to a comprehensive set of guidance after the course so that delegates apply what has been learnt.
- Digital course effectiveness surveys with results sent out to delegates and sponsors straight after the class.
Delegates are thrown in at the deep end and asked to produce working software in 30 minutes based on a backlog of requirements. It is often surprising to the delegates how they are able to organise themselves around this challenge. A review is then held to see what progress was made, whether features met expectations, and what should be done next. Incorrect assumptions are quickly identified and adjusted. Finally, a retrospective is held, allowing teams to improve on their process and deal with challenges they experienced; such as poor technical choices or ineffective collaboration.
This case study project is continued with up to four sprints over the two-day class, allowing delegates to learn some theory and then put it straight into practice. As teams learn more about themselves and their product, they are able to adapt their plan to meet changing demand.
The Scrum Framework
Having experienced the considerable uncertainty in the first sprint, delegates explore the uncertainties of complex software product delivery by considering what might change with regards to requirements, technology and people.
Students then dive into the Scrum framework itself:
- Scrum roles: product owner; development team; scrum master.
- Scrum artefacts: product backlog; sprint backlog; increment.
- Scrum events: sprint; sprint planning; daily scrum; sprint review; sprint retrospective.
Delegates then assign themselves roles and conduct a sprint planning session for the next sprint in the simulation.
Scrum is founded on some principles that are the key to moving beyond mechanical scrum where teams focus solely on showing up for a daily meeting and actually take control. We’ll explore the ideas of self-organisation, cross functional teams and cross-functional people and the accountabilities that arise from developers owning their sprint backlog.
Planning, Estimating and Forecasting
Delegates will learn the full set of complementary techniques used by many scrum teams to plan and track progress:
- Story point estimation with planning poker.
- Burn-down charts and velocity.
- Effective use of sprint reviews to keep stakeholders closely involved and informed.
Beginning your Scrum Transformation
The course concludes with practical tips on how to go about kicking off a scrum transformation, including establishing a sense of purpose amongst everyone involved, deciding whether or not Scrum is the right process for the work at hand and finally producing a backlog of things that need to be put in place. This backlog is specific to the attendees and may alternatively serve as an improvement backlog for established teams.
Professional Scrum Foundations Training Course Outcomes
Delegates will leave with a backlog of things they can do as soon as they get back to work. Whether they are planning on forming a new scrum team, or improving their existing process, everyone will leave with something tangible to do.