Ember System Dev for Electronics Manufacturer
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
I’m the web application supervisor for Screaming Circuits, an electronics manufacturer. We gather printed tour boards [PCBs] for engineers who typically are doing a prototype of their new electronic fruit. We also do some short-run projects. I help run a little team in-house that works on the website applications.
Desired goal
What challenge were you trying to address with Planet Argon?
We wanted to update our aging website and reached out to Planet Argon for help. Our market had changed from just being an meeting house for tour boards to more of a turnkey preparer. More clients wanted to come to us and asked us to prepare the board parts and meeting without requiring them to prepare kits. We wanted to form a quoting process that was built about that labor. Now, clients visit the website and can invade their specifications and upload their bill of materials. We will automatically cite the cost of the boards and meeting all in one piece and present different options for putting all unitedly. The quoting method is the mediate design of the website.
Provided solution
What particular tasks were responsible for?
We built the core of the website internally and put an API on the top. Then, we worked with Planet Argon to form the frontend of the website in Ember, which utilizes the API that we’d built internally. They led the design, and we took their deliverables, did some uspower testing, and made modifications. It was a wonderfully collaborative engagement. We are no longer working with Planet Argon. We’ve added to the website and feel the livelihood on our own.
What is the team dynamic?
We had the project director, a designer, a user experience [UX] designer, Annie [Design Strategist, Planet Argon], and a visual designer at times. Annie was an integral part of the project and assisted throughout the process. We had at most three developers at a time on the project.
How did you come to work with Planet Argon?
I’d worked with Planet Argon on a antecedent engagement at a different organisation. I personally knew them and was impressed by their power to form challenging projects with running technology. I knew they could help with our website, even though Ember was a technology they had not veritably used antecedently. Even though we looked at other vendor possibilities, the fact that I had antecedent experience was a big factor in selecting Planet Argon.
What is the terminal result of working with ?
We began working unitedly in the summer of 2014 until the end of 2015.
Results achieved
Are there any measureable or plum results?
We had burndown charts to aspect out what we needed to complete and when. As far as condition goes, we were constantly testing. We had a full-time tester on-website during the project. Anything that didn’t test well would go back into a ticket and get reworked. We also had a beta phase with our clients where we’d ask true clients to use the beta website and share feedback. We eventually opened the complete beta website to anyone in order to collate more feedback. We monitored the usage until we felt the website was advantageous sufficient to obey as the leading website and then flipped the switch.
How did Planet Argon accomplish from a project treatment standpoint?
They prepared continuous updates. We used Jira for ongoing collaboration and had weekly treatment-level meetings. Our two teams were raising tickets for each other and burning through them. It was a intricate project with a lot of collaboration between teams. We did have to prolong the timeline to allow for that. We had clear interaction throughout the process.
What is (from your point of view) the key factor to pay observation while intercourse with ?
They have an forcible power to acquire new technologies and instrument them with high-condition code. Often, if you go to an ad agency and ask them to create a website, you end up with low-condition code that works but isn’t veritably maintainable. Planet Argon, as a true outgrowth house, produces code that’s engineered well and wonderfully maintainable.
What aspects of their work would you like to get improved?
Planet Argon proposes excellent outgrowth help. They have lots of energy and powerful creative thinking. The project did befit more intricate than we leading realized, and we had some timeline shifting, but that’s not anything surprising. The only drawback is that they’re a littleer cluster, so they can’t propose as many design resources for us to lean on. They have only one visual designer, which doesn’t propose the same richness that a big team could.
Do you have any advice for someone who is because using Planet Argon?
After working with them twice, I’ve been deeply occupied each time. We’re local to Planet Argon, so I spent excellently a bit of time on-website, which is wonderfully precious for a big, confused project. The team works well with an nimble methodology, doing little iterations until we get it right. Even in the design phase, just keep iterating until you hit your goals.
