<img class="gwt-Image" src="/photo/38596681.cms" /> 
 As the whole <keyword id="1521" type="CITY" weightage="100" keywordseo="Cricket">cricket</keyword>ing world waits for the final judgement on James Anderson-Ravindra Jadeja case in the ongoing test series between two of the greatest cricket teams, Business Insider India gives you an insight into the Level 3 Offence, which might put Anderson under a four-test ban, if proven. 
 
Article 2 of the ICC Code of Conduct deals with the code of conduct offences committed by a player or player support personnel. 
 
Section 3 of this Article 2 mentions the Level 3 Offences, which are as follows: 
 
2.3.1 Intimidation of an umpire or a match referee whether by language or conduct (including gestures) during an international match. This includes appealing in an aggressive or threatening manner. 
 
2.3.2 Threat of assault on another player, player support personnel, or any other person (including a spectator) during an international match. 
 
If the match referee feels that a Level 3 Offence is committed in an international match, he can report the alleged offence by lodging a report with the ICC’s legal head as soon as reasonably practicable, and no later than seven days after either the offence was committed or was brought to his attention. 
 
When the charges are proven and it is the first offence committed by the person accused, the suspension can be of four to eight suspension points*, but the maximum period of suspension cannot be more than one year. 
 
If it is a second offence of the same degree, the suspension can be of eight suspension points or a period of time between the equivalent of eight suspension points and one year. In this case as well, the maximum period of suspension cannot be more than one year. 
 
If however, the offence is committed for a third time, the suspension can be between one year and lifetime. 
 
If the person accused thinks that he has been wronged, he can appeal the judgement. However, the ban would remain in effect even while under appeal, unless a properly assembled appeal panel orders otherwise. 
 
The only parties who can appeal a judgement shall be the player or player support personnel found guilty and the ICC’s chief executive officer. 
 
*Suspension Points: Two suspension points equates to either a ban of one test match or two ODIs, depending on the type of match the player is scheduled to play next. 
 
Source: <a href="http://www.cricket.or.jp/jca/data/pr05_ICC-Code-of-Conduct.pdf">Japan Cricket Association</a>

Level 3 Offences: What Exactly Do They Mean?

<img class="gwt-Image" src="/photo/39601211.cms" />Manchester: The countdown for an <keyword id="6355164" type="COMPANY" weightage="80" keywordseo="ICC">ICC</keyword> appeal against <keyword id="1035732" type="POSITION" weightage="80" keywordseo="Judicial-commissioner">judicial commissioner</keyword> Gordon Lewis' 'not-guilty' verdict on the spat between <a href="http://www.gocricket.com/player/james-anderson/3001/3040">James Anderson</a> and <a href="http://www.gocricket.com/player/ravindra-jadeja/4001/32004">Ravindra Jadeja</a> has begun. 
 
With Lewis listing the submissions and his own concerns in the case, ICC chief executive Dave Richardson has seven days to file an appeal if the world cricket body feels unhappy with the verdict. 
 The Board of Control for Cricket in India (<keyword id="6354756" type="CITY" weightage="80" keywordseo="BCCI">BCCI</keyword>) had gone straight to the ICC and pressed Level 3 charge against Anderson after the team management had insisted on it. 
 
The ICC, now headed by N Srinivasan, must quickly decide whether justice had been done in the case after Lewis let both Anderson and Jadeja off the hook. If the ICC bosses are unhappy with the verdict, they have a right to appeal. 
 
If they exercise their right to do so, a three-member appeals panel will be constituted to hear the matter afresh and Anderson will be back in the dock. He can, however, continue to play till the appeal, if filed, is disposed of. 
 Jadeja's case will not be under review even if the ICC appeals against Lewis' verdict because his part of the hearing was conducted under a different clause and on an appeal from BCCI, whereas in Anderson's case, the ICC was the <keyword id="137526" type="POSITION" weightage="80" keywordseo="prosecutor">prosecutor</keyword>. 
 
This complex situation would not have arisen had the whole issue, which is now three weeks old, had been handled more prudently by the BCCI as well as the England and Wales Cricket Board (ECB). 
 
By turning down ECB's request to tone down their charge against Anderson from Level 3 to Level 2, the BCCI not only overplayed their hand but also invited a tit-for-tat countercharge against Jadeja by the hosts. More so, because there was no clinching audio or video evidence to prove who was the guilty party in spat between the two players. 
 
