On the subject of Technical Debt, Martin Fowler identified a TechnicalDebtQuadrant in which technical debt is classified as either Deliberate or Inadvertent and either Prudent or Reckless. He then makes the case that software projects can reasonably see all four combinations, including Prudent/Inadvertent — even though he can’t think of a real-word analogy that can be used to describe it to management.
How about this? Continue reading Prudent/Inadvertent Technical Debt
One early, easy win to be had when organizing a new Scrum team is to let the team members name their team. It takes less than five minutes out of the first Scrum planning meeting, but gets team building and camaraderie off to a great start.
Encourage everyone to come prepared with at least one name suggestion each, along with a slogan for each name. Winning names always seem to have a catchy slogan.
If you use Bugzilla, here’s a quip for your quips file:
Seeing "Null Pointer Exception" in a log4j log is like smelling a fart in a crowded room. You are painfully aware there's a problem, but the culprit is never obvious.