The Software Development Edge: Essays on Managing Successful Projects

Table of Contents:

About the Author.

Foreword.

Preface.

I. GENERAL MANAGEMENT.

1. Beginning at the Beginning.

    The Importance of Good Software.

    Hard Rocks in the Swamp.

    Audience.

    The Iterative Problem-Solving Clock.

    Recap.

2. Computational Roots.

    The Precipitator.

    The Answer.

    How This Program Worked.

    Why Was This Generation of Engineers Special?

    Computation.

    Getting to Know the Numbers by Their First Names.

    So How About Those Computers?

    Our Computational Heritage.

    Recap.

3. Mountaineering.

    On Climbing Big Mountains.

    Common Causes of Failure.

    Ingredients for Success.

    The Human Factor.

    Recap.

4. Managing.

    Managing Teams.

    Recap.

II. SOFTWARE DIFFERENCES.

5. The Most Important Thing.

    Iterative Development.

    Roscoe Leroy.

    Going Over the Waterfall.

    The Other Extreme.

    Roscoe’s First Picture.

    Roscoe’s Second Picture.

    Wait a Minute!.

    Keeping the Vectors Short.

    The Application to Software Development.

    Applied Learning and Short-Vector Direction.

    Risk Targeting.

    Have You Heard This One Before?

    More on Applied Learning.

    Business Implications.

    The Staffing Effect.

    Just Plain Horse (shoe) Sense.

    Recap.

6. Modeling.

    How to Explain the UML.

    What Is the UML, and Why Is It Important?

    A Second, Less Trivial Example.

    The Third Example.

    And Now for the Relevance to Software…

    Raising the Level of Abstraction.

    Recap.

7. Coding.

    How Managers Can Learn a New Programming Language.

    The Problem, Better Defined.

    What Should the Standard Problem Contain?

    The Animal Game.

    Does the Animal Game Fit the Criteria?

    Does It Pass the “So What?” Test?

    It’s Your Game.

    Recap.

8. Getting It Out the Door.

    If You Build It, They Will Come.

    In the Beginning, There Was the Sandbox.

    Why Should the Product Build Be Hard, Anyway?

    What About Iterative Development?

    Recap.

III. THE PROJECT-MANAGEMENT VIEW.

9. Trade-Offs.

    The Project Pyramid.

    Five, Not Four.

    Enter the Pyramid.

    The Altitude Variable.

    The Pyramid’s Volume Is Constant.

    A Statistical Interlude.

    Right Idea, Wrong Distribution.

    Implications for Real Projects.

    What Does It Take to Get to a Coin Flip?

    More Confidence.

    Important Caveats.

    It’s All About Risk.

    Recap.

10. Estimating.

    What If We Used Common Sense?

    Chocolate Versus Vanilla.

    Roscoe Explains.

    Roscoe Goes Deeper.

    Roscoe’s Calendar.

    Roscoe Computes.

    Roscoe Gets into Software.

    Roscoe Reports In.

    Guess We Did Something Right.

    Roscoe Sums It Up .

    Roscoe Picks a Bone.

    Guess We Did Something Right, Part Two.

    Roscoe Admitted to Software Project Manager Fraternity.

    Recap.

11. Scheduling.

    Roscoe Poses the Problem: How Late Are You Gonna Be?

    Joe Makes a Slight Comeback.

    Roscoe Returns.

    Roscoe’s Rogue’s Gallery.

    Roscoe’s Graph.

    One Last Objection.

    Roscoe’s Parting Shot.

    Recap.

12. Rhythm.

    A Physicist Looks at Project Progress.

    Reality Intrudes.

    What About Iterative Development?

    One Last Graph.

    Recap.

IV. THE HUMAN ELEMENT.

13. Politics.

    Context.

    Definition.

    Three Scenarios.

    Politics Is Inevitable, But…

    When Things Get Political.

    The Engineering Mapping.

    High-Trust Environments.

    Other Variants of Bad Politics.

    Recap.

