Chapter 3 Expectations
What It Means for Software to Succeed
Chapter contents
- Introduction 32
- Software Development Sometimes (Accidentally) Succeeds 32
- Is Aligned with Business Needs 32
- Manages the Cost of Change 33
- Is Built in an Automated Way 33
- Factors Quality into the Core of the Process 33
- Is Not Constantly Being Redeployed 34
- Progress Is Constantly Being Made 34
- Delivers Something of Value 34
- Is Evangelical 34
- Is Predictable 35
- Is Both Tactical and Strategic 35
- Is Game Changing 35
- Allows Management to Stay Informed 35
- Is Measurable 36
Introduction
Sometimes—despite everyone’s best efforts to prevent it—software succeeds. This chapter discusses a few definitions of what “successful software” is. Because this topic is discussed extensively ...