The project provides an opportunity for businesses and learners to collaborate to identify and translate a real business problem into an analytics problem. 

The projects, which can be short, will allow the student to apply the skills acquired on the various tools to address the business problem. Students also learn how to implement real-time scenarios. A review of different Cloud providers will also be covered.

Some examples of potential projects:

• Identify the difference between No SQL and RDBMS
• Deploy and manage Elasticsearch clusters
• Develop search and analytics solutions
• Develop scalable and cost-efficient applications with MongoDB
• Build MongoDB data models for enterprise applications
• Implement Logstash as a log management tool
• Use Kibana together with Elasticsearch for visualizations

You should submit a high-level proposal/business problem statement including relevant data sets and definitions, a list of acceptable tools (if applicable), and expected deliverables. Business datasets could be provided based on a non-disclosure agreement or in an anonymized/synthetic data format that is relevant to your organization and business problem. The course instructors will review the documents to confirm the scope and timing of the proposed problem and its alignment with the capstone course requirements.

Analytics solution may be applicable for (however they are not limited to) the following topics:

1. Demand for social services (healthcare, emergency services, infrastructure, etc.)
2. Customer acquisition and retention
3. Merchandising for trade areas (categories)
4. Quantifying Customer Lifetime Value
5. Determining media consumption (mass vs digital)
6. Cross-sell and upsell opportunities
7. Develop high propensity target markets
8. Customer segmentation (behavioral or transactional)
9. New Product/Product line development
10. Market Basket Analysis to understand which items are often purchased together
11. Ranking markets by potential revenue
12. Consumer personification

To ensure students’ learning objectives are achieved, we recommend that the datasets are at least 20,000+ rows in size. Data need to be ‘clean’. If more than one database is provided, which must be conjoined, students will be required to integrate them. This supports the learning experience and minimizes partner data preparation.