Decisive moments in the India-South Africa test series

India managed a stunning comeback win at the Wanderers to improve the series scoreline and salvage some pride. But despite a 2-1 victory, it wasn't a series where South Africa dominated India completely. In fact, India claimed all the opposition wickets on offer - the first time this has happened in an away tour (outside the sub-continent), since the 1986 England tour - and for that, a lot of credit should go to the bowlers themselves and the bowling coach. It takes a lot of practice and significant mental adjustment to alter the natural length when bowling. Except for the first innings at Newlands, where barring Bhuvneshwar Kumar everybody else leaked runs and looked largely ineffective, the bowlers came to the party more often than not. For this, they deserve a lot of credit. Had they received slightly better support from their batting lineup (as well as fielders), India may well have achieved their first series victory in South Africa.

So what were the turning points in this test series? Following are some decisive ones.

1st Test - Cape Town

AB de Villiers' counterattack - 9th over of SA's 1st innings

Bhuvneshwar Kumar had taken three top order wickets in his four overs (and conceded only 7 runs) and he bowled the 9th over to AB de Villiers. ABDV counter-attacked India's best bowler, crashing him for four boundaries in that over (between point and covers) and shifting the pressure back on Bhuvi. South Africa, who were 15/3 after 8 overs, plundered 92 runs of the next 18 overs (run rate of 5.11) to go to lunch in a strong position at 107/3.

Dhawan's drop reprieves Maharaj - 47th over of SA's 1st innings

In the 45th over, Bhuvi had dismissed de Kock for a quick-fire 43 (off 40 balls) and hence, had broken a very threatening partnership with Philander (60 runs in 9 overs). In his next over, he moved the ball away, took the outside edge of Keshav Maharaj's bat but Dhawan put down a straightforward chance at third slip. South Africa were 202/6 then and by the time Ashwin found him short of his crease with a direct hit, Maharaj had compiled 35 brisk runs and put on 56 vital runs with Philander and Rabada. South Africa were eventually dismissed for 286 runs.

Elgar's drop lets off Pandya - 42nd over of India's 1st innings

India were struggling at 91/6 with Hardik Pandya on 15, when he punched a short ball outside off and it flew to Dean Elgar at gully. The South African opener dropped the catch (Steyn being the unlucky bowler) and Pandya went on to score 78 out of India's next 118 runs (he was also let off on 71 when de Kock missed a stumping chance). The Indian all-rounder put on a crucial 99-run partnership with Bhuvi and saved India from a massive first innings deficit.

Shami's misjudgement reprieves Elgar - 2nd over of SA's 2nd innings

South Africa, leading by 77 runs, hadn't opened their account in the second innings when Dean Elgar, on a pair, pulled Bumrah's first delivery and got a top edge. Shami ran in from mid-on but misjudged the skier slightly, and eventually missed the ball. A quicker fielder would've got to it and it was a missed opportunity that proved really costly for India. The two SA openers put on a 52-run opening stand before they lost their entire side for the addition of only 78 additional runs as the Indian quicks ran amok.

Philander setting up Kohli - India's 2nd innings

Chasing 208 for victory, India got off to a decent start before losing the top 3 for merely 9 runs and finding themselves in a spot of bother at 39/3. The stage was set for India's best batsman to take India through. Kohli and Rohit put on a confident stand and Kohli was looking very assured. In the 18th over (India had reached 60/3), Faf du Plessis brought on Philander with a specific plan. In a 15-ball spell (11 balls bowled to Kohli), Philander kept bowling outswingers outside the off-stump and the Indian skipper kept shuffling across in an attempt to cover the swing and defend the ball. Then Philander slipped in the in-swinger that caught Kohli napping. He had shuffled to off-stump and tried playing around his pads. However, he missed and was nailed in front of his stumps. It was a big moment in the game and one that surely broke the back of India's chase. India eventually lost by 72 runs to go 1-0 down in the series.

2nd Test - Centurion

Strange team selection by India

Bhuvi was India's highest wicket-taker and the second highest on either side at Cape Town (6/120). He had also scored more runs than all the specialist batsmen in his team. But in the strangest of selections in recent times, India dropped him for the second test and brought in Ishant Sharma (citing Ishant's ability to extract extra bounce). Not satisfied with that, the coach-captain duo of Shastri and Kohli also dropped the in-form Shikhar Dhawan and inducted KL Rahul.

Parthiv's drop lets off Amla - 51st over of SA's 1st innings

SA were 160/2 and Hashim Amla was on 30 when Parthiv Patel dropped him off the bowling of Ishant Sharma. The tall Delhi seamer had bowled a length ball slanting down the leg stump and Amla tried to glance it and got a thin edge which Parthiv failed to pouch. Amla would go on to score 82 and push South Africa to a challenging 335.

Pandya's brilliance & Philander's brain-fade - Overs 81-83 of SA's 1st innings

The hosts were sitting pretty at 246/3. Amla alongwith Faf du Plessis had stitched together a steady 47 run partnership and South Africa were looking at a 400+ total. Then, in the space of 14 deliveries, aided by some exceptional fielding, good bowling and poor running, the Proteas lost three wickets (two of them to run outs), including that of the innings top scorer Hashim Amla. Although, du Plessis batted well with the tail to take his team to 335, it was well below the 400 mark that looked very much achievable before this mini-collapse.

Ashwin's loose shot - 82nd over of India's 1st innings

India had fought back nicely from 164/5 with Kohli putting together two solid partnerships - first one worth 45 runs with Pandya (who got run out because of appallingly casual running) and then, an even more fruitful one of 81 runs with Ashwin. The tall offie was batting fluently on 38 (off 54 balls) and India, at 280/6 (and only 55 runs in the arrears), must have been targeting a slender first innings lead. Then du Plessis brought on Philander (who had gone wicketless till then) and took the second new ball. Off the third ball of Philander's over, Ashwin played a slightly loose shot to a widish out-swinger and the South African skipper took a really sharp catch at second slip. This was a crucial blow (Kohli was on 135 at the stage) and the Indian innings folded up for the addition of only 27 more runs, thereby conceding a crucial lead of 28 runs.

Parthiv's non-attempt benefits Elgar - 25th over of SA's 2nd innings

South Africa had recovered well, although not sufficiently so, from 3/2 to 70/2. Both Elgar and de Villiers had settled nicely into their respective batting rhythms before a rain-break held up proceedings for an hour. Post the resumption of play, Kohli immediately brought on his most successful bowler, Bumrah, and the lanky Gujarat seamer extracted disconcerting bounce from round the wicket that had Elgar fending. The ball took his glove and flew to the left of Parthiv Patel (Pujara was standing at widish first slip) who simply let the ball go by. It was clearly a keeper's catch and it went to Parthiv's natural side, yet he didn't even go for the catch (blaming Pujara later). This proved to be another crucial moment in the game as Elgar and de Villiers added another 74 runs to their partnership with Elgar, who was then on 29, going on to score 60.

Umpire's call reprieves du Plessis - 65th over of SA's 2nd innings

Philander and du Plessis had staged a solid recovery after South Africa had lost three quick wickets (from 144/2 to 163/5) but the target was still not out of India's reach as yet. On the third ball of his 2nd over of the innings, with the South African score at 199/5, Pandya trapped du Plessis in front with an in-swinger. The on-field umpire gave it not out and India used the Decision Review System (DRS). Everything was perfect except that the ball was just clipping the bails and hence the system went with the umpire's call. Had that been given out, the DRS would've stayed with that decision too. This turned out to be a crucial rub of green going South Africa's way as du Plessis, then on 20, went on to score 48 and took his team to 258, thereby setting India a target of 287 which proved well out of reach. South Africa won by 135 runs to take an unassailable 2-0 lead in the series.

3rd Test - Johannesburg

Umpire's call reprieves Pujara - 6th over of India's 1st innings

India chose to bat first on a greentop and already Philander was making that decision look like a foolish one, by moving the ball menacingly both ways. He had first taken out KL Rahul for a duck and Pujara too was on zero (team score was 7/1), when a series of out-swingers were followed by one that went straight on and hit Pujara in front. The on-field umpire didn't uphold the LBW appeal and the South Africans reviewed using DRS. In a sort of reversal of fortunes, the ball was just clipping the bails and hence umpire's call came to Pujara's rescue. This proved crucial as Pujara went to score a half-century (exactly 50) and put together a very crucial 84-run partnership with Kohli.

No-review reprieves Pujara - 20th over of India's 1st innings

Pujara again got lucky in the 20th over, while (incredibly!) still on duck. Ngidi bowled it fuller and beat Pujara for pace. The South Africans went up in an LBW appeal but after the umpire turned it down, they didn't opt for a DRS review. Replays showed all three reds, meaning Pujara would've been on his way had South Africa reviewed that decision. India, at 27/2, were still not out of the woods at that point.

Umpire's call reprieves Amla, twice - 27th and 35th over of SA's 1st innings 

The nightwatchman Rabada and Hashim Amla had put together a useful little partnership of 46 runs when Kohli brought Ishant Sharma back, to bowl the 27th over. He swung his first delivery back into Amla and the stylish batsman, who was shuffling outside the off-stump throughout this test match, got beaten by the swing and was wrapped on his pads. As the appeal wasn't upheld, the Indians opted for a DRS review. It showed umpire's call for height and Amla, on 20 then, got a massive reprieve. 

Then again in the 35th over, Bhuvi pinged Amla in front and after the appeal was turned down, Kohli opted for a DRS review. It was once again umpire's call on height and Amla (on 34 then) got another life. He went on to score 61 runs.

Amla's dismissal leads to SA collapse - 60th over of SA's 1st innings 

Philander and Amla had put together a decent 44 run partnership for the 7th wicket, when Amla, batting well on 61 and having had a couple of lives, played an uppish flick to a leg stump half volley from Bumrah, straight into the hands of Pandya at deep square leg. His dismissal started a mini collapse wherein the last four wickets fell for the addition of only 25 runs, thereby restricting South Africa's lead to only 7. In the context of the match, this wicket assumed massive significance.

