This page contains posts by Jayme related to using methods for development that adapt to changes, grounded in the principles of agile manifesto. Agile development methods embrace change by assuming it will happen. These processes have low friction when accommodating a change.
Agile development doesn’t force a team to use a single approach for developing software throughout the lifetime of its development. It encourages changing any aspect of the process whenever necessary.
Agile development does not prescribe a single specific process like SCRUM or Kanban that must be used. It also does not necessitate the use of a “burn down” chart, stand-up meetings, DevOps, or Continuous Delivery. These are all processes that can significantly contribute to the agility of a team that delivers software, however.
Though the movement for agile development began officially in 2001 – it is still a valuable and popular topic today. It continues to evolve as additional processes and tools emerge that push teams towards greater agility.