You Are Blamed:
- For bugs
- For escalating costs
- For system unreliability
- For not predicting the future
- For attempting to predict the future
- For not planning far enough ahead
- For planning too far ahead
- For taking too much time to make changes
- For making too many changes too quickly
- For not enough testing
- For too much testing
- For not enough configurability
- For too much configurability
- For not enough system flexibility
- For too much system flexibility
- For implementing too many features
- For implementing too few features
- For team sizes being too large
- For team sizes not being large enough
- For difficulty in training new team members
What's Going On Here?
There are many terms for this situation, depending upon the industry or environment being affected.
The bottom line is that when key factors are present, and when conditions are right, this situation is guaranteed to develop.
You may already be familiar with a number of terms associated with this situation:
- Technical Debt
- Committee (effect)
Fortunately, the factors that lead to this situation can be understood, allowing us to apply specific methodologies for both prevention and resolution.
In the next post, we will begin to discuss these factors and their associated methodologies.