Agile Principle 3: Deliver working software frequently


I’m not a fan of Agile. I am a devotee of the principled, disciplined, historical stance/philosophy that originally was known as Agile. A bunch of opportunistic entrepreneurs came in and commercialized it into something barely recognizable and ludicrous. I hate that kind of Agile. When teams do ceremonies like sprints and retrospectives without exercising wisdom in their practice it is a tragedy not a cause for celebration.

With that disclaimer out of the way here is principle #3 of the Agile principles:

Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.

Is Agile flat, or vertical?

Is Agile flat or vertical? Flat! It should be flat. Why do you think there aren’t supposed to be any titles in Agile? Why do you think the Scrum Master is merely there to facilitate communication?

Because none of the other people in your agile team should be there to tell you what to do. Instead, they are all there to help the team achieve its goal. That includes you. Your purpose is also to help the team achieve its goal. Continue reading “Is Agile flat, or vertical?”

Principles of Agile Software: 2

“Welcome changing requirements, even late in
development. Agile processes harness change for
the customer’s competitive advantage.”

Read the Principles of Agile Software

Changing requirements are a given. The law of nature itself dictates that requirements will continue to change. It is the result of the continuously changing landscape of your business. The beauty of Agile is that it recognizes these laws and builds in principles that address them.

I’ll leave you with two questions. When requirements change, what is your first reaction? How can you create and maintain a welcoming posture towards changing requirements in your organization?

Release as Often as Possible

I have written a short paper – Release Often – about why there is a common theme of fast release cycles in many prominent software movements such as RERO, Lean, XP, DevOps, and Continuous Delivery. There is an accompanying Prezi presentation deck below. I presented the talk at Seattle University this past week in our Software Economics class.

Here is a link to the paper:


And the Prezi: