Commitments from the team during the Sprint

- At the end of the sprint delivering a thoroughly tested bug-free software.

- Producing the code with the best of the present knowledge adhering to the design principles

- Most of the times developers maintain the code, it’s not always developed from scratch If the code can be improved structurally (refactor)which was missed due to timelines should be addressed in the following sprint.

- Ensure to provide valid commit comments

- Ensure to follow coding styles

- Making sure to write test with code coverage of 80%

- Spending time to learn in-depth, don’t forget to add it to the sprint

- Enabling productive work-space, ideally a workspace with no distractions

- Keeping the manual/readme document of the project up to date.

- Committing regularly to the version control and ensure it is peer-reviewed.

- Avoiding to work on multiple items at the same time. Strictly no context switching

- Never let your teammate feel that he/she is alone.

- Work selfless and help the team to complete the sprint.

- Communication is the key, the scrum board & daily stand-up enables it. Communicate effectively across the team & stakeholders by keeping the board up-to date.

- Attending the meetings on time, respecting others time and speaking with present consciousness, i.e., current sprint matters.

This is a never-ending list, feel free to share your thoughts as comments