# data[].attributes.body
retro: https://drive.google.com/drive/u/0/folders/1DGvnmALL__WFfwIeYiCFv8juW6NN7QRa?ogsrc=32

ppt:
suggestion: Shall we combine both of the ppt's?
August: https://docs.google.com/presentation/d/1aPkGsZseslqKjHRWVJevl1mKkZjvlMtcfqwwY-rXYNg/edit

July: https://docs.google.com/presentation/d/18YUQQco_9y07vcVzo-G-SSOu-VT0zGpMbjKUtT8-YOY/edit

# data[].attributes.body
1) Prepare yourself well before sprint planning/design discussions etc.
2) Post your stand-up on slack if not sure of attending stand up (even when you're WFH, to avoid any last minute mishap e.g network issue)

# data[].attributes.body
+Thanks Niraj for support and guidance
+Support team seems to be doing good

# data[].attributes.body
Lost lots of data including a lot of unpushed code, we should make a habit of creating backups (pushing code, configuration backups and other imp. data) in regular intervals to avoid any mishaps.

# data[].attributes.body
- productiveness seems to be getting reduced because of increase in interruptions
we should try to collect possible thoughts beforehand and call for meeting in case of more time required, we should avoid making workplace(open space) looks like battle ground.
- increase in unplaned leaves/WFH
we should try to give heads up in advance
- planned meetings / discussions are not given due importance
we should prepare our self before going to meetings / discussions, it will help us reducing time of the meetings / discussions, sometime it seems like we even do not have went through story/task

# data[].attributes.body
+ no more long waiting or critical tasks in support board
+ lots of most awaited stories/features delivered in PRO

# data[].attributes.body
We should properly divide and analyze task before starting.

We should try to push the code by EOD.

Too many sick leaves, can't do anything.

# data[].attributes.body
Thanks to Satheesh for his contribution in Pro while working on support.

Great collection of stand up data by Vikash.

Thanks Satheesh, vikash, Neeraj for time to time help.

# data[].attributes.body
- Lesson learnt, always create remote branch and keep pushing your code

- We didn't collaborative well. Always remember, we work as a team, if one person lag behind, it impact the whole team commitment. Seek help in the right time and avoid the last min surprises.
- PRO Team progress wasn't really speaking about our efficiency. Definitely our productivity need to be improved.

# data[].attributes.body
+ Good efforts @vikash for compilation of SU status, including attendees
+ @niraj Thanks for the help & assistance in support related works.
+ Reduction in number of support task, (Good work @niraj in ur support duration)

# data[].attributes.body
+ Thanks Niraj for your time to time input  on Task I work, Helps reduce review time.
+ Thanks Satheesh for helping in Pro while working on Support and for you feedback on personal growth
+ Nice to see SU time stats, Thanks to vikash

# data[].attributes.body
- SU punctuality, should we reconsider time?
(If late, plz post on slack instead of joining n between)
- Last minute absence notice, plz notify tentative leave/WFH (or missing SU) as early as possible
- Focus on delivering one task at a time i.e. development/review/feedback/review can be prioritize in a better way.

# data[].attributes.body
+ Satheesh handling support stuff and contributing on PRO too (WEll DONE)
+ Code quality improvement in Egreement PRO
+ SU time (Action point from last sprint) suggests we're doing good, there will always be room for improvement for explaining oneself
-Stats-
https://docs.google.com/spreadsheets/d/1s1fEfJLP_Z-AxCTEpJpWMNq1bxjs8ImHGWzHYcOLB6M

# data[].attributes.body
- Too  many unplanned leaves. Although it was due to sickness but we should at least try to give heads up for tentative leave by seeing last few days availability if possible, instead telling in morning.
- Try to push code at the end of the day ad we should not let our system ruin our days of work and It also help other person to continue if assigned person is not available.
- We should try to listen to the person untill he has finish before putting our point. When we make hurry to put our point sometimes we ignore the the point of person  we are talking to. (No for pointing towards someone, It happens to me also sometimes)