- Agile Leadership Development
- Product Owner
As I train and coach Scrum across the country, I’m often struck with the power how certain words can create a sense of fear in people. In my experience, no word creates as much fear as ‘commitment’. Yet commitment is one of the five Scrum Values per the Scrum Guide! IMHO, that’s a problem.
Do you ever get so frustrated you feel like pulling your hair out? I do (although that is NOT a picture of me to the left!). If you look at my pictures you will see that it would be difficult for me to pull my
Earlier this week I posted a blog entry “Agile antipattern: Burndown charts that hide the truth” which dealt with one way a burndown chart could hide reality. This blog entry shows another way it is possible for a burndown chart to be misleading. The
Time for a short blog entry (I tend to be way too verbose!). I often see teams trying to make sure they have all of the requirements for their projects before they start doing any substantive work on the project. Unfortunately, this often leads to long delays at the front of the process which in
Wow, has it really been more than a month since I posted something on my blog? Ouch! I guess I’ve been busier than I thought. I knew it had been a while, but I thought it was 2 weeks, not a month. For those of you who expect content from me more often, I’m sorry.
Yesterday’s blog post dealt with how to manage scope for an agile project. Today I have to admit it was a bit of a setup. It was designed to set up today’s blog post which is really the important one!
See that pile of money over there
The primary way I see teams release products faster is by reducing the scope of each product. However, this can’t be done in an arbitrary fashion. There are real business reasons for each feature request (hopefully anyway!). Having seen teams reduce scope successfully I’ve seen three primary ways it can be done. In order to
No. Only two letters. Very simple word. Yet for some reason, with the exception of when we are at “the terrible 2’s” stage of life we tend to forget how to say it! Agile teams and organizations need to remember how to say no! Too often agile organizations don’t get the full benefit of an