Better or Worse? | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Executive
Resources
|
Home > Departments > Methods & Means
When confronted with difficult choices in today’s complex project environments, project managers and teams need techniques to extricate them from the proverbial rock and hard place. A simple binary decision-making model, based on weighted criteria, might do the trick.
Once a year I visit my optometrist. To determine if I need a new prescription, he rotates through a succession of magnifying lenses and asks me the question, “better or worse?” When I compare this simple, effective decision-making process to the complex and onerous processes that IT project teams experience, I am envious.
Today’s project environments are often comprised of multiple technical and application architectures, cross-functional teams, internal and external resources, different time zones and cultures, and complex interdependencies among projects. Making decisions in these environments is not easy.
If you occasionally hear the expression, “we are caught between a rock and a hard place,” then your project teams may be challenged by the decision making process. Here are some sample issues that would lead a project team to that awkward state:
1. The architecture office has advised that .NET C# is the strategic development language.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement