Acquiring SEUs for CSP – and Agile Workshop Facilitation
13 Apr 2017
Many of our past students express an interest in the Certified Scrum Professional (CSP) qualification, and so recently we sent an email to them all providing further information about requirements – some useful reference information in order to help them acquire those illusive 70 Scrum Education Units (SEUs) and support their CSP application. A copy of the email is shared below. We will follow up this first email, in a series, with supplementary emails with additional advice so do get in touch if you would like to be added to the mailing list (firstname.lastname@example.org). We would also like to recommend one of our upcoming courses which is eligible for Category B SEUs. Our Agile Workshop Facilitation course, taking place on 25-26 April, is one of two Scrum Alliance-approved Advanced Agile courses (the other being the Agile Analysis and Story Writing course) and, our April course coming up will be the last taught by our wonderfully experienced Agile trainer, coach and facilitator, Julia Godwin. We’ve worked with Julia for over 20 years now and she is a passionate Agilist with a wealth of experience. She will be retiring this year and so her course later this month will be her last […]
Scrum is by far the most popular Agile approach. Indeed the terms Scrum and Agile are often used interchangeably and many people are not even aware that there are alternatives to Scrum. Scrum is very simple in its structure and very focused in its scope.
The agil8 Approach
The agil8 approach focuses not only on effective application of Scrum itself, but also integration with essential technical and management practices that it doesn’t cover. These essential technical practices include techniques such as continuous integration, refactoring, test automation and test driven development. Essential management practices include governance, architecture, programme and DevOps portfolio management.
The Scrum Framework
The Scrum framework itself organises work into short iterative Sprint cycles of no more than one month each. Each Sprint should have an agreed Sprint Goal to create an Increment of functionality to production quality, so that it could, if desired, be released.
Scrum Teams are small, cross functional and highly collaborative. The Scrum Framework defines 3 roles which together make up a Scrum Team
- Product Owner
- Development Team members
The Product Owner
The Product Owner works with relevant stakeholders to define the vision for the team, and the Product Backlog of requirements and other work items that will be put to the team. Typically it is a customer or business representative, or a business analyst acting as their proxy.
The Development Team
The Development Team consists of all those people who will do the necessary work to deliver the Product Increment at the end of the Sprint – this includes all necessary activities such as analysis, design build, testing, etc. The ScrumMaster and Product Owner may be Development Team members themselves if they are doing such work as well. The Development Team members determine what work they can do, and how they will do it. They work with the Product Owner to prepare or ‘groom’ the Product Backlog Items that are candidates for each Sprint in advance, and then have a timeboxed Sprint Planning meeting at the start of each Sprint to agree the Sprint Goal and the Sprint Backlog of tasks for the Sprint.
The ScrumMaster facilitates this process, and the other timeboxed Sprint meetings that are part of the Scrum framework. These include:
- a short, daily Scrum Meeting between all Development Team members to synchronise work (the Product Owner may participate in this as well)
- a Sprint Review meeting between the entire Scrum Team and relevant stakeholders at the end of the Sprint, to review the Product Increment and identify candidate Items for inclusion in the next Sprint
- a Sprint Retrospective meeting between Development Team members at the end of the Sprint, to determine what potential improvements to the process will be incorporated into the next Sprint (the Product Owner may participate in this as well)
The ScrumMaster is also responsible for coaching the rest of the Scrum Team in the use of Scrum, encouraging cross-functional collaborative team-working and self-organisation, dealing with impediments to progress that the other members of the Scrum Team cannot deal with themselves and promoting effective use of Scrum across the wider environment.