Business Analysis BA: how user stories demolition?

What is the User Story In fact, I think we need to make a definition of the User Story is quite hard.
I once thought that the so-called User Story User is to tell the Story.
You see, ah, write paradigm of User Story:
of As A Role, the I want to do something or A piece ... of functions on this page, the I CAN SO that the Achieve some of Statement of Business or the Intent value.
However, as the real practice, I found, User always a definer absence.
We expect User to define the User Story, which in most cases is up to us to define the group of BA.
Agile coach and I had a discussion, we always imagined BA user's needs and write User Story, this make sense?
This vice president from the United States said to me, at least you think from a user's perspective, is not it?
However, this does not answer my questions, I also believe that there are a lot of people and I have the same problem: User Story in the end come? Who will write?
A lot of people think the demand side should be made to write User Story, at least it should be confirmed whether the User Story appropriate.
But the reality is that many times we really rely on the imagination and take advantage of our "empathy" to imagination.
I turned a bit BABOK in the definition of the User Story:
A Story Represents by the User A Small, Concise of Statement of functions on this page or at Quality needed to The deliver value to A specific Stakeholder.
- "BABOK 3.0"
It would appear, User Story can only bring value to describe the function or quality of User demand, rather than having to be provided by the User.
Later this description more clearly point out this:
. With Focus ON A Stakeholder value, the User Stories INVITE at The Exploration of Promoting Additional requirements by Conversations with Stakeholders and GROUPING Functional requirements for Delivery
- "the BABOK 3.0"
Here, we pause , knock blackboard: value.
User Story is stressed to bring value to the user.
OK, we continue.
Well-known principles of Split User Story to write is not complicated, but from the perspective of agile small strides, most of the User Story is the need to be split.
The various writings are agile principles stated INVEST split User Story:
work of the Independent: User Story independence must be high cohesion, also is to have independence, does not depend on the realization of other User Story is achieved.
If you are a User Story will be split into foreground and background, it is certainly not in line with this principle, because both Story dependence is very high.
Negotiable: Negotiable User Story is not supposed to be a person lays down the law.
Before a small partner asked me, is not it should be written by BA User Story. I said, BA provided a first draft, final draft needs to make the team everyone involved agreed.
Valuable: Valuable again knock blackboard, value!
Value is the key User Story of the Story If the user is of no value, it would need to split or rewritten.
Estimable: Scrum can be evaluated in the previous article, I mentioned the fact to assess the issue of Point of User Story.
We must ensure that the User Story can be assessed as User Story is the basis of all realize that we need to plan based on the assessment results, tracking and review.
Small: small enough this principle also determines the User Story to tear down small enough as to be demolished how small, I personally feel that this should be consistent consultation by the team, at least it should be a degree can be completed in the Sprint.
I before the team, when the assessments of more than 3 points, we must be demolished.
Because based on our past experience, 5:00 and above User Story Sprint will lead to our failure, most likely not finish or finish measurement.
The process is a process of splitting again thought and discussion, you will probably find a place to hide before and omissions.
Testable: testable bring value to the user's User Story must be testable.
Please read again what I mentioned above this sentence.
The reason that the above principle is "known" because we all know that when the demolition of User Story to follow these principles, but still do not know how split.
How demolition are strange? I remember knocking the word above the blackboard it?
The value of
all User Story be split value-oriented, after the Chai Wan also need to "User Story has this little business value it brings to the user?" To verify that the appropriate split.
That might be a little abstract. Let me give an example.
There is such a library loan system User Story: As a user, I hope I can find the book information to meet the conditions, so that I can find it on the shelf.
The User Story a little big, well, not a little big, very big.
If you take this to the User Story and discussion, will face the answers to the following questions:
? This user is a registered user, or to access the user?
? Different types of user operations are the same as you?
?-Called "condition" refers to what conditions? Title? Author? ...... ISBN
? What books to show information include? Title? Call Number? Collection status?
......
so we discuss next, decided to dismantle. That this User Story to you, how you split it?
The following method is a split, split into two User Story:
First: establishing book information table, which includes various attributes of the book.
Second: In accordance with the prototype, painted three front-end interface, including: search interface and search results interface, as well as book information display screen.
Big enough for?
I'll second that split into three, each interface a User Story, small enough, right?
Do you feel where the wrong?
Some people say, because there is no User Story to write in accordance with the format did not write: As a user, I hope you can see the search interface, so I can start preparing search.
Even more surprising, is not it?
To, think about these split out Story has business value for users you?
You provide a front page to the user, not search, can only see, it is ready to print to hang out inside the Museum "for people to look" to it?
So how should split it?
I offer here an idea, we can try to figure out what.
Large User Story:
As a user, I hope I can find the book information to meet the conditions, so that I can find it on the shelf.
First User Story:
As a user, I hope I can find the book's title, author, call number and status information collection of books by name, so that I can find it on the shelf.
Second User Story:
As a user, I hope I can find the book's title, author, call number and status information through the collection of books, so that I can find it on the shelf.
Or so split:
large User Story:
As a user, I hope I can find the book information to meet the conditions, so that I can find it on the shelf.
First User Story:
As a user, I hope I can find the title of the book by book title and call number information, so that I can find it on the shelf.
Second User Story:
As a user, I hope I can find the book's title, author, call number and status information through the collection of books, so that I can find it on the shelf.
What do you feel?
Ah, so that everything will be fine thing?
I can only say, break the pattern Tucson ......
because there's a problem that extends, that is, to see this program ape GG User Story Split, I wanted to beat.
why?
Because in the implementation of the code, in fact, be the first User Story, they can "easily" the second User Story logical true.
And if you do not easily achieved, then a second time means doing the User Story will need to change before the first delivery of a User Story of the finished code.
Just as we decorate the house.
Before the split method is: water started entering, bricklayer approach started, started woodworking approach, the approach started painting, furniture and soft loading approach.
The two kinds of methods of resolution behind me is: after the first hydroelectric living room, floor tiles, walls, furniture, soft loading are done, come back out again in accordance with the order of the bathroom, bedroom and then do it again ......
But see the difference Well ?
In front of a jobs resolution procedures finish, then dry the next, only when all are finished, the house can be delivered.
The resolution process back guarantee at least the first User Story can deliver a complete living room to the user, it is valuable for users.
This is also the agility of esoteric lies.
However, workers are certainly not happy, I Xianpu some water to the living room, I would also like to spread to the back part of the living room pulled down the holes and go to the bathroom ......
Ha, also from the other side shows the agile approach is obviously not suitable renovation projects.
So how would you convince everyone to accept value-oriented User Story of split way?
The point is that agile another important job: reconstruction. Agile development process is actually very stressed reconstruction, automated build and so on. So, this is why I have always felt agile framework and process is a complete system. You can not put aside the Reconstruction of User Story Split, you can not ignore the value to write User Story.
I probably spent two or three years to write and explore it feels demolition User Story, of course, familiar with the business and there is a certain degree of relationship.
I want to say is, you want to dismantle good User Story is the need to continue to explore their own process, there is no way that I read today an article or listening to a lecture, I will be able to write User Story, dismantle good a.
The key is to personally get to dismantle, to write, to go to trial and error.
Having said that, you run into any problems in the demolition of User Story time?
This article can answer your question?