Our client is a publisher of the leading global telecoms magazine, and an organizer of more than 15 annual telecom conferences around the world.
Despite each conference has its own agenda, most people view them mainly as a good (and quite rare) opportunity to discuss business deals and partnership with various important people representing companies from different countries. The Customer realized that the more information and tools he provides to the potential delegates to plan their meetings with each other, the more likely they will attend the conference, and the more likely the conference itself will become a success for everyone.
The traditional means of planning meetings appeared to be not suitable in this case, because the delegates generally do not want to share their emails with everyone, and because the existing tools do not have some important conference-specific and telecoms-specific features. Thus, the Customer decided to create a new software product dedicated for these tasks — Meeting Planner, later renamed to MeetMe.
From technical perspective, creating MeetMe implied creating a lot of new (and complex) functionality on top of existing Customer’s codebase, and integrating with various company-wide subsystems (users, subscription, content management and so on).
Because of the need to integrate with the existing subsystems and to comply with Customer’s coding standards, we did not have much freedom in choosing tools and ways of development. This had not stopped us, though, from applying best design and coding principles wherever we could.
The solution also contained some critical parts of functionality (like sending emails to hundreds of people), where any mistake could significantly undermine the Customer’s reputation. These parts were designed and developed very carefully and thoroughly tested by both manual and automatic means.
From the project management perspective, we were acting as an offshore development and QA teams participating in the SCRUM process driven by the Customer.
In particular, we created the following main features during development:
We had been delivering the functionality incrementally for several conferences in a line during a half-year period, and had been receiving feedback from the end users on each step, constantly improving the MeetMe product in a predictable, iterative manner.
Because the functionality provided by MeetMe was highly demanded by conference delegates, and because the resulting product had enough quality to overcome all the real-world challenges, the MeetMe project was considered successful from both business and technical perspectives.