A life each for Rahane & Bhuvi as SA drop catches - 59th and 60th over of India's 2nd innings

India's 2nd innings saw an intriguing battle between bat and ball on a highly treacherous pitch. Kohli first combined with Vijay and then with Rahane to put India in a slightly better position but then India lost Kohli and Pandya in quick succession. Rahane was then joined by Bhuvi and the duo, overlooked in the previous test, were taking India to a stronger position when du Plessis brought Morkel back. Morkel produced steep bounce from round the wicket to induce a false shot from Bhuvi but Elgar couldn't cling on to an outside edge at gully. Three balls later, it was Rahane's turn to enjoy some luck. Rabada, probably getting tired from a longish spell, dropped one short outside the off-stump. Rahane tried to play an upper cut but lost control and skied it to Phehlukwayo at deep point but the South African all-rounder put down a relatively straight forward chance. India were 178/6 then and only 171 ahead. Eventually, this pair added 25 more and Bhuvi also combined with Shami to steer India to 247, in the process setting South Africa a far more challenging target of 241.

Amla's loose shot triggers another SA collapse - 53rd over of SA's 2nd innings

South Africa were chasing a target of 241 and contrary to all expectations, Elgar and Amla put together a gritty partnership of 119 runs for the second wicket. The hosts looked on course for a 3-0 series victory. With victory just 117 runs away, Amla played a loose shot. Ishant bowled a fuller length delivery, angled into the middle stump and the constantly-shuffling Amla flicked uppishly, straight to Pandya at short mid-wicket. South Africa then went on to lose their next four established batsmen (including Philander) for the addition of only 33 runs. This was mainly on account of some outstanding bowling by the Indian seamers, esp. Shami and Bumrah. South Africa were shot out for 177 thereby handing India a famous victory (by 63 runs). 

Sri Lanka test series: Key takeaways for India

This blog is available as a video blog on https://youtu.be/LytF_FFwfWY

A three-test series, billed as part of the first full tour by an Indian team since 2009, ended in 11 days of play. Sri Lanka managed to cross 300 only once in the first two tests, and then, couldn't even cross 200 in the final test. Such was India's domination that they had a first innings lead in excess of 300 in all three tests and enforced follow-on in the last two matches. When one team scores nearly 2,000 runs in three and a half innings (avg. RPW of 61), while the other team cannot even manage 1,500 runs in six innings (avg. RPW of 24), it demonstrates, not just the different performance levels, but also the gulf in class between the two sides. The winning team, therefore, finds it difficult to take positives from the series. However, on account of bold team selection as well as some luck, India managed some positives from this series.

Hardik Pandya's emergence as an all-rounder

With 178 runs in 3 innings and 4 wickets in the 32 overs he was asked to send down, Hardik Pandya began repaying the faith that the team management has shown in him, over the last 12 months or so. His rise through the ranks has been meteoric. A first class debut in November 2013 was followed by selection in the Mumbai Indians playing XI in the 2015 IPL season. The India limited overs cap didn't take too long and he impressed one and all with his explosive batting and effective bowling. In fact, it was the rapid improvement in his bowling that encouraged the Indian team management to earmark him for the longest form of the game. A casual glance at his batting numbers in this series, esp. his strike rates, may give the impression that he played the same way as he does in the ODIs and T20s. But while he did provide the impetus in the first test by scoring a quickfire 50, his maturity stood out in the 3rd test. He strode in at 322/6 after the fall of Ashwin's wicket and India quickly lost Saha at 339. On a pitch that was giving some assistance to the bowlers, Pandya first stitched together a patient 62-run partnership with Kuldeep Yadav and then, when running out of partners, smashed 70 out of the last 86 runs while consuming 42 of the last 69 balls. Three out of the four wickets he took, were that of established batsmen. He also pouched four catches, second only to Rahane amongst non-wicket-keepers. A genuine all-rounder is worth his weight in gold and given that the overseas tours of South Africa, England and Australia are coming up, a pace-bowling all-rounder like Pandya could make a big difference.

Kuldeep Yadav firmly established

It was only due to the suspension of Jadeja from the 3rd test, that allowed the left-arm chinaman, Kuldeep Yadav, to play a test match in this series. Despite his series-winning performance in his debut test against Australia in March, once the captain and coach had made up their minds to play Pandya as the third seamer, it was always difficult for Kuldeep to feature in the starting XI. However, it didn't take Kuldeep too long to make a mark. He ran through the Sri Lankan middle and lower order in the first innings to hasten them to 135 all out and then broke a dangerous partnership between Dinesh Chandimal and Angelo Mathews in the 2nd innings. Overall, he picked up 5 wickets in his only test match at an impressive average of 19 and an even more impressive strike rate of 36 balls per wicket. Once again, the selectors and the Indian team management deserve a lot of credit for blooding this Kanpur lad and what has been very impressive is that Kuldeep has been effective across all formats of the game. The fuller length that Kuldeep prefers is ideally suited for test matches; yet it has worked wonders in the slam bang variety too. This is mainly on account of the disguise that Kuldeep deploys, wherein he's able to bowl both the normal chinaman as well as the wrong-un, with a scrambled seam. Given Ashwin and Jadeja's struggles in the Champions Trophy, Kuldeep would ideally be the no. 1 choice spinner in both ODIs and T20Is. And his performances in the limited opportunities he's got at the test level, should firmly establish him as the no. 3 spinner. In fact, I believe that in the upcoming overseas tours, if India decide to play with 2 spinners, Kuldeep's wrist spin would be far more effective on the bouncy pitches as compared to the finger spin of Ashwin and Jadeja.

KL Rahul continuing from where he left

KL Rahul was in a rich vein of form before injury halted his golden run. Till the 4th test against Australia in Dharamsala, Rahul had hit a half-century in each test of that series including five consecutive ones. Given his form in IPL 2016 and his vastly enhanced attacking strokeplay, the Bangalore lad was supposed to make a big impact in the IPL as well as in the Champions Trophy. Unfortunately, his shoulder injury required a surgery and that meant, 4 months out of the game. Then again, in Sri Lanka, he was laid low by viral fever and had to sit out of the first test at Galle. However, the tall right-hander was amongst runs as soon as he was back in the playing XI. He scored a half-century each in the two innings he batted, thereby becoming the first Indian batsman to score 7 consecutive test 50s. The only worry for Rahul would be that his last 8 test scores in excess of 50, have all ended short of the century mark. Nevertheless, the captain would be very pleased to see Rahul back in the team and his inclusion at the no. 4 spot for the upcoming ODIs is a sure indicator of the high esteem in which Rahul's technique, temperament and performances, are held by the Indian team management. 

Mohammed Shami's successful return from injury

Mohammed Shami, India's best quick bowler in test matches over the last few years, has had long-injury layoffs over the last two and a half years and this has caused him to miss many test matches. He returned to play in the West Indies tour in July 2016 after the knee surgery post-the 2015 World Cup, kept him out of the game for several months. Then, he was laid low again by knee injury against England and he missed out the 2nd half of the England series as well as the entire Australian series. A penetrative, test match class, quick bowler is such a rare commodity for Indian cricket and hence, his performances in this series must have been keenly watched by both selectors as well as the team management. And Shami didn't disappoint. He picked up 10 wickets, which was 3rd behind Ashwin and Jadeja, at a very impressive average of 17.7 and an amazing strike rate of 36.5. He was truly in his elements in the 3rd test, bowling at blistering pace and prising out 5 wickets while conceding less than 50 runs. All this augurs very well for future tours but India needs to manage Shami's workload properly so that there's no recurrence of the knee injury.

India has rested all their main test bowlers for the ODI leg of the tour. While this seems to be a sensible strategy for fast bowlers, at least one of Jadeja or Ashwin should've been part of the squad, as their one-day form, of late, hasn't been impressive. On the other hand, the ODI batting line-up seems to be at full-strength and the likely first choice line-up for the 2019 world cup. Interestingly, while Yuvraj has most likely been left out for good, Dhoni seems to have secured his swansong as his closest rival, Rishab Pant, has been unfairly dropped from the squad. India is expected to experiment and use this series as a build-up to the 2019 world cup. Here's then, wishing for a more competitive one-day series!

Champions Trophy 2017: Asian Party in London

Let's start with a short quiz. When was the last time India played Pakistan in a major tournament final? Most of you will get it right - it was indeed the ICC T20 World Cup final 10 years ago. But what if the question was limited to finals of ODI tournaments involving more than 3 teams? One has to go back more than 23 years i.e. to April 1994, when the then reigning world champions, Pakistan, beat India in the finals of Australasia Cup (in Sharjah) to win their 3rd successive title. And the last time India and Pakistan met in the finals of a major global ODI tournament was in March 1985, when the then World Cup holder, India, beat Pakistan in the finals of the World Championship of Cricket (held in Australia).

The Romance of India-Pakistan encounters!

The South Asian cricketing giants have met less frequently in the last decade or so, as volatile political environment has restricted bilateral tours. The cricketing world has been poorer for this. This, and the fact that Pakistan is still banned from hosting cricket in their own country (8th year running) as well as excluded from IPL, has seen India-Pakistan matches lose their edge recently. This is such a far cry from those two decades (mid 80s to mid 2000s) when India and Pakistan ODI encounters produced edge-of-the-seat thrillers. Cricket fans would remember the match when India won while defending a lowly 125 runs in Sharjah (1985) or when Miandad hit a last-ball six off a Chetan Sharma full-toss to help Pakistan win the first Australasia Cup, also in Sharjah (1986). We all remember the world cup encounters, esp. the 1996 quarter-finals and the 2003 slug-fest. But, how many of you remember that 40-over ODI in 1987 where India, having set Pakistan a target of 239 and having them struggling at 174/6, still lost mainly due to Salim Malik's brilliance (who scored 72 of the last 80 runs at a strike rate of 200!)? Or, even that 1991 match in Sharjah where a young Tendulkar almost helped India chase down 258 against a bowling line-up comprising Wasim Akram, Aaqib Javed and Waqar Younis, in fading light (India lost by 4 runs!). Sharjah may have slowly faded into insignificance but India and Pakistan continued producing thrilling encounters - in Toronto (1996), when India lost by 2 wickets when defending 264 and despite having Pakistan down at 221/8 (Salim Malik the tormentor again); in Dhaka (1998) when India won the Independence Cup by chasing down a then-record 315 (won by 3 wickets); in Brisbane (2000) when Pakistan won by 2 wickets when chasing 196 and looking down and out at 153/8 (Saqlain and Waqar, as batsmen!); in 2004 (Karachi), when India sneaked home by 5 runs despite setting Pakistan a huge target of 350, as Moin Khan couldn't do a Miandad off the last ball, despite getting a full-toss.

