One of the tenets of many mainstream software development processes is proactively managing risk.
Of course this sounds like a good idea, but the question becomes: how do you do it?
I've learned that addressing the riskiest areas in a project first usually creates the biggest returns. This is difficult, however, because most people gravitate to the easy things first.
The problem with going with our natural tendencies is that we can tackle a lot of easy things without actually accomplishing anything of significance. And if the risky thing doesn’t work out as planned we may have to throw away some of the prior work, which is always a major frustration.
I'm curious how my readers manage risk in a software development process. Let me know!
-Judi
No comments:
Post a Comment