This feedback can be used to split the story where appropriate, or add more detail and examples to clarify the areas that caused confusion.Ī Kick off takes the form of a checklist that contains several items to be verified before starting the story’s development.
This gives the team an opportunity to discuss technical details, ask questions to clarify the requirements, and evaluate if the size of the story is appropriate. Two of these techniques have proven to be very valuable to us in the maintenance of quality in our project: Kick off and Desk Check of stories.Īs stories under analysis are still open to suggestion, a good idea is for the team to have a meeting where the Analyst (or another team member with good context) presents the upcoming stories, their origin, the proposed value and why they are required.
#DEFECT PROCESS IN AGILE SOFTWARE#
Since preventing defects in software as early as possible is desirable in any development project, there are many techniques available to prevent these issues before they manifest themselves, it is worth reading the new book by Gokjo, Fifty Quick Ideas To Improve Your Tests. Details that are apparently clear in the head of the Business Analyst, or even the client, could end up not being properly expressed in the description of a story.
These can lead to implementation defects if not validated before development. There are innumerous ways to slip up when creating a user story.
0 kommentar(er)
