# data[].attributes.body
Come up with a strategy to fix / improve in one topic from the discussion points.

# data[].attributes.body
Figure out what we couldn't achieve Sprint Goal and learn how to avoid it in future.

# data[].attributes.body
Discuss, room for improvement when it comes to handling Sprint Goal tickets, especially when it comes to urgent scope change and how to switch focus from and to respective tickets.

Are PRs getting frozen and again?

Discuss QA effect when it comes to exceptional cases (i.e. QA member is sick.. etc)

Discuss ways of collaboration or at least communication with Conichi to evade such cases of urgent requirements that interrupt our sprint.

# data[].attributes.body
Focus on really solving the planning / estimation problem or problems in execution of it in the sprint.

# data[].attributes.body
talk about daniel's concerns, the manpower approach in the QA and what "went wrong" in achieving the sprint goal + action points for all these

# data[].attributes.body
I would like to know what is blocking us from finishing the sprint scope.

# data[].attributes.body
talk about the sprint goal and the reasons for not achieveing it

# data[].attributes.body
What are the concerns from QA regarding the topic of Jenkins and how can we address it

# data[].attributes.body
Focus on really solving the planning / estimation problem or problems in execution of it in the sprint.

# data[].attributes.body
regarding Jenkins topic

# data[].attributes.body
Focus on really solving the planning / estimation problem or problems in execution of it in the sprint.

-- parallelize work
-- ask earlier for technical caveats found during sprint with respective to the time available
- proactively mention if there is a risk in completing the ticket during the sprint in dailies.
- proactively ask when a sprint goal ticket is achieved in dailies

# data[].attributes.body
-> external releases are affecting the QA scope
-> IUT is taking our QA manpower
Statement:  Automation efforts are not in priority
Affected by: IUT releases and Jenkins progress

-- track the amount of time spent on IUT release testing , take the numbers to dennis and understand how to tackle it @Sutini @Daniel

-- Finish the jenkins task in the next sprint and left over tasks can be handed over to devs

# data[].attributes.body
https://giphy.com/gifs/tired-gif-sleep-sleepy-Q42cpzgcUeZkA