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.

 I’m not a fan of using story points, however, one way or the other, estimates are a very important step in any project and a key to delivering on-time.  The result of not doing it is downright awful, and everybody in the team suffers the consequences.  In this post I want to share the steps we follow to make estimates.

You are about to start a new project, congratulations!  You are starting an exciting journey where you will gain new experience, learn some lessons and remove some barriers.  You’ll figure out something here and there, but absolutely nothing that you can’t deal with.  Unless, that is, you screw up the whole thing from the very start.  If you are in software development, I bet you know how to do that.  I certainly do.

This is my second posting and I want to talk about how we’ve implemented SCRUM at Nearsoft.