Documentation
Team Dynamics
- Treasury Swarm Tuesday 11:30am cst
- Biweekly 1:1s
- Monthly retrospective
Planning
Design and functionality questions should be addressed in the planning stage and usually this continues throughout the coding stage.
A project plan must be generated before starting any work on the project and should be updated throughout the project. Project plans serve as an eye into the project for others on the team and upper leadership.
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. Once a PR is approved the engineer who created the PR may merge it into the master branch.
Firefighting
The Treasury UX team has a weekly firefighter rotation where every Monday a new firefigter takes over the responsibility of triaging any customer issues. 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 & Education
Growth is an integral part of being an engineer in the Treasury UX 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 Associate Learning Portal offered by Jack Henry.