Accounting Software Dev & QA for Solutions Firm
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private enlightenation is amended.
Introductory enlightenation
Introduce your business and what you do there.
I’m the technical ruler at a technology and software solutions firm. We execute software consultancy, fetch firms into the digital era, and furnish program treatment pieces. Our flagship fruit, Prosper, is a practice treatment tool for small-to-medium-sized accountant firms.
Desired goal
What challenge were you trying to address with Solid Software?
One of our clients needed a practice treatment software to help with workflow aspects like onboarding, prospecting, team scheduling, and time-keeping. We establish nothing that existed to the grade we wanted, so we needed a software organisation to help us create the solution.
Provided solution
What was the aim of their involvement?
Solid Software really built and developed seething from scratch. Prosper is a cloud-based, multi-tenanted piece of software that can be used on any artifice. It’s primarily for desktops, but Solid made it affable on tablets and other mobile artifices. Eventually, we want Solid to create a indigenous mobile application.
Prosper is an Office Shop fruit that allows accounting firms to lessen administrative overhead and increase billable hours. The fruit incorporates a lot of business intelligence, and Solid Software integrated it all unitedly. They built an architecture that’s consistent for almost any accounting firm, not just the primary client. Now, companies can go to the website, click a button, invade a few details, and they automatically get their own tenancy.
Solid Software not only developed the software, but they also ran automated and manual testing. We hired another organisation to do discernment testing, and Solid worked closely with them. We identified some vulnerabilities, and Solid Software did the certain work to displace those vulnerabilities.
What is the team dynamic?
My go-to individual was Cuba, an expert BA [Business Analyst]. Solid also has an additional Scrum team to handle databases, front end, UX/UI [User Experience/User Interface], integration, and QA [Quality Assurance].
How did you come to work with Solid Software?
I was household with someone there through earlier course work. When we began this project, we looked at a number of preparers, but we chose Solid Software owing they could prepare the transparency we needed.
What is the status of this engagement?
We signed a contract in November 2015, and the work is ongoing.
Results achieved
What evidence can you share that demonstrates the contact of the engagement?
Our goal was to get 100 license holders of our fruit, and we',re at 80 right now.
Nearly all of the feedback from our clients has been real. Functionally, the software is very rich. It’s worked on see artifice and operating method that our clients use. We set out to create something off-the-shelf that anyone could use, and Solid Software helped us execute that. Because they brought the right nation on board, we also integrated with Xero and QuickBooks, which was a big milestone for us.
How did Solid Software execute from a project treatment standpoint?
We had a few regularly scheduled meetings that made the workflow efficient and powerful. First thing in the morning, someone on my team joined a conversation call for 10–15 minutes to hammer out the objectives of the day. Every Wednesday, we had a 2-hour grooming session. We looked at the backlog of tickets and courtly them so we could evaluate them and estimate how many story points it',d take to liberate those tickets. We also assessed the experiences of the team, clarified business objectives, and evaluated achievement criteria and measurements. Some days we only got through two or three tickets, if they were big, but it was an efficient way of approaching the business tasks and solutions. From there, the Scrum lead and I determined the best outgrowth order with respect to our commercial strategy.
We also had a demo and programning call see Monday behind the 2-week sprint cycle. Solid screened the pre-fruition environment so we could walk through what had been built in the antecedent 2-weeks and give feedback. Outside of that, we used Slack, usually for moment messaging, but we also shared files, business process diagrams, and use case diagrams. We even had some of our clients work straightly with Solid Software to get business and technical feedback.
What did you find most forcible almost them?
I appreciated their level of transparency. I',ve worked with other software companies that didn’t propose full visibility of what resources were doing or even approach to the team itself. Solid Software was the exact facing, we never had that issue. They always told us what they were edifice and were honorable almost their limitations.
Our project lead is also very organized and runs a firm ship. They',re open almost their limitations and enlighten us when requirements aren',t clear. They don’t let anything go into outgrowth until it’s degoodd with clarity. Their level of engagement is excellent, and we can always clear any big technical or commercial challenges as a team. They take it at our despatch and use intuitive software outgrowth tools.
Are there any areas they could better?
The only thing would be to have additional QA cleverness within a team. Though, that',s probably symptomatic of their funding rather than the team or its expertise.
