At the kick-off day your team's product manager will present feature requests of different departments that have passed the PMs' pit of trial. After discussing the pros and cons and resolving remaining questions, your team decides on a commitment and dives into programming.
Development will happen in pair programming or by yourself, but always with the backup of your team. Once your code is finished, it has to pass the code review process, which you initialize by creating a pull request on GitHub.
While you wait for the review, Jenkins will run your unit tests and allow or disallow the merging of your branch.
A few iterations later, hopefully all systems are green and your code has passed review. Depending on the feature size, you either create a sandbox or deploy immediately onto the productive system.
A sandbox creation is managed via web UI and enables the departments or QA to test the new feature easily.
Deploying into production is quick and painless. Just command our chatbot hubert to deploy the project for you.
Tools like grafana, graylog or new relic help you to verify that there are no issues and you can have a good night's sleep. Or the opposite happens and you have to bake a cake for the next day.
The next morning, in your team's daily stand-up, you update your team about your feature-of-greatness while high-fiving. Then, you pick a new story and challenge your gray matter once again.