The Ashes 2013: 4 Selection Issues Australia Must Consider Before Fifth Test

What Australia once termed "rotation policy" they now refer to as "oops, our players aren't that good." With nothing left but pride to play for in the final Test at The Oval, the visitors have a few things to consider. 

Their batting has been porcelain, and their bowlers have paid the price. Although there have been glimmers of hope in the last two Tests, the Aussies still haven't quite gotten the combinations right. There is one tour match left for the brain trust to get a feel of what should and shouldn't be. Darren Lehmann has already said that careers are on the line.

Who should get the chop, then?

Should Shane Watson Stay or Should He Go?

In 45 Tests, Shane Watson has managed just two hundreds. His efforts with the bat in this Ashes series have been unimpressive. Despite a good stint at No. 6 at Chester-le-Street, where he scored 68, it didn't take long for his issue with getting out leg-before to return.

Watson's effort with the ball is what has really been impressive. He has been superbly economical and has kept the pressure on batsmen when Australia have had almost nothing to bowl at. He looked slightly injured at Chester-le-Street, though. With bowling not really being the biggest problem for Oz, why not strengthen the batting?

Ed Cowan, Matthew Wade and Phil Hughes are all contenders to slot into the No. 6 spot. While Phil Hughes has looked dubious against spinners, perhaps he should be given another try. Besides, what have Australia got to lose other than pride? 

Should Mitchell Starc Come Back for Jackson Bird?

After taking three wickets and scoring an unbeaten 66 in Manchester, Mitchell Starc got the chop for Durham. His lengths have been somewhat wayward, and he's not exactly been a poster boy for the spearhead of an attack, but to drop Starc was perhaps a bit harsh.

Hindsight is a wonderful thing, and, if the selectors look back now, they would never have picked Jackson Bird ahead of Starc. Should Starc return for the Test at The Oval? That's something the selectors should ponder. If Shane Watson misses out—be that through logic or injury—Australia will be a bowler short, and whoever leads the attack will have an extra workload thrown at them.

Who'd want to be a selector?   

What of Usman Khawaja?

Usman Khawaja, like almost every other Australian player, is having a nightmare tour.  So nightmare-ish, in fact, that The Telegraph decided to refer to it as an "Asian immigration experiment." Oops.

"

Telegraph deleted the comments about Khawaja. If you missed it, I had a hard copy. It was definitely said: pic.twitter.com/amYLQCmnk8

— Jack Mendel (@JackMendel4) August 13, 2013"

That's obviously not what it is. However, once again, everything centres around Shane Watson's inclusion. If Watson is dropped, is it really worth making yet another change to the already struggling batting lineup? Ed Cowan is the best choice at No. 3 after Khawaja, but how many changes to a batting lineup is good for harmony? 

Will Woe Betide Nathan Lyon Once Again?

We've picked out a somewhat unrelated video for you, just to lighten the mood a bit. It does feature a selection issue in question, though.

Nathan Lyon seems to get dropped whenever he takes wickets. He took seven sticks in Durham, and all logic suggests that should be enough to keep him in the side, especially on an Oval track likely to turn.

History suggests he might not make it, though.

However, it all comes back to Shane Watson once more. If he misses out, Australia might consider bringing in an extra spinner in Ashton Agar. While the youngster looked innocuous with the ball at times, he does offer something with the bat. The Oval pitch will be dry and dull and have a little something in it for the spinners.

As long as there are no repeats of what happened in the video above.