Well-sized stories keep your work in progress small, your level of risk low, and your teams nimble.
Stories should be as small as possible while having some self-contained nugget of customer value.
If a story is too big when priorities shift you’ll have invested a bunch of time into work that can’t be put into production. If a story is too small, when priorities shift you’ll be left with a bunch of work fragments that are “done” but not useful without more time.
https://medium.com/swlh/three-drawings-i-use-to-explain-agile-9c0ef15b64b8
No comments:
Post a Comment