Community Blog

Scrum and agility create frameworks for diversity. A healthy mix of men and women will benefit from this. In this post I want to explain why.

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.

Usually conversation between developers and Product Owner goes around acceptance criteria just to negotiate scope of requirements for one user story, but knowledge and context are not conveyed in the same structured way. User Story Canvas can help Scrum Team to fix these problems by focusing team to confirm more complex aspects.

Even though applying agile processes in that context is often a good and valuable idea, business agility is a much bigger term than that. It means how well an organization is equipped to react to market changes, merging customer needs or other factors that impact the business as a whole. 

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.

The urgency of having the right type of conversation, especially today in a remote setting, has significantly increased overnight. This blog provides a perspective on a particular type of conversation and my own “personal experiences”  that show we need them more than ever.

What is a Product Owner? What are the differences between a Product Owner and Project Manager? Isn’t a Product Owner some kind of an Agile Project Manager? These are some of the questions we often get from people in our Scrum.org classes.

Lean Coffee is a powerful meeting faciliation technique that can be used in coffee shops, conferences, open space, Scrum events or simply replace existing corporate meeting formats.

In this blog, we’ll dive deeper into the topic: “Scrum Master vs Project Manager”. If you’re having a similar question about the Product Owner vs the Project Manager.

The terms "iterative" and "incremental" are used so frequently and naturally in the context of agile that their meaning is no longer challenged.

Part I of this Evidence-Based Management (EBM) blog post series covered a general introduction to show how evidence-based management can be a powerful instrument when being used in agile transformations.

In this article, I want to clarify the need for agility in modern businesses and what agility in organisational design actually is.

Bob and Carl Ferro are the proud owners of Nick’s Bar and Grill in Hollywood Beach since 1980 and this place is an institution in this South Florida beach town to say the least.

Not all companies need to be agile companies. What does it really mean to be an agile organization and how do you know if you need to be one? Watch this short 4 minute episode of Responsive Advisors Agile B-Sides video blog to find out!

I believe there are three things you need to do regardless of the framework, methodology or program you are embracing with your organization.

Katas and patterns go hand in hand and so does the Agile Transformation Kata (ATK) harmonize very well with the organizational change patterns published for example by Mary Lynn Manns and Linda Rising in their book  More Fearless Change.

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?"

Just to set the scene, I haven’t figured this out yet. I can tell you my story, in all its ugliness. It’s based on a real story, but it’s changed significantly from reality to protect the innocent. I hope you still find my account useful.

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.

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.

The core responsibility of the agile leader is creating the right context for the agile teams so they can thrive and self-manage. One of the characteristics of this context is all about ownership. In my book ‘Agile Leadership Toolkit’ I dedicate a whole part to this important topic.

“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 ...

Changing the way we work is extremely difficult — we all know this. It requires us to find novel solutions to wicked challenges, to deal with cultural baggage (‘the way we do things here’) and to bring along the people needed to make a change successful.

Overcome common transformation mistakes and enhance your agility.

I always assume that the people I work with are professionals - and not children. This is why I don’t like maturity models in whatever shape or form. And we’ve got a lot of those in our industry.

One of the most important things we can do to help individuals and teams improve is coach them to embrace the agile mindset. The Manifesto for Agile Software Development provides values and principles to help guide teams in navigating the complexities of product delivery.

One of the regular listeners, Daniel Lachmann-Nishibane, appeared on www.agile.fm after he has participated in one of my recent Professional Agile Leadership (PAL-E) certification courses in Munich Germany.

An executive is a person who owns the strategy or sets the direction of travel or sets justifications for spending. This exec could be the Product Owner for a chunk of the organization.

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 certification.

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.

Why do I think team coaching is a bad idea? Don't get me wrong, I believe team coaching can have a great amount of added value. It’s just that I often find that teams receive coaching while they should not even be a team.

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

What is Agile HR? How HR could support this journey of transformation into an Agile company?

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

As an Agile Coach, you frequently encounter situations which demand quick thinking to get things moving in the right direction. Over time I have found few techniques which come in handy and always keep these in my playbook in case needs arise. This is the third part in the series of tools that I have found useful in my role as Agile Coach – Asking Powerful Questions.

I have created a little exercise that I like to use to help focus the on things we can change, or at least situations to seek out or avoid, to help focus change efforts. The essence of it is summarized in a picture. I call this the agile affinity model, and the dimensions the key drivers of empiricism.

Let’s start with a question. When is the Sprint Planning over? Usually, the first answer that comes to mind is “when the time-box expires”. It is a good answer. However, Sprint Planning is a maximal time-box.

People always as ask me if agile is just for software. Saying agile is just about software is like saying software is just about science. Initially, computer science was about replacing manual processes. Now, it’s about creating human experiences.

One of the recurring Scrum Myth discussions I have with colleagues, teams new to Scrum and those attending training when comparing Scrum & DevOps relate to a misinterpretation of the following paragraph from the Scrum Guide.

One of the arguments used against Scrum and a common misconception at the same time is the idea that quality is traded for speed in Scrum. As a PST with years of experience in Quality Assurance I decided to challenge this myth.

Recently I got asked what I consider the most common challenges with Agile projects. These are projects that have such a high rate of uncertainty and complexity on how and what to build, an Agile approach is necessary.

​

Organizations who don’t understand why they want to become Agile also often take the wrong path to get there. Agility requires empowering teams and helping them make decisions on their own, learning from their experiences as they go.

I’ve spent a lot of time looking at how organizations are using DevOps to improve their software delivery cycle time, their ability to innovate, and their ability to improve quality.

This summer, during the Olympics, the Euro Soccer Championships and the Tour the France, while cheering  in front of the tv, I noticed something in the way teams perform. And it worried me.

If this post resonates with you, please consider spreading the message so we can educate and inspire others.