Bummer! This is just a preview. You need to be signed in with a Treehouse account to view the entire video.
Variants of “Agile”1:46 with Matt Anthes-Washburn
Over the years, many variants of agile software development models have emerged. Each of these models have different approaches, processes, and tools.
Wikipedia: Agile Software Development—Agile Methods
Agile Methodologies for Software Development An overview of several of the most popular agile models and their distinct characteristics
Agile Alliance: Subway Map A neat “subway map” with various practices of agile and the methodologies that support them.
It's been many years since the Agile manifesto was constructed and
shared with the world.
The principals of the manifesto have transformed the way people think about
methods and processes of building software.
Teams of all sizes have embraced the principles, from teams of one
to large enterprises with multiple teams working on a single product.
Over the years,
however, many variance of agile software development models have emerged.
Each of these models has different approaches, processes and tools.
To name just a few, Scrum, Lean and Kanban,
Extreme programming, or XP, and many, many more.
Scrum, the subject of this course, is built around a unit of work called
the sprint and the activities that a team carries out to accomplish the sprint.
Lean and ConBon are inspired by methods used by Japanese auto manufacturers
to maximize productivity.
These methods emphasize a continuous flow of delivery with the team repeatedly
picking up the item with the next highest value for development.
Extreme programming, or XP, is so
named because its founders proposed taking engineering best practices to the extreme.
Many of these practices are popular outside of XP.
Examples include pair programming, code review,
task driven development and uni-testing.
While these variants differ in important ways,
they're still guided by the values of the Agile Manifesto.
Each method emphasizes self-organization of individuals and
interactions within the team, measures success by delivering value with working
software, involves the voice of the customer in the process of development and
responds to changes in requirements and priorities.
You need to sign up for Treehouse in order to download course files.Sign up