Empiricism

“Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation." (Ken Schwaber and Jeff Southerland,…

Give Your Retrospective the Time It Deserves

Retrospectives are incredibly valuable and if you’re not doing them regularly, you’re doing yourself and your team a great disservice. Assuming that your teams are actively engaged in development activity, you may not be maximizing the value to its full potential. Great retrospectives can rapidly turn a good team into an even better team, but…

Choosing an Agile Methodology

With so many Agile methodologies out there it can be really tough to know which is the right one, and picking the right one is absolutely critical for your project. It’s critical because each has it’s own niche and each comes with it’s own weight and cost. It is so important that I can’t say…

Heart Monitor of the Agile Team

Traditional project management places a strong emphasis on comprehensive metrics. The general thought is if you can’t measure it, then you can’t control it. While comprehensive metrics has its place, it’s often overused and adds unnecessary weight and complexity to a project. Our experience is the larger the organization, the more layers of metrics there…

Comprehensive Documentation or Muda?

Ah, the age old Agile question: what is the appropriate amount of documentation? The Agile founders gave us the 4 Values and 12 Principles which have guided us from the beginning, and time has proven them to be great guides. The second item in the Agile Values states “Value Delivered Over Comprehensive Documentation.” This value…

Translating the Language of Agile

Users of agile sometimes create their “own version” of Agile terminology to suit an audience or an organization. Sometimes, this is done on purpose to reflect long held business terms. Other times, it’s because they simply didn’t know any better when starting out. While this helps puts terms in the context of a given environment,…

Kanban for Non-IT

If you are pursuing Agile from a non-IT perspective and looking for a good book to get you going on Kanban for “knowledge work”, then you may be wondering - where do I even begin? We are excited that you are looking to move yourself into the Agile world. Kanban is near and dear to…

The Agile Toolbox

Let’s talk about a common problem that is a very real threat to any Agile company or project. We’ve all heard the term “pounding a square peg into a round hole” when something is misused, and I would be willing to bet that we’ve all experienced it. Some of you might be experiencing it right…

Battle of the Century: Technical Debt vs. Feature Development

Our teams are asked quite a bit about performance testing in an Agile environment and how that might differ from the traditional waterfall approach. If you’re asking the same question, you’ve hit on one of the greatest heavyweight grudge matches in world history! Technical debt and feature development have battled for the spotlight since the…