Devarchit Varma
Devarchit Varma is senior writer with CricketCountry. He can be followed on Twitter @Devarchit
Written by Devarchit Varma
Published: Feb 01, 2016, 05:44 PM (IST)
Edited: Feb 01, 2016, 05:44 PM (IST)
Even a splendid century by Shane Watson was not enough for Australia to stop the Indian juggernaut that began in Sydney a few days ago and ended at the same venue. India held on to their nerves and smashed the Australians by 7 wickets in the third and final Twenty20 International (T20I) at Sydney Cricket Ground (SCG) on Sunday, and took the series 3-0. India were dominant, a more composed side and did well to find rhythm to thrash the Australians, who generally do not receive such treatment at home. The loss meant Australia’s future in international T20 cricket looks bleak, with the side being far off from a settled one and the impending ICC World T20 2016 will only add pressure on them. ALSO READ: India vs Australia 2015-16: India’s marks out of 10 in T20Is
Australia will find the going very tough from here on. ICC World T20 2016 certainly does not look anywhere in their priority list. and there is minimal effort being made to control the damage that has been made. In the series against India, the Australians struggled on many fronts, and their overall performance was a big letdown. Let’s take a look at how the Australians performed against India in the three-match T20I series: Pick of the tweets: Australia vs India, 3rd T20I at Sydney
1. Shane Watson (8/10): Watson returned with a bang as he ended the series with 151 runs in 3 matches, an average of 75.50 with a century in the final game. Watson was perhaps the best performer for Australia throughout the series, starting with his two-wicket burst in the first T20I at the Adelaide Oval. Watson’s revival gives Australia some hope as they build up for the ICC World T20 2016.
2. Aaron Finch (8/10): Finch captained Australia in two matches out of three and was one of the top performers with the bat. With key players rested and himself missing the third T20I, all he could do was to keep making runs so that there are no shortfalls. Finch could not do much with his bowlers who were inexperienced and were facing a rampant Indian batting line-up.
3. Steven Smith (2/10): Smith played only one match, and he was in the centre of a controversy that also involved Virat Kohli. Smith scored 21 runs in that innings, and fell at a time when Australia needed him the most. ALSO READ – India vs Australia 2015-16, 3rd T20I at Sydney: Statistical highlights
4. David Warner (2/10): Warner, too, played only one match. Warner looked in his element but fell only for 17. Warner, like Smith, was rested from the final two T20Is.
5. Shaun Marsh (3/10): Marsh played two matches and scored only 32 runs. Marsh certainly missed out on opportunities to get himself in for reckoning in ICC World T20 2016, as there will be a tight competition between Australian cricketers for a spot in the squad for the tournament.
6. Chris Lynn (3/10): Lynn came into the side riding on impressive performances in the Big Bash League T20 2015-16 tournament. However, he failed to carry on the good show as he could manage only 32 runs in 3 matches. Lynn batted in the middle-order and failed to capitalise on all the chances that he got.
7. Travis Head (3/10): Head, too, was included in the Australian side following the impressive performances in the BBL 2015-16. Head featured in two matches, and could manage only 28 runs. The failures of Lynn and Head, in the middle order, let down Australia and their chances of winning against India in tight conditions.
8. Matthew Wade (4/10): Wade’s struggle for runs has hurt Australia’s chances. With Wade’s experience Australia would have expected him among the run makers. Wade had earlier disappointed in the ODIs as well. Australia may look into his role and performances going ahead.
9. James Faulkner (4/10): Faulkner has been involved in many on- and off-field banters but his performances are not speaking highly. Faulkner returned to the national side in the ODI series after ICC Cricket World Cup 2015. Since his return, he was smashed all over the park and failed to make runs.
10. Usman Khawaja (2/10): There was tremendous hue and cry over the exclusion of Khawaja in the T20I squad. He was taken into the side ahead of the third T20I and had an ordinary outing. Khawaja scored 14 runs in the only match he played.
11. Cameron Bancroft (2/10): Bancroft would not have anticipated that his debut for Australia — being a red-ball specialist — would come in T20I format. Bancroft kept wickets for Australia in the third T20I, and took a catch as well. He, however, did not score a run as he remained at the non-striker’s end.
12. Andrew Tye (3/10): Australia experimented a lot in this series, but without desired results. Tye played two matches and failed to make a mark. Tye claimed 1 wicket and scored 4 runs.
13. John Hastings (2/10): Hastings played only one match in the series, and remained wicketless. In the second T20I at Melbourne, Hastings was punished by the Indian batsmen as he was hit for 35 runs.
14. Nathan Lyon (2/10): Lyon made his T20I debut this series. Lyon’s woes in limited-overs continued as he failed to make any mark. There was bounce and turn in offering but Lyon was not able to put any kind of pressure on the Indian batsmen.
15. Scott Boland (2/10): Boland continued to remain a soft target for the Indians. He played in two matches, and bowled 7 wicketless overs for 64 runs. He remains a work in progress.
16. Kane Richardson (2/10): India’s collapse in the fourth ODI at Canberra had handed Richardson a five-wicket haul, but he was found wanting in the T20I match. Richardson played only one game, and was slammed for 41 in 4 overs.
17. Shaun Tait (3/10): The ‘Wild Thing’ continued to be wayward. Tait played in the first two T20Is and was punished by the Indian batsmen. He bowled 8 wicketless overs for 91 runs, which effectively ruled out his possible selection in the ICC World T20 2016.
(Devarchit Varma is senior writer with CricketCountry. He can be followed on Twitter @Devarchit)
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.