Project Management Central

Please login or join to subscribe to this thread

Topics: Agile
Which point will be in more focus while writing Good User Stories wrt INVEST?
Network:1233



Which point will be in more focus while writing Good User Stories wrt INVEST?

Independent
Negotiable
Valuable
Estimable
Small Enough
Testable
Sort By:
Network:2251



They all work together united to ensure a good user story. They do not work independently.
Network:118380



Fully agree with Andrew’s statement.
Network:1431



Sachin -

the whole point of INVEST is to illustrate the competing forces which will mold a "good enough" story. If any one is given greater precedence we won't get a good story. For example, if we obsess over small enough, we will get micro-tasks which don't represent value by themselves and which required advanced degrees in scheduling to be prioritized.

Kiron
...
1 reply by Sachin Ghugardare
Mar 28, 2019 12:15 PM
Sachin Ghugardare
...
Well said Kiron.
Network:1233



Mar 28, 2019 12:09 PM
Replying to Kiron Bondale
...
Sachin -

the whole point of INVEST is to illustrate the competing forces which will mold a "good enough" story. If any one is given greater precedence we won't get a good story. For example, if we obsess over small enough, we will get micro-tasks which don't represent value by themselves and which required advanced degrees in scheduling to be prioritized.

Kiron
Well said Kiron.
Network:1819



None. Do not follow a checklist in advance. User Stories must be write but the users and they are just "a placeholder, an invitation to continue talking about" as Kent Beck said.
...
1 reply by Kiron Bondale
Mar 29, 2019 8:16 AM
Kiron Bondale
...
I look at Bill Wake's acronym as guidance not as a gate. Similar to the DoR or DoD, it is there to help the team, not to provide rigid constraints. Regardless of whether a team chooses to use user stories as the starting points for discussing requirements or some other requirements modeling technique, the different attributes of INVEST serve as a useful guideline similar to the S.M.A.R.T. acronym we associate with objectives & acceptance criteria.
Network:1431



Mar 28, 2019 6:46 PM
Replying to Sergio Luis Conte
...
None. Do not follow a checklist in advance. User Stories must be write but the users and they are just "a placeholder, an invitation to continue talking about" as Kent Beck said.
I look at Bill Wake's acronym as guidance not as a gate. Similar to the DoR or DoD, it is there to help the team, not to provide rigid constraints. Regardless of whether a team chooses to use user stories as the starting points for discussing requirements or some other requirements modeling technique, the different attributes of INVEST serve as a useful guideline similar to the S.M.A.R.T. acronym we associate with objectives & acceptance criteria.
Network:329



Good user stories are those that achieve a shared understanding within the team what needs to be done and delivered. In this respect Sergio's comment is very valid.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Impartial observers from other planets would consider ours an utterly bizarre enclave if it were populated by birds, defined as flying animals, that nevertheless rarely or never actually flew. They would also be perplexed if they encountered in our seas, lakes, rivers and ponds, creatures defined as swimmers that never did any swimming. But they would be even more surprised to encounter a species defined as a thinking animal if, in fact, the creature very rarely indulged in actual thinking."

- Steve Allen

ADVERTISEMENT

Sponsors