What exactly "valuable" is in INVEST in agile ?

Question

0.00/5 (No votes)

See more:

It has been said that user story in a sprint must be INVEST.

"I" ndependent (of all others)
"N" egotiable (not a specific contract for features)
"V" aluable (or vertical)
"E" stimable (to a good approximation)
"S" mall (so as to fit within an iteration)
"T" estable (in principle, even if there isn't a test for it yet)

And Each user story must be added some value to the customer or user or product.
What exactly means "Valuable" or "Vertical".

What I have tried:

Let say if I am developing a UI having a couple of fields (many textboxes, dropdown list etc.) in it and plenty of validations rules at the client end. I have splited this feature into stories like :

User Story 1-UI design.
User Story 2-Dropdown data population from the database.
User Story 3-Applying client-side validation rules in UI.
User Story 4-Saving all UI fields into the database.

1-My question is above stories are obeying the INVEST criteria or not?
2-Is each above story adding value to product or customer or user or not?

Posted 22-May-18 1:54am

Dinesh Singh Kushwaha (Dev)

Updated 22-May-18 18:20pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CHill60 · Answer 1 · 2018-05-22T03:49:00

Solution 1

"Valuable" - the user story must add something of value to the final experience... from an end-user perspective
"Vertical" refers to incremental development - see What is Incremental Development? | Agile Alliance[^]

Your stories don't really capture features of your system from an end-user perspective. They read more like technical requirements.

Sounds like you need to invest in a good agile book. This isn't really the right forum for training you in any subject

Posted 22-May-18 3:49am

CHill60

Comments

Dinesh Singh Kushwaha (Dev) 23-May-18 0:21am

Hi CHill60,

Thanks for your reply. Can you please give the exact answer to below-mentioned questions in YES or NO with the specific fact.

User Story 1-UI design.
User Story 2-Dropdown data population from the database.
User Story 3-Applying client-side validation rules in UI.
User Story 4-Saving all UI fields into the database.

1-My question is above stories are obeying the INVEST criteria or not?
2-Is each above story adding value to product or customer or user or not?

Your answer will be appreciated.

CHill60 23-May-18 2:25am

Your question "2" is repeating question "1",as if those "stories" obeyed the INVEST criteria they would, by default, be adding value.
But as I said, they don't read like user stories, just incremental technical requirements.
How is "UI design" testable for example?
Story 4 is more likely to have been presented as "on revisiting the page all previously entered data must be visible"...The user doesn't care how you do it and most don't understand databases