Agile, Collaborative and Client Focused.

We believe that by working together, and alongside our customers, we enable our collective success. Our process is central to this belief.

Process Hero Section

Our agile framework

Our agile framework is a combination of Scrum and Kanban. Kanban principles underpin our scrum framework which means our developers have a sharp focus on finishing tasks before starting others, and limiting work in progress for fast and efficient results.

agile

Key aspects

Highlights of our process


Collaboration

We manage and monitor progress via stand-up meetings with clients every 2 days. This creates a shorter feedback loop to create an amazing product.


Transparency

Our clients have full access to all project artefacts from day one, including project backlog (JIRA), technical documentation, and online project status reports.


Budget Control

You have full visibility of budget spent via online Project Status Dashboard, including budget burn-down vs features, feature delivery matrix, and a full review of project at the end of the sprint.

Our Quality Assurance Philosophy

Quality Assurance

QA

The team works closely to collaborate on feature build with developers showcasing the work to the rest of the team while in development to ensure that they are building the right Product

We follow an agile testing methodology. This means that the whole team is responsible for the quality of the product including Business Analyst, Developers and Testers.

As the whole team is involved from Story Grooming Sessions to the delivery of the feature, we focus on building the right feature the first time

We focus on Testing throughout vs Testing at the end; Preventing bugs over finding bugs; Testing understanding over checking functionality; Building the best system over breaking the system   

Requirements Gathering

User Story Grooming Sessions

We take a ‘just in time’ requirements clarification approach to product backlog. This means that the user stories that are selected for the upcoming sprints are groomed first and must be ready for the development to start

user stories

You have visibility

Project Status Dashboard

The project Status Dashboard starts with an overview with an overall project status including a budget burn-down to give status on the health of the project. The burn-down chart represents the features delivered against the budget. The team can use this information to make informed decisions on priorities

status dashboard

Hear from the team

Agile Blogs and Insights

You are faking agile without real customer collaboration Imran Qazi・Sep 16, 2020 Read more... The Art of Criticism Parham・Sep 15, 2020 Read more... Is your organisation taking care of the Golden Goose? Parham・Sep 15, 2020 Read more... How to improve Scrum using Kanban Imran Qazi・Nov 21, 2019 Read more... How we created a self-organizing Team Rewards Culture Imran Qazi・Sep 11, 2019 Read more... Make Everything Visible Imran Qazi・Feb 26, 2019 Read more... Make your team awesome Imran Qazi・Oct 18, 2018 Read more... Modern Agile — Ultra light guiding principles that might actually work Imran Qazi・Jul 2, 2018 Read more... Reflection on Principle 10 — Simplicity — the art of maximizing the amount of work not done — is… Imran Qazi・Apr 6, 2018 Read more... Reflection on Principle 7 — Working software is the primary measure of progress Imran Qazi・Apr 6, 2018 Read more...

Find out more

Supported browsers

For the best experience using Lapis website, we recommend using the latest version of Chrome, Firefox, Safari or Edge.

Lapis website also runs on mobile web browsers.

To upgrade to the latest version, click on your browser:

To check what browser version you are using, visit   What Is My Browser