<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=654248448055946&amp;ev=PageView&amp;noscript=1">

Why does methodology matter?

Our methodology builds increasing efficiency into the way we work. This means shipping code as early and regularly as possible. This is critical for getting to market quickly, where you will be able to learn and improve based on how your customers use your product.

Our framework is inspired by agile, lean, scrum and devops thinking. We’ve honed our approach over 9 years of building software for clients

continuous.png

Our Values 

client@2x

Transparency 

No hiding behind technical language, no surprise delays at the end of projects, no ambiguous expectation setting. Everyone on the same page, working towards the same goal.

dev@2x.svg

Inspection

Checking in each day to inspect progress towards the sprint’s goal and identify any problems to resolve. At Theodo, we use physical and digital project boards to give everyone - in the office or away - visibility on progress.

coach@2x.svg

Adaptation

Based on this reflection, we tweak and refine the way we're working. We react quickly in order to maximise the impact of improvements.

Projects change. We’re ready.

What can I expect?

Initial workshops to define project success

starter-needs.png

1 Tech Challenge & Starter workshops

The project kicks off with a technical challenge, where a senior developer builds a mini feature. This allows us to anticipate any technical issues before software development. Then we sit down together at a Starter workshop to clarify the business objective of the project and prioritise which features will get us there.

sprint-production

2 Plan

With a prioritised backlog in hand, we can now plan how to approach the work. Each week, we’ll spend two hours clarifying the detail of each feature with you and then estimating the complexity of this work. This means that both you and the developers have excellent visibility on what’s coming up next, and how long it will take to build.

continuous-improvement-4

3 Develop & Release

We work in one week sprints, focusing first on the features you have prioritised. A successful sprint is one where every item identified in this week’s backlog is done. Once we’ve built the minimum set of features, we can go into automatic deployment mode and release as each new feature is built. 

sprint-board

4 Follow Progress

We check ourselves against burn-down charts which map time against the amount of work we anticipated completing. This means no tunnel vision - if there’s a problem, we’ll solve it before the end of day. We’ll also send a concise daily email with an update on the work done that day.

continuous

5 Continuous Improvement

At the end of each sprint, the team takes time to both celebrate the successes and analyse the problems we encountered. We look to take at least one action each week to make us faster for the next, increasing velocity week on week to deliver value to you, and your users, in lightning time.