Kill a Project: A How-to Guide
I once joined a project that was doomed from the very beginning. The stakeholders wanted the project completed within a timeframe that was virtually impossible to meet. Of course, if you’ve spent some time in the software business, you know that’s standard practice. This case was different because the company had detailed data on an almost identical project, and they tried to game their data.
The historical records indicated that the project could be completed in roughly one year using their five in-house developers. This time, however, they had internal pressure to get it done in just three months. That’s a quarter of the time. So, how do you take a project that you know will need a year and compress it down to ...
Get Your Code as a Crime Scene, Second Edition, 2nd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
