Beruflich Dokumente
Kultur Dokumente
If you work in tech or spend any amount of time with engineers, you’ve probably heard about
“Scrum” and “Agile.” It’s a system mentioned in reverent tones by tech types and seems to
have its own strange language. Terms like “planning poker,” “stand-ups,” and “sprints” are
thrown about by its proponents.It can all be a bit intimidating to the uninitiated. So, Buckle up,
because we’re about to “sprint” through an intro to Scrum.
Agile refers to a set of “methods and practices based on the values and principles expressed in
the Agile Manifesto,” which includes things like collaboration, self-organization, and cross
functionality of teams.
Scrum has been used by everyone from the FBI, to marketing agencies, to construction crews.
Any time you’re producing some sort of product, be it software or an email campaign, Scrum
can help you organize your team and get more work done in less time.
Within agile development, Scrum teams are supported by two specific roles. The first is a
Scrum Master, who can be thought of as a coach for the team, helping team members use
the Scrum process to perform at the highest level.
The product owner (PO) is the other role, and in Scrum software development, represents the
business, customers or users, and guides the team toward building the right product.
The Scrum Master role involves the technical side of projects, while the product owner role involves
the business side
Scrum utilizes short iterations of work, called sprints, and daily meetings, called scrums, to
tackle discrete portions of a project in succession until the project as a whole is complete.
Scrum calls for four ceremonies that bring structure to each sprint:
Sprint planning: A team planning meeting that determines what to complete in the coming
sprint.
Daily stand-up: Also known as a daily scrum, a 15-minute mini-meeting for the software
team to sync.
Sprint demo: A sharing meeting where the team shows what they've shipped in that sprint.
Sprint retrospective: A review of what did and didn't go well with actions to make the next
sprint better.
Product owners are the champions for their product. They are focused on understanding
business and market requirements, then prioritizing the work to be done by the engineering
team accordingly. Effective product owners:
Scrum masters are the champion for scrum within their team. They coach the team, the
product owner, and the business on the scrum process and look for ways to fine-tune
their practice of it. An effective scrum master deeply understands the work being done
by the team and can help the team optimize their delivery flow. As the facilitator-in-
chief, they schedule the needed resources for sprint planning, stand-up, sprint review,
and the sprint retrospective.
Scrum masters also look to resolve impediments and distractions for the development
team, insulating them from external disruptions whenever possible.
Part of the scrum master's job is to defend against an anti-pattern common among teams
new to scrum: changing the sprint's scope after it has already begun.
Scrum masters are commonly mistaken for project managers. A scrum team controls its
own destiny and self-organizes around their work. Agile teams use pull models where
the team pulls a certain amount of work off the backlog and commits to completing it
that sprint, which is very effective in maintaining quality and ensuring optimum
performance of the team over the long-term. Neither scrum masters nor project
managers nor product owners push work to the team (which, by contrast, tends to erode
both quality and morale).
Scrum teams are the champions for sustainable development practices. The most effective
scrum teams are tight-knit, co-located, and usually 5 to 7 members. Team members have
differing skill sets, and cross-train each other so no one person becomes a bottleneck in the
delivery of work. All members of the team help one another to ensure a successful sprint
completion.
At the business level, the Scrum master creates a development environment that is
creative, safe, productive and supportive and enables multi-direction collaboration.
At the product owner level, the Scrum master facilitates planning and helps product
owners understand and adhere to scrum techniques and practices.
At the team level, the Scrum master provides guidance, coaching, support and facilitation,
and helps remove any obstacles that teams may encounter along the way.
At the individual level, the Scrum master supports individual efforts, addresses any issues
that arise, and removes obstacles to help individuals be focused and productive.
Two well-recognized organizations, Scrum Alliance and Scrum.org, offer Scrum training and
certifications.
Certified Scrum Master (CSM): CSMs “act as ‘servant leaders,’ helping the rest of the
Scrum team work together and learn the Scrum framework.”
Certified Scrum Product Owner (CSPO): CSPOs are “individuals who are closest to the
‘business side’ of the project. They are charged by the organization to ‘get the product out’
and are expected to do the best possible job of satisfying all the stakeholders.”
Certified Scrum Developer (CSD): The CSD certification “exposes students to the most
important tools and techniques that need to be applied in order to build good software in
the iterative and incremental fashion that Scrum requires.”
Certified Scrum Professional (CSP): A CSP “challenges Scrum teams to improve the
way Scrum and other Agile methods are implemented for every project.”
PSM I:PSM I certificate holders “prove they understand Scrum as described in the Scrum
Guide and the concepts of applying Scrum.”
PSM II: PSMIIcertificate holders “prove that they have an understanding of the
underlying principles of Scrum and can effectively apply Scrum in complex, real-world
situations.”
PSM III: PSMIIIcertificate holders “have a deep understanding of the application and
practices of Scrum and the Scrum Values in a variety of complex team and organizational
situations.”
Certified Scrum Master is a 2-day course that covers the basics of Agile and Scrum. The
course is taught through interactive activities, lecture (some), real-world experiences and
discussions and sharing. Don’t expect to sit in your seat for two days.
At the end of the course, you will be capable of being an Agile team member and will have a
good understanding of how Scrum works. For those pursuing the roles of Scrum Master/Agile
Coach, Product Owner or Agile Manager, this course will provide the needed foundation and
will jump start your journey in these new roles.
Following successful completion of the course, students will be qualified to take the Scrum
Alliance self-assessment. This multiple-choice, online assessment is required to become a
Certified Scrum Master. It is based on these resources and what you learn in the class.
Once you have earned the CSM Certification you will be listed as a Certified Scrum Master on
the Scrum Alliance website and will receive a 12-month membership in the Scrum Alliance
where additional Scrum Master–only material and information are available.
After the course, the CST will enter qualifying students’ registration information with the
Scrum Alliance and those students will then have access to the ScrumMaster exam. To pass,
students must answer at least 24 of the 35 questions correctly (includes multiple choice and
true/false questions). The exam is taken online, is not time restricted, and is open book.
You will have two attempts within 90 calendar days after you receive your welcome email to
pass the test at no cost. After two attempts and/or 90 calendar days, you will be charged $25 for
each additional attempt.
THANK YOU