Also see "On Risk and Estimating and Agile Methods". This post is yet another angle on a common theme.
Software risk management has two sides. First, there's the classical meaning of risk, we'll call that "casino risk" because it's really random events. This includes …
Got an email looking for help in attempting break through the RDBMS Hegemony. It's a little confusing, but this is the important part of how management says "no".
"Their response was nice but can you flush [sic] it out more"
[First: the word is "flesh": "flesh it out." Repeat after …
more ...See The Question of Risk.
Also, see Lean Projects -- Not Deficient Projects.
And Keeping the Customer Satisfied.
These are notes for a long, detailed rant on the value of Agile methods.
One specious argument against an Agile approach is the "risk management" question. In this case, however, it becomes a …
more ...Tweet:
People criticize for making tons of small classes instead of fewer larger classes.How is well-organized code more difficult to understand?
—jim christopher (@beefarino) May 31, 2013
This isn't really a question. Writing a few "large" omnibus classes is simply bad design.
There are several variations on the theme …
more ...Read this Computerworld posting: Should the CIO know how to code? The answer is "Yes." The examples of "well-functioning non-technical CIOs" are people as rare as hen's teeth. "These are leaders who know what they don't know. They are good at asking the right questions, probing for further insight, and …
more ...Tweeted by @brennandunn: Why Software Development Estimations Are Regularly Off.
"In reality, most projects worth doing are not repetitions of previous things."
Thank you for that.
If it has been done before -- same problem -- same technology -- then we should be able to clone that solution and avoid creating a software …
more ...Read this in Forbes: "Innovation's Return on Failure: ROF".
Also, this: "The Necessity of Failure in Innovation (+ more on CDOs)".
This, too: "Why innovation efforts fail".
While we're at it: "Accepting Failure is Key to Good Overall Returns on High-Risk Development Programs".
I can't say enough about the value of …
more ...See this Limitations of Agile Software Development and this The Agile "Religion" -- What?.
What's important is that the limitations of Agile are not limitations. They're (mostly) intentional roadblocks to Agile.
Looking for "limitations" in the Agile approach misses the point of Agile in several important ways.
The most important problem …
more ...I really dislike being asked to plan a project. It's hard to predict the future accurately.
In spite of the future being -- well -- the future, and utterly unknowable, we still have to have the following kinds of discussions.
Me: "It's probably going to take a team of six."
Customer: "We …
more ...