Approach

How we work

OUR APPROACH

Our agile working process tailored to your needs

At Maxcode, we aim to build a customer-centric environment where our employees are responsible for the success of their projects. Our dedicated teams are client-focused and their approach leverages Scrum to ensure client satisfaction. The well-known benefits of using Scrum are simple: Quick results, predictable duration, flexible and transparent from the start.

Starting a new project

Create a brief

1. Meeting with you

We schedule a meeting to exchange ideas and discuss concepts. It helps us to understand the requirements and expectations of your product or service. We like to understand your ambitions, the scope, and the overall context. This meeting can take place face-to-face on location, by conference call or a combination of both.

Create a brief

2. Describing the assignment

We write down the assignment, describing your initial ideas, concepts, and expectations. We share this with you and ask for feedback, corrections and approval. We want to achieve a mutual understanding of your project’s end goal, timelines and desired results.

Create a brief

3. Selecting the team

We select one of our teams to work on your project. Maxcode has several highly-skilled teams. The one chosen for you will be involved in defining and improving your idea up to the point it becomes a full-blown product. We strongly believe that the sooner a team is involved, the more effective future effort will be. Furthermore, whether you choose to do a small or large project with us, whether you stop for a while or continue development, we will do our best to maintain the team – client relation. This assures that knowledge of your application stays available, regardless if it’s about new development, maintenance or a simple question.

Create a brief

4. Creating the Product Backlog

We create a Product Backlog. The team assigned to handle your product works on the first version of this Product Backlog. A list with to-be-delivered functionalities (expressed in User Stories) that is prioritized in order of added-value of your product, and ultimately, of your business. This Product Backlog forms the basis for further discussions and will be the basis for our proposal.

Create a brief

5. You play an active role

You are invited to join the team as Product Owner and make decisions, such as determining the priorities of the functionalities in the Product Backlog throughout the development process. If your availability is limited, we can obviously provide assistance in handling the administrative parts of the typical Product Owner tasks.

Create a brief

6. Receiving your proposal

We create a proposal based on the latest version of the product backlog. It will include a couple of Sprints (usually periods of two weeks with a specific team size) enabling you to begin developing the product.


Product releases & MVP

The trend nowadays is to release a version of the application fast and perform ongoing updates throughout the development phase and beyond, also known as ‘Continuous Development’. It seems to be the driving force behind management’s decision to work in an agile way.

At Maxcode, we believe the process referred to as the Minimum Viable Product (source: The Lean Startup by Eric Ries) can be combined perfectly with Scrum. An experienced Product Owner uses his skills to collect as much information as possible from stakeholders and prioritizes it by means of a Product Backlog, but the most honest and maybe valuable type of feedback is the feedback coming from the end-user. The product may not be final, it pays to test ahead of time in order to assess as soon as possible what works and what doesn’t.

Used correctly, the framework guarantees that the functionality adding the most value for your product is built first.

The MVP is not that version of the product of which you are convinced that it contains all or exclusively the functionality you think it should have. The quintessential is to collect that information from real users as soon as possible, before you invest (or waste) too much.

The MVP is better described as a repetitive strategic process consisting of generating the idea, creating a prototype, collecting (user) feedback, analyse and learn. The end goal is to build a good product that users want to buy and use.

Each phase holds clearly-defined results:

  • The application or product
  • The feedback (from users)
  • (Modified) ideas for the next version of MVP

We encourage you to release your application in a early stage to figure out your customers’ needs and expectations. Throughout the measuring and learning phases of the development of your product, you continuously refine your next version of the MVP and update your Product Backlog. Following these steps, we are ready to continue with the next release.