Project Tasks and its multiple status 101

I struggle with this approach a bit. Here's why. In my experience status is just that and is temporary, a moment in time that should be reflected on a dashboard. Where are we today? In measuring the human resource, this is a metric that should be measured outside of a status. There are numerous ways to measure quality and rework and within these activities there are specific status that provide information back to stake holders and end users. However consistent metrics reported back to the business reveal pain points that need to be addressed and improved upon, the whole reason one has metrics and it also if things are going well, drives a message to the business of the value of IT.

I don't disagree with your assessment of resource profiling.But that's not the original point is it? Your point was to measure via status. I am hard pressed to agree that you will see the issue with a status of in test that someone is a bad fit for a task because they took longer than base-lined irrespective of where they are. I disagree that status is where that is measured. This is derived from actual vs baseline not in status.

Just my two cents as well.