Evaluating the Organization
Your project team might be a small group of software coders led by a single project manager or a large organization with a project management office, a quality team, a systems team and various other support areas. Regardless of the team, there may come a day when you (or your management) feels like the organization needs to be updated, reviewed or enhanced in some manner.
It is important to not make changes based on a knee-jerk reaction to something that happened. Instead, the organization should be evaluated and then changes made if they are needed. The evaluation of the organization is key to ensuring that the changes made do not backfire and have a negative impact on the work. If decisions are made quickly without access to all the facts, then that can often hurt the overall organization.
The first step is to define the organization as it exists right now; this establishes the baseline before any changes are made. Just as a project schedule has baseline dates that are not changed during project execution, the organization should have a baseline definition so that everyone understands how the organization is currently operated.
While this may already exist in the form of a staffing management plan or similar document, there are many organizations that do not have that formal definition. It is also a good idea to review the document and ensure that it is
Please log in or sign up below to read the rest of the article.