# data[].attributes.body
1. Still following Ostrich algorithm.
2. Not enough technical discussion
3. Document created but not being read
4. Always thinking in terms of business, in spite of being a technical team.

# data[].attributes.headline
Team leads should validate the stories and its relevant documents before assigning it to the developers.

# data[].attributes.subject
Team leads should validate the stories and its relevant documents before assigning it to the developers.

# data[].attributes.headline
Validate ticket and its acceptance criteria in detail before assigning it to the developers in hurry.

# data[].attributes.subject
Validate ticket and its acceptance criteria in detail before assigning it to the developers in hurry.

# data[].attributes.body
Documents provided by the business team. So, less to and fro between the teams.

# data[].attributes.headline
Acceptance criteria is not up to the standard

# data[].attributes.subject
Acceptance criteria is not up to the standard

# data[].attributes.headline
more time allocated for requirement  refinement

# data[].attributes.subject
more time allocated for requirement  refinement

# data[].attributes.headline
Easy to work on requirements. No much changes. Good coordination of team.

# data[].attributes.subject
Easy to work on requirements. No much changes. Good coordination of team.

# data[].attributes.headline
recurrent meetings were helpful to know the requirements better

# data[].attributes.subject
recurrent meetings were helpful to know the requirements better

# data[].attributes.body
Before asking when will be the task done, we should more focus on "how should we do it "

# data[].attributes.body
Too much busy and at the end of the day no any achievement / progress

# data[].attributes.headline
Work from home is productive these days. Let's continue it for few more weeks

# data[].attributes.subject
Work from home is productive these days. Let's continue it for few more weeks

# data[].attributes.body
Grooming can be done differently

# data[].attributes.headline
Proper task planning. Review mockup to and fro with third party/business team, before finalizing requirement. 

# data[].attributes.subject
Proper task planning. Review mockup to and fro with third party/business team, before finalizing requirement. 

# data[].attributes.headline
Business team is actively participating in integration discussions, follow ups and support along side the BA.

# data[].attributes.subject
Business team is actively participating in integration discussions, follow ups and support along side the BA.

# data[].attributes.body
AC and Mockup should be same and well maintain

# data[].attributes.body
1.Every task is different , because technical complexity will be different for each task
2. There should be discussed first with business team before jumping into development team

# data[].attributes.headline
Multiple Code review should be done in different levels

# data[].attributes.subject
Multiple Code review should be done in different levels

# data[].attributes.body
- The frequent requirement changes in the ACs makes the tasks boring, so, if it was made clear and updated before assigning to us, working time would have been more effective.

- Proper Grooming should be provided by BA to the ones engaged in the particular project so that the confusions would not prevail during the time of testing.

- Ticket validation along with the mockup is much required as it creates a lot of confusion while testing.

# data[].attributes.body
major tasks should be done on different sprint on frontend and backend should

# data[].attributes.headline
Qa regression sheet should be more standard

# data[].attributes.subject
Qa regression sheet should be more standard

# data[].attributes.headline
Qa should ask more questions to developers and BA before changing ticket to done

# data[].attributes.subject
Qa should ask more questions to developers and BA before changing ticket to done

# data[].attributes.body
0.Product team should be more responsive

1. Requirements can still be better- more improvement needed on story writing.

2. Adhoc hotfixes- I think we should manage better

3. Environment issues, resource issues

4. Proper planning for feature like refer and earn- allocate dev,qa,dba resource as per priority

5. Grooming still lacking, should conduct proper grooming feature wise

6. Timeline planning