Scope Management
Agile and traditional project management use different methods to address scope management and these are,
Discovering new project requirements that are defined by the project team which can be identified at any given time. Such requirements are added by the product owner (customer) in the product backlog (user requirements). Whereas in traditional project management, the project manager is in charge of defining the requirements, once the project requirements has been defined any changes made to it during the project is considered to be negative which is referred to as scope creep. (dummies book)
Time Management
Scheduling tasks, creating the schedule and assigning work in relation to the schedule and monitoring progress against the schedule is concerned with the traditional project management. The schedule is usually created during the initial planning phase and entered into a project scheduling system when the project is predictive. While for agile the requirements are always fluctuating, it can be difficult to create and maintain a meaningful project schedule. The initial planning effort will usually include the beginning set of requirements and divide the project to iteration with a preliminary assignment of requirements to iterations.(system analysis and desing)
Cost Management
Due to the unexpected requirement changes throughout the project, it is difficult for Agile project managers to estimate the time and cost of a project therefore estimating the cost isn’t as important as controlling the cost during the life of the project.
For traditionioal????
Risk Management
Since all the tests are conducted at the end of a project in traditional project management approach, meaning that if problems are found it can affect the entire project. Where as in Agile project management, tests are conducted at every stage, if a technical approach, a