<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

Screenshot 2017-02-15 10.44.42.png

Our Values

image

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

image

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

image

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?

Backlog

Technical Challenge and Starter

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 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

1
Scrum methodology board

Plan

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

2
release-1.svg

Develop and release

We work in weekly sprints, focusing 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

3
burndown-chart-1.svg

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

4
Continual-improvement-1.svg

Continual improvement

The development team has a daily stand-up to ensure they are as strong a team as possible. Moreover, we dedicate time each week to take stock, review the next week’s work and retrospect as to how we can tighten the process further

5

Scrum Masters

Each of our teams includes a Scrum Master. Their job is to coach developers and clients to implement best practice across the project 

Michael Thompson.jpg

Michael

BUSINESS DEVELOPER & SCRUM MASTER

X
8.jpg

Sadiq

BUSINESS DEVELOPER & SCRUM MASTER

University: Birmingham University, BSc Economics

Projects: Lifeshifter, KhanCycle, Driven, Conde Nast

Fun fact: Once completed a 90km in the Iraqi desert

X
Ele Gower.jpeg

Ele

BUSINESS DEVELOPER & SCRUM MASTER

X
Nolan Cain

Nolan

BUSINESS DEVELOPER & SCRUM MASTER

X

What are you working on?