Execution is not always everything. A team needs to care about people as well.
A wrong project work can lead to:
- destroy morale
- grind teams down
- erode trust
- crunch gears
- wreck the machinery of long-term progress
Cost($ & Manpower) <-> Time <-> Features <->
What shape up what to solve
- End the project within definite timebox
- Think about how the product will grow in long terms
- ???
Six-week cycles
Shape the work (define key elements of a solution)
Targeting risk
- not shipping on time
- building the correct thing
Shaping — preparing of work before schedule
Betting — pitching projects to do for next product iterations
Building — track known versus unknown, and FINISH the project ON TIME
Shaping (pre-work)
Wireframes too concrete -> implementation cannot map the actual work
Words are too abstract -> wrong understanding of requirements
Issue: hierarchical executor vs planner (Be aware)
