In this episode of the Agile.FM podcast, Professional Scrum Trainer Joe Krebs chats with fellow Professional Scrum Trainer Yuval Yeret, co-author of the Scrum with Kanban Guide and course steward of the Professional Scrum with Kanban course with Scrum.org.

In this blog post, Dave West, CEO and Product Owner at Scrum.org, will explore the benefits of using Scrum for Marketing, dealing with pressures from every side of the business and using Scrum to address complexity.

Scrum provides numerous opportunities for teams to inspect and adapt their progress, including on a daily basis.

In this episode of Ask a Professional Scrum Trainer, PST Tolga Kombak answers Scrum questions from the audience.

"You are not doing Scrum." How many times have you heard that? Scrum Police are a legion.

La velocidad es uno de los temas de Scrum más discutidos online y offline. Sólo hace falta acercarse a la comunidad de Scrum Masters en Facebook para comprobar como muchas de las cuestiones planteadas están en la linea de la velocidad de entrega de los equipos de desarrollo de Software.

Esta mañana estaba preparando una megamaleta para viajar durante las próximas semanas a Japón, México, Portugal y Alemania cuando me he encontrado el tuit que puedes leer más arriba.

For executives and for change agents who deal with executives in large contexts ...

Professional Scrum Trainer Yuval Yeret (@yuvalyeret) joined fellow Professional Scrum Trainer Ryan Ripley (@ryanripley) to discuss Scrum and Kanban sitting in a tree…along with the Professional Scrum with Kanban course from Scrum.org.

El Sprint Backlog suele generar bastantes dudas en cuanto a su gestión. En ocasiones se convierte en un arma arromadiza que los stakeholders, el Product Owner o incluso el Scrum Master utilizan para controlar el equipo. ¿Es esta su función?

In this blog post, I’ll share examples of how I experienced a Developer Culture, being a Scrum Master working with Development Teams.

As CEO and Product Owner for Scrum.org I get the amazing opportunity to visit lots of different companies. Recently I spent a week in Brazil visiting some amazing companies and talking about agility.

A few months ago we looked at how teams can optimize flow across the Sprint boundary, a technique which is founded on their ability to make limited and sustainable commitments.

We've all seen it. The Scrum Team that goes through the motions, implements all the mechanics of Scrum, and still when we look at what's going on it doesn't feel right.

Scrum Masters are often understood mostly as “team coaches”. Yet, their role is vastly more important. The Scrum Guide emphasizes that Scrum Masters are responsible for leading and coaching organizations in the adoption of Scrum and causing change that increases the productivity of the Scrum Team.

The comparison between Kanban and Scrum obviously comes up often when we're talking to teams, especially in the context of Professional Scrum with Kanban. While they are more similar than many practitioners realize, one key difference is the perspective on Teams. 

Flow of work and, most importantly, value is paramount. There are times when you keep looking at the process and don’t understand what is going on, what is wrong, and why stuff is not getting to done. Read to learn how flow can help while limiting work in progress.

What is Scrum Team Velocity? This is a tricky one, and you need to be answering it in the context of the organization you are interviewing with and its complementary practices.

In the first part of Getting to 85 – Agile Metrics with ActionableAgile we looked at the Cycle Time Scatterplot created by ActionableAgile software. The second part was all about the CFD. Now it's time to look at the Aging Work in Progress chart.

In the first part of Getting to 85 – Agile Metrics with ActionableAgile we looked at the Cycle Time Scatterplot as generated by ActionableAgile software. That piece also discussed some ideas the scatter plot could bring about and conversations that potentially might occur.

Scrum and Kanban are a great combination. With this insight more and more Scrum Teams become aware of terms and phrases used in Kanban. Like 'WIP'.

The topic of Agile Metrics inevitably comes up in many situations and conversations. For the Scrum practitioners these somehow are a subset of Velocity and Burn ups and downs. Now, there's a whole world out there, that operates with much reacher vocabulary of metrics. Professional Scrum With Kanban ...

As a Global Vice President at a major financial institution, I spend two days a week teaching Product Ownership, Agile Leadership, Scrum, and Kanban to 25 employees per week. As a Professional Scrum Trainer, I’ve taught over 1500 people through the years. This experience has made me a better leader.

Questions about agile certifications (especially those from Scrum.org) are an integral part of my routine. People always come to me saying that they are going to act as a Scrum Master / Product Owner / Developer on an agile project and they want to know what to study and what's the best first certif...

