From Iteration#1 to Iteration#5, our focus was on predictive project management. We learned how to initiate, plan, execute, monitor & control and close a project professionally. This knowledge is very much applicable for projects where scope of the project is fixed, technology is well known and the owner wants to see the fully completed product of the project at the end. Most of the infrastructure projects like a new airport , metro etc falls into this category. All projects or all phases of every project do not fall into this category. For example, development of a new product calls for a totally new approach as the scope is continuously evolving, technology is new, and the key stakeholders wants to see the product of the project frequently to provide additional inputs. Even within an infrastructure project, during the initial phases of the project like the architecture, structure and the engineering calls for frequent changes. These kind of projects demand a highly collaborative, iterative and incremental mode of working. Agile project management provides the model, methods and artifacts to manage these kind of projects or phases. The iterations 6,7 and 8 focuses on the Values, Model, Methods and artifacts of agile project management and the tailoring options which will help both agile and predictive models, methods and artifacts to co-exist and compliment each other as hybrid project management. With this as the context let us get into Iteration#6.
Iteration#6 – Agile Project Management
- What is agile?
- When to go for agile project management?
- Agile principles
- Servant leadership
- Agile chartering
- Roles and responsibilities of the Product Owner
- Roles and responsibilities of the Iteration Manager (Scrum master)
- Roles and responsibilities of the Self organizing team (Development team)
- Quick introduction Scrum, the most popular among the agile frameworks