The Lorax spoke with passion, knowledge and concern. So should every PO!

Agile lessons from the good Dr? Sure, why not? He wasn’t specifically writing for agile folks but there are lessons there… if you know where to look.

Even though agile can be pretty lightweight, there are still laws...

And why this is THE reason for feature teams…

Not only IS failure an option, it's the best opportunity for your teams to learn!

Creative teams can learn best from the new things, not from repetition. Because of this you need to create an environment where creative failure is NOT failure, but a learning opportunity…

What is the ONE part of the Scrum framework that actually makes the whole thing tick?

Boson: A force-carrying particle of elementary physics.

What is the part of Scrum that holds the whole shebang together?

Builders view their work VERY differently than everyone else; and that's a really good thing.

I believe that the “Builder’s View” is the single most important concept you’ll come across this year. Bold statement? Sure, but I’ll stand by it.

Many parts of Scrum break down into a dichotomy between Product and Process.

What is the differences between product and process?

For members of the build team, an overly-involved SM can look like this...

How a major, high-risk blocker put a huge grin on my face.

Estimate can be like gazing into a crystal ball, is there a better way?

Agile is about speed, right? Then why do we waste so much time estimating?

This monkey may look angry, but he's got a super-cool name!

Fail fast, sure, but proactively shooting my products in the head!?!

A closed backlog? What? I mean we all know that agile changes.

Betas have a subtle, beautiful effect on your team. Read on...

Lately the Agile Community has been so headstrong on fitting Agile methodologies into any and every situation that I think that many times we miss asking the question, “SHOULD Agile go in there?”