Category Archives for Agile

Pricing of technical debt

I talked recently about technical debt and the importance of cleaning it up via regular refactoring. This article will explain the pricing of technical debt and why we should do it. Any information system will probably at some point suffer from large scale or “macro” technical debt. This often happens when a project is implemented […]

Continue reading

Refactoring and technical debt

Importance of refactoring Refactoring and technical debt are important concepts, especially so in agile software development. What are they? Refactoring is modifying the internal structure of code without changing its behaviour. All functional tests should pass with the same results after the code has been refactored. If it behaves the same, why do we need to do it? […]

Continue reading

Scrum-but and Agile anti-patterns

There are many stories and anecdotes about Scrum-but and agile anti-patterns. If you’re wondering about the term,  it comes from the idea “we’re doing scrum, but we” [do something that is completely the opposite of what it says to do in Scrum]. Here are some common ones to look out for. Big up-front design “We […]

Continue reading

Misconceptions around Minimum Viable Product

One of the most controversial topics in Agile / Lean thinking at the moment is the Minimum Viable Product, or MVP. This article will try and clear up the misconceptions around Minimum Viable Product. This concept came from Eric Ries’ influential book, The Lean Startup. In that book, Ries suggests that startups should not focus on […]

Continue reading

Theory of constraints in Agile

A concept from Management Theory called “theory of constraints” has become popular in Agile and Lean circles. The theory is quite simple. This article will explain the theory of constraints in Agile, in a micro and macro context. In any given system, there will be one component that is the constraint or bottleneck for the […]

Continue reading

What does a cross-functional Agile team look like?

Although not declared in the Agile Manifesto, pretty much any Agile advocate will tell you that you need cross functional teams in Agile. What does that mean exactly? How wide does the scope of the team’s skills need to be? This is an interesting question and one that touches on organisational design, DevOps, HR, and a […]

Continue reading

Estimating defects in Agile is an anti-pattern

There is a lot of discussion in the Agile community about estimating defects. A lot of people seem to think you need to estimate defects. There are lots of people arguing about how to estimate defects. I think that estimating and assigning story points to defects is an anti-pattern and a dangerous practice for three simple […]

Continue reading
1 4 5 6