2014 Fantasy Football Profile: RB Shonn Greene
Although he has produced two solid fantasy football seasons, Shonn Greene has yet to meet the expectations that have been placed upon him by the fantasy football community. With Chris Johnson gone, Greene once again has a chance to step up and lead the rushing attack for the Tennessee Titans. With a flashy new rookie back on the team, however, the expectations for a productive fantasy season from Greene are very low.
While Greene was viewed as a disappointment by most during his time with the New York Jets, he was still a productive option if you drafted him in the right round. The former running back for the Jets had two seasons of over 1,000 yards rushing, and Greene scored 18 rushing touchdowns during his time in New York. At 5-foot-11, 233 pounds, the bruiser would handle the ball when near the endzone. The Titans lack depth at the running back position, so Greene should be lined up for a decent workload.
Greene is recovering from knee surgeries that hobbled him in 2013, and the fact that he will be turning 29 in August does not bode well for fantasy owners. Greene has also never been a fixture in the receiving game, and the Titans will look for ways to implement the dual-threat ability of Dexter McCluster. The Titans also did not blindly draft second-round pick Bishop Sankey, and a committee approach is going to limit Greene’s value.
It is hard to predict what you will get out of Greene. He probably isn’t going to take over the rushing attack, but he is a cheap pick that could surprise you. His value will most likely come from finding the endzone in short yardage situations, but that means his production could almost be entirely based off of his rushing touchdowns. Greene isn’t a hot commodity though, and he will be widely available on the waiver wire at the end of your draft.
Bye Week: 9
Projected Round: Last
Auction Value: $1(fftoolbox.com)
Fantasy Football 2015 Buy or Sell: DeAndre Hopkins
Should you buy stock in DeAndre Hopkins in fantasy football this season? Here's my take. Read More