Case Study Document
Case Study Document
Case Study Document
Brief Details:
Project Life cycle- Discovery + Execution
BA Involved- 1 BA domain consultant for Onsite Discovery phase for 4 weeks + 2 BAs Offsite
Tech Stack- Angular for Front end and .Net for Backend
Devops- AWS
Business Goals:
1. The client’s requirement was to build new applications on Mobile (for travel agents only) as well
as Web, which is a booking engine for travel agencies, extranet for hotels to manage rooms,
rates & a back office for the MG admin team to Onboard and manage markups and rates for
agencies.
2. Migrate data from existing systems/manual forms into new systems
3. Offer a seamless user experience to travel agents booking on the new web and mobile
applications
4. Have flexible markup management module to increase revenue and improve profit margins
5. Have a scalable & secured application
Customer Pain points:
1. The client’s data is scattered across different platforms and 3 rd party systems
2. The current onboarding of hotels and travel agencies is a manual process, and the data is stored
in paper files and folders
3. The current application is built on legacy platform offering limited scope for scalability &
usability
4. The current markup management module has limited rules for accelerating rates offering
limited scope to optimize revenue
Implemented Solution:
1. AWS Cloud Infrastructure support added to maintain the scalability of the application
2. A revamped B2B booking engine was designed with a secure & intuitive user-friendly design
3. Cache solution was designed to support multiple transactions
4. Seamless support for 3rd Party integrations
5. New & improved ways designed to support revenue & markup management
Once the high-level requirements were discovered, it was broken down into a feature list and was
supposed to be scoped in detail at Offshore for a detailed review & sign off from the client.
1. Minutes of Meeting
2. Business requirements document
3. Feature/Module list (High level)
4. Product Backlog list
5. Solution approach for each module
6. Modules scoped for different delivery phases
7. Sign off on mocked wireframes
Project/Sprint deliverables