Advertisement

Twitter baffled with Mohammed Shami not being picked against New Zealand

Shami has picked 14 wickets in four matches so far.

Mohammed Shami
Mohammed Shami. (Photo Source: Twitter)

New Zealand won an all-important toss against India in the first semi-final of the 2019 World Cup and opted to bat first. They brought back their warhorse Lockie Ferguson at Tim Southee’s expense for the crunch game. India, however, took a brave call of not including Mohammed Shami in the playing XI who was ‘rested’ for the Sri Lanka clash. It has also left the Twitterati including some of the cricket experts baffled and the pacer’s exclusion is being questioned.

Mohammed Shami has been a wicket-taking option in the mega event for the Men in Blue. He came into the playing XI after Bhuvneshwar Kumar got injured and set the stage on fire straight away. The Bengal pacer stunned Afghanistan by picking a hat-trick against Afghanistan in a thrilling game and has so far picked 14 wickets in just four outings.

Advertisement

Bhuvneshwar Kumar, on the other hand, looked off-colour after returning from the injury and endured his worst game against Sri Lanka. Many thought Shami should return for the knockout but Virat Kohli has kept faith in Bhuvi and it remains to be seen if the move will pay off.

A probable reason for Shami not playing

Mohammed Shami has not been clinical in the death overs in the tournament so far and that might have played a role in his exclusion. He had conceded 44 runs in his last three overs against England and also failed to nail his yorkers in the next game against Bangladesh.

Bhuvi, on the flip side, has not conceded more than eight runs per over in the last 10 overs so far in this World Cup. Also, his ability to swing the new ball under grey skies might have prompted the Indian team management to go with the pacer ahead of Mohammed Shami.

Only time will tell now if the decision was good enough and if, India, unfortunately, go on to lose the semi-final, leaving out Shami could turn out to be a big issue.

Here’s how Twitter reacted:

Advertisement