With fellow players appearing as eye witnesses for either side choosing to be highly biased towards their teammates, the judicial commissioner was quick to discard their testimony. 
 
In fact there was so little evidence before Lewis that he had no choice but to let both players go. That is something Lewis has admitted to, if a report based on his leaked verdict is to be believed. 
 
What remains unexplained is Lewis' reluctance to even book the duo for breaching the ICC Code of Conduct for players. After all, the ECB had admitted that Anderson had pushed Jadeja, but had done so in self-defence after the Indian all-rounder had turned aggressively towards him. 
 
Indian captain MS Dhoni is believed to have stopped Jadeja and shepherded him back to the dressing room. Even if there was no concrete evidence of physical contact, there are enough pointers to conclude that whatever happened between the two was certainly not gentlemanly and in the spirit of the game. 
 
The ICC, in the past, has fined and punished players for lesser offences. Letting Anderson, who has never been a model cricketer, and Jadeja, who celebrated his 50 at Lord's by waving his bat like a sword, go without even a rap on their knuckles sends out a wrong signal.

ICC May Appeal Anderson Verdict

Following an embarrassing 3-1 defeat to England, Gocricket.com has the Indian players' report cards ready here. 
 
<a href="http://www.gocricket.com/player/shikhar-dhawan/4001/28004">Shikhar Dhawan</a>: 5/10 
 Dhawan was India's highest run-scorer in the two-Test series against New Zealand with 215 from four innings. However, the Delhi batsman couldn't create the same impact against England: he managed 122 runs at an average of 20 with a highest of 37. His technical flaws were widely exposed by <keyword id="80896" type="PERSON" weightage="20" keywordseo="James-Anderson">James Anderson</keyword>, who gave Dhawan a tough time outside the offstump. While he looked good in patches during his innings of 29 at Trent Bridge, 31 at Lord's and 37 at The Ageas Bowl, he couldn't convert them into anything productive. Most of his dismissals came in the initial part of the innings which dented India's hopes of getting off to a decent start. 
 
<a href="http://www.gocricket.com/player/murali-vijay/4001/4102">Murali Vijay</a>: 7/10 
 
Dhawan's opening partner got off to a start few imagined him to. His 146 at Trent Bridge was his fourth century in Tests and first in England. He followed it up with consecutive half-centuries - 52 in the second innings and 95 at Lord's - but lost his bearings thereafter. In the next seven innings, Vijay made just 109 runs and his average - which at one point in the series touched 80 - dropped to 40.20. He wasn't troubled much at Trent Bridge and Lord's but in Southampton, Vijay was unlucky to play on and get run out. It was at Old Trafford and The Oval that he looked out of sorts, throwing his bat at away-going deliveries and flummoxed by those that darted in. A decent series all in all, but it could have been better. Considering the way his team-mates performed, Vijay was one of the few positives for India. 
 
<a href="http://www.gocricket.com/player/stuart-binny/4001/31034">Gautam Gambhir</a>: 0/10 
 
Returning after an 18-month absence, Gambhir showed so signs of improvement. He was the most unconvincing among the Indian batsmen. His replacing Dhawan for the last two Tests raised many eyebrows. He remained persistent with his tendency to poke at balls outside offstump and looked like a sitting duck in each innings. An edge to gully, a run-out and a caught behind while trying to leave the ball, such dismissals indicate that Gambhir may have played his last Test for India. 
 
<a href="http://www.gocricket.com/player/cheteshwar-pujara/4001/4106">Cheteshwar Pujara</a>: 4/10 
 
Pujara has endured one of the toughest series of his young career. He started off well with scores of 38, 55, 28 and 43 but Southampton, much like it did for India, led to his downward spiral. He had problems with the incoming delivery and even his rock-solid forward defence couldn't come to his rescue. Pujara was out caught behind on six occasions and fell prey to Moeen Ali's offspin twice. With a total of just 222 runs in 10 innings, India's No 3 looked very shaky. 
 
<a href="http://www.gocricket.com/player/virat-kohli/4001/25007">Virat Kohli</a>: 2/10 
 
The first real forgettable tour for India's most prolific batsman of the current era. The fact that Kohli couldn't score even a single half-century in 10 innings speaks volumes about his failure. With 134 runs at an average of 13.40, statistically he is India's worst batsman on tour. James Anderson had his number throughout the series, dismissing him four times. Kohli was twice out without troubling the scorers and the cobwebs in his head were clearly visible. Twice he was dismissed offering no shot - bowled by Liam Plunkett at Lord's and out lbw to Chris Jordan at The Oval. 
 
