Human stories

Abstract

Software requirement is one of the most important issues for starting any software projects. Especially in Agile software development, it is hard to be specific and complete, while customers/users keep asking about time and cost to finish their project. Fortunately, some researchers found that by improving the quality of requirements, the effort of estimation can be reduced. In this paper, we due with the quality in Agile software requirements focusing on their different written techniques. User-story and persona-story are two most famous written methods to deal with Agile requirement quality. While user-story focuses on the holistic view of the users that playing with role, persona-story focuses on the detailed view of the individuals that playing with people. However; throughout our research and other arguments, both of them have their strengths and weaknesses. Some researchers found that there is a coherent relationship between them, but the agreements are still the discussions. Therefore, we introduce human-story as a promising written technique to overcome the disadvantages of both existing stories, to enhance the key benefits of them and to fill the gap between differences. INVEST Grid is used to evaluate the quality of Agile requirements and to give the comparison among three techniques, the results show that persona-story and human-story have the higher scale values than user-story in most of the type of software requirements. Because the Grid cannot give us a clear comparative result to the significant different among three stories, the introduced Agile requirement checklist makes sure our proposals meet our goal. The results displays the percentage of the completeness in human-story is 84% while user-story and persona-story are 44% and 56%.