Although, India and Pakistan produce the occasional brilliant game even now, since 2006 India have dominated their neighbours, having won 17 out of 27 completed games. Contrast this with the overall record - it still stands at 72 wins for Pakistan vs. 52 wins for India. Their first game in the Champions Trophy 2017 was representative of how India has dominated Pakistan since 2006. Pakistan will hope that there's no encore in the final.        

What has India done well so far in Champions Trophy 2017?

India, the pre-tournament favourite, has lived up to their reputation and are functioning like a well-oiled machine. The top order has been both solid as well as swashbuckling, with Dhawan and Rohit topping the run charts and Kohli too in the top 5. Each of the middle and late order batsmen have played at least one significant innings or cameo. While Bumrah and Bhuvneshwar Kumar haven't picked up a bunch of wickets, they've been very economical (going at less than 4.75 RPO). The fielding has been very good too, with the fielders effecting 6 run outs so far and catching having improved significantly since the first match against Pakistan. Except for the 2nd innings against Sri Lanka, India has been very clinical in all their other games. They've won when defending a target (against Pakistan) as well as when chasing one (South Africa, Bangladesh).

Yet, certain phases of their bowling performance in the league game against Sri Lanka as well as the semi-final against Bangladesh will worry Virat Kohli and Anil Kumble. India's bowling has been largely unsuccessful to pick up wickets in the middle-overs. Sri Lanka successfully chased down 322 quite comfortably while Bangladesh, having crossed 150 in the 27th over for the loss of just 2 wickets, were on course for a 320+ score before the part-time off-spin of Kedar Jadhav induced a mid-innings collapse. In the finals, India will surely demand more wickets from their front-line spinners (esp. Ashwin) as well as their pace-bowling all-rounder, Hardik Pandya.

What has propelled Pakistan to their first Champions Trophy final?

Pakistan has been the most improved side in this tournament. They were the bottom-most ranked team when the tournament began (at no. 8) and even their most ardent fans gave them little chance to make the finals. But the Pakistani team decided to live up to its age-hold billing as "mercurial and maverick". After the big loss against India in their tournament opener and having lost Wahab Riaz due to injury, facing the top-ranked South Africa in a must-win game was daunting. But they've strung together a series of such amazing bowling performances that they've restricted strong batting line-ups of South Africa, Sri Lanka and England for less than 250 in 3 successive games. This has mainly been on account of penetrative middle-over pace bowling by Pakistan and this hasn't allowed the opposition to follow the tried-and-tested model of accumulation in the middle-overs followed by acceleration towards the end. Hasan Ali and Junaid Khan are amongst the top 5 wicket-takers and as a result, they've been economical too (less than 5 RPO).

However, Pakistan's batting is still a big concern. They got slightly lucky against South Africa with rain and D/L coming for help. Then, they were staring at defeat against Sri Lanka when chasing a modest 237 before an unbroken 8th wicket partnership of 75 runs rescued them. It was only against England in the semi-final that Pakistan produced a clinical batting display to chase down 212 with 8 wickets in hand and 77 balls to spare. Yet, Pakistan will be very aware of India's batting depth and it's unlikely, in case they are chasing, that they'll face a less-than-250 target in the finals.

So how does it look like?

If one looks at the strong and weak areas of both teams, they represent perfect contrasts. India will love to have Pakistan's bowling penetration in the middle-overs while Pakistan will feel complete if they can match India's batting prowess at the top order. To the die-hard fans on either side, this would sound very similar to a recurring theme in the 90s - Indian fans wished their team had a bowling attack (esp. fast bowlers) like Pakistan and Pakistani fans wondered when they'll get the kind of batting depth like India. 

The weather seems to be clear for the final and hence, toss may prove critical. Both teams would like to chase, esp. Pakistan. The final will be played on a fresh track and this may aid run-scoring. For Pakistan, Mohammad Amir will likely be back while India may retain the same team that won the semi-final. If India bat first, they'll look for a score close to 300 (may not want to go hard for a 325+ score). If they bat second, the Indian team would be confident of chasing down any score upto 325. Let's hope for a repeat of the high-scoring Independence Cup final in 1998 (the third final). That'll surely rekindle the old romance! 

IPL 2017: How did Pune manage runners-up?

"How did RPS not become champions of IPL 2017?" That must be the question ringing loudly in Steve Smith's ears as he packs his bags after a 3 month long-tour of India. This was his 2nd heartbreak as captain in less than two months and both came in matches where his team dominated at the outset. The fact that he topped the batting charts in the test series and was also the top run scorer amongst both IPL finalists (no. 4 overall), would be minor consolations. As the skipper of RPS, this snatching of defeat from the jaws of victory, will hurt Smith. And the brute reality of him being at the crease till the final over and esp. when the match was in RPS' control, will confound and hound him in equal measure. What played out at Hyderabad was a classic case of many a slip between the cup and the lip!

Mighty struggle for the MI batters

It all looked very different at the halfway stage, of course. RPS had put in a brilliant bowling display and restricted MI to a manageable 129. In fact, even 129 looked difficult at the 15 over stage. Rohit Sharma won the toss and, in keeping with the tradition in IPL finals, chose to bat first (my previous blog covering this). Unadkat continued his rich vein of form and quickly snuffed out both the MI openers with the team score still in single digits. Rohit Sharma and the local boy, Ambati Rayudu, tried to stem the tide but the going wasn't easy. The man of the match in the previous MI-RPS encounter, off-spinner Washington Sundar, kept things very tight and didn't allow MI to get away in the powerplay. Rohit plundered four boundaries off Ferguson in the 6th over to ensure that MI reached a respectable 32/2 (given the slowish pitch) at the end of powerplay. However, as things were beginning to look slightly better for MI, disaster struck. Rayudu played a firm cover drive, off Ferguson, straight to Smith at mid-off and tried scampering for a non-existent single. He was possibly hoping that Smith would miss hitting directly but the RPS skipper hit the bulls eye, finding Rayudu well short of the crease. At 41/3, MI were hoping that the free-flowing Rohit and the in-form Krunal Pandya would put on a partnership similar to the one in the Qualifier 2 against KKR. However, they were in for a rude shock. In the 11th over, the leg-spinner Adam Zampa first got the benefit of a bigger ground at Uppal when Rohit failed to get the distance while pulling a short delivery, and holed out to deep mid-wicket. In came Kieron Pollard and he looked like he wanted to break the shackles straight away. He smote an effortless six off the first ball he faced but then fell to some tactically brilliant field placement. Possibly on advice from Dhoni, Smith placed a very straight long-off and Pollard duly obliged, hitting a flighted delivery from Zampa, straight to that fielder. Hardik Pandya didn't last long and neither did Karn Sharma. At the end of 15 overs, MI were 81/7 and in real danger of being bowled out for less than 100.

Krunal Pandya rescues MI

The one man standing between RPS and the IPL trophy, however, was the exceptionally smart and versatile, Krunal Pandya. He quickly assessed the nature of the wicket and as the last recognized batsman, decided to delay the late innings assault. Receiving good support from the experienced Mitch Johnson, Pandya demonstrated great improvisation in dealing with both, the slower ones from Unadkat, as well as the seam-up deliveries from Dan Christian. Crucially, MI plundered 37 runs off the last 3 overs and gave their bowlers 129 to defend. MI's hopes now rested on a superlative performance from their more consistent discipline this year i.e. their bowling.

Over-cautious RPS keep MI in the game

Still, given that 129 was the lowest a team had scored when batting first in an IPL final, RPS were heavy favorites going into the 2nd innings. MI needed early breakthroughs and Bumrah did just that, trapping the explosive Tripathi in front. The lanky MI bowler got slightly lucky with the decision as the ball was going just over the stumps. MI should've picked up Rahane also but Krunal Pandya dropped a sitter after Malinga had foxed the RPS opener by a brilliant slower one. Like he has done all IPL, Rohit continuously rotated his bowlers. At the 10 over mark, the game was meandering along with neither MI picking up wickets nor RPS getting ahead of the required run rate (by way of aggressive batting). However this meant that even though MI were sloppy in the field, the combination of miserly bowling and over-cautious batting from Rahane and Smith, kept MI in the game. MI believed (and rightly so) that a couple of wickets could really make this chase, tense.

In the 12th over, the game suddenly opened up. First, Johnson picked up Rahane, thanks to an exceptional catch from Pollard. The tall West Indian ran quickly from long-on and then dived forward to complete an extremely tough catch. Then, RPS decided to bring Dhoni in at no. 4. This was a deviation from their earlier strategy of batting Tiwary at 4 and Dhoni at 5. Possibly, the RPS team management felt that Dhoni would take longer to get in and an equation reading 59 off 49 was manageable with Smith still batting. However, that equation soon became 47 from 30 balls as Karn Sharma, Krunal Pandya and Malinga delivered three exceptional overs, going for just 12 runs! As the tournament's last strategic timeout came about, Dhoni was struggling with 4 from 9 balls and Smith too was scoring at less than run-a-ball (25 off 35 balls). MI was making RPS sweat for every run but with the protagonists of the successful chase from this season's first MI-RPS encounter, at the crease, RPS were still the favorites.

Last 5 overs of IPL 2017 - ebbs and flows

