Documentation
Team Dynamics
- Stand-up meetings Monday thru Thursday
- Biweekly 1:1s
- Monthly retrospective
Assignments
- Planning
Design and functionality questions should be addressed in the planning stage and usually this continues throughout the coding stage. API documentation should also be merged into the consumer-api-docs page.
A project plan must be generated before starting any work on the project and should be updated throughout the project. Follow the instructions here on generating project plans. Project plans serve as an eye into the project for others on the team and upper leadership.
Jira tickets should be created in the Online team working board to keep track of the progress on each of the tasks documented in the project plan. Only one ticket per engineer should be in the ‘In progress’ column and each ticket should be linked to the Epic for the project.
- Coding
Once the project plan has been approved by two members of the team and the Jira tickets have been created, work on the project can start. The JS Code Style Guide is a great reference on best practices and guidelines followed by the team. A pull request should be created for each Jira ticket in the working board and can only be merged into the master branch once a member of the team has approved it. At the end of the project, the code will go through a QA process where any bugs or changes are adressed by the Product team. The engineer will then create a new PR with the fixes/changes in place and submit screenshots or video to the Product team for approval.
- PR (pull request) reviews
Deploying quality code to production is an essential resposibility for the team. Engineers should review and test PRs to catch any bugs and/or improve code before sending code to production.
- Firefighting
The Online team has a weekly firefighter rotation where every Monday a new firefigter takes over the responsibility of triaging any customer issues found in Jira service desk. More firefighting responsibilities and processes can be found here.
- Documentation
It is everyone’s job to maintain documentation. Doc day was established to set aside one day per quarter to update or add any new documentation to the wiki’s. This does not mean that documentation should not be updated frequently! Take time throughout each work week to update any outdated documentation or to add new documentation.
Growth
- Growth is an integral part of being an engineer in the Online team. Engineers are encouraged to continue learning best practices and new technologies related to the job responsibilites. There are multiple resources avaibale to engineers to continue their software engineering education found in the resources page. Engineers are also encouraged to continue their education through the Education assistance program offered by Jack Henry.