Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?
I was impressed with the quality of the code produced by Magora. We've done some iOS work in the past, but no one in our group considers themselves an expert on the platform. What I saw from Magora was more impressive than what we would have been able to produce in-house, within our timeframe.
We don't plan on releasing our app on the app store; it's meant to be used internally by a potential client who wanted to use our programs through an iPad.
How did Magora perform from a project management standpoint?
We didn't have a hard number in terms of budget estimates, but, based on the number of hours put in by Magora's team; I'm satisfied with the amount of work done. Our project managers were very responsive to my needs, and always asked what they could be doing better. At one point, I mentioned a new tool which we wanted to use, and Magora introduced it into the process. Towards the end of the project, we started using Trello as a task management tool, allowing us to move items around and prioritize them.
What did you find most impressive about Magora Systems?
There isn't anything in particular that stands out. I was overall satisfied with Magora's work. They delivered exactly what we wanted.
Are there any areas Magora Systems could improve?
One of our contracts with Magora was for a QA [quality assurance] engineer. As far as I can tell, Magora performed QA through the developers themselves and handed it to me for approval. I ended up doing the QA as well. We weren't delivering the app to a client, so I didn't mind that very much, but it would have been nice if I hadn't had to do it myself.
We initially had a deadline of July 1st and allowed Magora to add additional developers if they needed to speed the work along. By mid-June, I started to feel that we did need additional developers to hit the deadline, but Magora only added more resources by late-June. I did feel that we had an aggressive schedule, but it would have been possible to hit with multiple people working on it. Unfortunately, it didn't happen, and the project was completed at the beginning of August.
When we started our project, Magora proposed writing a document which would work as a functional spec for how the application was supposed to work and be used as a reference going forward, whenever new contractors would be introduced to the project. Magora started working on it early in the project, and abandoned it after a few weeks. I didn't care too much about it, and it didn't seem completely necessary, but I still hoped that it would be finished.
What tips or recommendations could you share that might increase the likelihood of success with Magora Systems?
I feel that we would have gotten more work done if I'd told Magora earlier to assign more resources to the project. I advise any clients not to be afraid of asking for more out of the developer.