How does your Increment support adaptation in order to minimise deviations from agreed goals? Each of the Scrum Artifacts serve to adapt. So does the Increment. Check it out!

How do you uphold Scrum without becoming a Scrum dictator? How do you lead the Scrum Team to ever greater adoption of Scrum within the organization… without direct authority? This article explores the challenges faced by Scrum Masters in their balancing act and how they navigate through it to ensure effective team performance and continuous improvement.

⚡🌩️#StormsOfNeglect: The Cataclysmic Consequences of Ignoring Usable Products in Agile!🌩️⚡ What if I told you that neglecting usable working products in Agile is like navigating a stormy sea without a compass? 🌊🚢 If you think skipping usable products in iterations is harmless, brace yourself for the torrential downpour of woes it can unleash! From eroding stakeholder trust to the tsunami of technical debt, from getting engulfed in the quicksand of adaptability to the barren desert of feedback. It’s a whirlwind of compounding issues that no Agile team should weather! 🌪️💥 Dive in as I illuminate the catastrophic perils of neglecting usable working products when it should foster trust, alignment, adaptability, and quality! 🛡️⚙️

Warum Scrum hinter den Erwartungen zurückbleibt kann — eine Systematik

Organizations have a habit of setting Product Owners up for failure. In this episode, Jeff and Mike discuss common anti-patterns and what to do about them.

How validating the value of the Scrum team’s work during the Sprint limits risk and increases predictability

Explore the challenge of 'Escaping the Product Owner’s Trap' in this insightful blog post. Learn how Product Owners often find themselves entangled in component thinking, losing sight of broader objectives and value delivery. Uncover key principles such as Vision, Value, and Validation, and discover actionable strategies to shift towards a product and value-driven mindset. This guide illuminates the path from mere component management to genuine Product Ownership, offering tools and techniques to align with organizational goals and customer needs.

This case study analyzes the transformation journey using Org Topologies™ Scans and focuses on the Business Banking Hub. The article is valuable if you want to understand how Org Topologies™ can help improve organizational design.

At the heart of Scrum is a unique and indispensable accountability: the Scrum Master. This enigmatic figure may not possess the traditional authority associated with managers, nor do they hold executive powers. Yet, they play a vital and indispensable accountability in the success of the Scrum Team and the organization as a whole.

The Scrum Anti-Patterns Guide, nearing completion, categorizes over 180 anti-patterns by roles, events, artifacts, and commitments. However, it lacks a meta-level taxonomy to address Scrum anti-patterns on broader levels, raising the question of developing such a comprehensive strategy.

Für jeden Trainer kommt der Zeitpunkt, an dem man in den Spiegel schauen und über sehr wichtige Fragen nachdenken muss: 👉 Was bedeutet es wirklich, ein Trainer zu sein? 👉 Konzentriere ich mich auf das Wesentliche? 👉 Warum sind die Teilnehmer in meinem Training? Die Beantwortung dieser Fragen ist für mich mit drei Lektionen verbunden, die ich als Trainer in den vergangenen Jahren lernen musste:

In the post-COVID business landscape, companies must innovate, embrace experimentation, and eliminate silos for success. Clear leadership and Scrum methodology foster collaboration and value creation. A shared vision and self-managed teams maximize value and navigate challenges effectively.

Scrum es un marco de trabajo para maximizar la entrega de valor. Con frecuencia se confunde el valor con entregar más cantidad de cosas en un menor tiempo. El valor es diferente viene desde la perspectiva de entender al cliente, asumir una postura de incertidumbre sobre lo que creemos o definimos acerca del mismo y entender la necesidad de aprender continuamente a través de la experimentación para descubrir, validar y aprender a través del uso de producto para adaptarnos de acuerdo con esto.

Are you using Scrum but not getting the results you want? If you're not producing usable increments, you're not alone. In this video I will explore why the increment is so important in Scrum and how to produce it consistently. I'll also share tips for mitigating risk, delivering value to stakeholders, and providing feedback and insights.

Managers in Agile organizations often struggle when their teams don't evolve into high-performing, self-managing teams. The struggle is to find the right balance between command and control management and being completely hands-off, letting the teams do whatever they want. How might a manager discover adjustments they can try to help their teams grow? this video blog might offer some ideas...

How does your Sprint Backlog support adaptation in order to minimise deviations from agreed goals? Each of the Scrum Artifacts serve to adapt. So does the Sprint Backlog. Check it out!

Does your Scrum Team often find itself with carryover work from the previous Sprint? Does that make your team an unproductive one? Whose fault is it? In this episode, Jeff and Mike share how to limit sprint-to-sprint carryover.  Listen and share with your team so things get DONE.

Find a better balance between solving problems and enabling growth and autonomy

🚀💥#UsableWorkingProduct: Your Ultimate Weapon Against Risks in Agile💥🚀 ⚠️ Ever wondered why some Agile projects falter? Is your fortress of documentation crumbling against the relentless tides of market change? 🌊 Here’s the secret sauce - It’s all about Usable Working Products! 🎯🔧 Too many Agile teams are trapped in the illusion of progress without creating shippable products. It’s time to unleash the secret weapon against risks - deliver increments that users can interact with, validate, and provide feedback on! 🛠🚀

