Our Process

The best way to get a project done faster is to start sooner.


Agile development

We employ an iterative, incremental development approach to optimise predictability and control risk.

Scrum, a better way to build software

Scrum is an iterative and incremental software development methodology for managing product development. It focuses on building software that meets business needs.

Scrum, a better way to build software

Scrum is an iterative and incremental software development methodology for managing product development. It focuses on building software that meets business needs.

Scrum
Scrum

Scrum Framework

A quick overview of the Scrum framework

A product owner creates a prioritised wish list / requirements called a product backlog.

During sprint planning, the team pulls a small chunk from the top of that wish list, a sprint backlog, and decides how to implement those pieces.

The team has a certain amount of time (a sprint) to complete its work, but it meets each day to assess its progress (daily Scrum).

Along the way, the Scrum Master keeps the team focused on its goal.

At the end of the sprint, the work should be potentially shippable: ready to hand to a customer, put on a store shelf, or show to a stakeholder.

The sprint ends with a sprint review and retrospective.

As the next sprint begins, the team chooses another chunk of the product backlog and begins working again.

The cycle repeats until enough items in the product backlog have been completed, the budget is depleted, or a deadline arrives. Which of these milestones marks the end of the work is entirely specific to the project. Scrum ensures that the most valuable work has been completed when the project ends.

Scrum Agile

Scrum Framework

A quick overview of the Scrum framework

A product owner creates a prioritised wish list / requirements called a product backlog.

During sprint planning, the team pulls a small chunk from the top of that wish list, a sprint backlog, and decides how to implement those pieces.

The team has a certain amount of time (a sprint) to complete its work, but it meets each day to assess its progress (daily Scrum).

Along the way, the Scrum Master keeps the team focused on its goal.

At the end of the sprint, the work should be potentially shippable: ready to hand to a customer, put on a store shelf, or show to a stakeholder.

The sprint ends with a sprint review and retrospective.

As the next sprint begins, the team chooses another chunk of the product backlog and begins working again.

The cycle repeats until enough items in the product backlog have been completed, the budget is depleted, or a deadline arrives. Which of these milestones marks the end of the work is entirely specific to the project. Scrum ensures that the most valuable work has been completed when the project ends.

Our Procedure

Before creation, there's thinking. Our process is sharp and lets us craft the best quality.

1
1
Think

It begins with conceptualizing. What features must be implemented and how to achieve this in a way that caters to the client's needs. We carefully think through the necessary steps to ensure the utmost quality of software or mobile applications.

2
2
Create

We don't just create plans. We execute them. The next phase is implementation, where great ideas are brought to life by our talented development team. The goal isn't merely starting the project; we intend to go beyond and exceed expectations.

3
3
Iterate

The final phase is trial and error. Find what works best, rinse, and repeat until we achieve the desired outcome. We collaborate with the client regularly in measuring project progression, so they can monitor if everything aligns with their vision and adapt accordingly if otherwise.

Product Owner

Innovation requires dedication, hard work, and discipline.

Backlog items

The Product Backlog

The product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The product owner is responsible for the product backlog, including its content, availability, and ordering.

The Product backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the mobile app or software in future releases. Product Backlog items have at least a description, order, estimate and value.

We will maintain the product backlog in an electronic tool (Jira) and provide you access to your project. Here you can view and maintain the product backlog, view the sprint backlog and have insight into the progress of the sprint.
Backlog items

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.

The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.
Sprint backlog

Our Deliverables, Your Product

We must meet the definition of 'done' to ensure quality.

Done

Definition of 'Done'

When a Product Backlog item or an Increment is described as ‘Done’, everyone must understand what ‘Done’ means. The scrum team has a shared understanding of what it means for work to be complete, to ensure transparency. The Scrum Team uses it to assess when work is complete on the product Increment. The product owner can also be assured that the increment delivered is according to BPO Technology’s standard.
Done

Our standard definition of done includes:

The code for the backlog item is completed

The code is commented, and checked in current version of source control

Peer reviewed (or produced with pair programming) and meets development standards

Build has no errors

Unit tests written and passing

Deployed to system test environment and passed system tests

Passed UAT (User Acceptance Testing) and the status updated on the project board

Build/deployment/configuration changes implemented, documented & communicated

Relevant documentation/diagrams produced and/or updated

Our standard definition of done includes:

The code for the backlog item is completed

The code is commented, and checked in current version of source control

Peer reviewed (or produced with pair programming) and meets development standards

Build has no errors

Unit tests written and passing

Deployed to system test environment and passed system tests

Passed UAT (User Acceptance Testing) and the status updated on the project board

Build/deployment/configuration changes implemented, documented & communicated

Relevant documentation/diagrams produced and/or updated

Definition of done

Our Talent

Develop talent for tomorrow, rather than just hire for yesterday.

Our talent

Good talent

Having good talent means taking our responsibility and being a good employer. We take care to be fair and socially responsible towards our talent. We pay above average wages, and for each hour we can book to a client, we will contribute a fixed sum to an employee share fund. This will be distributed evenly among employees irrespective of whether they have worked directly on projects or not.
Our talent

Our Rules

Our process requires some rule, they are:

1

The customer provides a description, specification (product backlog) and/or prototype of the required software or mobile application based on our set standards. User stories, behaviour & expectations.

2

The customer is the product owner and is responsible for the product backlog. He/she participates actively in the process.

3

There will be a defined standard for what we deliver according to our ‘definition of done’. There are optional items that can be added to the ‘definition of done’ resulting in additional hours.

4

Customer acceptance will only take place once we have delivered it according to the definition of done.

1
The customer provides a description, specification (product backlog) and/or prototype of the required software or mobile application based on our set standards. User stories, behaviour & expectations.

For fixed price contracts it’s imperative that we have a clear understanding of what is required before we agree on the scope and price. We can help with this on a time and materials basis and have experts in prototyping available to quickly simulate what you want.
2
The customer is the product owner and is responsible for the product backlog. He/she participates actively in the process.
3
There will be a defined standard for what we deliver according to our ‘definition of done’. There are optional items that can be added to the ‘definition of done’ resulting in additional hours.
4
Customer acceptance will only take place once we have delivered it according to the definition of done.

Contact us

Dont struggle anymore to manage your projects. Let us do the hard work.

Reach out for Support or any other question.

At BPO Technology, we know that your business is unique. That’s why we provide free consultations to understand you through your needs, the scope of your goals, and your budget.

Software quality begins with the quality of the requirements.

Get started