Notifications
Settings
Clear Notifications
Notifications
Use the toggle to switch on notifications
  • Block for 8 hours
  • Block for 12 hours
  • Block for 24 hours
  • Don't block
For Quick Alerts
ALLOW NOTIFICATIONS  
For Daily Alerts
 

IPL 2017: 5 reasons for Rising Pune Supergiant's loss in the final

Here are five reasons for Rising Pune Supergiant's loss against Mumbai Indians in the final of the IPL 2017.

New Delhi, May 22: Rising Pune Supergiant's dream of lifting their maiden IPL trophy as they suffered a defeat at the hands of Mumbai Indians by a margin of just 1 run in the final on Sunday (May 21).

IPL Special Site; Match Scorecard; Match Highlights; Photos

Chasing a low target of 130 to win, RPS could only muster 128 from the stipulated 20 overs and ended up on the losing side at Rajiv Gandhi International Stadium in Hyderabad.

IPL 2017: 5 reasons for Rising Pune Supergiant's loss in the final

Mumbai Indians, on the other hand, lifted their third IPL trophy after edging RPS in the nail-biting last ball thriller contest.

Pune needed 4 runs from the final ball but bowler Mitchell Johnson conceded just 2 runs to ensure his side successfully defends the total.

Young Krunal Pandya was awarded the man of the match for his all-round effort against Pune. Pandya's knock of 38-ball 47 and disciplined bowling effort (31/0) from his quota of 4 overs laid the foundation for Mumbai's win.

There were several things that went wrong for the RPS as they faltered in the run chase. Pune batted very slowly in from the start and let the asking rate go up and that ultimately proved too much for them to achieve in the final overs.

Here are the 5 reasons for RPS' defeat in the final:

1. Ben Stokes' absence

1. Ben Stokes' absence

Pune clearly missed the services of their most important player of the season. The England all-rounder was key to Pune's turnaround in the tournament after poor show in the early stages as they ended up second in the points table.

Final was a crucial game and they badly missed the services of the all-rounder. Had Stokes been part of Pune's Playing XI, things could have been different for them.

He would have contributed with the ball in the first innings -- as Pune felt a bowler short when Krunal was batting -- and his explosive batting in the middle overs would have reduced the asking rate for his team.

Pune lost the match due to their slow batting in the middle overs as none of their batsmen managed to hit big shots in between 10-16 overs and that proved fatal.

Pune missed the services of another seasoned campaigner in Imran Tahir who was very crucial for the team's success in the league stage.

2. Krunal Pandya's all-round show

2. Krunal Pandya's all-round show

The young Mumbai Indians batsman scored 47 off 38 deliveries to take his team to at least a fighting total.

At one stage Mumbai were struggling at 79/7, but Pandya's aggressive batting mixed with caution helped Mumbai put up a target of 130 for Pune to chase on a wicket that was getting slow.

Pandya's batting exploits in the final overs took the momentum in Mumbai's favour.

The left-arm spinner then opened the bowling for Mumbai, when Pune came out to chase. Pandya finished his quota of 4 overs by conceding just 31 runs.

Disciplined bowling by Pandya in the powerplay overs helped his team keep things tight for Pune and other bowlers capitalised upon it.

3. Poor start from Pune

3. Poor start from Pune

Pune didn't get to off a good start in the powerplay overs. Chasing a low total has always been tricky and a good start could have laid the foundation of an easy run chase.

But openers Rahul Tripathi and Ajinkya Rahane couldn't provide the best of starts to their team.

Tripathi's dismissal in the 3rd over by Bumrah gave Mumbai the advantage.

Rahane is known for building his innings with singles and twos and he did just that, but there wasn't a person on the other end to take a few calculated risks.

4. Promoting MS Dhoni over Manoj Tiwary

4. Promoting MS Dhoni over Manoj Tiwary

Pune's decision of promoting MS Dhoni over Manoj Tiwary backfired. Everyone knows Dhoni takes few deliveries to get into his grooves but by the time he walked in to bat, the asking rate was already high.

Team should have sent someone like Manoj Tiwary at number 4 after Rahane's dismissal in the 13th over. Tiwary, who had a decent strike rate this season, could have played aggressively and brought the asking rate down. Even if he was dismissed early, Pune wouldn't have been affected much because MS Dhoni was the next man in.

Dhoni and Smith batted very slowly in between 13th and 17th over and the required run rate kept mounting.

Finally, Dhoni's (10) wicket in the 18th over by Bumrah proved fatal for Pune.

5. Manoj Tiwary and Steve Smith's dismissal in the final over

5. Manoj Tiwary and Steve Smith's dismissal in the final over

Pune's hopes of winning the game were dashed when they lost the wickets of Manoj Tiwary and skipper Steve Smith in the final over bowled by former Australia seamer Mitchell Johnson.

Pune required 11 off the last six deliveries and the boundary from Tiwary made the contest exciting. But Tiwary was removed by a brilliant catch by Pollard in the deep on the very next ball.

Smith too was dismissed by a brilliant catch by Ambati Rayudu on the very next delivery to make the matters worse for his team.

Finally, both the batsmen Dan Christian and Washington Sundar couldn't outclass the experience of Johnson who kept his nerves intact and ensured Mumbai won the game by a margin of just 1 run.

All images taken from IPL Official Site.

OneIndia News

Story first published: Thursday, August 3, 2017, 7:50 [IST]
Other articles published on Aug 3, 2017
Gender
Select your Gender
  • Male
  • Female
  • Others
Age
Select your Age Range
  • Under 18
  • 18 to 25
  • 26 to 35
  • 36 to 45
  • 45 to 55
  • 55+