Resources

As a new Scrum Master what are some of the things you might want to consider to help you on the amazing journey ahead.

In this vlog, PST Joshua Partogi explains the flow of an effective Sprint Retrospectives with Kanban metrics.

Scrum with Kanban includes a definition of workflow, four practices, and four measures. The first practice is visualization of the workflow. The visualization of that workflow is essentially the Kanban board. 

Every Scrum Team, at some point, will struggle with how to facilitate the Daily Scrum. By using a Kanban Board and Flow Metrics, Scrum Teams can better collaborate on their work, visualize progress towards the Sprint Goal, and form the best plan possible for the day.

In this blog, Mark Kachanov shares a step-by-step guide to introducing WIP limits to a team based on a real-life example.

If you are an agile leader - do you know whether your teams are currently operating at a sustainable pace? Do you care? Would you rather not know because you’re afraid of the answer? 

Supposedly, Confucius said once: "Let’s start fixing the nation with fixing the concepts first". Whether he really said it or not, nobody can be sure. But what is important, I would like to specify the meaning of Kanban. Very often people understand it in their own way and when two people talk to each other about it, they mean two different things.

This workshop was delivered on 2nd September 2021 and focused on introducing the core concepts of Kanban & Flow.

As you know, in Scrum Guide 2020 there is no more prescriptions on how to run the Daily Scrum.

There is a new a new Scrum Guide out - version 2020. What has changed for Scrum teams practicing Kanban?

In business, the quest for predictability is universal. We all want to grab hold of the reality we face everyday and, somehow, bend it to our will.

So you have a couple of Scrum Teams that are working in adjacent areas and you're starting to face some challenges in delivering value in a coordinated integrative way.

With the launch of the Kanban Guide for Scrum teams in 2018, its 4 flow metrics have gained more popularity amongst the Scrum community.

A typical Kanban board shows a series of steps or activities that work passes through. Does this mean that Kanban is only suitable for "linear" processes? Scrum is a proven strategy for addressing complex adaptive problems, so if Kanban is linear, is it an unsuitable complimentary practice to add to Scrum?

Agility is not a state. Agility is an ability to change and respond to an environment you're in as an organization.  Once you realize that a binary Scrum-not Scrum stops making much sense.

The COVID19 pandemic gives us plenty of opportunities to think about uncertainty, complexity, and how to deal with those using Empiricism.

The Old Farmer’s Almanac is the oldest continuously published periodical in North America. It was first published in 1792 by Robert B. Thomas who wanted an almanac “to be useful with a pleasant degree of humor. Many long-time Almanac followers claim that its forecasts are 80% to 85% accurate. 

in today's vlog I am sharing with you how to use Scrum with Kanban.

In this article, we shall investigate why the learning and development of multi-functional specialists in Scrum is the core of organizational Agility and value optimization. Many Development Teams are not collaborating as real teams, but as a collection of narrow specialists focused on "their" tasks (QA, Backend, iOS, Android).

The emergence of the Kanban Guide for Scrum teams has given new metrics and practices to Development Teams on how they can augment their Sprint Backlog to manage their work.

One of the things leaders often say they want most is predictability. Predictability is defined as the consistent repetition of a state, course of action, behavior, or the like, making it possible to know in advance what to expect.

If there is one trend that has surpassed Agile in our profession over the last five years, I would say DevOps would be a good culprit. As we’ve seen an explosion of tools to implement CI/CD in our Scrum teams, we’ve also seen some of our Agile practices being challenged by this new reality.

I’ve been teaching the class Professional Scrum with Kanban (PSK) for the last year now and I strongly believe parts of its content will send some of our current practices and books to the Agile museum.

Somewhere between the CEO and 1st line management level, "you do Scrum, just get it done, how much money you need, and what kind of people you need."  "It's just another framework." Salespeople were saying, "you're doing Scrum magic and making it faster." Sometimes people don't want to change.

In football, the team that wins is the one that gets the ball in the other team’s goal most times. Not the one that runs the most.

Imagine a project with hundreds of people, a lead time in months, few releases a year. You could compare these as large cruise boats or tankers navigating for few weeks in the immensity and emptiness of the oceans and seas and then stopping to ports very far away from each other.

I often wonder about the Trustpilot reviews straight after a workshop. Did I entertain? Did I perform? Were attendees satisfied? Are attendees inspired? It matters. I just think it matters more if the workshop made a difference to the work lives of attendees. I can't take credit. The client does the hard yards.

When working with a flow-based Kanban system there are a few statements that I would suggest most teams should bear in mind.

A few weeks ago we considered the Agile Manifesto from a lean perspective. We saw that it is possible to map the 12 agile principles to the 7 canonical “Lean Wastes” in terms of a mitigation approach.

The legendary Steve Trapps has been talking to me for months about featuring in an interview. So here we are, I finally agreed and we spent 25 minutes talking about me; obviously mainly avoiding being narcissistic.

As part of the Scrum.org webinar “Ask a Professional Scrum Trainer - Martin Hinshelwood - Answering Your Most Pressing Scrum Questions” I was asked a number of questions. Since not only was I on the spot and live, I thought that I should answer each question that was asked again here, as well as those questions I did not get to.

The Kanban Guide for Scrum Teams aims to help Scrum Teams leverage the ideas and practices of Flow and Kanban in a way that is coherent with Scrum as defined by the Scrum Guide.

“A good review from the critics is just another stay of execution” -- Dustin Hoffman

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

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

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.

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.

Some teams of knowledge workers (En.wikipedia.org, 2019) work primarily on complex problems. Scrum operates in the complex problem domain, so it can be a natural choice.

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 previous 3 articles on the Agile Metrics topic, I reviewed some of the most important Agile metrics that ActionableAgile software helps you to get with ease. Here we take a look at the ways the software can help you in forecasting your work.

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 (PSK) by Scrum.org brings that world of fantastic Agile Metrics back to Scrum. In this series of posts I will review those metrics using great software - ActionableAgile, provided by fellow PST, Daniel Vacanti.

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.

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 de historia.

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.

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.