“This brings developers into contact with the day-to-day operation of their software. It also brings them into day-to-day contact with the customer. The resulting customer feedback loop is essential for improving the quality of the service." - Amazon CTO Werner Vogels
In Orbit, this means that we build it, we run it, we secure it, we scale it, we support it, we sell it, etc...
In Orbit we aim to be agile, without necessarily adhering to a certain methodology, but rather pick and choose from best practices to find OUR way of working.
The aim of this page is to give a simple introduction and explanation to some of our agile ceremonies and artefacts.
<aside> ‼️ All structure, governance and rules for which ceremonies we choose to adopt, how we work, and such, is to be viewed as “work in progress” and should be susceptible for change at any given time when improvements are suggested, tested and implemented.
</aside>
In agile we employ certain ceremonies. The aim of these ceremonies is to create a framework around which we build the structure of our way of working. It should be a loose (fr)agile framework.
What is it: The purpose of the planning is to decide on WHAT should be done in the next iteration, breaking them down into suitable sub-tasks if necessary and distributing them around the team.
Responsible: Tech lead for each team
Audience: Team, but other teams can observe to gain insights or if coordination is required.
Tips for the planning:
What is it: Daily team sync. Usually done by focusing on the three Ps: Progress, Problems & Plans. In its essence, it's all about getting everyone up to speed, and most importantly; to figure out impediments that are hindering progress, and how to mitigate those.
Responsible: Team