Adopting an Agile Approach to Project Management - Agile Project Planning

Full Course: https://www.udemy.com/adopting-an-agile-approach-to-project-management/?couponCode=PROMONOW

Traditional Project Planning
In traditional project management, a project plan is a document that helps project managers execute and control the phases of a project.
It typically defines a project's scope, cost, and schedule, as well as its activities, deliverables, milestones, and resources. Once project work starts, the aim is to follow the plan as closely as possible.
And, once a traditionally managed project is already underway, a project manager generally tries to prevent changes to the project's scope.
Agile Project Planning
If a customer asks for a new feature to be added to a product, for example, the project manager might suggest negotiating the terms of another project for releasing an updated version – rather than changing the scope of the current project.
Planning in Agile looks very different. In agile development, there's no work breakdown structure or time-phased and resource-assigned task list.
Just-in-time Planning
Instead Agile uses just-in-time planning. A project plan contains only the detail needed to get the development team started and generally maintains less details for work that's projected to take place in later iterations.
The customer, development team, and other stakeholders spend time on up-front planning, with emphasis on determining the customer's vision for a product, establishing requirements, prioritizing required features, and developing a tentative plan for what will be developed in each iteration.
Burn-down Charts
Instead of using traditional project management tools, such as Gantt charts, Agile replaces these with simpler tools like burn-down and velocity charts, which convey progress in a visual way. This ensures transparency, with all parties able to check the status of the project at any time.
Continuous Planning
In agile methodology, planning isn't a one-time, up-front activity. It's continuous. For example, you've completed the prototype of the database for the hospital. You invite a customer representative to review it before you move on to develop it.
During the presentation, your customer asks if it's possible to add a feature that would enable supervisors to approve specific entries. You realize this represents an increase in the project scope. You change the priorities of the required product features, and decide to integrate the new feature in the next iteration. (...)

Full Course: https://www.udemy.com/adopting-an-agile-approach-to-project-management/?couponCode=PROMONOW