We’re not even into a full week of training camp and the Green Bay Packers running back situation is already looking really interesting.

Only four practices have transpired two of those padded so it’s easy to overreact to the small sampling of football we’ve seen from the players so far. So I’ll try to avoid any grand reactionary statements in this piece.

But one thing is evident so far in camp: We all wrote James Starks off way too early.

I’m definitely guilty of this. Like many other Packers bloggers beat reporters and team analysts I had Starks pegged as the odd man out at running back and being the one most likely cut by the team heading into the season.

Were we all wrong? Did we jump to conclusions too soon?
Starks was nearly a non-factor last season. Only playing six out of 18 possible games and recording an unimpressive 255 yards with an average 3.6 yards per carry. In all fairness Starks’s 2012 season was sabotaged from the beginning by a string of injuries.

Starks has dealt with injuries most of his young football career. He missed most of his rookie season in 2010 due to a serious hamstring injury suffered before camp. He broke on the scene at the end of the season that year and became a key part to the Packers playoff push to the Super Bowl posting a league-leading 315 rushing yards in the playoffs.

2011 was suppose to be the season Starks took the reins and became the Packers’ featured back and even though he led the team with 578 rushing yards he missed a significant amount of time due to an ankle injury.

This trend continued last season when Starks dealt with a severe turf toe injury that kept him out of the majority of camp and caused him to miss the beginning of the season. When Starks finally returned to the lineup and began seeing carries he suffered a serious knee injury in early December that resulted in him missing the rest of the season.