In this episode of the Women in Agile Podcast, Chithra Ramachandran and Steve Holyer unpack commitment 7 of the Code of Ethical Conduct for Agile Coaching; Agreeing on Boundaries and the challenges that Coaches can have when establishing boundaries with their clients. (41 Minutes)

The story aims to showcase the transformative power of Agile and Scrum in leadership and team management within the tech industry. It's inspired by real-world scenarios where leaders face challenges in project management and team dynamics. The intent is to provide a relatable and inspiring narrative...

In this video, Martin sheds light on the intricacies of conducting a Sprint review in the Scrum framework. 🌟 He discusses the pivotal role of the Product Owner, the art of engaging stakeholders, and the strategy behind effective Sprint planning. 📊 This insightful exploration delves into making the m...

Building a Professional Attitude needs deep adherence to the Scrum Values. Watch this vLog to see how you can improve your knowingness and beingness.

Technical debt refers to the compromises made in software development, where quick and easy solutions are chosen over more robust and sustainable ones.

People learn in a combination of different ways and the same goes for how they choose to continue their learning journey and grow. In this webinar our panel will discuss the various ways people learn, the immersive learning approach and more.

Professional Scrum Trainers Ryan Ripley and Todd Miller explore how dependencies can impact the ordering of Product Backlog Items on today's episode of Your Daily Scrum.

Aprenda o que é Scrum, em poucos minutos, e de uma fonte confiável. By Professional Scrum Trainer Antonio Costa Neto.

In this video, Martin discusses the transformative power of immersive learning in organizational development. 🚀 He delves into how this approach can significantly benefit teams, particularly those in Scrum Master roles. 🎯 The conversation progresses from the foundational aspects of immersive learnin...

Create focus for your team and get more done by breaking down work. In this episode, Jeff and Mike explore the transformative impact of aligning teams to a Product Vision and creating incremental goals that bring your product toward that vision.

The Product Owner is responsible for creating all Product Backlog ItemsWhy is this a myth? The Product Owner is accountable for Product Backlog management, including the creation of the Product Backlog Items (PBIs). That means that the Product Owner owns the result or outcome of this work. However, ...

A Product Owner works to maximize the value of their product with the rest of the Scrum Team. To be effective in this accountability, a Product Owner must be strategic and resilient. They possess a combination of communication and analytical skills that allows them to drive a clear vision, make deci...

A Product Owner is the member of the Scrum Team that is accountable for “maximizing the value of the product resulting from the work of the Scrum Team.”The Scrum Team as a whole is accountable for creating a valuable product, specifically “for creating a valuable, useful Increment every Sprint.” It’...

In this Scrum Tapas video, PST Simon Reindl talks about being ruthless when it comes to delivering value and how the focus of product development and lean practices should be on delivering value. (4:04 Minutes)

Product Backlog refinement is a very important practice for Product Backlog Management. Often times, Ordering and Prioritization often get confused. In this Scrum Tapas video, Professional Scrum Trainer Oscar Styf shares how these practices should be used. (4:17 Minutes)

In this Scrum Tapas video, Professional Scrum Trainer Simon Reindl walks through the Kano Model and how it helps you focus on value and customer delight when it comes to lean product development. (5:20 Minutes)

Forecasting is often overlooked in Product Backlog refinement. In this Scrum Tapas video, Professional Scrum Trainer Oscar Styf explains the Cone of Uncertainty as a forecasting technique. (6:24 Minutes)

Creating Goals can be challenging. In this Scrum Tapas video, Professional Scrum Trainer Oscar Styf shares what to consider when creating effective goals in Scrum. (14:21 Minutes)

The OBJECTIVE Framework highlights nine key components to successful goal setting: Outcome-focused, Balanced, Journey-oriented, Engaging, Challenging, Innovative, Timeboxed, Valuable, and Evaluated.

The Developers are the Scrum Team members that create the product. Often people associate the word “developer” with coder or programmer in software. But that is not the case, think of a developer as someone who helps to create (develop) a valuable product for a customer, no matter what kind of produ...

Each Developer should have all the skills necessary to deliver the productWhy is this a myth? It’s true that each Scrum Team should have all the cross-functional skills necessary to deliver their work. However, it’s not true that each Developer has to have all the skills necessary, or that each Dev...

Developers on a Scrum Team are committed to working collaboratively with other Scrum Team members to reach the Scrum Team’s goals. Several characteristics embody a professional Scrum Developer, for example they:Are problem-solvers - Scrum is used to solve complex problems in which the solution is fo...

In this video, Martin explores the nuanced dichotomy between resource efficiency and flow efficiency in the modern workplace. 🔄 He delves into how organizations often lean towards optimizing resources - treating people and materials as cogs in a machine - and contrasts this with the holistic approac...

In Scrum, the Sprint Goal is collaboratively created by the entire Scrum Team. This ensures alignment and shared understanding of the objective for the upcoming Sprint.

