IT Project Management

Agile Project Management

Software projects may select various approaches that are fundamentally different from IT infrastructure projects. In agile software developments requirements may change dynamically in short iterative planning and execution cycles. Requirements and scope are defined and reworked throughout the project, resulting in a higher number of release versions.

Depending on the fitness of a project life cycle, four diverse approaches are available that differ in view of requirements (fixed vs. dynamic), activities (once vs. repeated), delivery (single vs. frequent), and goals (cost, quality, time, customer value).

Agile projects may include or exclude project managers

The role of the IT project manager is unclear in agile settings. Due to the self-organizing teams in agile environments, the need for project managers is not recognized. Scrum, a framework for implementing agile methods and presumably the best-known method for agile developments, does not mention project managers in its guide. The role of the “Scrum Master” is sometimes compared to the project manager. However, from the agile alliance perspective, Scrum Masters are process experts and coaches.