Could you share any evidence that would demonstrate the productivity, quality of work, or the impact of the engagement?
Respondent 2: I don't have any exact stats, but the Android downloads exceeded what we originally anticipated, surpassing iOS. We thought that the app would be iOS-centric.
There weren't many complaints on the Help section. Here and there, there were some things that came up but they were not Android-specific issues, such as one person’s issue not getting through the “age-gate.” That’s not an issue with the app—that’s present in all apps related to this one. We’ll have to see, but so far there have not been any problems.
How did Fuzz perform from a project management standpoint?
Respondent 2: Communication was mostly done through our JIRA instance; most members of Fuzz's team were given access to it. HipChat was used to communicate on-the-fly around tasks and bugs. We set up a weekly call with Fuzz in order to work out details. I was in direct contact with their project manager, whom I could call for any issues.
We were given weekly builds which we could check. The frequency increased towards the end, with daily builds which went through Fuzz's QA, as well as our own.
There was a lot of back-and-forth around how native Android elements should be approached, and we had some disagreements with Fuzz on this topic.
The developers from Fuzz worked almost exclusively out of their office, but they did visit us on-site once or twice, for an initial scope meeting, as well as for a UI/business requirements review which we put together and discussed with the team when we identified some misunderstandings. We described every screen of the site and how it would be translated into the app, offering a clearer picture of what the product would be at the end.
What did you find most impressive about Fuzz?
Respondent 2: Fuzz was responsive in terms of discussing requests, but we have had some back-and-forth around what the app's requirements were. Some elements were fluctuating on-the-fly.
Are there any areas Fuzz could improve?
Respondent 2: Now that we're working on phase two, our developers have been reviewing Fuzz's code. There's been some trouble managing the code base, so if we had to do it all over again, we would ask Fuzz to make more ample documentation, in order to make it easier for us to maintain the app and add features to it. Other than this, I don't have any negative feedback for Fuzz.
Respondent 1: It was the typical miscommunication which comes at no direct fault of any one party. There were some assumptions made which were looked over, but there's nothing that would keep us from working with Fuzz in the future.