Apart from his batting, his goof-ups in the slip cordon added to Kohli's woes. A gloomy series like this can be excused, especially after the string of success he has experienced, but Kohli must realise that a major chunk of India's batting revolves around him. His getting back among the runs is crucial if India are to have any chances in Australia later this year. 
 
<a href="http://www.gocricket.com/player/ajinkya-rahane/4001/32045">Ajinkya Rahane</a>: 7/10 
 
Another example of a batsman who squandered away a decent beginning. Rahane, in only his second Test in England, registered his name on the Lord's Honours Board, courtesy a match-winning century on day one to revive India splendidly. Two fifties followed in Southampton but the promising run was brought to a halt in the last two Tests with Rahane managing 21, 4, 0 and 1. He showed a lot of promise with 299 runs at 33.22 and but the team needs more from him. 
 
<a href="http://www.gocricket.com/player/stuart-binny/4001/31034">Stuart Binny</a>: 2/10 
 
Much was said about Binny after his selection in the 18-member squad, and as it would turn out, he was another hyped-up player. His only substantial knock came at Trent Bridge - a match-saving 78 in the second innings. He played a horrible shot in the first innings at Lord's and his credentials of an allrounder also took a big blow as he struggled with the ball and went wicketless in all three Tests he got. 
 
<a href="http://www.gocricket.com/player/ms-dhoni/4001/4057">MS Dhoni</a>: Batting 7.5/10, Captaincy 5/10 
 While <keyword id="6397" type="PERSON" weightage="20" keywordseo="Dhoni">Dhoni</keyword> the batsman raised his game in England, Dhoni the captain was another major setback in away matches. With four half-centuries in five matches, the India skipper had one of his best overseas series. His 82 at Trent Bridge was followed by 50 in Southampton where his biggest slip was falling early on day four when India needed him to stay in the middle. At Old Trafford and The Oval, his innings of 71 and 82 were one of only three Indian scores in double digits as the rest of the batsmen crumbled around him. 
 Dhoni's captaincy though looked lifeless yet again. His five-bowler strategy never really came to India's aid, and the decision to ignore Ishwar Pandey raised questions. After leading India to their fifth consecutive overseas series loss, this might mark the end of the road for Dhoni the <keyword id="195040" type="POSITION" weightage="20" keywordseo="Test-captain">Test captain</keyword>. 
 
<a href="http://www.gocricket.com/player/ravindra-jadeja/4001/32004">Ravindra Jadeja</a>: 5/10 
 
Despite the fact that he and Anderson kept on getting each other out, Jadeja's only meaningful contribution came in the second Test at Lord's, where his counter-attacking fifty set the game up in favour of India. With the ball, he was inconsistent. His wickets either were down to poor shots or the need for quick runs. Ian Bell and Jos Buttler took him apart in Southampton, where he was either too short or generous down the legside. Jadeja remains a strong contender at home but a doubtful starter for away matches. 
 
<a href="http://www.gocricket.com/player/rohit-sharma/4001/4095">Rohit Sharma</a>: 1/10 
 
Our very own flat-track bully was drafted into the team at The Ageas Bowl in place of Binny and what did he do? Played a silly shot to Ali in the first innings and fell early on day five to Anderson in the second. Might be a cinch to play on Indian wickets, but his modes of dismissal are only worsening his case of playing abroad. 
 
<a href="http://www.gocricket.com/player/ravichandran-ashwin/4001/26007">Ravichandran Ashwin</a>: 6/10 
 
Ashwin managed to surprise in a role-reversal of sorts. While at Old Trafford he impressed one and all with his batting, The Oval saw Ashwin get back among the wickets. He forged a 66-run partnership with Dhoni for the seventh wicket in the fourth Test and played textbooks shots. Ashwin played second fiddle to Dhoni, who at the other end took calculated risks. Ashwin scored 46 in the second innings as India went down by an innings and 54 runs. At The Oval, Ashwin finally took his first wicket since 2012 and his 3/72 kept things tight. 
 
<a href="http://www.gocricket.com/player/bhuvneshwar-kumar/4001/25023">Bhuvneshwar Kumar</a>: 8/10 
 
