Link to the complete presentation is here

Agile is usually amended to suit the exact use case in question.  Some Agile projects will fail due to a lack of training and automation; changes requirements; poor code and documentation; a dedication to purity of Agile theory as opposed to results and ensuring project success.

The linked presentation covers the key aspects of Agile, Scrum, Scrumban and conforming Agile methods to real world use cases.

It outlines how to organize and deploy an Agile project to ensure success.

Automation within Agile is central, and the use of proper tools mandatory.

===

Defining Agile

“Relating to or denoting a method of project management, used especially for software development, that is characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans.” (Agile Manifesto 2001)

•Agile entails:  Automation, Tool usage, Integrated testing, Flexibility, Collaborative culture, Improved Quality, Small teams collaborating

 

What is Scrum?

•Scrum is an Agile software development framework. Work is structured in cycles of work called sprints, iterations of work that are typically two to four weeks in duration.

•During each sprint, teams pull from a prioritized list of customer requirements, called user stories, so that the features that are  developed first are of the highest value to the customer.
•At the end of each sprint, a potentially shippable product is  delivered.

 

Full presentation link is here