Skip to content

aditipaitandy/IPL-SQL-Data-Analysis

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

20 Commits
 
 
 
 
 
 
 
 

Repository files navigation

🏏 Men's IPL (2018–2019) SQL Data Analysis

An analytical deep dive into the 2018 and 2019 Indian Premier League (IPL) seasons. This project utilizes structured SQL queries to extract key performance indicators (KPIs) for batsmen and bowlers, evaluate team distributions, and track cross-season player consistency.

View Portfolio Deck


📊 Portfolio Presentation Deck

To make this technical analysis accessible to executive stakeholders, I have synthesized my findings into an insight-led slide deck.

(Click the badge above to open the PDF slide deck directly in your browser!)


🚀 Key Insights & SQL Implementations

1. The Volume Trap & Outlier Bias

Analytical Goal: Expose how lookups on raw averages can deceive decision-makers if workload volumes are ignored.

Deduction: On paper, players like Yusuf Pathan look like defensive masterminds. However, evaluating bowlers using run suppression metrics without applying a threshold constraint (such as Overs >= 10.0) introduces heavy statistical bias.

/* Identifying bowlers with minimal workload to avoid bias */
SELECT Player, Overs, Runs
FROM `men_IPL.2018_Bowlers`
ORDER BY Overs ASC
LIMIT 5;

2. High-Yield Bowler Identification

Analytical Goal: Isolate premium, defensive anchor bowlers who maintain an exceptional economy rate while delivering consistent wickets.

Deduction: Rashid Khan and Jasprit Bumrah emerged as the premier defensive assets of the 2018 season—delivering high wicket volumes while successfully suffocating run production under the elite 7.00 RPO ceiling.

SELECT Player, Wkts, E_R
FROM `men_IPL.2018_Bowlers`
WHERE E_R < 7
ORDER BY Wkts DESC;

3. Multi-Season Stability (The Roster Anchor)

Analytical Goal: Map historical data across separate tables to find the single most consistent scoring anchor.

Deduction: K.L. Rahul represents the peak of batting longevity, contributing a massive 1,252 runs as a reliable top-order foundation over a 24-month period.

SELECT
  a.Player,
  (SUM(a.Runs) + SUM(b.Runs)) AS CombinedRuns
FROM `men_IPL.2018_Batsmen` AS a
INNER JOIN `men_IPL.2019_Batsmen` AS b
  ON a.Player = b.Player
GROUP BY a.Player
ORDER BY CombinedRuns DESC
LIMIT 1;

🛠️ Skills Demonstrated

Relational Query Operations

INNER JOIN logic to merge historical datasets side-by-side.

Data Aggregation & Filtering

Advanced GROUP BY, ORDER BY, LIMIT, and multi-conditional WHERE clauses.

Data Integrity

Identifying and resolving structural bias (e.g., small sample sizes distorting averages).

Strategic Translation

Converting raw SQL outputs into operational recommendations for sports management.


📬 Contact

Aditi Paitandy

🔗 LinkedIn: https://www.linkedin.com/in/aditi-paitandy-750629317

💻 Portfolio & GitHub: https://github.com/aditipaitandy

📧 Email: aditipaitandy2003@gmail.com

About

Exploratory Data Analysis (EDA) on 2018–2019 Men's IPL datasets using advanced SQL aggregations, multi-table joins, and conditional filtering.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors