We love finding out about the development processes that our clients’ go through with their teams and clients. Even more so when that process includes the use of BugHerd.
We spoke with Brett Pollett from Bigfish Creative Group about the nitty gritty of utilising BugHerd throughout the development, feedback and QA stages of a web project.
A little about Bigfish:
Bigfish is a brand strategy consultancy and full service ad agency headquartered in Scottsdale, Arizona. The agency’s clients range from blazing start-ups to flourishing cash cows looking for a fresh approach. Guided by the discipline of sound strategy – big ideas, stunning visuals, innovative campaign plans and game-changing UI/UX are the output of their everyday. Bigfish stays on the leading edge of ever-changing technology. They are true tech geeks who provide their clients with the innovative technologies that best optimize their business objectives.
Tell us about the development process and how BugHerd fits into that?
When we discovered BugHerd, we were close to completing a website and felt like it was going to be the perfect tool to get through the final client review. To be honest the first project we used BugHerd on we were actually really nervous. This client was particularly difficult to deal with during revision and creative review processes.
We were all incredibly apprehensive about what would happen when it reached the Dev phase and how we would tackle feedback and client reviews of milestones. If it could handle this client, it could handle anything. Long story short, it was a huge success and no one could believe how smooth the final stage of development and handoff went!
We realised we could go even further with it internally than just between Account Directors and Developers, as a final QA before sending it to the client to get their feedback. Now we use it during the initial development phase, where we send invites to the Designers for the project so they can give feedback and make sure that the Developers on the project met their intentions with the design. Then the developer working on the project will send me a note to check out the project in BugHerd as a technical double-check. Then we send to the Account Directors, who then end up sending the guest invites to the client. BugHerd has become an integral part of our development process.
You mention you “discovered” BugHerd, tell us more?
We do something we call “Inspire Sessions” every couple weeks at Bigfish where everyone in the company gathers for an hour or so and people bring links to anything they’ve seen lately, industry related or not, that inspired them in some way and we all share them with each other. I happened to come across the BugHerd website a couple days before an Inspire Session and was so excited after watching the promotional video on the site that I knew I had to share it with the team. We have been customers since June 2013.
What’s the number one reason you’re hooked?
It absolutely has to be how easy it is! I mean, just to know that there is this tool that requires little to no coaching with a client that lets them give real-time and easy to understand feedback is amazing enough. The fact that it’s also completely intuitive and easy for Developers and Account Directors to both setup and use too really puts BugHerd on a whole new level. I can’t imagine ever developing a project again without it.
What do you think we can improve on?
We also appreciate the ability to have a direct line of communication with the BugHerd team. We use this product every day, but obviously as Developers we also can’t help but analyze it as well 🙂
- It would be great if in addition to the Project Domains you could still set Project URLs for what gets sent to the client. BugHerd note – This has recently been fixed, let us know your feedback?
- It would be great if when leaving a comment there would be a checkbox that would only show that feedback to users with accounts or have the option to hide it from guests. BugHerd note – This is in the pipeline to be added. 🙂
- It could be cool if when leaving feedback the user could select a category for the feedback, such as Copy, Design, Functionality, etc. And then these could be color coded, both in the pins on the screen and in the admin area. BugHerd note – Tags are also getting an overhaul which may make this more easily digestible for clients/managers.
- Kind of tying into the first suggestion about Project URLs, it would be nice to have a little more Project organization like being able to have Child Projects under a main Project. An example folder structure may look something like Core Project (Client) > Child Project (Campaign) > GrandChild Project (Specific Deliverable). BugHerd note – We’ve discussed this one and are considering it as an option.