The conditions in England were supposed to ideal for Bhuvneshwar's style of bowling and he proved the theory right with figures of 5/82 and 6/82 in the first two Tests. But as soon as the English batsmen came into their own, the Uttar Pradesh bowler was a tired figure out in the middle. Once the batsmen negotiated with his early movement, scoring became easy. And even though in the third and fourth Test he took 3/101 and 3/75, Bhuvneshwar lacked support at the other end. 
 
To see him bat nicely in the series was a pleasant surprise. Scores of 63, 58 and 52 in the first three innings of the series were an added bonus for the team. With 19 wickets at 26.63 and 247 runs at 27.44, Bhuvneshwar had a series to remember. 
 
<a href="http://www.gocricket.com/player/ishant-sharma/4001/4094">Ishant Sharma</a>: 7/10 
 
Ishant was supposed to spearhead the Indian attack in England and many believed that the win at Lord's - where he took a career best 7/74 - had finally established Ishant as India's premier fast bowler. But an unlikely injury after the historic triumph was a case of bad luck for India. And when Ishant came back, it was fairly evident that he wasn't the same bowler who etched his name of on the Lord's Honours Board. At The Oval, he was predictably short and Stuart Broad took the attack to him despite batting with a broken nose. Ishant looked a bit ragged in his 4/96. 
 
<a href="http://www.gocricket.com/player/varun-aaron/4001/30019">Varun Aaron: 5/10</a> 
 
The Jharkhand fast bowler made a return to Tests after December 2011 with plenty of calls for his inclusion for the fourth Test, in Ishant's absence. And even though he dismissed Ali with a peach of a delivery and broke Broad's nose, Aaron was mostly erratic, wasting energy on bowling far too many short balls. He bagged five wickets at an average of 50 - which included him conceding runs at over five an over at The Oval. But there is no doubt that he caught a few eyes with his pace. 
 
<a href="http://www.gocricket.com/player/pankaj-singh/4001/4100">Pankaj Singh</a>: 4/10 
 Known as a workhorse in domestic circuit, Pankaj bowled with a lot of heart in Southampton after getting a debut in place of an injured Ishant. He was unlucky twice after Jadeja put down <keyword id="9234" type="PERSON" weightage="20" keywordseo="Alastair-Cook">Alastair Cook</keyword> in the first session followed by an umpiring error that reprieved Bell. Pankaj finally tasted success after toiling for 47 overs in Southampton and almost 23 overs in Manchester, where he bowled bad balls too frequently and went over four an over. 
 
<a href="http://www.gocricket.com/player/mohammed-shami/4001/30030">Mohammed Shami</a>: 2/10 
 
Shami bowled with good pace in three Tests but was overall ordinary. His five wickets in the series came every 115 deliveries and at the cost of 73.20 runs. But with the next series taking place against the West Indies, he might return on the basis of what he did against them last year.

Indian Players' Report Cards After England Debacle

After the high of Lord's, the low at Southampton. Following India's 266-run defeat at Ageas Bowl on Friday, gocricket.com assesses how each of the 11 players fared. 
 
<a href="http://www.gocricket.com/player/murali-vijay/4001/4102">Murali Vijay</a> 
Vijay followed his defiant batting at Lord's - 24 and 95 - with a stumbling performance. He looked out of sorts against <a href="http://www.gocricket.com/player/james-anderson/3001/3040">James Anderson</a> on day three and perished for 34 to a moment of indecision to <a href="http://www.gocricket.com/player/stuart-broad/3001/3067">Stuart Broad</a>. Worse, though, was Vijay's lethargic run out for 12 in the second innings. After two strong games, a low can be excused to an extent. And Vijay is a batsman who finds a way out of a slump. 
 
<a href="http://www.gocricket.com/player/shikhar-dhawan/4001/28004">Shikhar Dhawan</a> 
Vijay's opening partner has looked out of sorts in England and his place in the XI is now in jeopardy ahead of the Old Trafford Test. Six innings, 122 runs, highest of 37 in the second innings at Southampton. The cracks in his technique were again exposed by Anderson in the first innings, while in the second Dhawan fell to <a href="http://www.gocricket.com/player/joe-root/3001/73004">Joe Root</a>'s part-time offspin. Looks far removed from the dasher who bullied Australia in Mohali and stood tall in New Zealand. Has Dhawan exhausted whatever faith the management has in him? 
 
