Training camp is barely a week in. And while there are a few things that could raise some eyebrows, absolutely zero stock should be put into what order the players' names are listed at this point.

Does it really matter if Brady Quinn is slated to be Matt Cassel's immediate backup ahead of Ricky Stanzi at quarterback after a few days of throwing the ball around? Is there a legitimate advantage for Kevin Boss being the No. 1 tight end over Tony Moeaki right now?

The answer is a resounding no. And to be honest, the early release of the depth chart gives no indication as to who is in position to even make the team; it is just a tool to rouse interest among fans and so-called experts to form fruitless opinions about the inner-workings of the organization that they frankly know very little about.

Is it that obvious after a mere 10 days of running around in shorts that Poe already belongs in the same breath as Ryan Sims around Kansas City? Those who hold any truth to this are very reckless with their judgment.

Conversely, doesn't it make sense to ease Poe into his role by deflecting any extra pressures he may naturally endure as a rookie that comes with high expectations?

Denny Medley-US PRESSWIRE

Just ask running back Jamaal Charles how little it means to not be named the starter.

While it is obvious that he has been the best running back on the roster since being drafted into the league in 2008, Charles has only started 19 out of a possible 49 games throughout his career—yet has been one of the most productive and explosive backs during that time when healthy.

The biggest point to quell the validity of the early depth chart is the fact that wide receiver Dwayne Bowe was even mentioned at all.

It is still way too early to get caught up with where certain players fall on the depth chart. It will steadily shake itself out and be a completed project by the time the Chiefs kick off against the Atlanta Falcons on September 9.