How to prevent intentional over-estimation in user stories?
I am asking this from a purely hypothetical standpoint.
How do you deal with the costs of too-rapid change?
Like most modern developers I value Agile principals like customer collaboration and responding to change, but what happens when a product-owner (or whoever determines requirements and priorities) changes requirements and priorities too often? Like several times a day?
Evaluating a product owner [closed]
Closed 8 years ago.
Wrote an application for a friend. Who is the owner of the software? [closed]
Closed 11 years ago.
Selecting the (right?) application design [closed]
Closed 10 years ago.
Selecting the (right?) application design [closed]
Closed 10 years ago.
Selecting the (right?) application design [closed]
Closed 10 years ago.
Selecting the (right?) application design [closed]
Closed 10 years ago.
Selecting the (right?) application design [closed]
Closed 10 years ago.
Is it normal for developers to suggest feature ideas to product owners? [closed]
Closed 10 years ago.