<a href="http://www.gocricket.com/player/cheteshwar-pujara/4001/4106">Cheteshwar Pujara</a> 
India's No 3 had his poorest match of the series. Was tested by a fiery Anderson in the first innings where he looked uncomfortable against his bounce. Fell to a rising delivery from Broad that he failed to negotiate, and was caught behind when trying to weave out the ball's way. In the second, with India staring at a mountain, Pujara nicked off against <a href="http://www.gocricket.com/player/moeen-ali/3001/3153">Moeen Ali</a> for two. Pujara has not looked as shaky in Tests as he has in England. His rock-solid technique is being tested. 
 
<a href="http://www.gocricket.com/player/virat-kohli/4001/25007">Virat Kohli</a> 
India's superstar showed signs of shrugging off his poor form in this Test, but twice squandered starts. His dismissal to Anderson in India's first innings was an extension of a nagging problem - the corridor of uncertainty outside off stump. His dismissal to Ali's offbreaks in the second was just downright ordinary. How Kohli fares in the next two Tests could impact whether he is regarded as a truly exceptional player or just a good one. 
 
<a href="http://www.gocricket.com/player/ajinkya-rahane/4001/32045">Ajinkya Rahane</a> 
India's best batsman, with two fifties. Looked good during his first-innings 54 until he made a mess of a long hop from Ali. Batted 121 balls for 52 not out in the second, the only Indian to cross 37. Goes to Old Trafford the most confident player of the team. 
 
<a href="http://www.gocricket.com/player/rohit-sharma/4001/4095">Rohit Sharma</a> The case of India's most frustrating batsman continued. Drafted in for his first Test in England, in place of allrounder <keyword id="258548" type="PERSON" weightage="20" keywordseo="Stuart-Binny">Stuart Binny</keyword>, Rohit found himself no further fans with a silly dismissal to Ali in the first innings. Shortly before tea, Rohit dashed out and lofted to mid-off, then sunk to his knees in despair. In the second, he made six before falling early on day five, edging off Anderson. Could be swapped for Binny in a week's time. 
 
<a href="http://www.gocricket.com/player/ms-dhoni/4001/4057">MS Dhoni</a> 
His biggest lapse in this match was falling early on day four, when India needed to bat out time. On 50 overnight, and with two tailenders remaining, India's captain hooked at one from Anderson and top-edged to the wicketkeeper. He failed to add a run to his total and India's innings lasted 25 balls. Was flat in the field, letting the game slip away. As often in the past, when teams start to attack, Dhoni eases into defensive mode and this was glaring here too. Needs to shake himself and the team up. 
 
<a href="http://www.gocricket.com/player/ravindra-jadeja/4001/32004">Ravindra Jadeja</a> 
Was India's leading wicket-taker in this Test but his left-arm spin was very ordinary, and the way Bell and debutant Jos Buttler took Jadeja apart in England's first innings was striking. His wickets either owed to poor shots, wrong calls or the need for quick runs. He got Cook for 95 with a short ball down the leg side; Buttler heaved and missed when the declaration was imminent; Gary Ballance was incorrectly given out; Bell and Root both went looking for quick runs in the second innings. Jadeja conceded 205 runs in 56.2 overs (economy rate 3.65) and with the bat, made 31 and 15. Calls for R Ashwin to play in his place have grown louder. 
 
<a href="http://www.gocricket.com/player/bhuvneshwar-kumar/4001/25023">Bhuvneshwar Kumar</a> 
No doubt, his average returns had a direct link to India's loss. Struggled to show the consistency and determination of the first two Tests, taking four wickets for 160 runs and scoring 19 and 0. A failure was around the corner, and the fatigue showed on Bhuvneshwar when he walked off the field Wednesday. 
 
<a href="http://www.gocricket.com/player/mohammed-shami/4001/30030">Mohammed Shami</a> 
Turned in another poor showing, and should make way for a fresher pair of legs at Old Trafford. Cranked up some good pace on day one and did bowl some scattered short deliveries that tested England's batsmen, but overall Shami was ordinary and erratic. His five wickets in the series have come every 115 deliveries and at a cost of 73.20 each. Time to go? 
 