14. Negotiating.

    Communication Is Everything.

    Roscoe Explains His Theory.

    Are We Done Yet?

    Recap.

15. Signing Up.

    Roscoe Gets His Nose Bloodied…

    …And Immediately Cuts to the Chase.

    Vesuvius Erupts.

    How They Do It in Texas.

    The Relevance to Software.

    The Dog Ate My Homework.

    Spec Wars?

    The Three Most Common Excuses.

    And Another Thing…

    Thrust, Parry, and Riposte.

    Large Project Chicken.

    The End of Software Development as We Know It?

    Elaboration Versus Construction.

    Tough Love.

    Recap.

16. Compensation.

    Going for the Flow.

    Flow and Software Development Performance.

    Applying the Flow Model to Compensation.

    Money Isn’t Always the Answer.

    Recap.

V. THINKING LATERALLY.

17. History Lesson.

    Don’t Let the King Be Your Architect.

    Things Aren’t Always as They Seem.

    Checking the Design.

    Knowing What You Don’t Know.

    Continuity of Leadership.

    In a Hurry, As Usual.

    Focusing on the Wrong Features.

    When the Design Is Bad…

    The Relevance of Testing.

    Prototype Versus Product.

    The Inquest.

    Recap.

18. Bad Analogies.

    Houston, We Have a Problem.

    Fig Newtons.

    Everything’s Relative.

    Quantum Nonsense.

    Heat Death.

    Other Examples.

    Good Science.

    Recap.

19. The Refresh Problem.

    Refreshing Embedded Software.

    The Current Situation.

    The Software Upgrade Game.

    A Modest Proposal.

    Software Upgrades, Revisited.

    Some Nice Things Come for Free.

    Why This Will Work.

    Refinement.

    What About Software Piracy?

    Until the Sun Takes Over.

    Recap.

20. Not So Random Numbers.

    Roscoe Sets the Stage.

    Simulating the Batter.

    First Steps.

    Second Steps.

    Generating More Probabilities.

    Of Course, We’ve Already Left the World of Baseball.

    Reality Is Ugly.

    Monday’s Solution.

    Lessons Learned.

    Recap.

VI. ADVANCED TOPICS.

21. Crisis.

    The Five Days of the Fish.

    The Fish Market.

    Day 1: Unaware.

    Day 2: Avoiding the Issue.

    Day 3: Enter “The Fixer”.

    Day 4: The Turning Point.

    Day 5: Two Critical Paths.

    Moral of the Story.

    Recap.

22. Growth.

    Growth Issues.

    The Naïve Model.

    Consequences of the Model.

    An Illustrative Example.

    Non-Linearity.

    Call to Action.

    Conclusions.

    Nomograph.

    Spreadsheet.

    Recap.

23. Culture.

    What Is a Culture?

    Strong and Weak Cultures.

    Defining Corporate Values.

    And the Applicability to Software Is…

    Building a Strong Culture.

    When You’re Looking for a Job…

    The Bottom Line.

    Recap.

24. Putting It All Together.

    Schlepper.

    Macher.

    Mensch.

    More on Mensches.

    Population Distribution.

    Some Final Thoughts on the Model.

    Recap.

Acknowledgments.

Index.

目錄：

關於作者。
前言。
序言。
I. 總體管理。
1. 從頭開始。
- 優秀軟體的重要性。
- 沼澤中的困難。
- 讀者群。
- 迭代問題解決時鐘。
- 總結。
2. 計算根源。
- 沉澱劑。
- 答案。
- 這個程式是如何運作的。
- 為什麼這一代工程師很特別？
- 計算。
- 通過名字認識數字。
- 那麼電腦怎麼樣？
- 我們的計算遺產。
- 總結。
3. 登山。
- 攀登大山。
- 失敗的常見原因。
- 成功的要素。
- 人的因素。
- 總結。
4. 管理。
- 團隊管理。
- 總結。
II. 軟體差異。
5. 最重要的事情。
- 迭代開發。
- 羅斯科·勒羅伊。
- 跳下瀑布。
- 總結。