Description
Managing Projects in Agile with Scrum
Agile is a Project Management framework that is used as a means for managing change. Agile employs an iterative and incremental approach to all projects that reaps rewards with better quality products and a quicker time to market. Agile empowers your teams to work in a self-organised way using all the planning tools that Agile provides.
This two-day course gives delegates a complete introduction to Agile using practical exercises that demonstrate the skills required to manage an Agile project. While the course gives an overview of Scrum, the emphasis of the course is on practical applications of Scrum in a business context including project (release) planning.
Target Audience
The intended audience for this course is anyone interested in working in an Agile environment. Potentially working as a Product Owner or Scrum Master or Team members – this could be Project Managers, Team Leaders, Development Managers, Testers, Developers, Business Analysts etc.
Prerequisites
Delegates should have experience of working in a project team, whether or not an Agile approach was used.
Pre-Course Reading
Delegates should be familiar with the content and rationale for the rules of Scrum in the Scrum Guide, available at www.scrumguides.org
Benefits to the Delegates
This course enables the delegates to understand what the roles are in Agile, the planning and feedback that assists the Development Team to realise the project goals. It also looks at how an Agile project is managed and how an Agile team interfaces with other project and business roles.
Outline
Agile History and Background
- Scrum origins and the Agile Manifesto
- The 4 values and 12 principles of Agile
Why Agile
- Environments that are best suited to an Agile approach
- Benefits of Agile
- Project constraints in traditional projects versus Agile projects
- Empirical process and how this approach is used to develop a product iteratively and incrementally
- MoSCow Prioritisation and the ‘Iron Triangle’ of Time, Cost, Features (and Quality) and how we use this technique for planning and estimating.
SCRUM FRAMEWORK
Roles
- Product Owner – representing the voice of the customer and responsible for return on investment
- Scrum Master – responsible for facilitating and coaching the Scrum Team
- Development Team – self-managing and cross-functional and responsible for delivering ‘Done’ work during the sprint
Artefacts
- Product backlog – aprioritised list of requirements in the form of User Stories
- Sprint backlog – alist of tasks that the team will deliver during the sprint
- Sprint Burndown – charts tracking progress during the project or sprint
Events
- Release Planning – howto create a high-level plan to determine if the project is feasible and can be implemented using the Agile approach
- Sprint Planning – toplan what will be delivered during the sprint
- Sprint – aperiod from 1 week to 1 month during which the team produce a potentially shippable product
- Daily Scrum – a15-minute daily meeting for the development team
- Sprint Review – heldat the end of the sprint to show the business what has been achieved
- Sprint Retrospective – heldat the end of the sprint for the team to assess the work carried out, with a view for continuous improvement
Release Planning Exercise
- The delegates will create a product backlog of high-level features. They will then prioritise and estimate the backlog and create a Release Plan that can be used to set the project timeframe, resource costs and major deliverables.
Enterprise Scrum
- An introduction to scaling Scrum for use in large organisations
