Date: 9-10 September, 2013
Location: Cluj Napoca, Romania
Regular Price: €973 + VAT
This intermediate level training is recommended for all proﬁles who wish to successfully participate in Scrum agile projects. It provides an in-depth, hands-on introduction to why Scrum works and how to successfully implement it within your team and organization.
Students are given an introductory pre-reading material (The “Scrum Manual”). After successfully completing the course, the students are sent a high quality PDF handout containing a visual recount of the training.
Who should attend
All team members — programmers, analysts, testers, UI/UX designers — working (or planning to work) on a Scrum project will benefit from this training. Additionally, all other roles that come in contact with the team (ex. managers) will get a better understanding of how to collaborate with an agile team.
- Teams, Scrum Master, Product Owner
- Continuous improvement with retrospectives
- Product vision, roadmap
- Product Backlog, User stories
- Planning and estimation
- Dealing with change
- Visual Management
- Unit testing, TDD, Collective Code Ownership
- Lean Thinking (game)
In this opening module, learners vividly experience the underlying lean principles and values that make Scrum work: teamwork, self-organization, continuous improvement, etc.
- Why Scrum (lecture)
The beneﬁts of Scrum are introduced, and the history of Scrum and agile methods is brieﬂy covered.
- Empiric vs Deﬁned processes (guided lecture)
In this module the difference between traditional project thinking and agile/empiric thinking is explained
- Product Vision (exercise)
This module explains the product vision concept. Participants write product visions and choose some winning visions by prioritizing them.
- User Stories (lecture)
In this module the traditional format for managing agile requirements is explained.
- Story writing workshop (exercise)
In teams, learners write user stories and epics for their products.
- Agile Planning (guided lecture)
The concept of velocity is explained. The iron triangle in Scrum is explained. How planning and managing an agile (empiric) project is different.
- Relative estimation (guided lecture)
Explains concept of story points and relative estimation.
- Planning poker & team estimation (exercise)
Participants estimate their user stories.
- Prioritization (exercise & group discussion)
Students prioritize their user stories, building their product backlog. Includes exercise & discussion on how to divide user stories.
- Change management (lecture)
Explains how to manage changes requests from a Scrum perspective.
- Backlog grooming / Deﬁnition of Ready (lecture)
Explains how to maintain the backlog in good shape and how to prepare for Sprint planning
- User story lifecycle (lecture – the onion)
Review of requirements management and requirements lifecycle in Scrum
- Sprint Zero (lecture)
A review and wrap up of what must be done in order to start a Scrum project successfully.
- Roles & Responsibilities (exercise / group discussion)
In this module, students map existing roles and responsibilities in project and product management to the 3 Scrum roles. A discussion follows about the former role of the Project Manager and the new role of the ScrumMaster.
- Sprint Planning (lecture & exercise)
Learners plan their ﬁrst sprint. How to successfully facilitate a sprint planning is discussed. Stories are divided into tasks.
- Deﬁnition of Done (guided lecture)
Participants learn how to handle non-functional requirements and other requirements that are not included in the product backlog, and how to guarantee internal quality of the product.
- Visual Management (lecture & exercise)
Task boards, status tags, name tags: how to visually manage your Scrum project using a physical information radiator.
- Daily Scrum (exercise & discussion)
Pitfalls of daily scrums, how to facilitate them, do’s and dont’s. How to handle un- planned work.
- Sprint Review (lecture & group discussion)
How to successfully facilitate a sprint review is discussed. Two types of Sprint Review are covered.
- Technical Practices (lecture)
Brief introduction of fundamental technical practices: frequent commits, unit testing, automated builds, continuous integration, plus overview of XP practices (TDD, pair programming, collective code ownership, etc)
- Retrospectives (exercise)
Continuous improvement in Scrum
- Advanced / optional topics (time permitting) (group discussion or lecture)
Topics may include scaling scrum, distributed scrum, agile contracts, coaching, selling scrum to clients, etc.
- How to continue your education
What to do after the training is over
Scum Master certification (CSM)
Successfully completing this training* enables participants to take the online exam that awards the Certiﬁed ScrumMaster certiﬁcation from the Scrum Alliance.
* in order to successfully complete the training and qualify for certiﬁcation, participants must attend 90% of class time (13,5 out of 15 hours) and must be paying attention and participating at all times (i.e. not working on their laptops or on the phone).
PMPs: You can receive 15 Professional Development Units (PDUs) for this course.
More information: http://www.mozaicworks.com/public-trainings-and-workshops/xavier-quesada-allue-certified-scrum-master-csm-9-10-september/
All CSM courses are taught by Certified Scrum Trainers. Taking a CSM course, passing the CSM test, and accepting the license agreement designates you as a Certified ScrumMaster, which indicates that you have been introduced to and understand the basic concepts you need to perform as a ScrumMaster or team member on a Scrum team. This course also satisfies two elements of the CSD track: Scrum Introduction and Elective.