# data[].attributes.headline
Be cognizant of all aspects of the tickets that are being worked on 1) tkt number; 2) Dp number 3) priority of tkt 4) what problem it is solving etc..

# data[].attributes.subject
Be cognizant of all aspects of the tickets that are being worked on 1) tkt number; 2) Dp number 3) priority of tkt 4) what problem it is solving etc..

# data[].attributes.body
-Priti

# data[].attributes.headline
For tickets that need a handOff or FW from dev; add a subtask for it and close it once walkthru is done. Capture knowledge gained for re-use on future tickets.

# data[].attributes.subject
For tickets that need a handOff or FW from dev; add a subtask for it and close it once walkthru is done. Capture knowledge gained for re-use on future tickets.

# data[].attributes.body
-Priti

# data[].attributes.body
We are spending time with discussions that has nothing to do with the 3 basic questions. AI suggested: If someone has a parking lot item he/she should mention it in the status indicating who is needed for the post scrum discussion.

# data[].attributes.body
DP tickets visibility can be improved

# data[].attributes.body
All of us should know the business rules behind particular pages/flows, etc. To have a clear picture of what the system must do and must not do.

# data[].attributes.body
We are spending too much time on testing P1 prod issues. Fixing the issue in some cases take 10 to 20 mins but testing more than 3 days.

# data[].attributes.body
We are going to validate something in prod & we do not have the resources to validate it. Example Attendance mobile app issue

# data[].attributes.body
Late sprints' scopes change due to a lot of incomming prod issues and changes of priority. Daily meetings play an important role to catch up with what is going on. -mathi

# data[].attributes.body
unreal amount of story points assigned to one person

# data[].attributes.body
I think that for some complex tickets we should do a quick FW

# data[].attributes.body
Make Daily Status Order more efficient.
Possible action items:
1) Speaker will randomly pick next speaker
2) Keep it consistent
3) Pay attention
4) Non-status items to parking lot.

# data[].attributes.body
Try to anticipate FW in planning sessions and create a subtask to execute FW. Results should be captured and documented accordingly and attached to the ticket.

# data[].attributes.headline
Be cognizant for tickets that are currently being worked on

# data[].attributes.subject
Be cognizant for tickets that are currently being worked on

# data[].attributes.body
Everyone should be aware of:
1) TMS Ticket Number currently assigned to you in JIRA
2) DP ticket number (if applicable) and TMS Tickets Linked to the DP
3) Ticket Priority and Status
4) Problem being solved
5) Keep teammates updated with status