Software Best Practices

That should be the real question that any project should ask. Far too often the purpose of project work is to make lot of different customers happy. We get requirements from every Tom, ***, and Harry, from the business, from marketing, from sales, from the technology gurus, from the people who will have...

If you build EXACTLY what “they” tell you, you do it in the timeframe they ask for, and at the cost they wanted to pay, is that a successful project? The project is On time On budget Delivers the requested functionality No defects The team is ready for the next project Is it successful? “Yes,” you say...

Well, I better rephrase that. The functional part of a requirement is cheap. I can deliver the functional part of a requirement in as little time and in as small of a cost as you like if you let me control the non-functional parts of the requirement. That is a heck of a claim. So how do I back that up...

Steve McConnell put up a post on his lack of a real estimate for a child's fort and how that was related to a software project. I have a similar example of an agile bathroom remodel. The Story Our existing bathroom had a small problem. Water was leaking through cracks somewhere in the older tile...

My daughters like to square dance. They seem to, for whatever reason, really like the petticoats: the layers of fabric that make the square dance skirt get really poofy (as if poofy is a word). To support my daughters, I dance with them since there is a general shortage of males (even if we don't...

I am thinking of going on a crusade against functional requirements. Why? Functional requirements are overblown, over-specified, over-referenced, over-exampled, and we need to get over them. By the over-focus on functional requirements by tools, books, and pundits, we cajole our customers to attempt...