Compare the use of Scrum's Definition of Done to the professional procedures in other fields such as surgery and aviation.

This blog post is about what I learned working with my team as a Scrum Master and improved between one year using Professional Scrum with Kanban.

The Professional Scrum with Kanban (PSK) class was launched a year ago - Feb 26 to be precise. We've done some inspection and adaptation throughout the year but this anniversary is a nice opportunity to reflect on where we are and where we're going. So what did we have in this inaugural year of ...

No hay necesariamente una relación directa entre la complejidad de un PBI definido en términos de puntos de historia y el tiempo de desarrollo. Es decir, un PBI o historia de usuario que tiene mayor complejidad en puntos de historia puede terminarse en menos tiempo que un Item que tenga menos puntos...

As people become more empowered and capable of taking ownership of their process and executing on their decisions, the next area to focus is raising the bar. This is about a drive for continuous improvement. It will be demonstrated with valuable outcomes, higher quality, and growth in the capabili...

The 2019 Scrum Master Trends Report is an update to the 2017 Scrum Master Salary Report that Age of the Product conducted in 2017. By partnering, we have secured a larger sample and broadened the reach of the research, growing from over 500 to more than 2,100 respondents and adding more geographies ...

The Professional Scrum with Kanban (PSK) course has now been out for more than 6 months at Scrum.org. As one of the first few trainers who wanted to teach this course when it came out, I find it is a great way to combine the Scrum framework with Kanban as a strategy to deliver value to your customer...

As an agile coach and trainer, I have had the opportunity to reach thousands of students that are just beginning their journey into the Scrum and agile world.

The Development Team is both self-organizing and cross-functional and by the end of each Sprint provides an increment that is ‘done’ and releasable. The team defines how to organize work in a Sprint.

Many Agile coaches and Scrum Masters believe they know best. They believe teams must follow a certain set of steps and do things a certain way, and if they do, those teams will be more productive, happy, and successful than ever.

Hello great people of the world. It’s been a while since I wrote a blog post here. This time I want to share my experience working with Development Teams and a Product Owner at iPrice group who upgraded the way they ran their Sprint Planning.

At one point or another in our lives we have all experienced a long queue, stuck in a car on the motorway, sat on a train waiting for an open platform. My favorite memories stretch back to that line for the lunch at primary school where it was cake and custard day!

In this video, Scrum.org Professional Scrum Trainer and Professional Scrum with Kanban (PSK) course steward Yuval Yeret talks about the PSK course, helping viewers to understand more about the structure of the class and what they will learn when attending. 

The Scaled Agile Framework (SAFe™) is one of the most popular approaches to applying agile at scale out there. SAFe's perspective is that "Nothing beats an Agile Team" and it doesn't try to reinvent the wheel or even innovate too much when it comes to the Team level

One of the key Kanban practices we discuss in the Kanban Guide for Scrum Teams is Limiting Work in Process. 

This article discusses the growth of agility for customer-facing products with 3+ teams, probably tens of teams with Nexus and/or LeSS.

If you’re a veteran of the software industry, you probably remember those days where we released to production/GA every couple of months. Heck, many of the companies I meet these days still work that way.

In this post, we’ll explain the Liberating Structure ‘15% Solutions‘ and how we've used it. It’s a wonderful structure that can ignite big change by starting with small, individual contributions.

Don’t say this too loudly around agile conferences, but when it comes to the day-to-day work, Scrum and Kanban teams are very similar.

In this video, watch Dave West and Professional Scrum Trainer Yuval Yeret present on Scrum, Kanban and DevOps at Agile New England. 

Dear friends, I want to share an unusual view of Scrum with you. Perhaps you've never thought about such a point of view before. I hope it will be useful.

Bottom line - Toyota Improvement and Coaching Kata is the perfect partner for flow-based retrospectives.

"An Agile Coach know more than just Scrum", said one consultant in a boardroom meeting, "he/she knows organisation dynamics, executive coaching and other Agile practices like Kanban and DevOps", he continued.

Bottom line - PSK improves the performance of Scrum teams, but WiP must be optimized for flow and work in progress should not relatively age compared with other in progress items

Bottom line - WiP limits must be applied to improve flow of the delivery of value. It's a key lever to improve the performance of Professional Scrum Teams, and it's required by the Kanban Guide for Scrum.

The fundamental result of Little’s Law is that for a given process, in general, the more things that you work on at any given time (on average) the longer it is going to take for each of those things to finish (on average). As a case in point, managers who are ignorant of this law panic when they se...