We’ve all been there: You hold a guy on your roster week after week, watching precious free agents land on other teams.
You keep waiting for your player to break out.
Maybe you think he’s got too much talent and potential, or maybe you think he’s just had a tough schedule.
Regardless of whether any of these things are true, the fact is sometimes we keep bad fantasy football players for way too long.
By the time you realize they’re not going to produce for your team, it may be way too late. You could end up out of playoff contention and your season could be over.
It’s underperforming players like these, serious injuries and negative off-the-field incidents that can drag a fantasy team down. That’s why the Bruno Boys will be with you all season long to give you advice on the players to cut and the players you might want to start thinking about letting go.
Week One shed some light on players that were expected to do well and also on some players that weren’t.
With Week Two nearing its end, it’s important to remember that the season has just begun. Unless an injury has knocked out a player for a significant amount of time or you have much better options on your waiver wire, the Bruno Boys advice is to give players with upside a little more time to prove themselves before you cut them loose.
That being said, here are some guys that you should monitor closely going into week three.
Note: While you are watching to see if these players can redeem themselves, you should be checking out the Bruno Boys’ article, Fantasy Football Week Three Waiver Wire: Pick Them Up so you can start planning on whom to pick up to replace them. And, remember you can always visit our forums to get your questions answered about waiver-wire candidates, players to drop or anything at all related to fantasy football.
QUARTERBACKS—CUT THEM LOOSE
Jake Delhomme (Carolina Panthers)
No, Jake Delhomme did not throw five interceptions again in Week Two, just one. He actually had an OK day considering his last few outings. Against the Falcons in Week Two, Delhomme completed 25 of 41 passes for 308 yards and a touchdown.
Delhomme, though, is not off the hook, especially since he still can’t go a game without throwing a pick.
However, he’s proven in the past that he can be a decent fantasy QB, so if you have the space see how he does next Monday night against the Dallas Cowboys before you make a decision to cut him.
Chad Pennington (Miami Dolphins)
Chad Pennington threw for 176 yards, a TD, and an interception against the Falcons in Week One. While he could have done worse, the Dolphins offense looked pretty rough.
As the Bruno Boys mentioned last week, there are two young QBs on the Dolphins with lots of potential who could get the nod to take over as soon as Week Five, which causes Pennington’s value to be called into question.
Wait to see if Pennington and the Dolphins can bounce back Monday night against the Indianapolis Colts.
But, if he and the offense have another bad showing, you may want to start packing his bags and start looking for other options.
JaMarcus Russell (Oakland Raiders)
This could be a make-or-break year for the disappointing JaMarcus Russell.
In Week One, he was fairly unimpressive with only one TD, 208 yards, and two interceptions.
Week Two was even worse.
Despite a win against the Kansas City Chiefs, Russell was 7-of-24 for 109 yards and no touchdowns.
Right now, it looks like Russell is far from becoming the kind of QB the Raiders envisioned when they spent the first pick on him in 2007.
If you have space, you may want to see if the Raiders’ offense starts to click, but all signs point to Russell having no business being on your roster this season, unless you are desperate.
RUNNING BACKS—CUT THEM LOOSE
Rashard Mendenhall (Pittsburgh Steelers)
After only four rushes for six yards in Week One, Mendenhall had a better performance against the Chicago Bears’ defense in week two.
However, it wasn’t good enough to keep Mendenhall out of this article. He rushed three times for 39 yards and caught one pass for 13 yards.
While Mendenhall’s performance shows flashes of the kind of talent that made him a first-round pick in 2008, the jury is still out on the second-year back.
Until the coaches show more confidence in his ability and until he sees the field more, keep him monitored week to week. You don’t want to waste a roster spot all season long waiting for him to become a consistent fantasy back if that’s a year away.
If he gets more playing time in week three against the Cincinnati Bengals, he could take his game to the next level and become a much more valuable player to have in your lineup.
Justin Fargas (Oakland Raiders)
Justin Fargas didn’t see the field again in Week Two while Darren McFadden and Michael Bush had fairly unimpressive games.
If Fargas returns in Week Three and outperforms the other two backs, you’ll want to keep him as a third-option running back, but chances are with Bush and McFadden hogging the carries, Fargas may not be worth a spot.
Still, it’s not inconceivable that Fargas becomes the most consistent back, so wait a few weeks before you cut him.
Laurence Maroney (New England Patriots)
After being one of last season’s biggest busts, Laurence Maroney is out to prove 2008 was a fluke.
Unfortunately, his last two games have not been very convincing. In Week One against Buffalo, he only rushed for 32 yards, and this Sunday against the Jets, the Patriots only ran Maroney six times for 23 yards.
Maroney has a lot of upside if he could somehow return to the kind of fantasy back he was in 2007. Problem is the Patriots just don’t look the same, and Belichick may have totally lost confidence in Maroney.
He could still end up putting up good numbers, so give him a little wiggle room as the Patriots try to rediscover their offense. But in a few weeks, if he lacks of chances and poor play continues, he may have overstayed his welcome on your roster.
LaDainian Tomlinson (San Diego Chargers)
Putting Tomlinson on this list a few years ago would have warranted a trip to the padded room.
Heck, some fantasy owners will still think it’s sacreligious to have his name and the word “cut” mentioned together.
The truth is that things have changed. Even if Tomlinson went in the first round of many drafts, injuries could be a telling sign that the era of LT is officially over.
Tomlinson had 55 yards and a TD in Week One but was taken out of the game with an injury, which in turn kept him out of Week Two against the Ravens.
Let’s be completely clear; it isn't over 'til the 300-pound linebacker sings.
You should not drop LT from your team...yet.
He is 30 years old, and if these injuries continue, he may end up being a liability come midseason. Let’s hope this is the last you see of LT in this article, but watch his injury reports and keep an eye on his performance once he returns.
WIDE RECEIVERS—CUT THEM LOOSE
Michael Crabtree (San Francisco 49ers???)
In case you decided to use a flier on Michael Crabtree because of his tremendous upside, it’s time to cut him loose.
With no contract and no time spent with the team practicing or learning the offense, it’s safe to say that Crabtree’s sleeper status looks more like a coma at this point.
Drop him and pick up a better option, like a player who may actually see the field in 2009.
Anthony Gonzalez (Indianapolis Colts)
Reports are saying that Colts wide receiver Anthony Gonzalez will be out for at least eight weeks with a strained PCL. Gonzalez was expected to have a breakout season in 2009, and his injury sure puts a damper on a lot of fantasy owners' plans.
If you have space on your roster to keep him, he may be a great asset to have during the second half of the season.
However, even if he doesn’t require surgery, who knows how many games it will take him to get back into true playing form? After all, he was injured in Week One. If you have other options or need the space, you could make a case for dropping him.
Don’t be surprised if someone snags him up for the latter part of the season.
Hakeem Nicks (New York Giants)
Giants receiver Hakeem Nicks will be sidelined for at least two weeks with a sprained foot. Coach Tom Coughlin said that two weeks was the minimal time, so the best case scenario is Week Three or Four, but it’s very likely that Nicks could be out longer.
Nicks was already a little questionable considering he’s a first-year receiver, despite high expectations from the team and its fans.
Monitor his injury, but, as of now, it looks like Nicks won’t be worth holding on to for this season unless he returns early on.
TIGHT ENDS—CUT THEM LOOSE
Anthony Fasano (Miami Dolphins)
The 'Fins expect big things from Fasano this season, but he definitely did not deliver last week against the Falcons. Fasano was kept to only two catches for 10 yards and fumbled twice.
Like Pennington, Fasano is victim to a subpar offense.
There is no question that Fasano can be productive this year, so give him a few more weeks to redeem himself from his ugly Week One performance. If Miami continues along the underachieving path, though, replace him.
Randy McMichael (St. Louis Rams)
Randy McMichael had a decent Week One considering the Rams offense looked dreadful. In Week Two against Washington, he caught only two passes for 14 yards.
McMichael will have good games and bad games.
The only reason he’s in this article is because of the bad offense he currently plays on.
See how the Rams progress over the next few weeks, if they do at all. If you have better tight end options on the waiver wire, though, don’t wait for McMichael to become a consistent fantasy tight end because you could be waiting a very long time.
For more fantasy football insight and advice, click the link below...
*THIS ARTICLE WRITTEN BY BRUNO BOY DOMINIC BROWN*