# data[].attributes.body
Can we fix one mode of communication? Mail/Slack/Whatsapp/Skype

# data[].attributes.body
frequency

# data[].attributes.body
for demo, desk checks, qa and also general dev

# data[].attributes.body
We have to ensure there are no duplicates

# data[].attributes.body
Slack vs Email vs Call

# data[].attributes.body
backend web services with url, request and response can be made available before we consider start implementing story that requires to communcate with backend. As Android is also consuming same webservices, we can get the list of services and details using Charles/Fiddler.

# data[].attributes.body
Mention navigation flow, How do we land into that particular page?

# data[].attributes.body
Need more details in AC interms of scenarios, alternative flows

# data[].attributes.body
Stories needs to have complete acceptance criteria. Proper screen shots should be attached.

# data[].attributes.body
Full team is not invited for demo

# data[].attributes.body
Dev team was bound to estimate the stories within the limit of 200 points

# data[].attributes.body
Results of the early morning meetings are not revealed to the team

# data[].attributes.body
Could have been better

# data[].attributes.body
Stories were under-estimated.

# data[].attributes.body
Could have been better

# data[].attributes.body
As part of iteration process on 8th day of sprint code has to freeze and build should be deployed for QA.

# data[].attributes.body
Need to ensure code is reviewed thoroughly before pushing to Git

# data[].attributes.body
Need to understand more about all back end services

# data[].attributes.body
Document with webservice URL/request/response should have been created. This is part of process and was followed in all mobility projects.