Community Blog

Peut-on parler de management en Scrum?

In this blog post, PST David Sabine shares a real life story focused around transparency.

The Project Mindset approach, in which success is defined upfront based on Scope, Time and Budget, will (based on experiences) lead to less business involvement and more task management. The Product Mindset approach, in which success is continuously driven by business metrics like User adaption/retention, revenue cost saving per feature, will (based on experiences) lead to less waste, more creativity and more releases.

In this Unstuck Careers Leadership Moment, PST Mark Wavle explores the question, "How do I know if my measures are the best ones?"

Penser, agir, décider en tant que manager agile

There are loads of blog posts, articles and podcasts about agile - what it should be, what it should do, how it should look? The problem is that a lot of what’s out there is hypothetical and not based on field experience.

The term organizational agility is everywhere these days, but what does it really mean? Can we even define it at all? Deepen your understanding of the manifesto and why it is essential to implementing healthy agile that delivers meaningful value.

In the Peoples And Teams section of the Professional Scrum Master course, we discuss the impact of Task Switching. We discuss that task switching destroys efficiency and quality. 

The more Scrum Teams are empowered to make and own decisions about their work, the more benefits they will realize.

Since the Industrial Revolution, increasing competition has driven businesses towards strategies that preserve and increase their market share.

The Scrum Master tactics series are a series of articles in which I write about and explore contemporary techniques that will aid you in your journey as a Scrum Master. The tactics explained stem from my personal experience as a Scrum Master which I accumulated over the years in working with many different teams and contexts.

The Agile Transformation Kata is for example such a practice that reinforces an agile mindset during an agile transformation, and through many reflection cycles allows to adapt to new emerging needs, like COVID-19.

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.

Many thanks to attendees at my PAL-E workshop in London on 26-27 October who reviewed & debugged my change story for "what is organizational agility?"

The term Agile Transformation is often mingled together with a series of other things, for example a business transformation or a digital transformation. These are however very different things.

Teams often run through the motions of Scrum and get very hung up on story points, velocity, committed percentages and as a result struggle to deliver value. But what I’ll share today is what unlocks the value of Scrum;

Imagine for a moment what frequently asked questions around agile transformations look like. Which questions do you hear most often as it seems agile transformation has been a hot topic lately?

Why is it that when the going gets tough, “agile” gets the blame? There is so much online bashing of [insert random agile framework or method] going on, that it made me wonder if there is a pattern behind it. I believe there is.

“We want to be more agile in our delivery.” “We need to build up our teams.” “How can we do Scrum well?” Companies are asking themselves these questions every day and looking in various places for the answers.

The traditional approach of RFI – RFP – Review – LOI is neither lean or agile. The Lean Agile Procurement approach reduces the sourcing cycle time to days, with collaborative clarification of the product with prospective partners while reducing the risk of a poor partner and company evaluation.

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

Overcome common transformation mistakes and enhance your agility.

Often I hear people say that Scrum does not take care of risk: there is no risk log, risk is not on the agenda of the Sprint Review or Retrospective as a standard agenda-item. The Development Teams need to be accountable for the quality of the product and how it's made. That's a risk right there! If there is not one person accountable for quality, being on time, within budget, building the right thing... How is risk managed in Scrum?

The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of them and knows when and how to apply them, depending on situation and context. Everything with the purpose of helping people understand and apply the Scrum framework better.

Are you a Manager that believes in the power of Scrum? There is a difference between thinking, believing and knowing. Don't miss out on a huge opportunity to become the next market leader in your space.

I have found that coaching managers is a different approach than with Scrum teams. While you are (most of the time) involved directly with the Scrum Team as a Scrum Master, managers are less accessible.