Let’s talk about #NoEstimates

Should we expect estimates for software development? There’s a movement called “No Estimates” that suggests there is a better way to develop software without using estimates as part of the process. In an interview with InfoQ, Woody Zuill states, “Personally for me, what No Estimates is about, is alternative ways to make decisions, that don’t require that we use estimates.” Read More …

Classic IT Challenges – Understanding Project Complexity

This is the fifth post in a series of writings to discuss issues facing Information Technology (IT) departments. If you have not read any of the first four challenges you can find them under project work vs production support, prioritizing work, operations vs innovation, and estimating work. IT shops vary in size, budget, and processes. But all IT shops share a common Read More …

Classic IT Challenges – Estimating Work

This is the fourth post in a series of writings to discuss issues facing Information Technology (IT) departments. The first three challenges were project work vs production support, prioritizing work and operations vs innovation. IT shops vary in size, budget, and processes. But all IT shops share a common set of challenges that shape how they interact with their inter-company Read More …

The most powerful step in software development

What’s the most powerful step in a software development process? It’s not uncommon for analysts to label steps in a process. The critical path, bottlenecks, waste, and non-essential steps come to mind.  So I would say that common wisdom agrees that all steps in a process do not hold equal weighting of importance. Maybe there isn’t a single most powerful Read More …