<a href="http://www.gocricket.com/player/pankaj-singh/4001/4100">Pankaj Singh</a> A domestic stalwart for Rajashan with 300 wickets in 77 first-class matches, Pankaj was handed a Test cap when <keyword id="11685" type="PERSON" weightage="20" keywordseo="Ishant-Sharma">Ishant Sharma</keyword> was ruled out, and finished with a record he won't want attached to his name: the most runs conceded by a debutant bowler without a wicket. However, he bowled far better than the stats suggest, particularly on day one, and should have had <a href="http://www.gocricket.com/player/alastair-cook/3001/3056">Alastair Cook</a> early as well as <a href="http://www.gocricket.com/player/ian-bell/3001/3048">Ian Bell</a>. Was the best of India's three pacers, doing whatever was asked of him, but a lack of pace and those awful figures could confine Pankaj to a solitary Test appearance.

A Report Card On India's Defeat

Mumbai: The irony can't be missed when you see <keyword id="6355478" type="COUNTRY" weightage="20" keywordseo="Australia">Australia</keyword> Tourism brand ambassador, <keyword id="13825" type="PERSON" weightage="20" keywordseo="Glenn-McGrath">Glenn McGrath</keyword>, welcoming Indian tourists Down Under to watch the <keyword id="1521" type="CITY" weightage="20" keywordseo="Cricket">cricket</keyword> action unfold later this year. As he reels off names of exotic places, the mind jogs back to the years when he made batsmen feel unwelcome in Australia with his no-holds-barred verbal volleys. 
 
It didn't end there. He translated his strong words into wickets and, along the way became one of cricket's all-time greats. "In my 14-year-career I've featured in only two series defeats and on both occasions it was against India. The one-off Test at Delhi in 1996 and the 2001 series," he says of his impeccable 124-Test career, which ended in 2006-07 with 563 victims to his name. 
 
Excerpts from an interview to TOI: 
 
Do you see this Indian team challenging Australia? 
 We've seen England dominate the last three Tests, which isn't a good sign. Indian teams have always struggled in Australia because of the extra bounce and seam movement. It has always been an issue for them, but I think the bowlers do enjoy playing in Australia. If the Australian team plays the way it did against England last year, then it will be a tough series for India considering they have a fair bit of work to do. Their fielding in England was horrendous. You can't afford to drop three or four catches every game. With <keyword id="11010" type="PERSON" weightage="20" keywordseo="Mitchell-Johnson">Mitchell Johnson</keyword> bowling at 150 (kph), and with control, India have their work cut out. Tour matches will be important for India. 
 
The Aussies love to see their team being challenged? 
 
They did enjoy Australia beating England 5-0. Yeah, they want to see challenging cricket, not one-sided affairs like it happened in England. 
 
You were never afraid to back yourself publicly... targeting the main batsman of the opposing team. Where did this confidence come from? 
 
I always had that self-belief. Growing up on a farm you are instilled with certain work ethics. When I was seven, I was working on the farm and driving tractors and cars. It gives you confidence as well. I enjoyed the challenge that is why I liked to make predictions and target batsmen. I believed I was good enough to deliver. But if they were good to beat me at my game, I could live with it. If you like to be like anyone else, you do what everyone else does. If you want to be different or better than everyone else, then you need to do something apart from them. 
 
You are one of the few fast bowlers who played 100-plus Tests. You think there'll be fewer bowlers reaching the landmark in the post T20 era? 
 
It is tough bowling day in and day out. There were few things that kept me in good stead right through my career. I didn't bowl a great deal when I was younger. I was prepared to work as hard as possible off the field and that made my life easier on it. The idea was to get fit and very strong. I could handle the rigors of fast bowling quite well. You need an off season to recharge the batteries. Probably genetics, too, played a role in my case. My bone density is very high and that helped me get through injuries. I just wanted to bowl every second over of the innings. I wanted to play every game and I never wanted to be rested. That is the attitude you've got to have. You've got to work hard off the field to get through on it. 
 
What are your views on the Anderson-Jadeja spat? 
 
I think that was a big turning point in the series. The England team steeled themselves after that. India were leading 1-0 but they got distracted. They were talking more about that than executing their on-field plans. England went from strength to strength and India went from bad to worse. You need to put these things behind when you enter the field.

You Searched For "Anderson Jadeja case" and got 5 results

Level 3 Offences: What Exactly Do They Mean?

Nandini Sharma

ICC May Appeal Anderson Verdict

gocricket staff

Indian Players' Report Cards After England Debacle

gocricket staff

A Report Card On India's Defeat

gocricket

McGrath: India Will Have Their Work Cut Out In Australia

gocricket staff