Like I mentioned in my previous blog post I will be elaborating more on what are the best practices we can use when we're working in an Agile environment. I hope you all are familiar with the term Agile and we can easily put it as building a software incrementally from the start of the project, instead of trying to deliver it all at once near the end.That's simply what Agile means. Scrum is one of the subsets of the agile methodology and the most widely used framework process in agile development. (A “process framework” is a particular set of practices that must be followed in order for a process to be consistent with the framework. (For example, the Scrum process framework requires the use of development cycles called Sprints) I am purely writing this blog post based on my professional experience which I gathered when working with an agile environment. Plan your Sprint at least a week prior As business analyst you have to work closely with the scrum master
What is a User Story ? We can define a user story as the short and simple description of a functionality used in Agile practice. Basically they are written to capture the requirement from the customer or the end user perspective. It will simply say What type of users, What they want and Why they want it. The user stories should be written in a language where it is clear to both the customer and the development/QA teams as to what the customer wants and why he wants it and what kind of customer wants it. Development team should understand the customers need and they should take care of how to cater the requirement from technical perspective. There is a simple structure to a user story. As a <<CUSTOMER TYPE>> I want <<WHAT CUSTOMER WANTS>> So that <<WHY CUSTOMER WANTS IT>> Let me elaborate more on this taking an example. Assume a tutor wants to publish his/her tutor services for students online for students to apply.