16th over - As Krunal Pandya got ready to bowl his final over, the experience duo of Smith and Dhoni instantly realized that they needed to attack the left-arm spinner by taking calculated risks. Off the 3rd ball, Dhoni used his fast bat speed and strong wrists to hit a vertical bat square cut, and got a welcome boundary. Then off the 5th ball, Smith played, arguably, the shot of the match. He unleashed a powerful reverse sweep and hit it well over the point boundary for a six. 14 runs came off that over, equation was brought down to 33 off 24 balls and Rohit Sharma's gamble of bowling a spinner at this stage of the innings, seemed to have backfired. Advantage RPS!

17th over - Realizing that he needed wickets as well as stem the flow of runs, the MI skipper brought on his trump card and his clutch bowler, Bumrah. Earlier in this season, Bumrah was preferred over Malinga to bowl the superover against Gujarat Lions and he successfully defended 11 against batsmen of the calibre of McCullum and Finch. He was entrusted to bring MI back in the game and he didn't disappoint. Off the 2nd ball of the over, a fast in-cutter got Dhoni slashing and edging to Parthiv Patel. In came Manoj Tiwary and almost immediately had a huge LBW shout turned down. Overall, Bumrah bowled three dot balls (including the wicket-taking delivery) and conceded a single each of the other three balls. To summarize, he brought MI right back into the match with an over of the highest quality. RPS now needed 30 from 18 balls; remember, MI got 37 runs from their last 18 balls! Slight advantage to RPS!

18th over - Malinga was entrusted with bowling the 18th over. The old Sri Lankan warhorse didn't have a great IPL but he was mostly accurate in this match. First four balls included two dots and two singles. Equation climbed up to 28 runs from 14 balls and also went up MI's chances. Then Smith produced another moment of magic - a near yorker on the leg stump was expertly dealt with (by staying deep in the crease) and whipped to the backward square leg fence for a crucial boundary. 7 runs came off Malinga's final over and the equation now read, 23 runs from 12 balls. Still advantage to RPS but MI in with a fair chance!

19th over - Rohit continued with Bumrah for the crucial 19th over. With so much riding on his young shoulders, Bumrah possibly felt the pressure and delivered a full-toss first up. Smith too, possibly nervous, couldn't take full advantage of this and nearly holed out to deep mid-wicket. The next three deliveries went for three singles (1 leg bye). At this stage, the equation read 19 off 8 balls and if Bumrah managed to concede only 2-3 runs, the last over equation would've been very tough for RPS. Instead, Smith, who was sitting very deep in his crease and hence was able to generate leverage for the just-short-of-yorker length, smacked the 5th ball for a six over long-off. The last ball was another high full-toss and yet again, Smith couldn't make a good connection (they ran two). Nevertheless, with 12 runs coming off that over, the equation was down to 11 runs off 6 balls. Big advantage to RPS with MI's chances dimmed slightly!

