3 ms·
Interesting. How do you keep track of all the in progess TTLs? How do you decide the TTL length? Won't this process end up ultimately filling the team's/projec
by egman_ekki 6y ago
Interesting. How do you keep track of all the in progess TTLs? How do you decide the TTL length?
Won't this process end up ultimately filling the team's/project schedule with revisions of previous decisions?
- siliconc0w 6y agoThe TTL is based on the cost, time to implement, and time needed to gather enough signal to make a determination. So if you doing normal 'mvp' style of development where you ship intermediaries you should have some signal whether something works in at least six months, ideally sooner. Sometimes this means you might reconsider or even reverse a decision or apply what you learned to a new problem but mostly this just builds confidence and trust in the team that the decision making process is generally 'good enough'. The TTLs are tracked in the decision log which is reviewed in project retrospectives. You can schedule these in a slot a week you hold open for presentations, document reviews, demos, wheel of misfortunes (debugging simulated production problems if on-call), production reviews, etc.