News for hackers. Stuff that matters.
Re:Requirements volatility is the core problem of software e... by raiflip on Saturday February 22, 2020 @03:25PM (#22393123)
The binary thinking in this thread strikes me as odd. Is it bad to try and plan everything 6 months ahead of time? Yes. Is it also bad to fly by the seat of your pants and only plan 1 week ahead? Also yes. Instead, why don't we plan out by some intermediate time period. Say, 3, 4 weeks ahead of time. Or whatever time horizon ends up being the most efficient.
Re:Requirements volatility is the core problem of software e... by nradov on Saturday February 22, 2020 @07:31PM (#22394306)
Yes there is no single correct planning horizon. The optimal horizon is proportional to requirements stability. At the extreme when requirements flux is extremely high then the best approach can be a Kanban process, planning no more than a day in advance.