In this article, we have crafted interview questions to help identify the best Product Owner for your Scrum team.

Scrum Werkzeuge, Teil 2: Von Design Thinking über Lean UX zu User Story Mapping

Learn how Scrum Product Owners and Scrum Masters can employ techniques to enhance the user experience and ensure product success.

Dispelling Agile and Scrum myths. Learn how Scrum enables Agile principles. Empower your teams to adapt, innovate, and deliver excellence.

ATTITUDE is the composition of our way of thinking, feeling, and acting. Every team member has an attitude defining their way of being in the Scrum Team. The question is if it is a constructive attitude or not.

The essence of a team is that people collaborate. Else it's incredibly hard to perform as an actual team, rather they just happen to work simultaneously and not together. What to do in such a case?

Scrum Tools, Part 2: From Design Thinking to Lean UX to User Story Mapping

Einen peinlicheren Moment hatte ich noch nie erlebt:

Scrum is a Product centric approach to delivering value. But what if your team is not aligned with a Product? In this blog, we discuss what Product means in Scrum and why it can help a team even if they do not feel they are working in a Product organization. In this blog, we talk about why Product is used in Scrum, the characteristics of a Product, and how those characteristics can even help if you are working on a Project.

Durant une session de coaching avec Martin, Scrum Master évoluant du côté du Canada, nous avons mis en évidence cette relation et les conséquences qui en découlent. 𝙐𝙣 𝙙𝙚𝙨 𝙧𝙚́𝙨𝙪𝙡𝙩𝙖𝙩𝙨 𝙧𝙚𝙢𝙖𝙧𝙦𝙪𝙖𝙗𝙡𝙚𝙨 𝙙𝙚 𝙘𝙚 𝙘𝙤𝙖𝙘𝙝𝙞𝙣𝙜 𝙖 𝙚́𝙩𝙚́ 𝙙𝙚 𝙥𝙚𝙧𝙢𝙚𝙩𝙩𝙧𝙚 𝙖𝙪 𝙎𝙘𝙧𝙪𝙢 𝙢𝙖𝙨𝙩𝙚𝙧 𝙙𝙚 𝙙𝙚́𝙢𝙤𝙣𝙩𝙧𝙚𝙧 𝙦𝙪𝙚 𝙡𝙖 𝙫𝙖𝙡𝙚𝙪𝙧 𝙙𝙚́𝙡𝙞𝙫𝙧𝙚́𝙚 𝙥𝙖𝙧 𝙪𝙣𝙚 𝙚́𝙦𝙪𝙞𝙥𝙚 𝙎𝙘𝙧𝙪𝙢 𝙥𝙚𝙪𝙩 𝙖𝙪𝙜𝙢𝙚𝙣𝙩𝙚𝙧 𝙩𝙖𝙣𝙙𝙞𝙨 𝙦𝙪𝙚 𝙡𝙖 𝙫𝙚́𝙡𝙤𝙘𝙞𝙩𝙚́ 𝙙𝙚 𝙘𝙚𝙩𝙩𝙚 𝙢𝙚̂𝙢𝙚 𝙚́𝙦𝙪𝙞𝙥𝙚 𝙗𝙖𝙞𝙨𝙨𝙚. 𝘾'𝙚𝙨𝙩 𝙪𝙣 𝙥𝙖𝙧𝙖𝙙𝙤𝙭𝙚 𝙞𝙣𝙘𝙤𝙢𝙥𝙧𝙚́𝙝𝙚𝙣𝙨𝙞𝙗𝙡𝙚 𝙥𝙤𝙪𝙧 𝙡𝙚𝙨 𝙢𝙖𝙣𝙖𝙜𝙚𝙧𝙨 𝙚𝙣 𝙦𝙪𝙚̂𝙩𝙚 𝙙𝙚 𝙫𝙚́𝙡𝙤𝙘𝙞𝙩𝙚́. Dans cet article, où nous étudions un exemple concret, nous vous donnons des clés pour 👉 Comprendre et pouvoir expliquer par vous-même, à vos collègues et managers, l'impact de la Définition of Done sur la vélocité 👉 Expliquer la relation irrationnelle qui existe entre #valeur et #vélocité 👉 Coacher votre équipe à la planification de Sprint 👉 Augmenter la satisfaction client et le nombre de ventes de vos produits, en modifiant la Définition of Done Pour continuer à développer vos compétences, suivez-nous et contactez-nous sans hésitation sur https://agilethinking.pro

How does your Product Backlog support adaptation in order to minimise deviations from agreed goals? Each of the Scrum Artifacts serve to adapt. So does the Product Backlog. Check it out!

Time off and vacations/holidays are a reality for all Scrum Teams. What does Scrum say about this and how do you deal with a missing Scrum Team member under these circumstances?

