Agile Methodology: Types & Examples

An error occurred trying to load this video.

Try refreshing the page, or contact customer support.

Coming up next: What is Agile Methodology? - Overview, Definition & Steps

You're on a roll. Keep up the good work!

Take Quiz Watch Next Lesson
Your next lesson will play in 10 seconds
  • 0:03 What Is Agile?
  • 0:34 Scrum & Lean
  • 2:18 Extreme Programming…
  • 4:39 Dynamic Systems…
  • 5:42 Feature Driven…
  • 6:31 Lesson Summary
Save Save Save

Want to watch this again later?

Log in or sign up to add this lesson to a Custom Course.

Log in or Sign up

Speed Speed Audio mode

Recommended Lessons and Courses for You

Lesson Transcript
Instructor: Laury Hales

Laury has taught in professional adult education settings for over 10 years and is currently working on a PhD in Organizational Psychology.

The term agile covers several project management approaches, all characterized by using incremental work packages. This lesson will look at the six agile approaches and show how each is used.

What Is Agile?

Agile has been the buzzword in project management for about a decade, and with good reason. Agile is actually an umbrella term over several project management approaches that are characterized by their ability to allow project teams to respond to changing requirements and priorities by using incremental work packages. While all agile methods have common characteristics, each agile method has unique processes that set it apart. Let's look at how each method is used with Charlie's team, who is developing a new software game.

Scrum & Lean

Scrum is a framework for developing and sustaining complex products. Let's look at scrum in action. Charlie's team is beginning an iterative cycle, called a sprint, so Charlie reviews the product backlog with the customer. The product backlog is essentially a prioritized wish list created by the customer of features the new game needs. Charlie selects the top tasks to work on for that sprint, keeping within a two- to four-week timeframe. This task list is called the sprint backlog.

Every day during the sprint, Charlie's team holds a quick meeting called daily scrum to set the work for that day and resolve any work stoppages or roadblocks. Once the work is complete, Charlie meets with the customer to hand over the product, review the product backlog, and reprioritize the requirements. Charlie's team continues working in sprints until the entire game is built.

Now, let's look at lean. Lean started in Toyota's lean manufacturing movement. Now adapted to project management, lean focuses on eliminating waste and delivering value to the customer. Let's look at how Charlie's team would use lean to develop a new software game.

First, Charlie's team breaks down the overall project into iterations that will deliver working pieces of the game. For each iteration, Charlie's team maps the process they will use. The team examines the process and eliminates waste, removing unnecessary steps and reducing delays.

The team uses the improved process to complete the iteration. At the end of each iteration, the team checks if the improved project process worked better and starts the next iteration using the successful changes. This cycle of plan-do-check-act continues, increasing project efficiency until the final game is delivered.

Extreme Programming (XP) & Crystal

Extreme Programming, or XP, is an approach specific to software development that amps up the speed of product release to every one to three weeks. XP is unique among other software development methods because it specifies engineering practices. Let's see how Charlie's team can use XP to develop the new game.

Charlie's team starts gathering requirements for the new game by having the customer describe the features in short user stories. Charlie combines all the user stories to develop a release plan for the entire game.

To deliver working iterations of the software, Charlie develops an iteration plan. It breaks down the release plan into objectives that can be completed in one to three weeks. The software developers write the test plan for each iteration as a final planning activity.

The team starts coding the software, using pairs of developers at a single computer to work together. The old adage 'two heads are better than one' is true here. Two programmers working together produce a higher quality software the first time around. The code is sent for unit testing, again using paired programming. During the iteration, the team holds a daily meeting to ensure there are no roadblocks to completing the day's tasks.

Once the code is written and tested, the software is released to the customer for acceptance testing. User stories are reviewed and prioritized, and the project team begins the next iteration plan. The team continues working through all iterations until the final software is delivered.

Now, let's learn about crystal. Crystal isn't a single method, but a family of methodologies that focus on frequent delivery. However, crystal avoids processes whenever possible and relies on individual contributions to ensure project success. Let's take a look at how crystal might be used with the same software game project.

To unlock this lesson you must be a Member.
Create your account

Register to view this lesson

Are you a student or a teacher?

Unlock Your Education

See for yourself why 30 million people use

Become a member and start learning now.
Become a Member  Back
What teachers are saying about
Try it risk-free for 30 days

Earning College Credit

Did you know… We have over 200 college courses that prepare you to earn credit by exam that is accepted by over 1,500 colleges and universities. You can test out of the first two years of college and save thousands off your degree. Anyone can earn credit-by-exam regardless of age or education level.

To learn more, visit our Earning Credit Page

Transferring credit to the school of your choice

Not sure what college you want to attend yet? has thousands of articles about every imaginable degree, area of study and career path that can help you find the school that's right for you.

Create an account to start this course today
Try it risk-free for 30 days!
Create an account