KAPIL DEV
Reasons for selection:
- Kapil Dev wasn't the most skilled among the four golden all-rounders of the 80s, but he is without any doubt the most natural choice for a t20 match due to his playing style.
- Dev's numbers in ODIs are ruined partly by him playing past his peak, particularly with the bat. At his peak throughout the 80s however, Dev had an average of nearly 27 with the bat and a mind-boggling strike rate of almost 102. These numbers are good enough for a handy all-rounder who could bowl a bit to merit selection in the modern ODI lineup of most teams. When you consider that he was also the best bowler in his side for a large portion of his career, the decision becomes a no-brainer.
- One of the fittest and most disciplined players to have ever graced the game, Dev never missed out on a game due to injury. Gavaskar also remarked that he had never seen Dev bowl a single no-ball in practice sessions either in addition to official games, a sign of how disciplined he was with the ball. In addition, he was an excellent outfielder. Who could forget his outstanding catch running backwards to dismiss Viv himself in the '83 finals?
- He was once dropped by Gavaskar for a test due to his reckless batting in the previous game. While frowned upon the longer format, this style of play will be warmly embraced in the t20s of today where dot balls are a sin. 10% of his runs in ODIs came via sixes, another sign of how destructive he was.
- The greatest pace bowler in Indian test history without any doubt, Kapil was also once the highest wicket taker in test history. His outswingers were some of the most deadly in his times and his record is even more outstanding for a player who bowled mostly on Indian pitches. He also had a handy yorker which he used to maximum effect in ODIs.
- Kapil Dev's bowling career can be split into two phases. In phase one, he was one of the best strike bowlers in the world, picking 250 test wickets in just five years up until his knee surgery in 1984. After that however, he lost some of his pace and instead opted to become more accurate, leading to him exchanging strike rate for economy. This also coincided with his shift from purely relying on outswinging deliveries to developing more varieties such as the inswinger too. All of these are things that hold in him good stead to bowl in a t20, where accuracy and variety are essential to thrive.
- Most importantly, he was the man who led India to one of the biggest sporting upsets in history, winning the World Cup in '83 and the World Series in '85. He was also a man for the big occasions, proven by his outstanding numbers with the ball versus one of the strongest sides in history. His 175* also stands as one of the greatest ODI innings ever particularly with context and who can forget him smashing four sixes in a row to avoid the follow-on with a number 11 at the other end who was dismissed the very next over? As an Indian, Kapil is one of the sporting heroes who you've always seen as a larger than life person and you're almost obliged to pick him if he's available.
The natural and obvious comparison would be with Hardik Pandya, another quick all-rounder who hits hard from India and it makes sense when you consider batting alone. However, Kapil Dev was more of a swing bowler who bowled with the new ball in comparison with Pandya who relies a lot more on cutters and bouncers along with raw pace. Bhuvi is a lot more similar to him with the ball, as he has a good yorker and a bag of tricks up his sleeve too.
Role in the team:
His ability to swing the ball naturally means he should bowl as many overs with the new ball as possible. In addition, he is a very economical bowler and can keep things tight during the powerplay. 3 overs during the powerplay would be the ideal way to use him, with the final one for the death or middle overs depending on the game situation. With the bat, he will be the primary finisher and should be promoted quite often in most games to provide a late flourish. The ideal time to send him in would be around the 13-14 over mark if the run rate needs a boost.
1.
2.
3.
4.
5.
6.
7. K. Dev
8.
9.
10.
11. J. Garner