How we deliver

We do monthly evaluations on how we deliver and why we do what we do. This process or methodology is constantly evolving and, most importantly, adapting itself to the newcomers. Each new employee, collaborator or client brings something new that we learn from. Hopefully you'll join us and bring something new to this ever evolving team.


We've met, we've agreed to the usual terms and we are ready to start. We haven't done any work together in the past, or maybe we did! But we need to learn from each other in the next month or two before considering we are at full steam.

1 Discover

While the tools are being put in place, we need to understand the bigger goal but also the smaller goals. We need to map out the best route towards what you consider success.

We'll never stop learning from each other but this would be the ramp up. While we process this information a backlog will be put in place and that will be the output of this stage.

2 Plan

Now we have everything in place the team wants to plan out how to go from A to B.

We divide the work in sprints, in the usual Scrum methodology but with a touch of BR's own learnings. We identify task and put them in order according with the priorities and expectations.

3 Design

If a piece of the project needs a prior analysis, then we sure need to gather with the SMEs to come up with the architecture or design before development.

We take the time to document this piece as much as needed, this is instrumental to be able to pass on the knowledge.

4 Develop

Our eager developers are ready to start their coding. We have a sprint to deliver.

5 Test

Our team will run tests locally, debug and then move on to testing in a sandbox environment.

That's when we release for UAT as well. We take testing seriously and UAT is a huge piece of it, final users making a test run before deploying to production.

6 Deploy & Release

When the final users are happy with the new functionality, and we've agreed on a proper time and date, then we'll deploy to production and be on standby for go live support.

All throughout this process you will have the support of key people within Broken Rubik that will represent your interests. The resource manager will be making sure people are aligned to hit the deadlines, the product owner will make sure your requirements are understood and the technical lead will make scalable, performant solutions.


Start sprint iteration again