Agile Principles and Structures

This is how our agile company works.

Agile principles are a structured approach to develop software products in a lean and agile manner. At Ryte we work in an agile organisational structure, that gives us the ability to change faster and invent products, that enable and inspire our users. Therefore, we pay particular attention to technical excellence and great design. Furthermore we always try to improve our processes and give individuals, teams and their ideas the space they need to evolve.

Ryte howto

How did we get there?

Compared to other companies, we invest a lot of time in finding the best talents. And yet, despite the strong growth of the team, the extremely high pace of updates of our software declined. There were more and more projects that depended on cross-team collaboration. After all, with the growth, we had initially set ourselves on a traditional divisional structure. In our search, we came across a publication by Spotify, which describes in detail how an agile organizational structure works. Convinced of the benefits, we decided to change our divisional structure radically and to transform Ryte into an agile organization with so-called „squads“ and „chapters“.

Read more about our agile journey! (PDF, 10Mb)

Working in Squads

Squads are basically mini start-ups within Ryte. They physically sit together as a team and have all the skills and tools they need to develop the particular product. Their common goal is to produce the best product on the market. The basis for the development is the “release early, release often” principle.

At Ryte, we do not fiddle about with project plans for features for months, but quickly build viable prototypes (minimal viable products), bring them to the market, constantly work on improvements, observe and question the resonance, and keep optimizing them.


What are Chapters?

Chapters are the specialist home base of our new structure. Within a Chapter, employees share their professional knowledge. Team members, and thus their Squad, benefit from the experience and expertise pool of their own Chapters. Therefore, the wheel does not have to be reinvented whenever when somebody else has successfully solved a similar problem in another Squad.


Product Owners

Product Owners always have in mind what new products we are developing. They are therefore pursuing the further strategic development of the products and product ideas. They give guidance, are drivers of projects, recognize obstacles, and plan ahead. The PO is a product expert who is strategically brilliant and capable of churning out further developments with the team at a high frequency. They breathe the “think it, build it, ship it, tweak it” principle and makes decisions based on KPIs. He/she reconciles the advancement and development with the highest possible added value for our clients.

Chapter Leads

Chapter Leads are responsible for the how beyond the Squads. They actively work in their subject field, e.g. frontend software engineering in a Squad. Otherwise, they would lose touch with practice and best practice innovations, which would compromise the currentness of our quality standards as well as question their own function as a role model. Chapter Leads ensure that Squad team members use the most effective methods and efficient tools. They assume a professor’s role in their area of expertise and are mindful of technical excellence as well as to the observance of certain standards such as design, branding, code review processes, and other things.

Agile Meeting Structure

agile meeting Sprint1-2 weeks Daily Scrum Meeting Sprint Backlog Product Backlog Sprint Planning Meeting Input from End-Users, Customers, Team and other stakeholders Sprint Retrospective Sprint Review Product BacklogRefinement