# 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

# data[].attributes.body
Use the test cases in HipTest while performing regression test

# data[].attributes.body
Try to have less comments from other team members  after code review.

# data[].attributes.body
Stop working as 1st line support team , it's not our job.

# data[].attributes.body
When learning new technology , do more practice before starting real task and implementing it in a project, to exclude time waste.

# data[].attributes.body
Try to estimate time left for finishing the user story more precise.

# data[].attributes.body
Predemo

# data[].attributes.body
Update the documentation on architecture of the project

# data[].attributes.body
New style of reporting the problems for the issues

# data[].attributes.body
Take predemo comments in account

# data[].attributes.body
1) Prepare more responsibly for DEMO

# data[].attributes.body
Eman
1) Code refactoring of CLibrary as well as WCF service. because code is getting more compresses only in one files.
2) Background messaging is still not stable, So we need to work more on background streaming.

Vladimir
1) Try to estimate time left for finishing the user story more precise
2) Prepare more responsibly for DEMO.

Krishna
1) Team collaboration

Anton
1) Don't understand how much time I can spend for the project

# 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
Confluence documentation should be self describing and easy to understand for a new comer

# data[].attributes.body
Better to add Snapshots in JIRA tickets as mandatory thing to report, especially for bugs