This one-day course takes participants into the fundamental principles and practices of Agile software development. We start with an introduction to Agile software development by discussing its origin and the Agile Manifesto. We then explore workflows, roles and artefacts of Agile teams. Finally, we bring this all together at the end of the day by discussing how we put this all together. Exercises and discussions are liberally scattered around these different sections to encourage deeper understanding.
Through this course, participants will gain practical experience working with Agile approaches and practices. The course is structured around the Scrum framework and participants will learn how to get the most out of using this approach.
The Scrum for Teams course meets the Scrum Foundations Learning Objectives published by the Scrum Alliance in February 2017 and this the first foundations course in Australia to be approved by the Scrum Alliance.
Morning – work through the Scrum Framework.
• Starting with Product Owners setting a vision we then create a backlog with the team before developing the first product increment.
• We cover the roles, events and artefacts of Scrum through the morning.
Afternoon – principles and Sprint 2
• Work through why Scrum works, the principles and values.
• Do some inspecting and adapting exercises.
• Finish the day with a second Sprint of our product. (edited)
• A brief review of the origins of Scrum and how the Agile manifesto came to be. What is in the Manifesto and what that means for developing products. Some of the underlying principles that make Scrum work.
• Principles of Scrum delivery. The key principles of Scrum delivery including inspection and adaption, transparency and always delivering value to the business.
• How work flows in Scrum teams. Most teams are familiar with their traditional workflows and the introduction of a different approach to delivering products can lead to confusion and uncertainty. We discuss how work flows within a Scrum team to help participants understand the wider context of delivering products.
• Roles in Scrum teams. We explore how do roles and responsibilities change with Agile software development. What are the roles found in an Agile team and how do they coordinate to effectively deliver a product.
• What are some of the artefacts we use in Scrum.
• How to put it all together and deliver something. The big picture of how Scrum teams work so that participants can understand the products are delivered. This brings together all everything discussed during the day.