Scrum, Kanban, Scrumban and Banjos
While at one time the project manager had to choose between traditional and agile project approaches, that is no longer the case. Should a PM choose an agile project direction, they now have an additional choice to make; what kind of agile project approach should be taken?
This presentation will take a look at the roads the PM can take when deciding to manage a project using agile methods. While specifically looking at Scrum and Kanban approaches, the pros and cons of agile approaches within an organizational context will be explored.
Projects differ, and so do the organizations that sponsor them. To successfully set up, staff, and manage a project using agile methods (without sounding like you are simply playing a musical instrument in the corner for no apparent reason!) you need to understand a number of things about your project and your organization. These include:
- the staff that can be made available for the project; especially their skills and breadth of knowledge;
- the priority of the project being delivered using agile methods;
- the breadth of organizational change the project will create;
- the degree of “operational responsibilities” each of the key team members will retain, especially from those who report to the product owner;
- the degree of portfolio management that exists in the organization and how portfolio conflicts are managed; and
- the overall degree of agile acceptance from your management team, and the degree of agile experience present within your team
All of these factors will be discussed in this energetic and relevant presentation.
PMI Talent Triangle Skill: Leadership