Working Agreement on Team Availability/Jira/PR Activity
If you are
away or on leave for more than
two 2 days,
it is it’s your
individual responsibility to catch up on project updates by checking
in with
your teammates. Please ensure you are informed about any important developments or changes you might have missed.When updating the team.
When moving a Jira story
status to
"In Progress,
" please remember to add a short comment
summarizing with the current status or
any relevant details. This helps
anyone who missed the Daily Standup Meeting (DSM) others quickly understand the progress
or any impediments related to the task by reviewing the comments in Jira.If you encounter if they missed the DSM.
Raise any blockers or issues
with your tasks, please raise them during in the DSM
. This allows the team to address the problem promptly and enables anyone with potential solutions to assist.- When teammates ask about the progress of your tasks, please respond politely and constructively, even if you have already updated the information in Jira. Open and respectful communication strengthens team collaboration.
- Always maintain professionalism, be courteous to your teammates, and follow workplace decorum in all communications.
- Senior and Mid need to approve the PR PR Shouldn't remain
so the team can help solve them quickly.
If someone asks about your task, reply politely even if it’s already updated in Jira. Good communication keeps teamwork strong.
All PRs must be approved by a Senior and Mid.
PRs should not stay open for more than 2 days.
Releases are
being managed in a round-robin
mannerrotation.
BRANCHING STRATEGY:
We are following Git Flow Branching Strategy in our partner portal, that defines a strict branching strategy designed around the project release. It provides a robust framework for managing larger projects with multiple developers. Here’s a concise explanation of the Git Flow model:
...