Fantasy Football Week 2: Who to Start and Sit
Happy Sunday, everyone! Following the college football action, I know a lot of you are looking forward to the full slate of action in Week 2 of the NFL season.
If you were like me and played both Brandon Marshall and Matt Forte, you probably aren't enjoying it yet, but don't fret! There's plenty of football action left this week, and a good strategy can help you catch up at a moment's notice.
So here's a list of players you should start/sit, and I wish for my advice to help you to a win—unless you are playing against someone else who is taking my advice; then I wish for a tie.
As a reminder, I'm not going to point out the obvious and tell you to play Tom Brady. You know you should do that.
Robert Griffin III, Redskins
It couldn't possibly be better than last week, could it?
Well, probably not.
But even he just takes a small step back from his debut, you'll have yourself a fine fantasy quarterback.
This is the Rams, after all. Even though they held Matthew Stafford to some ugly numbers in the first half, they finally got worked in the second to help Stafford rebound to a respectable fantasy day.
Consider the fact that down the road, Griffin is going to run into the end zone a few times, and a one-yard touchdown scamper is worth as much as a 60-yard touchdown pass. So even if Pierre Garcon doesn't get the 88-yard dash to pay dirt again this week, I feel that we'll see Griffin make up for that with his legs.
Matt Cassel, Chiefs
No, I haven't lost my mind—don't worry. I know the Chiefs quarterback was a couple (several hundred) notches below stellar in Week 1 against Atlanta, but they play the Buffalo Bills in Week 2.
These are the same Buffalo Bills that made people forget who Tim Tebow was when they let Mark Sanchez toss the ball all over the field in the opener. Cassel and Sanchez are about on par with one another, and Cassel has about the same to work with in the receiving corps.
Expect similar numbers, as I project Cassel to be around 18 for those of you that use standard scoring.
Michael Vick, Eagles
Did you see how awful Vick was in Week 1? Yeah, that was against the impenetrable Cleveland Browns defense. This week, the Eagles say hello to the Baltimore Ravens.
If that doesn't scream matchup nightmare, I'm not quite sure what would. I don't think he's good for more than a handful of points this week, and that's assuming he makes it out of the first quarter uninjured.
Ben Roethlisberger, Steelers
By no means am I saying that Big Ben will have an awful game, but against the Jets in Week 2, this looks to be a boring game with a minimal number of points. In fantasy football, it doesn't matter if your quarterback is efficient; he needs points.
Even with the absence of Darrelle Revis, I expect a tough day fantasy-wise for Roethlisberger, who has a lot of trouble putting up big numbers in these kinds of knock-down, drag-out games.
Stevan Ridley, Patriots
The safe assumption here is that New England is going to beat Arizona on Sunday. The general consensus also says it will be up by a lot of points. At some point, New England will likely stop airing it out (but with Bill Belichick you never know).
Ridley had a big fantasy game last week, and although he may not get into the end zone for a second straight week, he's definitely worth starting.
Alfred Morris, Redskins
You'll probably notice that I'm a Redskins featured columnist and think I'm a homer. I'm not going to confirm or deny that, but you have to ride the hot hand for as long as you can. This week, it's still the running back I refer to as "Tickle Me Al-Mo."
I made that up; please don't steal it.
I'm thinking of a nice scenario where both Morris and Griffin have huge games (again) for the Redskins against St. Louis, and you can't go wrong after watching Stafford and Kevin Smith last week in the second half for Detroit.
Chances are Morris won't be the starter for every game, but right now he is getting just about every carry and is becoming as close to a feature back as there is in this league.
Chris Johnson, Titans
Just end it right now. He blew up for your fantasy team when he ran for over 2,000 yards in 2009, and you've probably had him each season since. It just gets worse and worse.
Not only should you bench him, but you should try to trade him while he has that 2K memory still somewhat fresh in your league-mates' heads and you can get a backup tight end for him.
Shonn Greene, Jets
As I stated earlier, it looks like the Jets-Steelers game will be a low-scoring brawl. Roethlisberger was the first victim in the list due to this game, and Greene will be the other big one.
He had a nice opener against Buffalo, but against a much tougher Steelers defense, the sledding gets much tougher. He'll be a tweener with about seven fantasy points, and there are much better options out there this week.
Reggie Wayne, Colts
It's only been one week, but there's no argument about who Andrew Luck's favorite target is. Wayne had the NFL's most receiving yards in the first week with 135. He didn't get into the end zone, but there is plenty of time for that.
Get him in a trade while you can, because it looks like Luck will be riding the Wayne train for the last 15 games of the season.
Lance Moore, Saints
Moore had a huge second half for the Saints last week and racked up a total of 18 points (120 yards, one touchdown). If Marques Colston's struggles continue, then Moore emerges as the top target after Jimmy Graham.
He may still be available on your free-agency list, and if you did pick him up, he would be worth a start against Carolina. The Saints will throw the ball about 650 times, and a few of those targets have to go to Moore.
Did you draft Eric Decker?
DeSean Jackson, Eagles
As the old saying goes, "If the quarterback is in the Sit 'Em section, then his No. 1 target should be too." Maybe that wasn't the case for Antonio Brown or Mike Wallace, but chances are Jackson was taken to be a WR1 in your league.
It will be hard to get the deep receptions he's known for against the stingy Baltimore defense, and for that reason alone, don't bother watching the whole game and waiting for that big play to come. It never will.
Eric Decker, Broncos
Whenever you try to guess which person Peyton Manning will favor the most anytime a new season starts, it's never the person you think.
A lot of people hopped on the Decker bandwagon assuming that Manning would pump the ball his direction repeatedly. Here are better Broncos options for you: Demaryius Thomas, Brandon Stokley, Jacob Tamme. Go another direction.
Jacob Tamme, Broncos
Well, speak of the devil. As I noted here, Jacob Tamme is the biggest sleeper that the Broncos have this season. After getting a touchdown to start the 2012 campaign, it looks like he will be the go-to guy in the red zone for Manning.
And you thought Eric Decker would be the man—shame on you.
Kyle Rudolph, Vikings
Rudolph the red-nosed tight end probably isn't going to set records this year for Minnesota, but it can't hurt to have a tight end who has the ball thrown to him once in a while.
This week, the Vikings play the Colts in the "Game of the Week," and he should be good for 60-70 yards. Add in a touchdown, and you have yourself a great fantasy day for any tight end.
Fred Davis, Redskins
Hopefully this will bring me back some credibility after telling you to start two Redskins. Unfortunately, it doesn't look like Davis is going to be a big part of the future in the RG3 era. He will certainly be a part of it—just not someone you can depend on to put up big fantasy numbers.
If you're stretched thin on tight ends and Davis is the only option you have, then start him, but there's nothing here that tells me he will have a big week.
Brent Celek, Eagles
See: Ravens defense.
Well, that wasn't so bad, now was it? Hopefully we've all learned lessons here today and from Week 1. If you lost, don't panic; if you won, don't gloat too much.
I wish you the best of luck in your contest, and if everything went well with these picks, I will see you here next week!
What is the duplicate article?
Why is this article offensive?
Where is this article plagiarized from?
Why is this article poorly edited?