# data[].attributes.headline
Last sprint was not a perfect sprint. Most of the things we had decided to "stop doing"  in previous retros were brought back e.g.

# data[].attributes.subject
Last sprint was not a perfect sprint. Most of the things we had decided to "stop doing"  in previous retros were brought back e.g.

# data[].attributes.body
1. Data Model: Tables's structure ( relational or Core)  is getting finalized during  sprint after multiple question/answer se
ssion among  Dev , Data Modeler. E.g. LOCATION/LOC_DIM, PRODUCT/PROD_DIM, story
2. Mapping: Dev Team is working on mapping after picking up the story which is  not a best practice , hence multiple sessions / comments introduced delay in task which could have been completed in  less time and have been delivered to QA in early days of sprints. e.g. SEGMENT, MEM_SEG_LKP story
3. Grooming sessions and picking up of stories for current sprint  is going on in active sprint which is not a best practice.

# data[].attributes.body
Include defect root cause in the end of sprint report

# data[].attributes.body
Usage of checklist for reviews so as to avoid common mistakes

# data[].attributes.body
Implementing a new solution must be taken as a spike instead of story as the effort required cant be estimated

# data[].attributes.body
Taking up tasks into sprint without creating an associated story

# data[].attributes.headline
Considering two more weeks left for current sprint and one more development sprint left let us effectively manage hard dependencies and by when to close depenencies. Let us call out in the daily standup call also

# data[].attributes.subject
Considering two more weeks left for current sprint and one more development sprint left let us effectively manage hard dependencies and by when to close depenencies. Let us call out in the daily standup call also

# data[].attributes.headline
Continue the collaborative approach and ways of working with opportunity to optimize to meet the Magrabi timelines

# data[].attributes.subject
Continue the collaborative approach and ways of working with opportunity to optimize to meet the Magrabi timelines

# data[].attributes.headline
Core decisions taken should be documented in confluence or  DSD to avoid the questions/discussions about same  or similar situation in upcoming sprints. e.g.  

# data[].attributes.subject
Core decisions taken should be documented in confluence or  DSD to avoid the questions/discussions about same  or similar situation in upcoming sprints. e.g.  

# data[].attributes.body
1. For SEGMENT entity new table was created in CORE schema whereas for MEM_SEG_LKP not in R4 sprint and then we were discussing about  LOCATION entity  in R5 sprint  to whether have a new entity with new name or reuse already existing entity i.e. LOC_DIM.
2. In sprint 6, we got a statement about when to have  _DK, _KEY, _Id attributes  in CORE entities and when not.
3. Decision about have default values in DDL .
Such things if would  be documented somewhere at a central place , it would be easy to go back and verify whenever  some concerns occurs.

# data[].attributes.headline
Review and update code review checklist as an ongoing process based on learnings

# data[].attributes.subject
Review and update code review checklist as an ongoing process based on learnings

# data[].attributes.body
Start confluence usage to upload relevant baseline documents for ADP to ALPSaaS solution

# data[].attributes.body
Continue generation of test data from the available ALPSaaS sandbox for testing of stories and limit self mock of sync files

# data[].attributes.body
Responding to questions raised in JIRA

# data[].attributes.headline
All Stakeholders should attend the grooming sessions and communicate of delays or if they cannot attend a meeting/grooming sessions as it wastes time of the team

# data[].attributes.subject
All Stakeholders should attend the grooming sessions and communicate of delays or if they cannot attend a meeting/grooming sessions as it wastes time of the team

# data[].attributes.body
create standard test scenarios for unit tests

# data[].attributes.body
moving meeting schedules just assuming this is fine for everyone

# data[].attributes.body
Baseline of Infrastructure document for the product production BOM and setup of the AWS infra as per this document is a prerequisite before start of release sprint