Late deliveries are a nightmare—especially if you are ”the face” of the team and you have to explain the reasons for it to either your customer or end users.  In this post I intend to list three reasons why your project might be late and some suggestions to a) fix it and b) avoid the same problems in the future.

Traditional code reviews are not much fun, particularly for the author.  They are very valuable, but can easily devolve into a bashing session.  Using the Charrette Protocol could be a more effective alternative that leaves the author in control and makes it more fun for everyone involved.  The charrette is also more in-line with Agile practices.

Here's an actual, practical example of how a company can come up with better solutions by applying Agile principles throughout their business.

Scrum, unit testing, code reviews and automated daily builds practices are not an end—they’re just the means to creating quality products, on time, every time.

“Are we going to make it on time?”  This is the unspoken question that CEOs of software product companies ask themselves day in and day out.  The “wrong” answer can kill your chances of making it through this economy.