next case study >

Case study #1

has been the market leader in video conferencing room rental for 12 years, and they continue to gain significant traction in the meeting room rental space. They turnover several million each year and have offices in 3 countries


1. Overview

had been in business for 12 years and the biggest challenges were:

  • an aging, deteriorating code base written in Classic ASP
  • lack of long term modernisation and code quality improvement strategy
  • lack of development policy, process and standards
  • a desire to enter new markets and open up new sales channels

As CTO and lead developer of I was responsible for our software architecture, development, outsourcing and future road map.

I implemented industry best practices including source control, build automation, and use of project mangement tools for tracking bugs and features, and introducing Agile methodologies.

We undertook a phased migration to more modern technologies. Migrating the public facing website to Laravel and Wordpress.

The result of which whyGo is now well equipped with a firm foundation and road-map to sustainable, maintainable development.

2. The Context and Challenge

Up until the point at which I was engaged by whyGo, they had been relying on 3rd party agencies and developers to develop their applications

This meant that there was no overall guiding hand that had an overview of where the company was coming from and where it was going to.

External contractors and agencies had no motivation to invest in the future of the code, and little time or energy was put into architecture and maintainability.

The starting point was a mess of spagetti code.

Additional issues included:

  • Complex, undocumented business rules that had evolved over many years, including many sinlge use case exceptions, all hidden in the code.
  • Technological integration issues. The core of the code had been written in .net, so refactoring and architecting existing code wasn't and option
  • Little or no Orthogonality - seperation of concerns in the code
  • A lot of duplication and repetition in the code meaning that there is no single source of truth for data, for example a phone number - hardcoded in many places
  • Requirement to get our stock into an Outlook plugin and allow for us to get availability and accept bookings
  • Integrate our stock and booking system with a 3rd party booking system, also allowing live availability checks and bookings
  • Expand into the Meeting Room space, taking as much exising functionality with us as possible

3. The Process and Insight

The process we followed is that all new code must be written in a new technology.

Solutions

  • Architect and develop a Software and a service architecture (SOA) so that we could more easily modularise and develop new components with more modern technologies
  • Create a .net WCF api for booking, availability, making stock available, pricing. This allowed us to integrate with a 3rd party outlook plugin, and also to use the services in our re-built search search results. This also allowed us to integrate with the other 3rd party websites, making our stock available to them.
  • Redevelopment of search results as a single page application, using BackboneJS, and RequireJs
  • Development of a new Booking flow for the new Meeting Rooms product
  • I was responsible for outsourcing, managing code quality, source control and future development stategy

The Results

For most business owners, it’s all about the numbers. That’s why this section is crucial for an effectively written case study. The Results section will cover the qualitative and quantitative success metrics from your project. While the type of metrics you report on can vary from one project to another, they should directly address the objectives you established in The Context and Challenge section. Having these results in hand will allow you to show your prospects that your work had a direct influence on your client meeting their goals. If you can do this, you’ll help them feel more comfortable putting their business (and their money) into your hands. In addition to, or in lieu of, quantifiable metrics, consider including one to three testimonials in this section. These testimonials are another great tactic for boosting the confidence of your prospects. Since the source of these reviews come from outside your business, prospects are more likely to trust them as a reputable reference. When including your testimonials, however, keep them short and sweet. They can be as simple as one or two sentences, so long as they illustrate your previous client’s satisfaction with your work.

next case study