Improving the world with software
Better software. Better questions.
Essays on software development, teams and the craft of building things that last.
Essays from April 2009
3 essays from April 2009
-
Does Toyota really use waterfall for software development?
I saw this post and could not resist leaving a comment. Here’s what I wrote as a comment to that post: How can they [Toyota] apply waterfall and be predictive, fast and high-quality? Those are all qualities that waterfall lacks. Predictability is lost because of lack of visibility into quality until it is too late …
-
Marketing fail redux, the Agile Process edition
I was reading a web-site from a “well know” process person/company in the software field (which will remain unnamed) and found the following quote (names changed to protect the guilty): XYZ corporation senior management decided that ABC Unified Process is the way for better quality, higher productivity and lower cost. I can’t begin to describe …
-
The curious case of buttoned-up Benjamin
Benjamin works in a consulting company where there was no dress-code unless the client would have a dress-code. Since most consultants were testers and coders (and you know how we dress) the clients understood not to demand a formal dress code. Then Benjamin’s company changed his boss. The new boss required and insisted on everyone …
Nothing matches that yet.
Keep the conversation going
The essays work best in company. Join the community to keep the questions coming.