🎯#Agile Usable Products vs. Documentation in Traditional Project Management📝 💡Are you still torn between embracing Agile's nimble strides or holding onto the tried-and-true documentation-heavy Traditional Project Management? Let's crack the code! 🕵️‍♂️ In an ever-evolving software development landscape, striking the right balance is pivotal.🔧 Agile’s focus on continuous delivery of working products 🚀 might be the silver bullet in risk mitigation, whereas Traditional Project Management lays the groundwork with its elaborate documentation. 📚 But can we merge the best of both worlds? 🌍 Or does Agile already include sufficient documentation an planning?

Tests zur Selbsteinschätzung von Spotify über The Liberators bis zu selbst gemachten Tools

Este artigo discute as diferenças entre as metodologias de gestão de projetos Agile e Waterfall. O Agile é flexível e incremental, adaptando-se às mudanças, e é adequado para projetos com requisitos voláteis e necessidade de entregas rápidas. O Waterfall é estruturado e sequencial, exigindo planejamento detalhado, sendo adequado para projetos com requisitos estáveis e em ambientes altamente regulamentados. A escolha da abordagem deve considerar as características do projeto e do ambiente, mostrando que em gestão de projetos não existe uma abordagem "tamanho único".

In our quest to improve the working place, we propose to view an organization as an ecosystem. #OrgTopologies is a framework agnostic thinking tool that will allow managers to purposefully design organizations for high performance. In this article, we describe an A-level ecosystem and how to improve it.

Part of the Scrum Master's job is to work with the Product Owner. This specific person has tried OKRs, but asked us what else is available to work with. There are many things and areas that you could try! In this video, Evelien and I dive into this question.

The purpose of the Scrum Master is to enhance the efficiency and productivity of the Scrum team. It’s an important accountability for the success of the Scrum team, and yet, it is surprising that many people are uncertain about the qualities they should seek when hiring a Scrum Master. In this article, we will present ten interview questions that will aid you in selecting the perfect Scrum Master for your team.

It's very common to use waterfall to develop hardware since hardware can be very difficult to change once built. But have you ever wondered if Scrum can be used in hardware development? In this video, Professional Scrum Trainers Robb Pieper and Jason Malmstadt look at ways you can change how you make hardware to more easily benefit from the agility Scrum provides.

Discover how asynchronous meetings are transforming collaboration in today's fast-paced business world. Explore the challenges faced by Scrum Teams, particularly with stakeholders missing Sprint Review events. Learn about two experiments we have been running for effective Sprint Reviews: Recorded Sprint Reviews and Asynchronous Sprint Reviews. Uncover the benefits and considerations of each approach, and join the discussion on improving Sprint Reviews and gathering valuable feedback.

The Agile Leader's commitment goes beyond mere lip service to the Agile Manifesto. It's about creating a conducive environment for teams to innovate, collaborate, learn, and grow. It's about leading by example and embodying the principles and values that Agile upholds. But what exactly are these commitments an Agile Leader should make? Here, we delve into the '10 Commitments of an Agile Leader.'

From Spotify to The Liberators to Self-Made: Eight Self-Assessments to Get You Started.

Vom Diskutieren zum Handeln: 4 Entscheidungsregeln, die du unbedingt kennen solltest. Diese sind besonders wichtig, wenn du für die Produktivität eines Teams verantwortlich bist.

Agile cannot be implemented effectively if the culture of the organization doesn’t evolve with the process. In this episode we invite a special guest, Jim Ruprecht (an agilityIRL founder), to share why and how organizational culture is so important.

How lead- and cycle time are incredibly helpful metrics to drive change where it matters

How does your Sprint in its totality support adaptation in order to minimise deviations from agreed goals? Each of the Scrum Events serves to adapt. So does the Sprint itself. Check it out!

Über die negativen Auswirkungen eines kompletten Produkt-Backlogs auf Innovation, die Fähigkeit Ihres Scrum-Teams, Werte zu schaffen, und Ihre Beziehung zu den Stakeholdern.

🔍 *Agility in Red Markets: A Paradigm Shift* 🔍 Alpha organisations, once formidable, now face challenges in red markets due to their hierarchical structures. Slow decisions, stifled innovation, untapped talent, and customer disconnect are evident. In contrast, Beta organisations thrive with agility and responsiveness. Let's embrace this shift for a prosperous future.

Sprint Retrospektive: 3 Schwierigkeiten, bei denen selbst erfahrene Scrum Master aufgeben, und Tipps, damit du nicht dazugehörst

Another question we frequently get is whether Scrum Masters are truly needed. We can do the work without the Scrum Master, right? In this week's video, Evelien Acun-Roos and I address this question. To give you a quick answer; no, we don't think there's ever a point where you can do without the Scrum Master.

Scrum e la reazione autoimmune aziendale è una riflessione sulla mia esperienza dell’applicazione di Scrum professionale in azienda. Rivela i meccanismi socio-aziendali, ai quali ho assistito, che impediscono di trarre massimo beneficio dallo sviluppo empirico di un prodotto.