1. Understand each ticket before sprint starts
2. Get different approaches for solving particular issues
2.1. DEV: i would go through the tickets and come up with approach/es before the refinement session.
2.1.1. Allocate time before refinement sessions
2.2. SP: use domain/project knowledge
2.2.1. SP: Take the time to explain clearly
2.3. SP: gain experiences from other team members before start.
2.4. TL: Check pros/cons of upgrading current system vs implementing new solutions (e.g. Micro-services)
2.5. SDET: Ensuring that the correct testing strategy is applied
3. Unblock any future blockers
3.1. TL: Act upon any blockers that are brought up and talk to other relevant leads.
3.1.1. Bring up blockers immediately so that there is ample time to act on them
4. Understanding the domain
4.1. SP: use domain knowledge
4.2. DEV: Spent time before refinement sessions to understand / learn ticket domain.
4.2.1. Schedule these time-slots so they don't come as a 'surprise'
5. To come up with questions early for PO to ask beforehand
5.1. SP: use domain knowledge
5.1.1. SP: Help PO understand what is being asked of the ticket
5.1.2. Open ourselves up to absorb new domain knowledge and not only what we already know or accustomed to
6. To get acceptance criteria for testing
6.1. SDET: Writes a test plan build around this
6.1.1. Share the test plan with the team to get more input.
7. Clarifying criterias and asking questions
7.1. SP: Preparing questions before having the session
7.1.1. Allocating pre-refining time
8. To better understand what needs to be done and how to do it, splitting work on subtasks
8.1. SP: Ask questions to PO or who create the ticket.
9. To set the priorities
9.1. Dev/Qa- To clarify such things while planning with PO
9.1.1. Just do it :D
9.2. SDET: Helps by Calculating the impact/risk of the feature will have on the system.
9.2.1. Collectively we get a better understanding of the whole system / complaince
9.2.2. Maintaining a healthy regression system
9.2.3. Starting different regression systems for perf
9.3. TL: Give good estimates and possible heads ups so that PO can set priorities correctly
10. Estimate effort
10.1. SP: Give input on complexity
10.2. SDET: Check the amount of effort required for testing.
10.3. SDET: Determines whether a task should be automated or not
11. To be able to plan things better and complete sprint tasks on time
11.1. SDET : Have test plan ready before testing
11.2. SP: Estimates refinements
12. To have refined tickets with no unanswered questions/blockers once they are added in the sprint
12.1. SDET: Bring up edge cases so we can clear and any blockers.
12.2. TL: See how the requirement will fit in the current system. Check for dependencies on other teams / departments.
12.3. SDET: Think on how the new feature will effect the current system as a whole
13. Part of a knowledge share mentality
13.1. TL: Ask the right questions which opens up discussion on the domain in question.
13.2. SDET: Shares the knowledge of other domains and features within the system
14. Accept reject tickets
14.1. SP: check ticket completeness
14.1.1. SP: Reserve time to look at up coming tickets.