If you've read the last few of my Advisors on Google Glass and Babel fish, you will have noticed that I've been more than a little overwhelmed by the speed with which technological change is outstripping my limited sci-fi-augmented imagination. Some of the products that I was forecasting to be years away (like real-time translation of speech in one language to another) are actually going to be available (in beta form, at least) as early as the end of this year. So the possibilities are really getting interesting.
At a recent conference on software measurement, several industry experts, including Tim Lister, Tom DeMarco, Bob Grady, and David Card, were asked to discuss the software triangle: should the focus be on people, process, or technology?
After more than five years of agile software development, we understand its nuts and bolts pretty well: we know how to build software in an agile manner; we know how to set up an agile team; we have built an impressive set of powerful support tools
After more than five years of agile software development, we understand its nuts and bolts pretty well: we know how to build software in an agile manner; we know how to set up an agile team; we have built an impressive set of powerful support tools
In this month's CBR, we take on a classic issue: software estimation. It's a classic because it looks, on the surface, like something we ought to have figured out by now. There's a "way it's supposed to work" that looks plausible.