How To Run Successful Projects III. The Silver Bullet 

1 2 3 4

• 1. How To Run Successful Projects III: The Silver Bullet

• 2. Table of Contents

• 3. Copyright

  Copyright British Library Cataloguing in Publication Data Library of Congress Cataloging in Publication Data Dedication

• 4. PREFACE TO THE NEW EDITION

  PREFACE TO THE NEW EDITION

• 5. PREFACE TO THE SECOND EDITION

  PREFACE TO THE SECOND EDITION

• 6. Acknowledgments

  Acknowledgments

• 7. And finally, a note on sexist language

  And finally a note on sexist language

• 8. PREFACE TO THE FIRST EDITION

  PREFACE TO THE FIRST EDITION

• 9. ABOUT THE AUTHOR

  ABOUT THE AUTHOR

• 10. INTRODUCTION

  INTRODUCTION

• 11. The Silver Bullet

  The Silver Bullet

• 12. Permission acknowledgments

  Permission acknowledgments

• 13. Part 1: ANALYZING AND PLANNING PROJECTS

  THE NATURE OF PROJECTS STRUCTURED PROJECT MANAGEMENT: THE TEN STEPS

• 14. Chapter 1. STEP 1: VISUALIZE THE GOAL

  Chapter 1. STEP 1: VISUALIZE THE GOAL; SET YOUR EYES ON THE PRIZE

• 15. INTRODUCTION

  INTRODUCTION

• 16. IDENTIFYING THE GOAL

  IDENTIFYING THE GOAL

• 17. DEFINING THE GOAL

  DEFINING THE GOAL

• 18. THE REASON FOR THE GOAL

  THE REASON FOR THE GOAL

• 19. MOTIVATING THE TEAM

  MOTIVATING THE TEAM

• 20. CHANGES TO THE GOAL AND CHANGE CONTROL

  CHANGES TO THE GOAL AND CHANGE CONTROL

• 21. APPLICATION TO SOFTWARE ENGINEERING

  APPLICATION TO SOFTWARE ENGINEERING

• 22. PSI CONTRIBUTION

  STRUCTURED PROJECT MANAGEMENT PSI CONTRIBUTION

• 23. Chapter 2. STEP 2: MAKE A LIST OF THE JOBS TO BE DONE

  Chapter 2. STEP 2: MAKE A LIST OF THE JOBS TO BE DONE

• 24. INTRODUCTION

  INTRODUCTION

• 25. MAKING A CHECKLIST

  MAKING A CHECKLIST

• 26. IDENTIFYING THE JOBS WITH FORM 1

  IDENTIFYING THE JOBS WITH FORM 1

• 27. APPLICATION TO SOFTWARE ENGINEERING

  EXAMPLE 1: PRELIMINARY PLAN TO GET ISO 9001 CERTIFICATION EXAMPLE 2: PLAN FOR A SOFTWARE ENGINEERING PROJECT APPLICATION TO SOFTWARE ENGINEERING

• 28. PSI CONTRIBUTION

  STRUCTURED PROJECT MANAGEMENT PSI CONTRIBUTION

• 29. Chapter 3. STEP 3: THERE MUST BE ONE LEADER

  Chapter 3. STEP 3: THERE MUST BE ONE LEADER

• 30. INTRODUCTION

  CASE STUDY 1 CASE STUDY 2 CASE STUDY 3 CASE STUDY 4 INTRODUCTION

• 31. A ROLE MODEL

  A ROLE MODEL

• 32. APPLICATION TO SOFTWARE ENGINEERING

  APPLICATION TO SOFTWARE ENGINEERING

• 33. PSI CONTRIBUTION

  STRUCTURED PROJECT MANAGEMENT PSI CONTRIBUTION

• 34. Chapter 4. STEP 4: ASSIGN PEOPLE TO JOBS

  Chapter 4. STEP 4: ASSIGN PEOPLE TO JOBS

• 35. INTRODUCTION

  INTRODUCTION

• 36. EACH JOB HAS A NAME

  EACH JOB HAS A NAME

• 37. PEOPLE S OTHER COMMITMENTS

  EXAMPLE 1 EXAMPLE 2 EXAMPLE 3 PEOPLE S OTHER COMMITMENTS

• 38. MONOLITHIC TEAM OR FLAT STRUCTURE

  MONOLITHIC TEAM OR FLAT STRUCTURE

• 39. HIERARCHY OR TEAM STRUCTURE

  HIERARCHY OR TEAM STRUCTURE

• 40. MAXIMIZE STRENGTHS

  MAXIMIZE STRENGTHS

• 41. ASSIGNING PEOPLE TO JOBS

  CASE STUDY 5 ASSIGNING PEOPLE TO JOBS

• 42. ASSIGNING PEOPLE TO JOBS WITH FORM 2

  ASSIGNING PEOPLE TO JOBS WITH FORM 2

• 43. APPLICATION TO SOFTWARE ENGINEERING

  APPLICATION TO SOFTWARE ENGINEERING

• 44. PSI CONTRIBUTION

  STRUCTURED PROJECT MANAGEMENT PSI CONTRIBUTION

• 45. Chapter 5. STEP 5: MANAGE EXPECTATIONS, ALLOW A MARGIN FOR ERROR, HAVE A FALLBACK POSITION

  Chapter 5. STEP 5: MANAGE EXPECTATIONS ALLOW A MARGIN FOR ERROR HAVE A FALLBACK POSITION

• 46. INTRODUCTION

  INTRODUCTION

• 47. CONTINGENCY: ALLOW A MARGIN FOR ERROR, HAVE A FALLBACK POSITION

  CONTINGENCY: ALLOW A MARGIN FOR ERROR HAVE A FALLBACK POSITION

• 48. MANAGE EXPECTATIONS

  MANAGE EXPECTATIONS

• 49. A WORD ON COMMITTING

  CASE STUDY 6: MANAGE EXPECTATIONS CASE STUDY 7: ALLOW A MARGIN FOR ERROR CASE STUDY 8: HAVE A FALLBACK POSITION CASE STUDY 9 A WORD ON COMMITTING

• 50. APPLICATION TO SOFTWARE ENGINEERING

  APPLICATION TO SOFTWARE ENGINEERING

1 2 3 4