📎 Webclip
A New Way of Working: A Two-Month Recap
The post recaps the first two-month term under a new working model with small three-person teams, two-week iterations, and a goal of reducing scope and tightening deadlines. The author says the period was highly productive, though it also led to several process adjustments.
Reading notes#
- Small teams of three worked in fixed two-month terms with four two-week iterations to cut scope and keep deadlines short.
- Design needed an early start, so programmers handled small tasks at the beginning of an iteration while the designer worked on the first major feature.
- Features were deployed as soon as they were ready instead of waiting for one final release at the end of the iteration.
- Final Friday deploys caused weekend problems, so the team moved final deploys to Thursday to leave Friday for fixes.
- Scope had to be reduced earlier, with reviews on Monday of the second week and again on Wednesday before the iteration ended.
- The team found that one-week, two-week, and three-week iterations can all make sense, but the length has to be chosen up front.
- The next two-month term began on March 1, and the author says they will apply what they learned and report back in early May.
