|
|
|
|
| LEADER |
00000cam a2200000 7i4500 |
| 001 |
0000053601 |
| 005 |
20090303093000.0 |
| 008 |
090226s2006 nju eng |
| 020 |
|
|
|a 0321336623 (pbk.)
|
| 020 |
|
|
|a 9780321336620 (pbk.)
|
| 090 |
0 |
0 |
|a QA76.758
|b .B463 2006
|
| 100 |
1 |
|
|a Bennatan, E. M. [
|q (Elli M.)] ,
|e author
|
| 245 |
1 |
0 |
|a Catastrophe disentanglement :
|b getting software projects back on track
|c E. M. Bennatan
|
| 260 |
|
|
|a Upper Saddle River, NJ :
|b Addison-Wesley ,
|c c2006
|
| 300 |
|
|
|a xii, 270 p. :
|b ill. ;
|c 24 cm.
|
| 504 |
|
|
|a Includes bibliographical references (p [245]-253) and index
|
| 505 |
0 |
|
|a .1 An introduction to catastrophe disentanglement -- 2. When a project a catastrophe? -- 3. Step 1-stop -- 4. Step 2-assign an evaluator -- 5. Step 3-Evaluate the project -- 6. Step 4-evaluate the team -- 7. Step 5-define minimum goals -- 8. Step 6-can minimum goals be achieved -- 9. Step 7-rebuild the team -- 10 Step 8-risk analysis -- 11. Step 9-revise the plan -- 12. Step 10-create an early warning system -- 13. Epilogue: putting the final pieces in place
|
| 650 |
|
0 |
|a Software engineering
|
| 856 |
4 |
1 |
|3 Table of contents only
|u http://www.loc.gov/catdir/toc/ecip066/2006000158.html
|
| 999 |
|
|
|a 1000119757
|b Book
|c OPEN SHELF (30 DAYS)
|e Tembila Campus
|