How to Think About This Chapter
This chapter is about why software projects succeed or fail. It focuses on decision-making, tradeoffs, and managing complexity.
The biggest idea: projects fail not because of technology, but because of poor management, unclear requirements, and scope creep.
Core Vocabulary and Concepts
Citizen Developer
A non-technical user who builds applications using low-code/no-code tools.
Compliance
Ensuring that systems meet legal, regulatory, and internal standards.
Feature Creep (Scope Creep)
The gradual addition of new features beyond the original project scope, which increases complexity and risk.
Product Owner
The person responsible for defining requirements and prioritizing features in a project.
Programming Language
A formal language used to write instructions for computers. High-level languages are easier for humans; low-level languages are closer to hardware.
Low Code / No Code (LCNC)
Tools that allow users to build applications with minimal or no coding, increasing speed but sometimes increasing risk.
Total Cost of Ownership (TCO)
All costs associated with a system over time, including maintenance, training, and upgrades.
Triple Constraint
The tradeoff between time, cost, and scope. Changing one affects the others.
Software Development Lifecycle
The structured process of planning, building, testing, and deploying software.
Methodologies (Agile vs Waterfall)
Waterfall is linear and structured, while Agile is iterative and flexible.
Key Relationships You Should Understand
- Scope creep is the biggest threat to project success.
- The triple constraint forces tradeoffs between time, cost, and scope.
- LCNC tools increase speed but can increase risk if unmanaged.
- Clear requirements reduce project failure risk.
- Agile allows flexibility; Waterfall emphasizes planning and structure.
- TCO matters when deciding whether to build, buy, or rent.
Interactive Study Questions (Click to Reveal)
What factors matter in make, buy, or rent decisions? (click to reveal)
When should LCNC tools be used? (click to reveal)
What are risks of LCNC and citizen developers? (click to reveal)
Why do firms use development methodologies? (click to reveal)
What is the biggest threat to project success? (click to reveal)
Why do technology projects fail? (click to reveal)
High-Value Compare / Contrast
- Agile vs Waterfall: flexible vs structured.
- Make vs Buy vs Rent: control vs cost vs speed.
- LCNC vs Traditional Coding: speed vs control.
- High-level vs Low-level languages: ease vs control.
Application Practice
- Why is scope creep so dangerous?
- How would you prevent project failure?
- When would you choose Agile over Waterfall?
- Should a company use LCNC tools? Why or why not?
- What happens if scope increases but time and cost stay fixed?