# data[].attributes.body
SP# 08 - 39 vs 43 (110%)
SP# 09 - 53 vs 48 (91%)

# data[].attributes.headline
Challenges or issues discussion while taking individual updates in standup

# data[].attributes.subject
Challenges or issues discussion while taking individual updates in standup

# data[].attributes.body
Discussion on any story with challenges or taking inputs from other team members should be done as part of parking lot item instead of discussing during the scrum updates. This will help in taking updates from all the team members and only respective folks can stay to further discuss on their challenges or issues

# data[].attributes.body
Story description should be elaborated more with the requirements for better understanding

Stories should be delivered to QA by mid of sprint so there will be ample time to finish testing instead of delivering on last day sprint and rushing QA for closure on the 1st day of next sprint

Stories should be deployed to test env for QA validation instead of testing in dev env

Code should be merged into the main branch before moving for testing instead of feature branch

# data[].attributes.body
Create Tasks once the planning is completed (Tasks to be created on the same day before Sprint is started).
Update Effort estimation and hours spent on daily basis (before the standup).

# data[].attributes.headline
Developer onboarding documents should be improved and centralized, taking long time for new developer to onboard.  

# data[].attributes.subject
Developer onboarding documents should be improved and centralized, taking long time for new developer to onboard.  

# data[].attributes.headline
Sprint planning should not be on same day and should be divided and completed before sprint day (Wednesday)

# data[].attributes.subject
Sprint planning should not be on same day and should be divided and completed before sprint day (Wednesday)

# data[].attributes.headline
Team making progress however we have many assumptions and unknowns.

# data[].attributes.subject
Team making progress however we have many assumptions and unknowns.

# data[].attributes.headline
Ad hoc tasks should be planned better so that it will not impact sprints. (Ex: Devops, Security)

# data[].attributes.subject
Ad hoc tasks should be planned better so that it will not impact sprints. (Ex: Devops, Security)

# data[].attributes.body
Effective planning was done - however Astra Core was a new team, Groomed the stories based on the Backlog available. Worked with the Product Owner.

# data[].attributes.body
Co ordination is very effective, we will continue to do the same.

# data[].attributes.body
Feature Branch should be used for Development Branch.
QA will rely on the Test Branch.

# data[].attributes.headline
We should have proper grooming for stories. 

# data[].attributes.subject
We should have proper grooming for stories. 

# data[].attributes.body
- Grooming should be done after the Mid sprint , so that the team will have better clarity in Estimation which inturn helps in effective planning.

# data[].attributes.body
Please add more details , will help us to improve?

# data[].attributes.body
Documents should be be centralized for the new joiners which will reduce the time in co ordinating with the Peers.

# data[].attributes.body
Impact analysis to be performed when there is an Adhoc request and make the requestor and the team aware .
Obtain Approval before accepting.