# data[].attributes.body
1) Stabilizing app. Fix bugs and try not to produce other bugs with your fix.

Eman.

1) Create help material or document for difficult tasks like Template programming, and animation.
2) Proceed on fixing bugs. App is not stable. A lot of bugs on Production, some of them were appearing during exhibition.

Vladimir.
1) Create help material or document for difficult tasks like Template programming, and animation.
2) Proceed on fixing bugs. App is not stable. A lot of bugs on Production, some of them were appearing during exhibition.

Zia
1) Create help material or document for difficult tasks like Template programming, and animation.
2) Proceed on fixing bugs. App is not stable. A lot of bugs on Production, some of them were appearing during exhibition.

# data[].attributes.body
Refactoring of all templates. Big mess in all templates.

# data[].attributes.body
Proceed on fixing bugs. App is not stable. A lot of bugs on Production, some of them were appearing during exhibition.

# data[].attributes.body
Start writing specification of the Project

# data[].attributes.body
1- Update documentation as discussed in last retrospective.

2- Introduce a step "Ready for Test" in scrum board.

3- There is scope of improvement in Search Message process

4- Prioritize bugs w.r.t :
a- Errors
b- Optimizations
c-Suggestions

# data[].attributes.body
Do more testing before Release on Production

# data[].attributes.body
Create help material or document for difficult tasks like Template programming, and animation.

# data[].attributes.headline
We count that story is done when we are ready to demonstrate that with all following discussion on demo. Ready for demonstration = you are ready to put feature in the production (and testers can only help you to be sure of that)

# data[].attributes.subject
We count that story is done when we are ready to demonstrate that with all following discussion on demo. Ready for demonstration = you are ready to put feature in the production (and testers can only help you to be sure of that)

# data[].attributes.body
1) Confluence documentation should be self describing and easy to understand for a new comer

Eman
1) Take predemo comments in account
2)Update the documentation on architecture of the project

Vladimir
1) Try to estimate time left for finishing the user story more precise.
2)When learning new technology , do more practice before starting real task and implementing it in a project, to exclude time waste.

Krishna
1) Use the test cases in HipTest while performing regression test

Anton
1) Take pre-demo comments in account
2)Confluence documentation should be self describing and easy to understand for a new comer

Zia
1) Pre-demo
2)Confluence documentation