We got a request with the following context:
“The product was started back in 2005 and currently is used and the database of cases/files and time logged on those. But the logic of the product was not completed in full, mostly the invoicing part, balance and billing reports etc…”
The firm has thousands of clients, and that made them look for a way to control the cases and the payments received.
We did a proper discovery phase and captured what the current solution provides and what improvements requires, along with additional features. We migrated product to a safer framework with LTS (long-term support) version for better security, stability and performance. We had to do a good amount of refactoring to ensure features are working smooth and bugs-free. The product included the following features set:
- Database of clients and related cases;
- Contract details, cases types and pricing information;
- Detailed case logs with all information added and presented in a format of a journal with time stamps;
- Creation of invoices and automated regular billing on a defined cycle;
- Tracking of expenses and payments from clients on their cases.
We rewrote legacy PHP system with a more robust and modern framework (Laravel) for scalability and further easier functional extension.
With new solution the firm could scale their entire internal process with automated massive invoicing and accurate data tracking. As a result, we delivered a scalable system that allows tracking operations, financial management allowing significantly reduced time on paperwork.
Process of work
We took the Scrumban approach. Scrumban is a framework that combines important features of two popular agile methodologies: Scrum and Kanban. The Scrumban framework merges the structure and predictable routines of Scrum with Kanban’s flexibility to make teams more agile, efficient, and productive. Scrumban involves applying Kanban principles—visualization of workflow, and flexible processes—to a team’s Scrum framework. But, Scrumban removed some of the more rigid aspects of Scrum and left each team to create a custom approach to development.
We had regular weekly calls about progress and product. Our tasks board was based on Jira tool. Release planning was on monthly basis.
Tools used: Jira, Zoom, Skype, Google spreadsheets.