# data[].attributes.body
Wherever possible breakdown stories such that it falls within 3 SP. This makes it easier to manage.

# data[].attributes.headline
Guneet: Link the bitbucket commits to the story

# data[].attributes.subject
Guneet: Link the bitbucket commits to the story

# data[].attributes.headline
Guneet: - Move the status of Jira tickets on regular basis

# data[].attributes.subject
Guneet: - Move the status of Jira tickets on regular basis

# data[].attributes.headline
Guneet - Planning of grooming session ahead of time to avoid last minute changes to the story

# data[].attributes.subject
Guneet - Planning of grooming session ahead of time to avoid last minute changes to the story

# data[].attributes.headline
Guneet: PT results/ P2 bugs in the Sprint to be highlighted in daily scrum calls as soon as they are realized. In case of P1 or critical issues, this can be shared in high importance emails

# data[].attributes.subject
Guneet: PT results/ P2 bugs in the Sprint to be highlighted in daily scrum calls as soon as they are realized. In case of P1 or critical issues, this can be shared in high importance emails

# data[].attributes.headline
ARP source was picked up in last sprint( just prior to release sprint) to load all 3 layers ( STAGE, RELATIONAL & MD). This should have been avoided and STAGE loading should have been picked up in earlier sprint. ARP got many data issues and unanswered questions, which delayed RELATIONAL tables loading and testing.

# data[].attributes.subject
ARP source was picked up in last sprint( just prior to release sprint) to load all 3 layers ( STAGE, RELATIONAL & MD). This should have been avoided and STAGE loading should have been picked up in earlier sprint. ARP got many data issues and unanswered questions, which delayed RELATIONAL tables loading and testing.

# data[].attributes.headline
Guneet- Analysis of the stories before the sprint begins to avoid last minute updates in dev

# data[].attributes.subject
Guneet- Analysis of the stories before the sprint begins to avoid last minute updates in dev

# data[].attributes.headline
Publish the Sprint plan to entire team for timelines and share weekly maybe a Friday or Monday Update

# data[].attributes.subject
Publish the Sprint plan to entire team for timelines and share weekly maybe a Friday or Monday Update

# data[].attributes.headline
Instead of having a generic statement of "working on xyz story", scrum call tracking should talk about in-progress, completed, open subtasks. i.e. what is completed y'day and what will be picked up today.

# data[].attributes.subject
Instead of having a generic statement of "working on xyz story", scrum call tracking should talk about in-progress, completed, open subtasks. i.e. what is completed y'day and what will be picked up today.

# data[].attributes.headline
subtasks are created at implementation level which helps in tracking whats completed and whats pending.

# data[].attributes.subject
subtasks are created at implementation level which helps in tracking whats completed and whats pending.

# data[].attributes.body
In case of stories needing detailed analysis, the analysis spike should be taken in the sprint prior to story development. so that there will be less questions once dev starts.

# data[].attributes.headline
permissions to embed the  response on users comments in JIRA.

# data[].attributes.subject
permissions to embed the  response on users comments in JIRA.

# data[].attributes.headline
start providing the confluence link in related story e.g. if DSA updated or data model changed or a new confluence page got created to store some information  as part of discussion of a story then please provide link of confluence in story.

# data[].attributes.subject
start providing the confluence link in related story e.g. if DSA updated or data model changed or a new confluence page got created to store some information  as part of discussion of a story then please provide link of confluence in story.

# data[].attributes.body
Data mappings given in jira comments and emails

# data[].attributes.headline
Start creating mapping sheet for relational to multi dimensional loading.

# data[].attributes.subject
Start creating mapping sheet for relational to multi dimensional loading.

# data[].attributes.body
Data mapping should be kept in a single place with version control ON . It is will be easy for a new person if its given in a single place

# data[].attributes.body
Stop the back and forth changes in datamodel and mapping  atleast from second week of sprint . This will probably reduce the other concern of having lot of comments in the Jira

# data[].attributes.headline
Stop taking integration stories before the Release Sprint, needs to be picked well ahead

# data[].attributes.subject
Stop taking integration stories before the Release Sprint, needs to be picked well ahead