Refactoring to Agility 

1 2

• 1. Refactoring to Agility

• 2. Table of Contents

• 3. Copyright

  Copyright Dedication

• 4. Chapter 1. Introduction

  Chapter 1. Introduction

• 5. Section 1.1. Agile and Plan-driven Methodologies

  1.1. Agile and Plan-driven Methodologies

• 6. Section 1.2. How Time-boxed Iterations Help Us Handle Change

  1.2. How Time-boxed Iterations Help Us Handle Change

• 7. Section 1.3. Managing the Risk of Transitioning to Agility

  1.3. Managing the Risk of Transitioning to Agility

• 8. Section 1.4. Phased Transition and Refactoring to Agility

  1.4. Phased Transition and Refactoring to Agility

• 9. Section 1.5. Outline of This Book

  1.5. Outline of This Book

• 10. Section 1.6. References

  1.6. References

• 11. Chapter 2. What Is Agility?

  Chapter 2. What Is Agility?

• 12. Section 2.1. Agility Is Not Binary

  2.1. Agility Is Not Binary

• 13. Section 2.2. How Much Agility Is Realistic Today?

  2.2. How Much Agility Is Realistic Today?

• 14. Section 2.3. What Do We Need to React to with Agility?

  2.3. What Do We Need to React to with Agility?

• 15. Section 2.4. Agility Is Not an End State

  2.4. Agility Is Not an End State

• 16. Section 2.5. Agile Values

  2.5. Agile Values

• 17. Section 2.6. Agile Teams

  2.6. Agile Teams

• 18. Section 2.7. Agile Management

  2.7. Agile Management

• 19. Section 2.8. References

  2.8. References

• 20. Chapter 3. Phase 1Getting to Fixed-length Development Iterations

  Chapter 3. Phase 1Getting to Fixed-length Development Iterations

• 21. Section 3.1. Start with the Coding Phase

  3.1. Start with the Coding Phase

• 22. Section 3.2. Plan and Release FunctionalityNot Components

  3.2. Plan and Release FunctionalityNot Components

• 23. Section 3.3. Example of Planning by Functionality

  3.3. Example of Planning by Functionality

• 24. Section 3.4. Is It Refactoring or Rework?

  3.4. Is It Refactoring or Rework?

• 25. Section 3.5. Preparing for Changes That Affect External Entities

  3.5. Preparing for Changes That Affect External Entities

• 26. Section 3.6. Common Pitfalls of Phase 1

  3.6. Common Pitfalls of Phase 1

• 27. Section 3.7. Evidence That Phase 1 Is Complete

  3.7. Evidence That Phase 1 Is Complete

• 28. Section 3.8. References

  3.8. References

• 29. Chapter 4. Phase 2Measuring the Process

  Chapter 4. Phase 2Measuring the Process

• 30. Section 4.1. Using Metrics to Affect Behavior

  4.1. Using Metrics to Affect Behavior

• 31. Section 4.2. Agile Metrics Philosophies

  4.2. Agile Metrics Philosophies

• 32. Section 4.3. What Is The Goal?

  4.3. What Is The Goal?

• 33. Section 4.4. What Should We Measure?

  4.4. What Should We Measure?

• 34. Section 4.5. Techniques for Defining Other Metrics

  4.5. Techniques for Defining Other Metrics

• 35. Section 4.6. Deploying Metrics

  4.6. Deploying Metrics

• 36. Section 4.7. Conclusions

  4.7. Conclusions

• 37. Section 4.8. References

  4.8. References

• 38. Chapter 5. Phase 3Refactoring the Process

  Chapter 5. Phase 3Refactoring the Process

• 39. Section 5.1. Are We Ready for Optimization?

  5.1. Are We Ready for Optimization?

• 40. Section 5.2. What Is a Process Smell?

  5.2. What Is a Process Smell?

• 41. Section 5.3. Picking Which Smell to Work On

  5.3. Picking Which Smell to Work On

• 42. Section 5.4. Making the Selected Change

  5.4. Making the Selected Change

• 43. Section 5.5. Measuring the Effect of a Change

  5.5. Measuring the Effect of a Change

• 44. Chapter 6. Process Innovations by Type

  Chapter 6. Process Innovations by Type

• 45. Section 6.1. Planning Innovations

  6.1. Planning Innovations

• 46. Section 6.2. Estimation Innovations

  6.2. Estimation Innovations

• 47. Section 6.3. Process Management Innovations

  6.3. Process Management Innovations

• 48. Section 6.4. AnalysisDesign Innovations

  6.4. AnalysisDesign Innovations

• 49. Section 6.5. Development Innovations

  6.5. Development Innovations

• 50. Section 6.6. General Process Innovations

  6.6. General Process Innovations

1 2