Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?
We have not launched the app yet, but we did a software review at the end of the project. Everything was solid. The quality of the code was very solid too. They were also very responsive. The Agile process went very smoothly, thanks to a capable Scrum master.
While we have not completed building the system, AndPlus provided incredible service. Most of the initial deliverables in the original proposal were delivered. Unfortunately, there were some delays on our end with the backend API. Both AndPlus and our team also underestimated some aspects of the project.
How did AndPlus perform from a project management standpoint?
The project management system we used was run by them. We used their JIRA system, and it documented all of the tickets. We had daily stand-ups through a web conferencing tool because we were working in different places. We also used our own Slack account and brought their team into a specific channel. A lot of back-and-forth questions, answers, and notes were exchanged there.
What did you find most impressive about AndPlus?
The app required domain-specific knowledge of publishing metadata, which AndPlus’ team learned quickly. They were a pleasure to work with. The developers were extremely friendly and professional without being stodgy.
Are there any areas AndPlus could improve?
One area of improvement for them is attention to detail — making sure that the design is completely followed. Over the course of the 4 sprints, there were some details that dropped off when we were doing the development work. It’s not carelessness per se, but I would say high attention to detail should be part of their service.
When they first crafted their business proposal, it had quite a lot of detail to it. Most of the details were relevant. By the time we started work, most of the designs on our end had been fleshed out. There were some changes as we continued to work on this project on our end. However, we noticed that there was somewhat of a difference between the original proposal and what was built.
For example, the time estimates were off. They thought they could launch within 3 sprints, which did not happen. We not only tacked on a fourth sprint to extend the work, but we’re still working on it now to clean up some stuff. Also, we were missing the automated regression testing, which was laid out in the original proposal.
This isn’t a big criticism because the work that they provided, once the project officially started, was great. If anything, not expecting that the original proposal would be followed exactly is perhaps the only area of improvement that I can provide.