# data[].attributes.body
You mean tasks statuses are not reflected properly on the board?

# data[].attributes.body
As a whole team know what limitations Hybrid applications have. And discuss this limitations with each other and PO in order to make better desicions on quality. Might result in spending less time on less important bugs

# data[].attributes.body
quicker build delivery. CI takes 30 minutes. why wait 4 hours to have the build?

# data[].attributes.body
Communication/Alerts from developers

# data[].attributes.body
Successful demo

# data[].attributes.body
Effective way of delivering the services

Internal call for the issue

# data[].attributes.body
User story specific task completion

# data[].attributes.body
Dap server issue.

# data[].attributes.body
Backend environment issue

# data[].attributes.body
Delivery of web-services within one week of sprint start date

# data[].attributes.body
We should develop front end without back end; the UI can be tested without backend (Windows scroll issue, iOS remove amount)

# data[].attributes.body
We should add more capacity at backend level, on the contrary this bottleneck can impact all the sprints

# data[].attributes.body
Better management of device specific defects.

# data[].attributes.body
Environment stability-Services unstable

# data[].attributes.body
Consistency in implementing learnings from previous sprint

# data[].attributes.body
Defects -subtask tracked in JIRA

# data[].attributes.body
Better planning and sprint vision

# data[].attributes.body
Why we have open defect at front end level (Windows scroll issue, iOS remove amount,...)? Can we develop and test part of front end UI without backend?

# data[].attributes.body
Build should be received every day on fixed schedule

# data[].attributes.body
Why the webtrekk Android issue happened? Who/Why the basic code has been updated?

# data[].attributes.body
Unplanned activities

# data[].attributes.body
Focus on single user-story at a time.

# data[].attributes.body
Why the webtrekk Android issue is not fixed by RTB team?

# data[].attributes.body
Using Jira dashboard can help the check the status of the sprint

# data[].attributes.body
Multilingual central file is a good improvement

# data[].attributes.body
Consistent multilingual translations

# data[].attributes.body
Story must be burned by priority and not by availability

# data[].attributes.body
End to end scenario was covered

# data[].attributes.body
Evaluation and planning is something we have to manage more carefully

# data[].attributes.body
Focussed pertaining to user storywise

# data[].attributes.body
We've been more carefull to use Jira as base to request acrivities to the team.

# data[].attributes.body
Defect discussion respective to user story with product owner

# data[].attributes.body
Integration of services in time.

# data[].attributes.body
We organized stories on end2end process and not by pillars

# data[].attributes.body
DSM should be 15-20 mins

# data[].attributes.body
We've been more ambitious to accept more story points (maybe too many)

# data[].attributes.body
Environment availability

# data[].attributes.body
Mulitlingual file should be finalized very early

# data[].attributes.body
Timely communication

# data[].attributes.body
Effective Communication

# data[].attributes.body
Poor quality of builds, no user story wise

# data[].attributes.body
Multilingual needs to be finalised at the earliest

# data[].attributes.body
Very heavy loading story points

# data[].attributes.body
Dependency on Multilingual

# data[].attributes.body
Dependency on Services

# data[].attributes.body
Middleware story should be separate for smooth sprint

# data[].attributes.body
Attempt to achieve more story points