DrupalCon Dublin 2016: Choosing The "Right Agile Methodology" for Your Drupal Projects
If Agile is an umbrella of methodologies, which one should you pick? The Agile Manifesto says that: individuals and interactions come before processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
But while every Agile methodology follows iterative and incremental delivery, the execution processes and artifacts produced are very different.
What You’ll Learn
This session will explore and compare different Agile methodologies and share tips on how to choose the right one so you can accelerate your Drupal project. In the process, we will also discuss effective use of CYNEFIN (a popular decision making framework) to differentiate between Drupal projects and picking right agile methodologies for the same. Each insight will be backed by clear, real world examples from our projects. We’ll cover:
Scrum
Extreme Programming
Feature Driven Development
Scrumban
Kanban
Lean Development
You’ll walk away with
A clearer idea of which methodology is right for each project, with project size, team size, iteration length, roles and responsibilities, distributed team support, risk mitigation level, customer interaction, taken into consideration.
But while every Agile methodology follows iterative and incremental delivery, the execution processes and artifacts produced are very different.
What You’ll Learn
This session will explore and compare different Agile methodologies and share tips on how to choose the right one so you can accelerate your Drupal project. In the process, we will also discuss effective use of CYNEFIN (a popular decision making framework) to differentiate between Drupal projects and picking right agile methodologies for the same. Each insight will be backed by clear, real world examples from our projects. We’ll cover:
Scrum
Extreme Programming
Feature Driven Development
Scrumban
Kanban
Lean Development
You’ll walk away with
A clearer idea of which methodology is right for each project, with project size, team size, iteration length, roles and responsibilities, distributed team support, risk mitigation level, customer interaction, taken into consideration.