Explore the Knowledge base.

Best Practice Guidelines Codebots Basics Features and Extensions Techies Activity Kit Way of Working Release Notes

What do I need to start developing a software application?

Brodie O'Carroll, 25 June 2020

So, you have a rough idea for an app to address some problem in your business - what next? Getting started on any software project can often be overwhelming, so it is crucial to be equipped with the right artefacts prior to building your application.

How often should you be scoping when building software?

Jordi Kitto, 25 June 2020

Discussing how often you should be scoping when building software.

What is a product backlog?

Mikaela Robertson, 24 June 2020

This article will help you understand a little more about building a product backlog. The product backlog is the basis for how a software project is estimated and the roadmap constructed. For the old school, the product backlog is a list of requirements.

Do you scope legacy systems differently?

Tessa Holland, 23 June 2020

Or, how do you scope a legacy migration? While we talk about the many different approaches to scoping, there are certain aspects which can be done differently when you are trying to modernise an existing system. This article explores what those differences are, and the most effective way you can modernise your product.

What do you need to design to build software?

Brodie O'Carroll, 15 June 2020

The basics of what you need to make while scoping a product.

How do I scope like a pro?

Isaac Joe Kong, 15 June 2020

Scoping is more than process, its a whole mindset that can help you unlock

How can I use Design Thinking to scope products?

Isaac Joe Kong, 15 June 2020

Design Thinking is a fantastic method for getting ahead in business.

Why is scoping important?

Tessa Holland, 15 June 2020

Understanding the importance of scoping out a project before you begin work.

What is the difference between Scrum and Kanban?

Mikaela Robertson, 09 June 2020

The quick answer is that Scrum uses sprints and delivers software at the end of each iteration. There is a Scrum guide that details all of the principles and practices of Scrum. Scrum is considered to be Agile. On the other hand, Kanban uses a continuous flow of work and delivers software when it is ready. The Kanban philosophy has roots in lean manufacturing and limits the work in progress through a pull mechanism to do work. It can also be considered to be Agile.

When is the right time to converge or diverge my scope?

Isaac Joe Kong, 02 June 2020

Understanding when it is time to foster ideas or when it is time to focus on solutions during a project scope.

What are some scoping best practices?

Tessa Holland, 22 May 2020

A few of the key things you can do when scoping a product to ensure it hits the mark.

How do I scope out a project?

Tessa Holland, 22 May 2020

Part of being a product designer is learning how to navigate the start of a project so you can help your team and clients understand exactly what needs to happen to get started.

The cone of uncertainty experiment

Declan Healey, 15 May 2020

The cone of uncertainty is a powerful tool depicting the uncertainty about the time required to complete a project, based upon the amount of knowledge (or lack thereof) at the beginning of a project. In this article, we explore an experiment conducted by a team of people at Codebots to determine how the application of a cone of uncertainty could enhance project estimations.

The tech spike experiment

Mikaela Robertson, 15 May 2020

Tech spikes are an important part of our Way of Working, as they help us reduce the complexity and unfamiliarity of an issue for high risk projects. The tech spike experiment was conducted following the introduction of the risk matrix, as we began to notice issues that had higher risks were too difficult to estimate with a reasonable level of precision. In this article we will follow the how to propose an experiment methodology to understand why Codebots decided to start using tech spikes in our projects.

The software risks experiment

Jordi Kitto, 13 May 2020

In this article we will look at an experiment the Codebots team conducted to discover how we could best manage software risks.

What are experiments? Using science to solve business problems with heart.

Tessa Holland, 11 May 2020

An experiment is a scientific method of evaluating ways to solve a problem. In this article, we’ll explore how we run experiments at Codebots, and explain why it’s essential for all businesses to encourage their employees to develop an experimental mindset.

Why is science so important?

Declan Healey, 11 May 2020

In an age dominated by the spread of misinformation, it is crucial to remember the pursuit of truth is what lies at the heart of the scientific endeavour. As we embark on this journey of discovery, we should always be asking ourselves the following - How do we know what is true? Who and what should we trust?

How do you convince people not to use Waterfall?

Eban Escott, 01 May 2020

Have you ever been in a meeting where someone is stuck in a waterfall mindset? I have. Many times. And if you start out a project where this still lingers, you have effectively left your future self a land mine and when you step on it … bang! Your project will derail and life will not be fun.

What is the best software development methodology?

Eban Escott, 01 May 2020

If you are new to software development methodologies, you can think of them like a recipe for cooking. A cooking recipe usually gives you a list of ingredients with their weights/volumes, an instruction list of some sort, and eventually you will serve it up for people to eat. Because the recipe is written down, other people can follow it.

What is a Way of Working?

Eban Escott, 01 May 2020

Every organisation has a different way of working. Some organisations align themselves with a specific methodology, but the truth is they usually only use a subset of what’s available and end up making their own hybrid approach. The philosophy behind a Way of Working is to embrace this.