Design - NextensArelB/SwaggerGenerationTool GitHub Wiki

##Objective Getting a Feature in a Sprint ready state

##Who

• Quality engineers (QA)
• Developers (DEV)
• Delivery Manager (DM)
• External parties: Belastingdienst, external connected applications
• [optional] User Experience (UX)

##What During the sprintplanning, refinements are taken into a sprint. The most common cadense is sprint 1 refinement of a feature and sprint 2 development of a feature, as it can take some time to collect, analyse, describe and discuss. The Product Owner has a clear demand for a Feature, and together with all the stakeholders the requirements are researched and refined.

• Next Feature in priority
• Refinement sessions are done weekly
• The goal of the session is to find out what needs to be done to get the Feature to a state of "Ready" for the coming Sprint(s).
• When done with a refinement task, put it on someone else's name so that it can be reviewed.
• When review and tech analysis are completed, the DoR can be filled in to have a final check if every criteria has been met

##Where

• PO/DM prioritizes the feature in the Backlog
• PO/DM plans the next feature into the sprint for refinement

##When Team wide refinement is done on a weekly basis. The goal is to use every week's refinement session to check up on the progress for getting to 'Ready' for future Sprints. The aspired goals and timeline of the refinement sessions can seen below in the tables:

Participation	Entire team
Preparation	Goal of the Sprint is known
Content	High level overview of the Features for next Sprint and review of the related designs
Outcome	Form a "Focus group" consisting of a developer, tester and UX team member for each feature (UX is not necessarily needed in all meetings)

Participation	Focus group
Preparation	* Focus group is familiar with the contents of the specific Feature * All questions are asked and answered * Design sign-off
Content	* Continue Test and Tech Analysis * In-depth review of Feature ask
Outcome	Feature is further refined

Participation	Entire team
Preparation	* Team is Familiar with the contents of the refined feature * Test analysis is done * Techn Analysis * Business Sign-off * Feature is split up into smaller User Stories in the Backlog
Content	Present User Stories and tasks to the team
Outcome	* Agreement that User Stories are divided into consumable size * Agreement that the Feature is Sprint-ready (checklist Definition of Ready)