If you don’t have a baseline, you don’t know where you are starting from. If you don’t know where you are starting from, you can’t create a plan because whatever plan you come up with will be based on something that may or may not exist or may or may not be correct. Baselines set the foundation from where we start, they are ground zero and they are the point from which we move forward…
Good Architects find the bad in a design that you might be in love with and perfectly aligns to your comfort design. They look at what you’ve done and show you where it could fail and point out gaps you might have missed. They are the second set of eyes that raises the game of your code and ensures you are learning new things all along the way. In short, they ensure quality is delivered,…
You can kick off the formation of a Team at the first event. But the building, the trusting, the working, the coming together, the ups, the downs, the failures, and the eventual, actual formation of the team, doesn’t happen till much later, when the team has taken all those small steps to becoming a team. But it doesn’t happen at the end of the first, second or third day, it only starts then.
There is a difference between commenting out code and leaving old code in a solution. It is assuredly impossible for commented code to call because it might never exist (if compiled) or because it is commented, it can never be reached. But when you enter into the practice of deploying code that lives but is never called, rest assured, where there is a code path, there is a way, and that code could at some…
Done, is not always the checkbox on the project plan. Sometimes, Done can be the first step in having an idea of what to do next and creating the spark for the discussion that will ensue. Done can be so much more than what we treat it as today.