Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Development/Configuration projects. (i.e., not facilities, hardware rollout, VOIP, etc.)
  2. "Project Complexity" is not an effective measure of project cost.
  3. Software development process exists; i.e., this complexity study falls within any project development life cycle.
  4. The task is not the role. Roles may be served by the same person, or several different people.
  5. Everyone owns the product. The common goal is the client-identified benefit to completing the task.

hypothesis: project complexity increases the need for task GRANULARITY. task number and granularity leads to headcount. which eventually leads to defined roles.

Factors which increase project complexity

...