20th over - In the first MI-RPS encounter this season, Bumrah had delivered the 19th over and by conceding just 7 runs in that over, he left 12 runs to be defended in the final over (and Pollard couldn't defend those). Here, he had gone for 12 runs in the penultimate over and hence, left only 10 runs to defend. However, the key difference was that Rohit had one over from Johnson and hence, didn't have to go to any non-regular bowler. With Tiwary on strike, Johnson bowled the first delivery from over the wicket and his slower one was dispatched for a boundary. Now, just 7 runs were needed off 5 balls - looked like all over for MI! Johnson switched sides and Tiwary, looking for a big hit, got the inside half of the bat (off another slow off-cutter) and his lofted drive landed safely into the big hands of Pollard at long-on. However, importantly for RPS, the batsmen had switched ends as the catch was being taken and hence, with 7 needed off 4 balls, it was Smith on strike. The time for the knockout punch was now or never! Johnson delivered a seam-up delivery just outside off and Smith hit an amazing lofted square drive. The connection was very good and the ball was headed for 6 but it was also headed in the direction of the only outfielder on the off-side, Ambati Rayudu. Rayudu positioned at sweeper cover, plucked out a very good catch since the ball was travelling flat and quick. In fact, a few inches on either side, would've meant a 6 thereby almost finishing off MI's chances. This was a crucial wicket for MI - two wickets in two balls also meant that there were two dot balls. The equation had become a more difficult 7 off 3. And the batsmen couldn't cross in time and hence, instead of Dan Christian, it was Sundar on strike. The batsmen stole a bye on the hattrick ball and it was now in the hands of Christian. 6 needed off 2 and Christian got a length ball on the leg stump but the burly all-rounder couldn't deposit it for a boundary or six. Hardik Pandya dropped a tough chance at deep mid-wicket and the fumble allowed a couple. So it was down to 4 runs off the final ball! Two Aussies faced up to each other with the Indian Premier League trophy on the line! Johnson bowled another quick ball on the leg stump, Christian could only manage to get it to the substitute fielder (Suchith) at deep square leg. Suchith made a nervy stop, possibly aware of the boundary rope behind him, and even fumbled when making the throw. However, his throw was accurate enough and as the RPS batsmen attempted the third, Parthiv Patel effected the run out and MI won the match and hence IPL 2017, by a solitary run! It was an exhilarating performance by MI and they won a match in which, at the innings break, nobody gave them a chance.

Conclusion

This victory was made possible due to excellent all-round bowling performance by MI and over-cautious approach by the RPS batsmen. It was sweet revenge for Rohit and his men and in many ways, this match was a microcosm of all the previous MI-RPS encounters this season. Similar to the first match, it was MI batting first and Smith and Rahane batting well for RPS. In that match too, Smith took the chase to the last over. Also had commonality with the 2nd match; the chasing team botched up a chase which was under their control for most parts. In that game it was MI's skipper Rohit who batted well and brought his team close before falling in the last over, thereby failing to take the team over the finishing line. And Krunal Pandya's late innings (and match winning) assault in this match was very similar to Dhoni's in their last match, both in terms of nature and impact. 

The IPL rules are set for an overhaul this year and, given that CSK and RR will make a comeback next year, a lot of things are likely to change. The first decade of IPL is nicely bookended by two similar last ball finishes. What better advertisement for the edge-of-the-seat thrill that IPL promises!

IPL turned 10: How has it evolved?

The Indian Premier League, which was born in 2008, has turned 10! And look at how things have changed around us - when Lalit Modi declared the tournament open on 18th April 2008, Barrack Obama was yet to become the US President, Virat Kohli was still 4 months shy of debuting for India and the Chinese economy was still growing in double digits. Lalit Modi is no longer associated with the league but during this time, IPL has grown to become one of the world's most valuable sports leagues (worth $4.2 billion and with revenue of $378m in 2016). It'll be interesting, however, to see how various on-field aspects of the game have evolved in these exciting nine years.

I've attempted to evaluate the performances, season-by-season, using tournament stats. Using this approach, we try to address the following questions:

• Are teams scoring faster now?
• What is a safe score to defend?
• Are batsmen more consistent now?
• Are bowlers bowling better now?
• Are teams evenly balanced?

1. Are teams scoring faster now?

Highest team totals

For this analysis, I've shortlisted the top 30 team scores for each season. Further, I've created separate 25-run buckets for team totals (151-175, 176-200, 201-225, 226-250, 251-275). Then, I've plotted, season-wise, the number of occurrences of team totals (or frequency) within different buckets. Further, on the right side Y axis, I've plotted the median of the top 30 scores in each season. The chart is produced below:

Data source: ESPNcricinfo.com

Surprise! Surprise! I was expecting the team totals to climb and show an upward trend. However, if one observes closely, it's clear that there's an increasing trend of more scores between 176-200 vis-a-vis 200+ scores (more orange than grey!), esp. when compared to IPL 2008 and 2010. For example, in 2008, amongst the top 30 team totals, there were 11 scores above 200 while in the last two editions, that figure has come down to 6 (in 2016) and 7 (in 2015), respectively. The median score has remained fairly stable (except for 2009) even though the highest median score was achieved in the first season itself, and has been matched twice since. IPL 2009 season is a bit of an aberration since that edition was held in South Africa (due to general elections in India) where batting conditions are relatively tougher.

Highest match aggregates  

Is the above outcome an anomaly? It'll be useful to look at a similar analysis based on match aggregates. 

Data source: ESPNcricinfo.com

In IPL 2008 and 2010 (2009 again an exception), there were 5 and 4 instances, respectively, of match aggregates exceeding 400. This too has come down to 2 in each of the last two editions. However, the 351-400 bucket shows higher frequency in the last few years. The median match aggregate has hovered around 350.

Conclusion

Based on the above evidence, it's safe to conclude the following:

Teams are scoring more consistently between 175-200 instead of 200+. This is further demonstrated by looking at a statistical analysis of the top 50 team totals in each season. While the average score (of top 50 scores), at 185, has remained the same in IPL 2008 as well as in 2015 and 2016, the variance and standard deviation has come down in the last two seasons. The steeper normal distribution curves in IPL 2015 and 2016 clearly bear this out (comprising top 50 team totals).

Data source: ESPNcricinfo.com

This could be pinned down to batting strategy where teams, at the start of the innings, are now deliberately targeting 175-200 instead of taking additional risks to score 200+, believing that this score is safe to defend. This can have an impact on the team composition as well. Of course, teams will have different strategies for different venues - at Bengaluru, teams typically target 200+ while at Eden Gardens, 160-170 is considered as a good score. But alternately, its also possible that the bowlers have become adept at keeping the runs down as well as picking up wickets at regular intervals.

2. What is a safe score?

Based on empirical evidence over the last 9 IPLs, let's try to deduce a safe target when batting first. For this, we've adopted two approaches. First, we've looked at all matches where the team batting first has won with a margin of 15+ runs i.e. comfortable victories. Here's what we get:

Data source: ESPNcricinfo.com

In IPL 2008, the average target set when the team batting first won by a margin of 15 runs or more, was 193 and 12 such wins were recorded during that season. The corresponding figures for IPL 2016 were 193 runs and 11 wins. The average target across all editions is 180.

Next, we've taken those matches where the chasing team has won a close match with only 3 balls (or less) remaining. Here's how it looks:

Data source: ESPNcricinfo.com

In IPL 2008, the average target which was successfully chased down with 3 balls or less remaining, was 174 and 9 such victories were recorded in that season. The corresponding figures for IPL 2016 were 173 runs and 8 wins. The average target across seasons is 163.

Comparing this with the above figure of 180 (winning comfortably when batting first) and taking into account the 3 balls in hand, it's reasonable to assume (based on empirical evidence) that 180+ is generally a safe target when batting first. For the above analysis, abandoned matches, ties and matches by Duckworth-Lewis method have not been considered.

3. Are batsmen more consistent now? 

How about batsmen? The record for most runs in a season has been improved from 616 runs in IPL 2008 (Shaun Marsh) to 973 runs last year (Virat Kohli). While Marsh scored at a very impressive strike rate of 139.68, both Kohli and Warner (who got 848 runs in 2016) got their runs at an incredible strike rate of nearly 152 per 100 balls. While only three centuries were struck in 2008, Virat Kohli himself scored four centuries in 2016 (overall six centuries were scored). What do the numbers tell us? On a season-by-season analysis of the runs per innings (RPI is slightly different from batting average) and strike-rate (runs per 100 balls) of all batsmen who've scored 300+ runs, we get the following:

Data source: ESPNcricinfo.com

In the inaugural edition, the average runs per innings (RPI) by all the top batsmen who aggregated 300+ during the season, was 31.3 and the average strike rate was 137.3 per 100 balls. The RPI has gone up from around 29 between 2012-14, to 33.4 in IPL 2016. This is the highest across all editions. Further, the strike rate has dipped only marginally, from 137.3 in 2008 to 136.2 in 2016. Hence, it would be safe to conclude that the batsmen are managing more consistency now without compromising too much on the strike rate. Also, increasingly there are more top order batsmen in the Top 10 batsmen list than in the past.

4. Are bowlers' bowling better now?

Let's look at how bowlers' performances have evolved since IPL 2008. For this, I've taken two important parameters - economy rate and bowling strike rate (i.e. no. of balls / wicket). Bowling average has deliberately not been considered since in a T20 match, balls remaining in the innings are a more important resource vis-a-vis wickets in hand. So, I've first taken the bowlers who've taken at least 10 wickets in a season and then tweaked the economy rate computation - instead of runs conceded per over, I've considered runs conceded per 100 balls (let's call it RP100B). This change in computation thus makes it directly comparable to batsmen's strike rate. Here is what we get:

Data source: ESPNcricinfo.com

While the RP100B had dipped to 120-125 between 2010 and 2014 editions, the figure has again risen up and is touching 131 in the last two editions. The average strike rate has, more or less, remained in the 18-20 balls / wicket range.

Further, I slice the above by bowling type i.e. pace or spin. This is how it looks like:

Data source: ESPNcricinfo.com

Over the years, except for IPL 2015, spinners have done better than pacers in keeping the runs down. On the other hand, as is the norm across formats, pacers have managed slightly better strike rates than spinners. During 2009-2014, the spinners were significantly better than the pacers in keeping the runs in check and they were close to the pacers in terms of strike rates too. This isn't surprising given that this period saw some world-class spinners operate - Warne, Kumble, Muralitharan, Harbhajan, and also saw some excellent talent emerge - Ashwin, Jadeja, Sunil Narine (before his modified action), Amit Mishra, Chahal, Axar Patel etc. Over the last couple of seasons, apart from ever-green performers like Malinga and Bravo, there's a group of seamers who've impressed - Bhubhaneshwar Kumar, Mustafizur, McClenaghan, Bumrah, Russell, Chris Morris etc.

5. Are teams evenly balanced?

One of the more remarkable and less-talked-about things with respect to IPL, is the concept of "equal purses" for all franchises. It started out as "equal auction purse" in 2008 ($5m for each team) i.e. all teams were allowed to spend upto $5m on buying players in the auction. This figure was increased to $9m in 2011. However, there was no limit on what teams could spend outside the auctions (i.e. trading players between each other). This was then further regulated in 2013 when IPL governing body stipulated an upper limit of $12.5m for the entire squad ("equal purse"). This equal purse concept has ensured a level playing field.

I've tried to analyze the competitiveness of the league for each season, using a measure called Herfindahl Index (Economics students will be aware of this concept). It's a measure of the size of firms in relation to the industry and an indicator of the amount of competition among them. HHI is an economic concept widely applied in competition law, antitrust and also technology management. It is defined as the sum of the squares of the market shares of the firms within the industry (sometimes limited to the 50 largest firms), where the market shares are expressed as fractions. The result is proportional to the average market share, weighted by market share. The results are to be interpreted as follows:

An HHI < 0.01 indicates a highly competitive industry.
An HHI < 0.15 indicates an unconcentrated industry.
An HHI 0.15 - 0.25 indicates moderate concentration.
An HHI > 0.25 indicates high concentration.

To compute IPL HHI, I've used the points garnered by a team during a season and divided by the total points available during that season (comparable to market shares). The IPL HHI is charted out below:

Data source: ESPNcricinfo.com

The first thing that jumps out - more the number of teams, more competitive the league. In 2011, when two new teams were introduced, the HHI fell to 0.106. Similarly, in 2012 and 2013 when there were 9 teams in the league, the HHI was 0.121 and 0.125, respectively. For an 8 team format, 0.131 is the lowest HHI, achieved in 2010 and then again in 2016. It's fair to conclude, looking at these figures, that the tournament has managed to stay highly competitive over the last nine years.

Conclusion

The above is simply an ex-post analysis of IPL data over the last nine years. There are multiple ways to analyze the same data and I've tried to take a different approach as compared to the traditional methods. Some of the conclusions may appear to be intuitively obvious. Yet, the humble attempt is to see whether empirical data leads to the same conclusions.

Classy India overcome tenacious Australia

In the end, India's all-round class proved too much for Australia. Till Day 2 in Dharamsala, Australia competed on equal terms, never let India run away and put enough pressure through their tenacity and resolve. This was best exemplified by their bowling performance on Day 2 - didn't allow India to score quickly, and picked up crucial wickets in the top and middle order. Then, on Day 3, it all came apart. Almost as if, the Aussie dam made up of resolve & grit couldn't hold up any more as India's superior class burst through.

Match recap

Australia won a very important toss and elected to bat. While Smith's men were unchanged from the last match (see my blog on Ranchi test), India made two changes. With Kohli injured, India chose to hand a debut to "chinaman bowler", Kuldeep Yadav. Further, given the likelihood that the ball would swing, India opted to replace Ishant Sharma with Bhuvneshwar Kumar. The changes meant that India went into the series decider with five bowlers i.e. a batsman short. 

Australia 1st innings

Bhuvneshwar Kumar started to swing the new ball immediately and could've had Warner off the first ball, but Karun Nair dropped a slightly tough chance at 3rd slip. Umesh got Renshaw with a beauty in his first over, but then Smith and Warner launched a very aggressive partnership. Smith especially looked in sublime form and punished both the seamers. The spin duo of Ashwin and Jadeja put some brakes on the run-rate but both Smith and Warner looked largely untroubled as Australia galloped to 131-1 at lunch. The match completely turned in the post-lunch session. The Indian captain, Rahane, continued with Kuldeep Yadav after lunch (he was introduced just before lunch) and the debutante's left-arm chinaman completely bamboozled the Australian middle-order. He first took out Warner with a flipper (caught at slip), then foxed Handscomb by a flighted chinaman which bowled him through the gate and then out-thought Maxwell by a fast googly which zipped through the surface and took out his off-stump. In between, Marsh fell to a loose shot, caught behind off the bowling of Umesh Yadav. Suddenly, at 178-5 having lost 4 wickets for 34 runs, Australia were under tremendous pressure and understandably, Smith became very circumspect. He eventually scored his 3rd hundred of the series and Rahane knew that the Aussie skipper had the ability to combine effectively with the lower order and put up a huge 1st innings total. He introduced Ashwin before tea and the tall off-spinner prized out Smith for 111. Australia went to tea at 208-6, adding just 77 runs during the session and losing 5 wickets in the process. Wade and Cummins tried hard with Wade specifically, having little problems dealing with Kuldeep Yadav. Wade went on to score a well made half-century but eventually, Australia were all out for 300, well short of the score they had in sights at lunch. For India, all the bowlers picked up at least 1 wicket with Kuldeep Yadav being the star, picking up 4 wickets. 

India 1st innings

Unlike Australia, India started slowly, reined in no doubt, by tight Aussie bowling. Hazlewood got rid of Vijay very early, and that brought together India's most prolific pair of this series. KL Rahul and Pujara again combined well, with the in-form Rahul completing his 5th half-century of this series. However, soon after reaching his half-century, Rahul's concentration wavered as he played a few loose shots and was eventually bounced out by Pat Cummins. Rahul and Pujara put on 87 for the second wicket. While Cummins was hostile, the Aussie spinners were not looking penetrative. However, the pitch offered bounce and soon enough, Lyon started to find his groove. Immediately after tea, Lyon accounted for Pujara (who had reached another half-century) as the extra bounce generated by the overspin, got the bat & pad, and lobbed to short-leg. Karun Nair didn't last long either, as he got out to Lyon in a similar fashion. Rahane and Ashwin put together a fifty-partnership before Lyon struck again. He took out both Rahane and Ashwin in quick succession, and India were on the backfoot, having lost the last 5 wickets for 113 runs. With Saha and Jadeja new to the crease, and India still 79 runs behind, Australia sensed an opportunity to take a sizable first innings lead. They took the 2nd new ball and were immediately presented with an opportunity. Cummins had Saha edging to an out-swinger but Renshaw dropped a fairly straightforward catch. This was his second drop of the match (he had dropped Rahul earlier) and one that would prove decisive in the context of the match. Like in Ranchi, the 7th wicket partnership proved match-turning for India. The pair added 96 runs for the 7th wicket before Jadeja was dismissed for a well made 63. India eventually got all out for 332, a lead of 32 on a pitch that was rapidly deteriorating. Lyon took a 5-wicket haul and looked at his most dangerous since Day 1 in Bengaluru.

Australia crumble, India rumble

India's lead wasn't substantial and Australia would've been confident of quickly wiping that off. Instead, they were greeted by India's best all-round bowling performance of the entire season. Both Umesh Yadav and Bhuvneshwar Kumar were very hostile to begin with, bowling at high pace, swinging the new ball as well as bowling nasty bouncers. Even though Karun Nair let-off Warner in the slips again, it didn't prove costly for India as the seamers got rid of both the openers, as well as the batting mainstay, Steve Smith, before Australia could even erase India's lead. Maxwell and Handscomb then led a min-revival as they put on 55 for the 4th wicket. Both Ashwin and Jadeja, however, were getting enough assistance from the pitch and causing problems for both Maxwell as well as Handscomb. Finally, just before the tea interval, Ashwin forced Handscomb to nick a straighter delivery to 1st slip and in the very next over, Jadeja got Marsh caught at short leg. By then, Australia had lost 5 wickets and were ahead by only 60. Maxwell was holding fort from the other end and had reached an aggressive 45, before he padded up to an off-break from Ashwin and was adjudged LBW. That finally broke the back of the Aussie resistance. They eventually managed 137, setting India a target of 106. Ashwin, Jadeja and Umesh Yadav, each picked up 3 wickets.

A target barely crossing 100 was never going to test this Indian team, given that the pitch was still good for batting. KL Rahul got another half century (his 6th 50 in 7 innings in this series) and even though, Vijay and Pujara departed early, an aggressive Rahane ensured that win was achieved quickly and without any further hiccups. India won the match by 8 wickets and the series 2-1. The series win ensured that India regained the Border-Gavaskar trophy and also made India the holder of test trophies against all test playing nations simultaneously (only the 3rd team ever to achieve this). Ravindra Jadeja, with 127 runs (63 in this match) and 25 wickets (4 wickets in this match) in the series, was adjudged as the Man of the Match and Man of the Series. India's gamble of playing five bowlers worked and the debutante, Kuldeep Yadav, picked up four crucial wickets in the first innings.

In the end, India just had too much firepower, too much class for Australia. Like in Bengaluru (see my blog), Australia lost the match due to a poor batting performance in their 2nd innings. Ultimately, they needed someone other than Smith to produce a gritty batting performance (like Handscomb and Marsh did in Ranchi). India finished their 2016-17 test season with 10 wins, 2 draws and just 1 loss - joint 2nd for most test wins in a season. And though they dominated both New Zealand and England, this victory against the gritty Aussies would taste the sweetest!

    

Dharamsala test: Series decider in the shadow of the Himalayas

So we finally arrive in the hillside city of Dharamsala, with the series tied at 1-1, with hours of exciting cricket already played, and yet with everything to play for in the venue's debut test. There's been some banter on-the-field, some words spoken off-the-field, the media has played its role but overall, these incidents have been overshadowed by some terrific cricket played by both teams. Many expected India to steamroll their opponents but clearly Smith & his team were quietly confident about their chances, even before the Pune test. Its perhaps apt then, that they come into the decider on the back of a hard-fought draw, with both teams confident of their chances and yet, aware of the opposition's threat.

Will India make it 10 for the season?

Leading up to this series, India had won 8 tests and drawn 1 during this home season. In this series, they've won their 9th test, drawn their 2nd and lost their 1st test match of the season. Kohli & Co. will undoubtedly look to record their 10th victory at Dharamsala and take the series along with it. Given the quality of their opposition, this would be one of Kohli's sweetest series victories as a captain. In each of the three tests, Australia has grabbed the initiative and put India under severe pressure. And yet, apart from the failure in Pune, India has stood up to the challenge. They turned the tables both in Bengaluru, where they won, as well as in Ranchi, where they put Australia under tremendous pressure on Day 5. The bowlers have looked good and if the batting clicks as a unit, the Border-Gavaskar trophy could be won at this picturesque venue.

Will Smith & Co. conquer India in India?

Australia's last test series victory in India was in 2004-05. In fact, since that series winning test at Nagpur, Australia went 11 tests in India without a victory. They finally broke that winless run in Pune and had chances both in Bengaluru, and less so in Ranchi, to seal the Border-Gavaskar trophy (as a previous winner, Australia will retain the trophy even if they draw the series). Despite that, it can't be denied that the Aussies have held on valiantly after the morale-crushing defeat at Bengaluru and the subsequent sidelining of Mitchell Starc on account of injury. Pat Cummins showed in Ranchi that he's perfectly capable of filling in as a strike bowler. If the Dharamsala pitch lives up to its reputation of assisting seamers, then Australia can pick up Jackson Bird in place of the struggling Nathon Lyon and hope that they can use Maxwell's off-spin more effectively. A win or a draw will help Smith & Co. to retain the Border-Gavaskar trophy, a result unthinkable for many, even in the Australian press, just four weeks ago!    

How are the teams placed?

Australia is likely to field the same eleven that secured a draw in Ranchi. Pat Cummins has been cleared to play after precautionary tests on the back. Australia would be hoping that Nathan Lyon comes back into form on a pitch that will likely to have more bounce and pace than Ranchi. If the curator leaves more than a tinge of grass on the wicket, then Australia may be tempted to replace Lyon with Bird. However, that seems unlikely and even Australia won't want to change a stable, successful combination for a crucial test like this.

India has been bothered by a few injury issues, the biggest among them being the shoulder injury of Virat Kohli. Cricket fans will remember, that twelve years ago, Australia headed into the Nagpur test 1-0 up and on a greenish pitch that offered massive assistance to fast bowlers, India's captain (Sourav Ganguly) had to miss the test due to injury. The Aussies were pleasantly surprised by that pitch; their seamers picked up 16 wickets to help Australia win the match by a huge margin and secure the series. With the likelihood of a pitch assisting the seamers and the captain missing out on account of injury, there's a sense of déjà vu. Indians would be hoping to avoid an encore though. Shreyas Iyer has been called as a cover for Kohli, and Rahane will captain if Kohli fails to pass the fitness test. An additional headache has emerged in the form of M Vijay's fitness. He didn't attend the practice sessions and it's likely that the shoulder injury, that kept him out of the Bengaluru test, has flared up. If he does sit out, then Abhinav Mukund will take his place. On the bowling front, it's unlikely that India will tinker with the combination, except if there's potentially some swing available. In that case, Bhuvneshwar Kumar may replace Ishant Sharma. 

Pitch

The pitches in this series have come under intense scrutiny. And the quality of the pitches have thrown up some intriguing battles. The pitch at Dharamsala has traditionally assisted pace bowlers. And the cool climate (with temperatures in the low 20s) is likely to assist swing. Kohli expects the pitch to have bounce and carry. With the almost anti-climatic behavior by the Ranchi pitch after the massive hue & cry raised prior to the match, the predictions have been far more guarded this time around. Or may be, with so much at stake, everybody is too tense to venture into predictions!    

India & Australia: Perfecting the Art of Comeback

At the end of day 5 in Ranchi, a draw was probably a fair result. And the series scoreline, with a test to go, is also a fair reflection of how both teams have competed relentlessly on even terms. The Ranchi test ebbed and flowed in a manner symptomatic of this series. Australia pushed India on the back-foot through a sizable first innings total and by making inroads into the Indian middle-order. India then pulled things back through a monumental 7th wicket partnership and then applied pressure on the Aussies by picking up their first 4 wickets cheaply. Finally, it was left to the young, Handscomb and the experienced, Shaun Marsh to combine and save the day for the visitors.

Recapping Day 4 and Day 5

Australia had a slight upper hand going in to Day 4 with India still trailing by 91 (Check out My previous blog). The overcast conditions (necessitating the use of flood-lights) seemed to be tailor-made for Cummins and Hazlewood. However, the ball was soft (50 overs old) and the next new ball was available only after another 30 overs. Australia tried very hard, dried up the runs but couldn't break the resistance offered by Pujara and Saha. While Pujara remained resolute in defence, Saha used his feet intelligently against the spinners. Even though only 75 runs were added in the morning session, this pair ensured that India didn't lose a wicket and in the process came very close to the Aussie first innings total. Australia took the new ball as soon as it was available, in the hopes of breaking the partnership & then running through the Indian lower middle order. Those hopes were to remain suspended for another session though. And any hopes of India going for quick runs in the 2nd session quickly evaporated as the overnight pair ensured another wicketless session with the addition of 68 runs between lunch and tea. Post-tea session, however, was the most eventful of the match. Saha quickly completed his 3rd test century and then Pujara completed his double century, the 3rd of his career and 2nd against Australia. He got out shortly after that, giving Lyon his first wicket since the first innings of Bengaluru test, and ending a monumental 199 run partnership with Saha. Jadeja quickly got into the groove and even though Saha departed shortly after Pujara, he along with Umesh Yadav piled on further misery on the Australians by putting together a 54 run partnership. Jadeja got a quickfire fifty (54 off 55 balls) before Kohli declared, with India 152 in front and Australia facing the daunting task of seeing off 8 overs before close of play. They ultimately didn't have to play the full 8 overs as the nightwatchman, Lyon, fell to 2nd delivery of the last over. Jadeja was expected to be the danger-man for Australia and he got both Warner and then Lyon by two absolutely top class deliveries. Australia ended Day 4 at 23-2, still 129 runs in arrears, and staring at a real prospect of defeat.

Day 5 began with Australia's most prolific pair (during this series) on the crease. Both Renshaw and Smith had played the Indian spinners reasonably comfortably throughout the series and India knew that breaking this partnership would almost mean a foot in the door. The pair survived for another 21 overs and had brought the lead down to less than 100, when Renshaw fell LBW to Ishant. The Indian quick who was bowling from round the wicket, set up Renshaw very nicely. He bowled a couple of nasty bouncers and followed those up with a full delivery that caught Renshaw on the crease, dead in front of the stumps. Three balls later, Jadeja accounted for Smith when the Australian captain, in a moment of indecision eerily similar to his Indian counterpart in Bengaluru, padded up to a delivery that was relatively full and in line with the stumps, and lost his off-stump. With both in-form batsmen back in the hut and Australia still 89 runs behind India, Kohli & Co. must have started harbouring hopes of wrapping up a victory in the 2nd session. That however proved to be a false dawn with Shaun Marsh and Handscomb displaying superior defensive technique and putting up an outstanding rearguard action. Very importantly, the rightie-leftie pair kept the scoreboard ticking thereby eating away at India's lead. By the time Jadeja got Marsh, they had added 124 runs, eaten up 62 additional overs and the match was already in the last hour. Even though, Ashwin got Maxwell shortly thereafter, both Handscomb and Wade ensured no further damage and finally, with 10 minutes left, Kohli and Handscomb shook hands, signalling the end of a very thrilling encounter. 

Stats Stack-up

Two of the top 3 batsmen from both teams continue to dominate the batting charts. And, Peter Handscomb is slowly starting to make his mark in this series. He combined brilliantly with Shaun Marsh (who's at no.6 in the list below) to pull Australia out of the woods and help them save the Ranchi test. And who would've thought that Kohli would muster less than 50 runs in 5 innings! 

Data source: ESPNcricinfo.com

There's not much change in the bowling charts either. Jadeja has emerged as the most effective as well as the most consistent bowler from either side. Steve O'Keefe has been steady over the last two tests following his spectacular 12-wicket haul in Pune. Both the off-spinners will be slightly disappointed - they've been good in patches (one inning each in Bengaluru) but haven't looked consistently penetrative. Umesh Yadav continues to be the best fast bowler from either side but he may be in for some competition from Pat Cummins (given the likely conditions in Dharamsala). 

Data source: ESPNcricinfo.com

Everything on the line in Dharamsala

The next test in Dharamsala starts in 5 days and this gives very little time for the players to recover. This is especially true for bowlers - on an average, the fast bowlers bowled 40 overs while the spinners bowled 70 overs (mainly because of Jadeja and O'Keefe) in this match. However, with the season coming to an end, the respective team managements will push the players to give it all. Plus, there's plenty on line here. Whoever wins the next match, wins this series as well as the Border-Gavaskar trophy. In case of a draw, Australia will retain the trophy. 

A fighting draw in Ranchi may give the momentum to the Aussies and hence make them favourites for the next test, but there've been enough instances during this series where teams, when counted down and out, have made spectacular comebacks. Recall how India seemed down and out at the end of Day 1 in Bengaluru (check my blog during Bengaluru test), and having already lost the Pune test (check my blog after Pune test), were in serious danger of losing the series. Instead they mounted a superb comeback, led by their bowlers as well as Pujara and Rahane, and pinned the Aussies on the mat. Coming into the 3rd test, remember the kind of pressure Australia and Steve Smith were under (following the DRS-issue). India were considered heavy favourites to continue their winning momentum in Ranchi. And yet, Australia, led by Smith and comeback man Maxwell, mounted an impressive first innings total. Further, Pat Cummins, returning to test cricket after 6 years, put India under serious pressure. Then again, Pujara and Saha rescued India with the bat while Jadeja, with both bat and ball, gave a mighty scare to the Aussies. Prediction won't make for a lucrative profession in this series. 

Dharamsala, making its debut as India's 27th test centre, will have a much cooler climate. It has traditionally assisted fast bowlers. We are all set for the final test of this season. Here's hoping that Dharamsala adds another exciting chapter to this riveting series!

Ranchi Test, Day 3: Hard to separate the two teams!

What a contrast Ranchi has presented when compared to Pune or even Bengaluru! Contrary to expectations, this looks like a fantastic test match pitch which allows run making as well as wicket-taking, but only to those who can ally skill with perseverance. Thankfully, both sides have thrown up a few players displaying this trait and this has resulted in a riveting test match till now.

Match recap till Day 3

Australia scored 451 in their first innings, thanks largely to Steve Smith's unbeaten 178 and Glenn Maxwell's maiden test century (104). On a good batting wicket, Smith won the toss and chose to bat. Renshaw and Warner gave the Aussies a frenetic start, putting together 50 in less than 10 overs, before a combination of loose strokes and good bowling, pulled them back to 89-3. Smith and Handscomb led a minor revival before Umesh trapped Handscomb LBW with a superb in-swinging yorker. At 140-4, Smith knew he needed support from his teammates to take Australia beyond 350, a score that would've kept Australia in the game. He found one in Glenn Maxwell. Together they put on 191 runs for the 5th wicket; in the process, Glenn Maxwell hit his maiden test century. Smith also got some useful support from Wade and Steve O'Keefe to help Australia finish with 451. Jadeja and Umesh were the standout bowlers for India, picking up 5 and 3 wickets, respectively.

In reply, India got off to their best start of the series with the aggressive KL Rahul combining very well with M Vijay to put on 91 for the first wicket. Rahul continued his rich vein of form to score a brisk 67 before he was undone by a superb bouncer from the comeback man, Pat Cummins. Then, Vijay and Pujara put together their 6th century partnership of this season before Vijay, in what was a brain-fade moment, stepped out to O'Keefe in the last over before lunch and was stumped by a long-way. He fell 18 short of a well-deserved 100. However, Pujara did get to his 11th test century - the first by an Indian in this series. Despite receiving little support from the other end, with both Kohli and Rahane falling cheaply, Pujara held one end up, picked up the scoring rate once the 2nd new ball was taken and ensured that India remained within touching distance of Australia. Pat Cummins was the most impressive Aussie bowler on display, picking up 4 wickets.

India ended Day 3 at 360-6. Both India and Australia would be reasonably satisfied with this day. India, because it is now within striking distance of Australia's total and with Pujara still on the crease, can harbor hopes of overhauling 451. Australia on the other hand would be pleased that it restricted the Indian scoring rate on Day 3 and just allowed 240 runs while picking up 5 wickets, on a pitch that is still very good for batting. It doesn't look like that the pitch will crumble at an alarmingly rapid rate and hence, this test match may last the distance. Coming in to Day 4, Australia would like to wrap up the last four wickets for not too many, score quickly in their 2nd innings and possibly declare an hour before the end of day's play (ideally setting India a target of 350). India, on the other hand, would like some quick runs from Jadeja and Saha, and then look to dismiss Australia cheaply. They would ideally want to chase a score of not more than 150 in the final innings.

Key factors that may shape the outcome of the match

• Jadeja & Ashwin - Apart from the quick runs India expects Jadeja to make, they will also want him to continue his rich bowling form. There are foot-marks created outside the left-hander's off-stump (by the right arm quickies from both sides) and given the predominance of lefties in the Aussie lineup, Jadeja would like to exploit this to the hilt. He's been the best spinner from either side in Ranchi and India's hopes for a win will rest largely on his shoulders. India would also expect Ashwin to find the match-winning form that he displayed in the 2nd innings of Bengaluru test. 

• Warner & Maxwell - Australia will need quick runs in their 2nd innings and would look up to the explosive duo of Warner and Maxwell to deliver the goods. Warner is due for a big score and the match situation may de-clutter his mind and enable him to commit fully to an aggressive batting strategy. Maxwell on the other hand, would be supremely confident after his first innings century. He's had success against Ashwin in the past (during IPL) and his unorthodox methods can upset bowlers' rhythm.

• Aussie bowling - The Aussie bowlers would have their task cut out in the 4th innings of the match. While Cummins has looked very impressive in his comeback match and Hazlewood continues to toil away diligently, both Lyon and O'Keefe haven't looked threatening since the first innings of Bengaluru test. The Aussie spin duo will have to come to the party if Australia wants to seal the Border-Gavaskar trophy at Ranchi. Additionally, reverse swing will also be a factor going forward.

• Pitch - The Ranchi pitch has played very well till now. However, both teams will be hoping that it starts assisting the spinners more & more on Day 4 and 5. Typically, one would expect spin and variable bounce, thereby making run-scoring difficult. The conditions are likely to assist reverse swing too. 

Both the captains would be very keen to win the Ranchi test. If Australia win, they'll retain the Border-Gavaskar trophy irrespective of the result in the next test. In case of an Indian victory, the team will definitely enter the next test as strong favorites to regain the trophy. The match situation will clearly test the patience as well as pro-activeness of both the captains. On this pitch, a proactive captain will strive to make things happen. Here's hoping that fortune favors the brave!   

  

Ranchi's test debut with series nicely set up at 1-1!

India made a stunning comeback in the Bengaluru test to level the series 1-1. The thrilling final day at Bengaluru has left the cricket lovers gushing for more! All the events - wickets, runs, swing, seam, spin, DRS reviews, momentum swings; everything seemed to be happening in fast-forward mode. Almost as if, Day 4 was a microcosm of the three previous days. So the long gap between the Bengaluru and Ranchi tests was welcome. Everybody, including the fans, needed to catch some breath after that breathtaking match.

Reliving the Thrilling Day 4

The day started with the match in balance. India started off cautiously - only 11 runs came off the first 8 overs. There were a few nervy moments for India - both against Pujara. First, when he a popped up a Steve O'Keefe delivery to forward short leg, where the usually brilliant Handscomb could only catch this one on a half-volley. And then again in the next over, when Lyon trapped Pujara LBW through a viciously spinning delivery which kept low, only to be overturned by DRS. The ball-tracker confirmed that the ball was spinning down the leg side. These anxious moments aside, the first 45 minutes of the day were calm & serene. This, however, turned out to be the calm before the storm. Australia took the new ball immediately after the 80th over. And this decision turned the match in Australia's favour. Mitch Starc, bowling fast & full, swinging the new ball into the right-handers, created havoc and within a space of 3 balls, had the well-set Rahane LBW, castled the in-form Nair and nearly got Saha too. In the very next over, Hazlewood got Pujara and Ashwin in quick succession. Pujara could not get to a well-deserved 100, falling in the nineties for the first time in his career. In his next over, Hazlewood got Umesh Yadav and this left India tottering at 258-9. Ultimately, Saha and Ishant got 16 more runs before O'Keefe got Ishant. India were all out for 274, losing the last 6 wickets for 36 runs, thereby setting Australia a target of 188. This was an in-between kind of a target; neither the 225+ that would have made India the firm favorites (esp. given the position they were in at the start of Day 4) nor the kind of total that Australia could've just cantered through.

The Aussies started their chase in a brisk manner, probably aware that the new ball was the best time to pick up quick runs. Ashwin started off very well, repeatedly troubling the shorter man, Warner. On the other hand, Ishant got the Aussie bedrock, Renshaw, pretty early. It was a very good ball - bowled from round the wicket, angled in, bounced & seamed away, taking the glove on its way to Saha. Despite this early hiccup and a few other nervy moments, Australia had galloped to 42-1 after 9 overs, a run rate of 4.67 (far ahead of the run-rates achieved in the previous three innings of the match). This is when disaster struck for Australia. Ashwin, who was bowling from over the wicket to Warner and was hit for a 6 off the last ball of his previous over, switched to round the wicket and on the very first ball, Warner tried to sweep a flighted off-break and was wrapped on his pads. The umpire gave it out and after a surprising moment of hesitation, Warner went for the DRS. The ball tracker showed that the ball barely hit Warner in the line of off-stump (in fact, to the naked eye, it appeared that the ball had hit him outside the line) - this was adjudged as umpire's call. Further, the ball seemed to be hitting the outside of off-stump - again adjudged as umpire's call. Given the evidence, DRS had to agree with the on-field umpire's decision but it was a highly contentious decision and one that would have a lasting impact on the outcome of the match. Smith and Shaun Marsh continued the steady flow of runs and took Australia to 67-2 when a slew of serious errors in judgement rocked the Aussie boat again. Firstly, Shaun Marsh shouldered arms & was wrapped on his pads to a Umesh Yadav delivery from round the stumps. Then, the umpire Nigel Llong, adjudged him LBW when the ball was clearly going to miss the stumps. Shockingly, Smith and Marsh decided not to review the decision! That decision of not reviewing was probably based on the fact that they had just lost a review (Warner) and did not want to risk a scenario where they would be left with no reviews for 65 overs. India of course, did not mind these dollops of luck but were very much aware of the danger that Smith posed. He was expertly handling the spinners and was keeping out the grubbers delivered by Indian seamers. However, in the 21st over, another grubber from Umesh proved one too many for Smith and he was hit plumb in front of his stumps. Surprisingly, this time, Smith was rather keen on reviewing and even looked up to his dressing room for help with DRS. This was a clear breach of rules and the umpires intervened, sending Smith on his way. Even Kohli had a thing or two to say to his Aussie counterpart. This was the final nail in the coffin for Australia, and despite Handscomb and Mitch Marsh putting up a brief resistance, a rampaging Ashwin proved too much for the lower-middle order. Very much like their opponents, Australia lost the last 6 wickets for 38 runs with Ashwin picking up 5 of them. He roared back into form with a match-winning spell of 6-41 in the 2nd innings while KL Rahul, for his twin-fifties in a low scoring affair, was adjudged the Man of the Match. India won the match by 75 runs and leveled the series in emphatic fashion.

The much-dreaded thunderstorms arrived in the evening but thankfully, the match was over by then. It would've been cruel if rains were to decide the outcome of such a thrilling match.

Key themes in this series

Pitches

While it's fair to say that the pitches have been spinner friendly (spinners have taken 57 of the 80 wickets to fall in the series), the fast bowlers have also had an impact, esp. in the Bengaluru test where they accounted for 14 out of the 40 wickets that fell. Pune served up a rank-turner with the pitch crumbling on day 1 itself thereby offering vicious turn & bounce. On such a pitch, quick left-arm orthodox spinners became more dangerous and both the captains relied more on spin vis-a-vis pace. The Bengaluru pitch on the other hand offered variable bounce (more on the lower side) which brought the fast bowlers into play as well as slow turn which forced the spinners to rely more on variations in flight & uneven bounce. The charts below bear this out.

Data source: ESPNcricinfo.com

Data source: ESPNcricinfo.com

Starc, the batsman, as crucial as Starc, the bowler

As Australia's premier strike bowler, Mitch Starc has bowled at high pace throughout the series. He's got the ball to swing into the right-handers from over the wicket, got it to rear up from a good length and has gone round the wicket in search of reverse swing. Even though he's picked up only 5 wickets, each of those have been top order batsmen. Equally impressive has been his performance with the bat. He's amongst the top 5 run getters having out-scored both Warner and Kohli. In fact, he's accounted for 54% of the runs scored by the last 5 Australian batsmen across all innings (118 runs out of 217). In a series punctuated with low scores, where no team has crossed 300 and teams have not been able to cross 125 on three separate occasions, Starc's contribution with the bat has had a major impact. His absence for the remainder of the series, therefore, will be a massive blow to the Aussies.

Top order thrives, middle order flops

From both sides, an opener and the no. 3 batsman has thrived. KL Rahul has been India's star performer with the bat, and with 215 runs, is the highest run getter on either side. He, alongwith Pujara, has ensured that, even though India has not got off to solid starts during the series, it has made a comeback as a batting unit. On the other hand, Aussies have been assured of a solid start mainly due to the increasingly dependable Renshaw and the captain-prolific, Steve Smith. These four batsmen occupy the top four positions in the batting charts. On the other hand, the failure of David Warner and Virat Kohli has been most surprising. Neither of them has totaled even 100 runs in the series. While Warner has got starts in 3 out of 4 innings, he has generally struggled against Ashwin and hence, has not been able to convert them into big scores. Kohli, on the other hand, has misjudged either the line of the ball or the movement off the pitch on three occasions, and this has resulted in cheap dismissals. All in all, the middle and lower order has undone the good work of the top order.

Data source: ESPNcricinfo.com

Aussie spinners outbowled the Indians; Umesh stands out amongst quicks

In their first three innings, the Indian batsmen were dominated by the Australian spinners. They kept the runs down and picked up 26 out of the 30 wickets. The impact was such that India could only stitch together two 50-run partnerships across these 3 innings. On the other hand, Ashwin, Jadeja and Jayant Yadav were less impactful in the first test match and couldn't run through the Australian batting line up. This allowed the Aussies to stitch together four 50-run partnerships in the first test itself. However, first Jadeja and then Ashwin began pulling things back in the 2nd test. They matched the Aussie spinners in the first innings of the 2nd test match and then finally, outbowled them in the 2nd innings with Ashwin leading the way. 

In the pace bowling department, while both Starc and Hazlewood have had their moments, Umesh Yadav has been the standout quick bowler from either side. He picked up 6 wickets in the Pune test and 3 top order batsmen in the Bengaluru test. Umesh has been quick, economical and has consistently generated pace & movement. 

Data source: ESPNcricinfo.com

DRS usage & impact

The Decision Review System has added spice to the ongoing series. It's not just those decisions which were reviewed, but even those that could've been reviewed but weren't, that added to the drama. By common consensus, India were pretty ordinary with their usage of DRS in the first test. While fielding, in both their innings, they wasted their reviews within the first 40 overs. While batting in the 2nd innings, they wasted their reviews within the first 6 overs! None of the wasted reviews were even close to overturning the umpire's decision. On the other hand, Australia were very judicious with their usage of review system, never reviewing those where they had some doubt, and they ended up with multiple successful reviews throughout the match.

India's first innings at Bengaluru seemed to be a continuation of Pune when Kohli left a relatively straight & fuller delivery from Lyon and was trapped plumb in front. If the leave wasn't shocking enough, he decided to outmatch that with a shocking review! In Australia's first innings, India missed a trick by, ironically, not going for a review against Shaun Marsh when he gloved a Umesh Yadav delivery to Saha. He was on 14 at that time and went on to make a crucial 66. In between, Marsh went for a great review when adjudged LBW to Yadav and managed to get the decision overturned. India meanwhile continued with the trend of "hopeful" reviews and were out of their 2nd set of reviews (granted after the 80th over) by the 94th over!

Things however, began changing in India's 2nd innings. Kohli reviewed what looked like a genuine 50-50 LBW call and was probably unlucky that there was no conclusive evidence proving whether the ball hit the bat first or the pad. Even Pujara got an LBW call overturned. The Aussies, meanwhile, continued to be judicious with their use of DRS.

The review system left a significant impact on the match in Australia's 2nd innings. First, the Warner dismissal was clearly a contentious call where the benefit of doubt should have gone in favour of the batsman. Then, Shaun Marsh not reviewing a howler was clearly influenced by the Warner review. Lastly, the Smith episode where he, after being adjudged LBW, looked up his dressing room for advice on whether or not to go for the review, caused a lot of bad blood between the two teams. Smith insisted "brain-fade", Kohli alleged ongoing tactic and ultimately, the two cricket boards had to intervene and call a truce.

Leading up to the Ranchi test

Pitch

The JSCA International Stadium at Ranchi is set to make its debut as India's 26th test center. The average first innings total in the two Ranji matches held earlier this season is 140. Progressively the pitch became better for batting in those games. Also, it has been known to assist both the seamers as well as spinners. As per media reports, the pitch for the upcoming test match has an unusual dark color about it and experts believe that it won't bounce a lot. The dark color of the pitch may be on account of moisture which would mean that spinners relying on overspin (like Lyon) may extract some bounce on the first couple of days. The moisture in the pitch should also help bowlers who can extract seam movement. The pitch should become better for batting on Day 2 and Day 3.

Team compositions

Mitch Starc's injury will be a big blow for the Aussies. Another Mitch (Marsh) has also been ruled out due to injury and that means Australia will be forced to make at least two changes. They've flown in Pat Cummins as a replacement for Starc and he's likely been rushed in to enable a like-for-like replacement (strike bowler to be used in short bursts). However, I won't be surprised if Australia opt for Jackson Bird. Also, I expect them to bring in Marcus Stoinis to replace Mitch Marsh. 

For India, M Vijay should make a comeback as an opener. It's unlikely that they'll drop Karun Nair and bring in Jayant Yadav. 

With the series now in balance and with both teams now aware of each other's strategies, this should be another engrossing affair. Australia can retain the Border-Gavaskar trophy if they win here. Kohli & co. would be eager to prove that Pune was an aberration. Let's Play!