Open Agile Adoption
Open Agile Adoption is an ‘open’ approach to adopting and evolving agile, eg, in a given company. By ‘open’ we mean that we are getting the people that will be ‘changed’ to engage in designing the change. We do not … Continue reading →
Question: How do I implement Scrum?
Question from Denise: My organization has decided to go from Waterfall to Agile SCRUM. I have experience with SCRUM, but very little experience implementing it. I was wondering if anybody has this experience? If so, what were some of the … Continue reading →
Agile Reading for Executives
A recent email I sent, slightly edited. Dear Mike and Mark: You asked for something to give the executives and managers. I might send them “The New New Product Development Game” article (see below). With a short explanation. And then … Continue reading →
Planning Poker Tools
Mike Cohn has the phrase ‘planning poker’ registered. So, this is acknowledgement of that. And, like Kleenex, that’s what we call the thing itself. It no longer has a generic name. And, as some readers know, I like Priority Poker … Continue reading →
What does it mean to be ‘Ready’?
Jeffry Hesse wrote this blog post. And it inspired me to write the post below. The new Scrum Guide says that PBIs (product backlog items) must be well-understood and granular enough (just before going into) for Sprint Planning. And that … Continue reading →
Scrum Values
All of you should be aware of the Agile Manifesto and the Agile Principles. To me, they are not perfect, but they are an excellent expression of many of the key ideas behind Agile. And we should be thinking about … Continue reading →
SAFe, LeSS, DAD, and ScrumPLOP
First, I wanted to say that I feel each ‘large scale agile’ situation is different. The key problems are different. And therefore, the solution(s) should be different. And I like the idea of patterns. This is the patterns idea: “Here … Continue reading →
Why I prefer ‘Release Plan Refactoring’ to ‘grooming’
I was just doing a course with Dave Muldoon in Canada. One of the workshops was scaling. In that context, we discussed release plan refactoring or product backlog grooming. To me, the Scrum community has many definitions of ‘product backlog … Continue reading →
Deliver Faster
Why do we want to deliver fast, and then faster? Well, the first reason is…that’s what the customer wants. The customer is thirsty. They want a drink now. She does not want to wait for 3 months to get a … Continue reading →
What is culture? And do we start to change it?
Some of us in the Agile community think: an organization’s culture needs to change before agile can be fully adopted. This certainly seems to be true. Let’s define this more precisely. The idea is this: Before a company can realize … Continue reading →