# data[].attributes.body
Set aside some time each sprint for analysis of stories for the upcoming sprint

# data[].attributes.body
Data Model to be completed and share ahead of sprint

# data[].attributes.body
Technical impediments to be highlighted as and and when observed so as to avoid last minute decisions.

# data[].attributes.body
Regularize Pre-grooming and PO-Arch catch ups sessions, stories were directly taken into grooming where a lot of time was spend and solution is still in progress

# data[].attributes.body
Regular catch ups with the team on low level technical/functional scenarios which are missed during grooming so as to avoid bug fixes at later point in time

# data[].attributes.body
Performance test data to be prepared ahead of time before release sprint.

# data[].attributes.body
Interface file handling scenarios should be considered early in the release

# data[].attributes.body
Avoid adding new stories into release sprint as we can't start testing confidently until code is frozen.

# data[].attributes.body
Take inputs from end users when adding/updating views

# data[].attributes.body
[SIBY] : Stop sharing the entire datamodel DDL in emails , that too when changes are happening on a daily basis. DDL changes hasto be version controlled (either in confluence, Bitbucket or anywhere where we can find what has been changed from the latest version easily).Same applies to mapping sheet as well . Mapping sheet should be a consolidated one with version control ON and to be kept in a common place.

# data[].attributes.headline
Start providing the complete set of files(Magrabi files) prior to release sprint.  

# data[].attributes.subject
Start providing the complete set of files(Magrabi files) prior to release sprint.  

# data[].attributes.headline
[SIBY]: We probably need to revisit the points and actions that we have discussed in the past when the same points are repeated in the retro meetings 

# data[].attributes.subject
[SIBY]: We probably need to revisit the points and actions that we have discussed in the past when the same points are repeated in the retro meetings 

# data[].attributes.headline
SIBY;Whenever we integrate altogether a new source with ADP as part of a release , we probably have to park some buffer for dev completion due to unforeseen delays etc.  we have seen we ended up doing major functional stories in the last week of sprint or in the release sprint which will eventually avoid slogging , weekend working etc. 

# data[].attributes.subject
SIBY;Whenever we integrate altogether a new source with ADP as part of a release , we probably have to park some buffer for dev completion due to unforeseen delays etc.  we have seen we ended up doing major functional stories in the last week of sprint or in the release sprint which will eventually avoid slogging , weekend working etc. 