To clarify my definition: Changing requirements should only happen outside the scope of committed work; otherwise you're building churn, poor features, and poo

To clarify my definition: Changing requirements should only happen outside the scope of committed work; otherwise you're building churn, poor features, and poor code. This lever of "committed work" can be adjusted per team (1 week, 2 weeks, 4 weeks, and so on). It seems you agree with my view of a minimum of 1 week before it can change. I agree also with fine grained tasks/stories. As small as possible and as consistent as possible. They should all have clear DOD's though. Definitely agree with smallest possible units of value (that also varies per a person).