# data[].attributes.body
Have a dedicated dev resource in release sprint for supporting PT

# data[].attributes.body
Avoid stories in the release sprint that needs to be part of the same release.

# data[].attributes.body
Need to come
up with a strategy to decide on usage of same env by multiple user working on different stories impacting same table.

# data[].attributes.headline
approach on maintaining or updating the mappingsheet where we have changes either in table structure or mapping in different stories.

# data[].attributes.subject
approach on maintaining or updating the mappingsheet where we have changes either in table structure or mapping in different stories.

# data[].attributes.body
We first do dev and then later we reflect these changes in mappingsheet , it should have been done other way round.

who is owning mappingsheet? Is every individual is supposed to update it as and whn we are working on stories ? if yes, please incorporate a rigid approach to follow this.

# data[].attributes.headline
[Dhana] Include NFRs in the Stories, including OAT like Interface mechanism when adding new feeds

# data[].attributes.subject
[Dhana] Include NFRs in the Stories, including OAT like Interface mechanism when adding new feeds

# data[].attributes.headline
Please take latest code from bit bucket before working on any changes..

# data[].attributes.subject
Please take latest code from bit bucket before working on any changes..

# data[].attributes.headline
Start attaching the updated metadata and DDL into the bit bucket rather than attaching the updated metadata sql query in JIRA.

# data[].attributes.subject
Start attaching the updated metadata and DDL into the bit bucket rather than attaching the updated metadata sql query in JIRA.

# data[].attributes.headline
The deployment of all the stories should adhere to the timeline

# data[].attributes.subject
The deployment of all the stories should adhere to the timeline

# data[].attributes.headline
Guneet: Lots of Gaps found in the Release Sprint and new dev stories had to be absorbed in Release Sprint, We need to be pro-active and analyse gaps before the release sprint, Also, there is a gap between Dev and architects understanding, more collaborative work environemtn is required

# data[].attributes.subject
Guneet: Lots of Gaps found in the Release Sprint and new dev stories had to be absorbed in Release Sprint, We need to be pro-active and analyse gaps before the release sprint, Also, there is a gap between Dev and architects understanding, more collaborative work environemtn is required

# data[].attributes.headline
Guneet : More catch ups between business and architects required- There has been assumptions and gaps in this Sprint - related to CORE Views - probably because DSA was not updated and approved

# data[].attributes.subject
Guneet : More catch ups between business and architects required- There has been assumptions and gaps in this Sprint - related to CORE Views - probably because DSA was not updated and approved

# data[].attributes.body
and Token type/code changes in Order Fact table

# data[].attributes.headline
New Version Control Data Model needs to be in place ASAP, lot of rework is happening because of datamodel updates - need to fix hard deadline for this

# data[].attributes.subject
New Version Control Data Model needs to be in place ASAP, lot of rework is happening because of datamodel updates - need to fix hard deadline for this

# data[].attributes.body
We should take a rule that pre-requistes for development such as mapping and datamodel is updated before taking up any task. We currenty reverse engineer

# data[].attributes.body
All stakeholders need to be in standup call especially in release sprint so that issues can be highlighted if any

# data[].attributes.body
Evaluation of fitnesse test automation options which will also be estimated for.