Professional Scrum Training Courses
Enables all members of the Scrum Team to learn Scrum while doing it, experiencing what it is like to deliver products using the Scrum framework
Learn Scrum theory, roles, events, and artifacts through individual and group activities along with trainer instruction.
In this advanced class, experienced Scrum Masters learn to overcome challenges they face through immersive facilitated exercises.
Students learn how to maximize the value of products and systems through instruction and team-based exercises.
Mastering the Product Owner Stances course focuses on helping experienced practitioners expand their ability to establish a solid vision, validate their hypotheses, and ultimately deliver more value.
Enables all members of a software-focused Scrum Team to learn Scrum while doing it, experiencing what it is like to build products with modern Agile and DevOps practices.
Hands-on workshop teaching managers and other leaders how to best support, guide, and coach their teams.
Teaches Scrum practitioners how to apply Kanban practices to their work without changing Scrum, bringing greater transparency and flow.
Learn modern UX techniques and practices that effectively enable Scrum Teams to best work with customers and their feedback to deliver higher value.
Designed for anyone involved in building products across multiple teams to learn how they can scale product delivery with Scrum.
Professional Scrum Competencies
Scrum.org has created these Professional Scrum™ Competencies to help guide an individual’s personal development as they learn Scrum.
New and Now at Scrum.org
Scrum Guide 2020
Resources Describing Scrum Guide Changes
Find a series of resources that discuss and describe the changes between the 2017 and 2020 versions of the Scrum Guide.
Case Study
Building Understanding Between Scrum Teams and Management with Liberating Structures
This case study looks at how Philips used Liberating Structures to improve communication across their group of teams.
White Paper
Scrum: A framework to reduce risk and deliver value sooner
An overview of the Scrum framework, for people new to Scrum and those who’d like to refresh their understanding. The aim of this white paper was to write in a practical, down-to-earth manner from the perspective of what the Scrum framework makes possible. This paper should be easy to read, clear up potential confusions and deepen your understanding.
Why Scrum.org
What Makes Scrum.org Different
Learn how Scrum.org is unique in the market as a mission based organization that provides consistent experiential training around the world.
Professional Scrum Certification Assessments
There are three levels of Scrum Master assessments to validate and certify your knowledge and understanding of Scrum and the Scrum Master role.
There are three levels of Product Owner assessments to validate and certify your knowledge and understanding of the Product Owner role.
The Professional Scrum Developer assessment validates and certifies you knowledge and understanding of the Development Team Member role in Scrum.
The Professional Agile Leadership assessment validates and certifies an understanding about how leaders can best support their teams in an agile environment.
The Professional Agile Leadership - Evidence Based Management assessment validates and certifies an understanding about how leaders can best support their teams in an agile environment.
The Scaled Professional Scrum assessment validates and certifies an understanding of scaling fundamentals to enable multiple Scrum Teams working together.
The Professional Scrum with Kanban assessment validates and certifies an understanding of how to use Scrum with Kanban to improve value creation and delivery.
The Professional Scrum™ with User Experience assessment validates a fundamental level of understanding of integrating modern UX practices into Scrum.
Featured Videos
What is a Product
Play Video
How to Become a More Effective Agile Manager
Play Video
4 Ways to Coach with the Scrum Values
Play Video
New Blog Posts
Ryan Ripley
On today's episode of YOUR DAILY SCRUM: How Do I Get Scrum Master Experience? A listener asked Todd and Ryan how to get Scrum Master experience after getting certified as a Professional Scrum Master. Quite a few Scrum Master's have gotten creative as they've looked for ways to apply their learnings before getting their first Scrum Master gig. Ryan and Todd discuss the things that they did that ultimately led to their first Scrum Master roles. Sometimes they had to think about what they could in their current roles to get experience. Sometimes, they volunteered and found fulfilling ways to practice their Scrum skills.
{"preview_thumbnail":"/drupal/s3fs-public/styles/video_embed_wysiwyg_preview/public/video_thumbnails/lpM_W-K0e4U.jpg?itok=TN6P4qGi","video_url":"https://youtu.be/lpM_W-K0e4U","settings":{"responsive":1,"width":"854","height":"480","autoplay":0},"settings_summary":["Embedded Video (Responsive)."]}
Ryan Ripley and Todd Miller are the author of Fixing Your Scrum: Practical Solutions to Common Scrum Problems. They are the co-founders of Agile for Humans, the premiere Scrum and Kanban training organization.
Jan 18, 2021
Read blog
Alexandre Mac Fadden
Qualquer pessoa responsável pela gestão de resultados dos negócios também deseja aprimorar esses resultados, melhorando seu desempenho nos negócios. Independentemente de quais estratégias eles usam, espera-se que os gerentes revisem e aprimorem regularmente os processos de negócios. Não apenas para aumentar as vendas ou expandir as margens, mas como uma condição de sobrevivência contínua do negócio.
Ao mesmo tempo, as empresas devem respeitar o que seus clientes desejam de seus negócios, ou não terão sucesso. Dessa perspectiva, mudar a maneira como você dirige seu negócio não deve contradizer as expectativas do seu cliente. Por exemplo, os clientes querem pagar menos por seus produtos, mas não ao ponto de mudar para processos de produção mais baratos que podem ser ruins para o meio ambiente.
É mais simples lidar quando são commodities
Por sua própria natureza, as commodities são mais simples de lidar quando equilibramos as melhorias nos processos de negócios com as expectativas do cliente. Ao fabricar um produto padrão que se encaixa perfeitamente na maioria dos clientes, você pode encontrar melhorias nos processos de negócios por meio de ganhos de produtividade.
No entanto, se você tentar e deixar de produzir soluções de tamanho único para acomodar as necessidades de clientes diferentes, você perderá as economias de escala que tornaram a produção das commodities mais simples de gerenciar, monitorar e melhorar.
Esse problema é especialmente verdadeiro quando se olha para o mundo digital. Ao fornecer serviços online, software e aplicativos, há muito espaço para inovar e fornecer soluções flexíveis para seus clientes. Mas, você só pode atingir os mesmos níveis de melhorias de produtividade que as commodities, se seus processos de negócios digitais forem flexíveis o suficiente para se adaptarem aos requisitos do cliente. E essa flexibilidade só pode ocorrer se seus processos de negócios tiverem agilidade para se adaptar às necessidades do cliente.
A própria natureza dos métodos de desenvolvimento de software torna os processos de produção em alta escala tradicionais inadequados para o mundo digital. Em algum ponto e em algum nível, o desenvolvimento de software leva à experimentação, enquanto avalia constantemente as necessidades do cliente e adapta seus produtos de acordo.
Os desafios do mundo digital
Hoje, as empresas de software entendem que as economias de escala não se aplicam mais, e se afastaram das abordagens tradicionais de gerenciamento preditivo para, em vez disso, focar nas necessidades dos clientes. Eles reconhecem que consciência e agilidade são agora a regra de sobrevivência obrigatória.
Ao lidar com as necessidades do cliente que mudam freneticamente, você deve adotar uma abordagem diferente para melhorar seu processamento de produção e, ao mesmo tempo, fornecer o valor agregado para diferenciar seus produtos da concorrência. Essa perspectiva é o que a maioria das pessoas chama de processo de inovação: um ciclo de feedback orientado para o cliente onde você reúne informações, extrai insights, cria, entrega e realiza valor, obtém mais feedback e interage com o cliente o máximo de vezes possível. Isso é o que chamamos de ciclo de vida do produto.
O desafio, então, é definir com que rapidez você deve interagir por meio desse processo e com que eficiência você pode moldar seu negócio com base na agilidade. E o time-to-market está intrinsecamente relacionado à mecânica desse ciclo de feedback. Isso está intrínseco na metodologia Ágil e, dentro do Scrum, relacionado diretamente ao que chamamos de Sprint.
Como uma empresa ágil, sua meta deve ser coletar feedback, não apenas implantar e agregar valor. A coleta de feedback é a chave para se adaptar às necessidades do cliente e seguir em frente. A consistência e a frequência do seu ciclo de feedback não é apenas uma boa prática, mas permite que você ajuste o processo, criando “time-boxes” que permitem uma adaptação rápida aos novos requisitos do cliente.
A importância do time-box e do time-to-market
Essas expressões, como limitador de tempo máximo, são o que chamamos de time-box. Em geral, quanto menor for o time-box, melhor. A metodologia Scrum inclui muitas oportunidades para inspecionar e adaptar, e o time-box é crucial para manter seus objetivos no caminho certo para que você possa se adaptar continuamente às necessidades atuais do cliente. Tudo tem um tempo máximo para falhar e, se você falhar, terá muitas oportunidades de mudar de direção e redirecionar seus esforços. É por isso que o time-to-market depende do time-box.
Um sprint é um contêiner que deve reconhecer os objetivos do feedback de uma perspectiva de alto nível, permitindo entregas frequentes, transparentes, mais alinhadas e adaptáveis ao cliente. Ao reconhecer isso, as empresas podem evitar o erro de dizer que, com a metodologia scrum, você só deve entregar atualizações quando um sprint é concluído.
Associar um sprint à entrega é justo, mas frequentemente mal interpretado. Um sprint está melhor associado à coleta de feedback para expandir a frequência de entrega de apenas uma vez por sprint para pelo menos uma vez por sprint. Entender essa diferença abrirá outra perspectiva que é mais natural e sem atrito: você pode implantar várias vezes durante um sprint.
A importância do fluxo para seu time-box
Se necessário, você pode implantar atualizações todos os dias para atender às necessidades do seu cliente. Se não puder, a pergunta deveria ser: o que o impede de seguir nessa direção? Este problema é sobre fluxo e como atingir um fluxo mais suave e como seu fluxo pode ser otimizado para ser mais produtivo com base na resolução de quaisquer gargalos que você possa ter.
Seu time-box também é um espaço reservado usado para definir um limite para a quantidade de tempo que você tem para produzir algum incremento de valor, inspecioná-lo e se adaptar. Especificamente, para um sprint, também cria a oportunidade de ouvir a voz do seu stakeholder e melhorar o valor de cada entrega, não apenas em termos de fluxo, mas também sobre como priorizar o que traz mais valor.
Nossa experiência
Os conceitos explorados neste artigo são exatamente o que vivenciamos dia após dia por mais de trinta anos de experiências, permitindo que nossos clientes vejam seus produtos pelos olhos de seus clientes. E o time-box é o elemento crucial para otimizar continuamente o fluxo, especialmente no qual o time-to-market mais curto é o objetivo.
Nesse ponto, você verá os benefícios da metodologia ágil como o scrum, criando de forma interativa e colaborativa uma mentalidade orientada para o cliente e estabelecendo condições adequadas para agilidade de negócios.
Jan 18, 2021
Read blog
Simon Kneafsey
One of the most common questions I receive via the Contact Us page on TheScrumMaster.co.uk is – How can I get my first job as a Scrum Master?
I always reply to anyone that inquires. Here are my thoughts on how to do it and some answers to common related questions. I have also added an experience report from one of our wonderful clients who has recently been on this journey.
I DON’T HAVE ANY SCRUM/IT/SOFTWARE EXPERIENCE, CAN I STILL BECOME A SCRUM MASTER?
Yes. The more relevant experience you have, the more opportunities will be open to you straight away. However, everyone must start somewhere. If you are committed and persevere you will be able to learn what you need as you go. Some of the best Scrum Masters I have worked with did not have a technical background and came to Scrum after trying other career paths.
TheScrumMaster.co.uk’s Scrum.org Professional Scrum Master course does not require you to have a software or IT background. No prior knowledge of Scrum is required. It’s wonderful if you do know something already of course, but is not essential. All our courses contain a mix of people from a variety of backgrounds and experience levels so there will be someone in a similar situation to you. We will cover all you need to know about Scrum to get you started successfully.
WILL SCRUM TRAINING MAKE A DIFFERENCE?
Yes. Training from Scrum.org will help you learn and understand the basics of Scrum and the Scrum Master accountability. You can of course learn this in other ways (books, videos etc) but there is something powerful about learning with other like-minded people in a group. You may also make some new useful connections and meet others in a similar position.
DO I NEED A SCRUM CERTIFICATION?
In theory no, but in practice yes. Many employers require certification from Scrum.org or another authority to demonstrate your basic understanding of Scrum. Without it, most employers will not even shortlist you for an interview. There are of course exceptions, but without it, your opportunities will be much more limited.
CAN YOU GUARANTEE I WILL GET A JOB?
No. Training and certification will help you to learn and demonstrate what you have learned. Finding your first role in a new industry will take more than this and there is of course risk and no guarantees.
The good news is that many have been in your position before and gone on to make the transition. At some point, everyone who now uses Scrum had to get their first role. Demand for people with Scrum & Agile experience is growing rapidly. More organisation are becoming agile including many outside of software and I.T.
Patience and perseverance will be essential. Expect it to take some time. Get started, keep going and inspect, learn and adapt as you go.
AMBA’S STORY
Still not sure? Want to hear how it can be done? Amba attended Scrum training with TheScrumMaster.co.uk in 2018. She was new to Scrum and has gone on to build a successful career as a Scrum Master. Here is her story and some tips on what worked for her along the way:
“I did not have an IT/software background so I knew it would be a challenge moving into the world of Agile and finding my first Scrum Master job! However, it can be done and I am proof of that. Here are some things that helped me along the way.
Attending a Scrum.org Professional Scrum Master course with TheScrumMaster.co.uk really helped me to learn what Scrum is and what being Scrum Master is all about.
Gaining the Scrum.org certification confirms your understanding, builds confidence and is really important to demonstrate your knowledge. Nearly all Scrum jobs require certification and without it, you will be at a significant disadvantage to others that have it. The training and certification together gave me the confidence to talk about Scrum effectively in interviews.
Just because your previous role wasn’t as a Scrum Master, doesn’t mean you haven’t used elements of the required skill set before. Good employers will value you and your skills and not only look for direct experience. Be creative and think of examples where you have used the skills in a different setting. Have you supported a team before or facilitated a meeting? Have you helped make a team successful?
Network! There are so many Scrum & Agile meetups that there really is no excuse for not attending some. Meetup.com is great to find such groups. At these events, you get to meet some great people and learn new things. Some of the people you meet might even be recruiting. The “hidden” job market is where many of the best jobs are. You can also join TheScrumMaster.co.uk’s Slack community and make connections there.
Contact businesses and introduce yourself. Offer your services at a discounted rate (or even for free if you can afford to) in order to gain some industry experience for your C.V. Once you have some experience, finding the next role will be much easier. In the long run, you will often earn much more.
Apply for jobs even if you think you do not have all the experience required. You will receive plenty of rejections, but eventually, you will get a ‘Yes!’. Recruiters often ask for more skills and experience than a role requires and will be willing to compromise to find someone.
Don’t give up! I had plenty of rejections, bizarre interviews and a low paid first role. However, 8 months into my agile journey I was receiving permanent employment offers and recruiters were seeing the value I could offer.
Now with 2 years of experience, I am able to move into more demanding Scrum Master roles. I am enjoying sharing my passion for agile and helping turn groups of people into great teams. It wasn’t an easy journey, but it is one I am glad I made!”
Hi, my name is Simon Kneafsey and I am a Professional Scrum Trainer with Scrum.org & TheScrumMaster.co.uk. I am on a mission to simplify Scrum for a million people. I have helped over 10,000 people so far and I can help you too.
Learn more at TheScrumMaster.co.uk and signup for our newsletter with 80,000+ other Scrum practitioners.
Jan 18, 2021
Read blog
Thomas Schissler
Zum 10. Januar 2021 hat die scrum.org das bisherige Professional Scrum Developer Training (PSD) in Applying Professional Scrum for Software Development (APS-SD) umbenannt. Gleichzeitig wurde auch das Professional Scrum Foundations (PSF) Training in Applying Professional Scrum (APS) umbenannt. Hinter dieser Umbenennung steckt wesentlich mehr als nur neue Namen für die Trainings. In diesem Blog-Post wollen wir einige der Hintergründe und Auswirkungen für das APS-SD Training näher betrachten.
Überblick Änderungen bezgl. APS-SD
Ein Training für das gesamte Scrum Team
Konkrete Umsetzung des Scrum Frameworks im Kontext von Softwareentwicklung
Scrum erleben
Ein Training für das gesamte Scrum Team
Als die scrum.org von Ken Schwaber gegründet wurde, war es naheliegend, für die 3 Rollen in Scrum jeweils spezifische Trainings anzubieten. So entstanden das Professional Scrum Master Training (PSM) für Scrum Master, das Professional Scrum Product Owner Training (PSPO) für Product Owner und das Professional Scrum Developer Training (PSD) für die Mitglieder des Development Teams. Mit der Zeit hat sich herausgestellt, dass dieser Ansatz einen Nachteil hat. Wenn die Mitglieder eines Scrum Teams unterschiedliche Scrum Trainings besuchen, bleibt der Aspekt der Zusammenarbeit zwischen diesen Rollen auf der Strecke.
Das PSD Training bot eigentlich schon immer die idealen Voraussetzungen, die Wichtigkeit und Ausgestaltung dieser Zusammenarbeit nicht nur theoretisch, sondern auch praktisch in Sprints zu erleben. Deshalb war auch bereits vor der Umbenennung die Empfehlung, dass idealerweise das gesamte Scrum Team inkl. Product Owner und Scrum Master an einem PSD Training teilnimmt. Jedoch wurden durch das "Developer" im Namen viele Nicht-Programmierer abgeschreckt, das Training zu besuchen, da sie befürchteten, dass für sie das Training zu technisch sein könnte. Mit diesem Vorurteil räumt der neue Name APS-SD nun auf und macht klar, dass es sich dabei um ein Training handelt, bei dem Scrum im Vordergrund steht, hier aber konkret für die Anwendung im Kontext von Softwareentwicklung.
Konkrete Umsetzung des Scrum Frameworks im Kontext von Softwareentwicklung
Während Scrum ja ursprünglich aus der Softwareentwicklung stammt, sind das Scrum Framework und der Scrum Guide über die Jahre immer agnostischer zum Anwendungsumfeld und der jeweiligen Problemdomäne geworden, um aufzuzeigen, dass Scrum durchaus auch in anderen Bereichen nutzbringend eingesetzt werden kann. So wird Scrum heute als ein Framework definiert, das hilft, komplexe Probleme zu lösen. Diese Generalisierung hat allerdings auch den Nachteil, dass das Framework damit auch unkonkreter wird. Während das APS Training Scrum allgemein und ohne Bezug auf eine konkrete Domäne erläutert, hat das APS-SD Training einen ganz klaren Fokus auf den Bereich der Softwareentwicklung. Hier werden konkrete Praktiken und Konzepte vermittelt, die den Nutzen von Scrum in diesem Bereich unterstützen und Teilnehmer erhalten konkrete Empfehlungen. Diese Empfehlungen sind sehr hilfreich für Teams, die Scrum neu einführen, um bereits eine gute Ausgangsbasis zu erhalten. Für Teams, die bereits Scrum nutzen, zeigen diese Empfehlungen Bereiche auf, in denen diese Teams entsprechendes Entwicklungspotenzial haben. Ausgehend davon starten die Teams dann einen kontinuierlichen Verbesserungsprozess (Inspect & Adapt), um das Vorgehen noch besser an die individuelle Situation anpassen zu können.
Je konkreter diese Empfehlungen jedoch bereits auf die Arbeitsdomäne des Teams passen, desto einfacher können diese in die eigene Arbeit integriert und weiterentwickelt werden. So wird im APS-SD Training ausführlich besprochen, was Done für ein Softwareprodukt bedeutet und welche Praktiken und Vorgehen hilfreich sein können, diesen Zustand ohne viel Stress zu erreichen. Herausforderungen wie z.B. die Nachhaltigkeit von Software-Architektur und Codebasis und vor allem auch die Kollaboration zwischen Product Owner und Developern in diesem Spannungsfeld werden erläutert und hilfreiche Konzepte, dies im Arbeitsalltag zu meistern werden vermittelt. Die konkrete Fallstudie, anhand der im APS-SD Training von den Teilnehmern eine realistische Softwarelösung entwickelt wird, bietet vielfältige Herausforderungen und damit Erkenntnisgewinne, die eine Transformation in den Arbeitsalltag der Teilnehmer gegenüber abstrakten Simulationen deutlich vereinfacht.
Sollten Teams und Organisationen also Scrum einführen oder das Scrum-Verständnis und Praktiken verbessern wollen, dann empfehlen wir das APS-SD für Teams, die Softwareprodukte erstellen und für Teams aus anderen Domänen das APS Training.
Scrum erleben
Die Trainings der APS Trainings-Serie zeichnen sich vor allem auch dadurch aus, dass die Teilnehmer im Training Scrum erleben können. Statt nur darüber zu diskutieren, wird Scrum im Training von den Teilnehmern angewendet. Dadurch werden Zusammenhänge und Mechanismen deutlich besser vermittelt und Skeptiker überzeugt. Je besser diese Scrum-Simulation den Alltag der Teilnehmer abbildet, desto einfacher lassen sich die Erkenntnisse übertragen. Vor allem wenn das gesamte Scrum-Team am APS-SD Training teilnimmt, stellt sich bereits in den Übungssprints ein gewisser Rhythmus ein, den die Teilnehmer dann nach dem Training einfach in ihrem realen Projekt fortsetzen. Dies verkürzt die Zeit bis ein Return On Invest (ROI) erreicht wird und erhöht den Einfluss, den das Training auf die Arbeit des Teams hat.
Dieser Artikel wurde erstellt von Peter Götz und Thomas Schissler, den beiden Stewards für das APS-SD Training
Jan 18, 2021
Read blog