Category Archives: Key problems

Advice from an experienced successful PO

I was doing a course with Dave Muldoon in Ottawa. And Rich O’Grady visited us. He had become a very successful product owner in a difficult environment where others had failed.  He mentioned 6 ‘top tips’ that day, and then he wrote me explaining them a bit more.  What he wrote was pretty much what […]

Read More »

What’s wrong with that impediment list?

Let’s pretend that the impediment list I just posted (the one from the Charleston class) was a real public impediment list for your team. What would be wrong with it? First, the most important thing to say is: GREAT!  Finally, a public list of key things to work on.  And, if we worked hard on […]

Read More »

At first, when Scrum and when Waterfall?

When your company is first starting Scrum, how do you decide which projects use Scrum and which ones do it ‘the old way’?  (Let’s assume the old way is a form of waterfall. You are waiting to transition them from waterfall, later.)  Assuming for now (for a transition period) some projects must remain in waterfall. […]

Read More »

Enabling Specifications

I recommend using the ‘Enabling Specification’ practice. This is NOT part of the bare framework of Scrum. But it is a frequently recommended practice. Typically recommended. This is: Just-enough, just-in-time documentation. Meaning that the implementers in the Scrum Team have enough information to build the user story correctly the first time. Or at least they […]

Read More »

Why I prefer ScrumBan to Kanban

I have spoken about why I like Lean and why I like ScrumBan, a combination of Scrum and Kanban. Some people prefer ‘Kanban’, as it is being called in the software development community.  Sometimes: Kanban Method. To be honest, I think I know what Kanban is in Lean Manufacturing. But I am unsure what ‘Kanban’ […]

Read More »

Story Points rather than hours

Jeff Sutherland has a great post about this, here.  A must read.    

Read More »

‘They still want us to deliver too much in too little time!’

In a class, we had a large group of people from one company.  The company is doing or getting close to doing mostly Scrum. The managers and the Board have not attended a Scrum class. In any case, ‘management’ is still asking the Teams to deliver too much in too little time.  Both say the […]

Read More »

Why should the PO attend the Daily Scrum?

Umm. Good question.  We partly discussed this in an earlier post. First, the Scrum Guide (2011) does not require that the PO attend the Daily Scrum.  If you asked Jeff Sutherland his preference though, he would say it is better if the PO attended regularly. OK, but why? Well, first, the Team needs to know it […]

Read More »

Leading Fearless Change Workshop – Apr 12th!

I recommend that all agile advocates and all ScrumMasters and Product Owners learn more about making change happen. Change both in the large ( the organization adopting Scrum or better) and in the small (changing to fix each impediment). Mary Lynn Manns will be leading a 1-day workshop on change. In Charlotte. April 12th. I […]

Read More »

Making Change Happen

Things need to be a lot better at work.  And they can be, in every way. Thus, we need for people or the organization to change.  And we hope we know the direction. And we hope we know the specific changes. In Scrum, we believe in fairly big changes. In Lean these are called kaikaku.  […]

Read More »