In diesem Artikel erkläre PST Simon Flossmann, wie du die Definition of Done erfolgreich nutzt.

In this article, PST Stefan Wolpers unravels the secrets of what makes a Scrum Master not just good but amazingly outstanding. Also, he sheds light on the pitfalls to avoid if you want to keep the respect of your teammates.

En este artículo, Guillem Hernandez Sola habla de la situación de porqué se están despidiendo Scrum Masters y Agile Coaches en organizaciones.

Have you ever tried piecing together a jigsaw puzzle without knowing what the final picture should look like? Knowing what the outcome should be can guide you in reaching project success.

🔍💻 Facing the hidden dangers of technical debt in software? This article dives into the world of software development, unraveling the often-overlooked risks of technical debt. 🚧📉 Learn why understanding and managing this aspect is crucial for your business's success and sustainability. 🛠️💡 From Micr...

Scrum's empirical approach promotes adapting to reality rather than sticking rigidly to predefined KPIs. Success in Scrum focuses on continuous improvement, value delivery, and customer satisfaction.

The Scrum framework is deliberately incomplete, so when teams start to fall for Scrum myths, frequently these myths are actually holding the team back from embracing the true flexibility of Scrum. Teams should find out what works best for them, not works best for other people.

A self-managing team is a fundamental part of effectivity. How can this happen during your Sprint Retrospective? Check it out!

Last week I was invited to give a lecture at the Free University of Amsterdam at the faculty for Digital Business Innovation. I consider it a real honor to teach the students of a University. The lecture triggered a lot of thoughts about the relevance of teaching Agile/Scrum.

Scrum Masters need to have technical skills, but they aren't the same skills that the Developers on their Scrum Teams need. Discover the benefits of a Scrum Master's technical toolkit.

In this Scrum Tapas video, PST Joanna Plaskonka talks about the purpose of Product Backlog refinement and who should be involved from the Scrum Team. (4:20 Minutes)

In this Scrum Tapas video, PST Joanna Plaskonka shares some good and bad examples for Product Backlog refinement (5:54 Minutes).

In this Scrum Tapas video, PST Joanna Plaskonka, explains the concept of ready in Scrum and some common myths and pitfalls around this topic. (3:58 Minutes)

Ashley Pulhuis from Gladwell Academy talks with Leslie Morse from Scrum.org on how to create the ultimate working environment for continuous improvement.

This episode of the Women in Agile podcast unpacks the 6th commitment in the Code of Ethical Conduct for Agile Coaching; Upholding Social responsibility, Diversity and Inclusion. We uncover the thinking behind the section, its inclusion in the Code of Ethics and its application in coaching. (29:31 M...

In questo video Stefano Milanesi e Fabio Panzavolta analizzano una situazione frequente nei team Scrum: la distanza fra la "teoria" di Scrum e la sua applicazione provoca spesso disfunzioni nel team e riduce efficacia e crescita del team.

In this video, Martin delves into the intricate world of Scrum Mastery, illuminating the traits that shape an effective Scrum Master. 🌟 He explores the situational nature of this pivotal role in Agile teams, focusing on the team and organizational fit and the influence of internal dynamics. 🚀

Warum erfolgreich sein, wenn man scheitern kann? Stefan Wolpers analysiert zehn todsichere Wege, das Verfehlen von Sprint-Ziele sicherzustellen.

Flow Metrics are pretty easy to understand and use, but getting started with a tool like Actionable Agile can be tricky.

A Product Owner is the member of the Scrum Team that is accountable for maximizing the value of the product resulting from the work of the Scrum Team. Learn more about what that means and a few of the common myths about Product Owners.

The Developers are the Scrum Team members that create the product. They have specific accountabilities to the team. Learn about these accountabilities and debunk a few myths about being a Developer on a Scrum Team.

There are several reasons why Scrum Teams are left with un-done work at the end of the Sprint, including:They don’t understand the importance of time-boxes or Sprint Goals. If Sprints are just periodic check-ins on progress and if Sprint Planning merely involves updating an existing overall project...

There are reasons why Scrum Teams may have un-done work at the end of the Sprint, but these occurrences should be infrequent as they are detrimental to the team’s ability to deliver value. There are various techniques that they can try to minimize having un-done work, including:Ensuring that everyon...

The phrase “un-done work” refers to work that is not finished by the end of the Sprint, according to the Scrum Team’s Definition of Done. Un-done work is, simply put, waste. It adds no value to the product Increment and may even reduce its value. Ultimately, un-done work represents time that the Sc...

Un-done work is work that does not conform to the Definition of Done and is therefore unfinished. It represents time the Scrum Team spent creating something that delivered no value. Learn what un-done work is, what causes it and techniques for eliminating it.

In this video, Martin delves into the transformative journey of becoming a Scrum Master, a role crucial for aspiring leaders in any dynamic work environment. 🚀 He articulates the essence of this career path, highlighting its significance in personal growth and team dynamics. 🌟