Session 3.1 - Development Strategy Overview
Chapter 4: The Development Strategy | Duration: 1 hr
Learning Objectives
By the end of this session, you will be able to:
- Explain why TSPi teams build a strategy before planning
- List the core questions a strategy must answer
- Identify principal components and their functions
- Describe the cyclic development approach in TSPi
Introduction
Strategy is the bridge between “what success looks like” and “how we will build it.” Chapter 4 opens with a simple scenario: you are given a product and a schedule—your job is to decide how to deliver. The development strategy captures those decisions before detailed planning begins.
Why Create a Development Strategy?
Clarity
- Aligns on “how” before estimating “how long”
- Shapes architecture and component choices
- Drives risk identification early
Control
- Prevents ad-hoc decisions during crunch time
- Anchors scope for later planning and tracking
- Enables meaningful trade-offs (scope vs. time vs. quality)
Key Strategy Questions (Chapter 4)
- Based on what we know, how would we build this product?
- What are the principal components?
- What functions must these components provide?
- What risks and open issues do we see?
Outcome
A concise strategy document answering these questions guides estimation, planning, and design.
Identify Components and Functions
Strategy work includes rough decomposition—enough to see major pieces and their responsibilities.
Cyclic Development
TSPi favors multiple cycles: build a small, working subset first, then enhance. Strategy decides cycle content.
Cycle 1
Minimal viable subset
Prove architecture
Cycle 2
Enhancements & quality
Refine process
Cycle 3
Remaining function
Hardening
Summary
- Strategy answers how we will build the product before estimating effort.
- Ask and document the core questions: approach, components, functions, risks.
- Rough component/function mapping anchors later design and planning.
- Cyclic development is central to TSPi—strategy defines cycle scope.