Category Archives: Key problems

Dark Scrum – Some comments

We have been talking about this issue for years. Well, we do not entirely agree on what the issue is. Ron Jeffries calls it Dark Scrum. To quote (almost): “too often “Scrum” is used to oppress people”…and he explains that it was his aim that agile would make the world safe for programmers and testers. […]

Scrum and Power

Many organizations are built around power.  It is an old old idea.  Power and hierarchy — I think I was told — goes back to the days of Babylonia.  Roughly 5,000 years ago.  And the birth of the city and of city-civilization.  They needed some organizing principles, so they adopted those. If one has a […]

The Team and Fun

Long ago I took a course on Homo Ludens. Man playing. And the idea was that man is in his most natural state when playing. At least for people who innovate, I think this is true. It may also be true of children. It is not true of ascetics, or those who believe they earn […]

Seven Actionable Ideas for NOW.

I gave the attached talk (see slides) to Agile Midlands last Thursday night. Enjoy! Agile Midlands – NOW ver2    

7 Actionable Ideas Now

This is my outline for a talk with Agile Columbia –  Sept 2018. I made some choices.  You might make different choices.  It certainly does not stand on its own, but I hope you can fill in the blanks pretty well.  Or ask. Start: Here are 7 ideas you can act on today.   Do […]

Velocity: How is it useful?

So, apparently people are doing Scrum and not tracking their Velocity.  Why? One key reason: they do not see how useful it is. Here are some explanations. Helps the SM focus The Velocity is the key metric for the ScrumMaster (SM). The SM should increase the Velocity 100% in the first 6 months.  Which means […]

Velocity: Some preliminaries

It is important to know the Velocity of the team. What is velocity? Each team has a DOD (definition of done).  The Team has small stories at the top of the product backlog. When each small story, which has story points that estimate the relative effort, …when each story is “done-done” per the DOD, then […]

Why not?

Rijon Erickson (sounds like “Ryan”) has an excellent post in LinkedIn. See here:  https://www.linkedin.com/in/rijonerickson/detail/recent-activity/ His (currently) latest posts asks for a DOR (definition of ready) and then a DOD (definition of done) (visually, he uses post-its).  The next post-it says “Simple (but) Not Easy”. To me, he is saying: We should be able to use […]

Waterfall is done. Where is the debate now?

It is important to note that waterfall is over. Dr. Royce defined waterfall in 1970.  See his paper here. His son, Walker Royce, said that waterfall was over, and said we are on to iterative and incremental now.  He said this before we started calling it agile (before the Agile Manifesto was written).  See his […]

Scrum – Observations from Sutherland’s book

Alisha Parry recently read Jeff Sutherland’s book, “Scrum: The art of doing twice work in half the time.” Here are some of her observations that she shared with a work colleague. 1. Bugs take 24x as long after you wait to work on them. We have seen this even on Kronos, as we have previously […]