User stories are part of an agile approach that helps shift the focus from writing about requirements to talking about them. All agile user stories include a written sentence or two and, more importantly, a series of conversations about the desired functionality.
In the course of agility of software development ,face to these question that is a normal things we challenge. It is a crucial step of pull the project process not shrink ,not delay and come over the difficult radically .So ,in here, I will summarize and share some points for us:
Q1，How to guide the user team to write or participate in the writing of stories?
We usually see -- It's the product owner's responsibility to make sure a product backlog of agile user stories exists, but that doesn’t mean that the product owner is the one who writes them. Now as far as this question is concerned, i think guide the user team join into the edit of storied is the rather good way to boost the real in stories. XP program is not only just a duo but also as resemble as software team management , let the client to be a member of writing, can improve the stories accuracy and well up to criterion that making ,many demand up to the user ,and down it into the note during very writing of stories.
Q2,Ｈow to define the prior of a story ,including what parameters in it ?
<The first> The cost of story .The reason that I still put the cost is a vital essential of per story of users ,due to if you will lead to the consensus by the clients and lose more market after per software publicity ,then effect the brief of business expands. Also, the cost of story ,including R&D member cost, time-cost ,and the corporate structure and services and so forth.
<The second>The benefit of business . Put the benefit of business at first if possible -- Maximize business organization.
<The third > Considering the speed of team development ,the speed of the team play an important role as well Mostly ,for instance ,if a team speed is 5 points in very stories,and the next time (software publicity ) improve to 6 points per stories,so as we can use the some math to evaluate the project parameter in all .
Q3，What if the relationship between story's point iterations is too high？
Not amazing thing that we face two or more stories have a high relationship amid them ,so-called "H-R" we define it in here so as to writing convenience. the demo derive from own note :
seeing this picture,demonstrating if we want to write the story at first ,it is adjacent to the story 1 and the story 2 , basic on the story 1 ,have huge relation about the content of between story 1 and story 2 ,so how to deal with this problem? last time , a conversation with some friends in nanshan district ,some have more skills and experience in management ,as usual do it is let the story more program-independent modularity if possible ,segment the story to more small stories if possible too.
Q4，The keys of compose a user story ？
User stories have keep shorting, simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. While , there are some key we have to handle in writing it : independent ,negotiable,estimate and so on .
Q5，How to check and accept the software result？
As my opinion,I adopt that there have been a profession of IT member specialize in someone who excel for the R&D or software test in client team,while, let him to do this thing when very project check and acceptance.
best wish!
by Joel <original>
