Comparing Agile Process Frameworks, Explained

UPI Study › Courses › Software Engineering › Free lessons › Lesson 5.6 Free with a free account

Comparing Agile Process Frameworks

Software Engineering · Chapter 5: Agile Methodology in PracticeSection 5.6 · lesson 36 of 1036 min · free with a free account

← XP Engineering Practices: Pair Programming, TDD, Continuous Integration, and RefactoringNext lesson: Running Projects with Scrum →

Earn 3 college credits for Software EngineeringRecommended for credit by NCCRS · Computer Science 301 · self-paced · one payment, lifetime access
Enroll in Software Engineering · $250 →Download the syllabus (PDF)

In this lesson

Scrum, XP, Kanban, Lean, and Crystal - 1 set of values, 5 structures.

  • Explain why several agile frameworks share the same values
  • Name 5 widely used frameworks
  • Describe what each framework emphasizes
  • Judge which framework is a better starting fit

Transcript

Everything said in the video, section by section (791 words). Read along, or search it.

Agile Methodology in Practice

Comparing Agile Process Frameworks

Agile is not one single process. It is a set of values that several frameworks put into practice in noticeably different ways. This section compares five of them. Scrum, X P, Kanban, Lean, and Crystal. It covers what each one emphasizes, and what might make one a better starting fit than another.

1 Foundation

Agile Is Not 1 Single Process

Every framework in this section shares the same underlying agile values. Working software, delivered often. Close collaboration. And comfort with changing requirements. What differs between them is not the values. It is the practical structure each framework builds around those values. This section stays at an overview level. Scrum and X P each get much more detailed treatment elsewhere.

Table 1

5 Frameworks at a Glance

Here are the five frameworks at a glance. Scrum focuses on structured, team-level delivery, with fixed-length iterations and defined roles and ceremonies. X P focuses on engineering discipline, with practices meant to keep quality high under frequent change. Kanban focuses on a continuous flow of work. Items move across a board, limited by work in progress caps rather than fixed iterations. Lean, borrowed from manufacturing, focuses on cutting anything that does not add value for the customer. And Crystal is a family of approaches that scales how much process is used, based on team size and project risk.

Figure 2

How Each Organizes Work

This map compares how each framework tends to organize work, and how much structure it prescribes. Left to right runs from continuous flow to fixed iterations. Bottom to top runs from lighter-weight to more structured. Scrum and X P sit toward fixed iterations and more structure. Lean and Kanban sit toward continuous flow and lighter weight. Crystal is drawn as a range, not a point, because scaling its formality to the project is its defining idea. Treat this as a simplification that aids comparison, not a precise measurement.

Profiles (1 of 2)

Scrum and XP

Now, short profiles of each. Scrum organizes work into short, fixed-length iterations, with a small set of defined roles and recurring ceremonies for planning, working, and review. It is the most widely adopted framework built around fixed iterations. X P focuses less on team ceremonies, and more on the technical practices developers use every day. Disciplined testing, continuous refactoring, and close collaboration around the code. X P treats engineering discipline as what keeps quality high under change.

Profiles (2 of 2)

Kanban, Lean, and Crystal

Kanban organizes work as a continuous flow, rather than fixed iterations. Work items move across a visual board, and work in progress limits keep the amount of active work manageable. Lean is not unique to software. It is adapted from lean manufacturing. Its central idea is removing anything that adds no value for the customer. Unnecessary handoffs, unfinished work sitting idle, or features nobody uses. And Crystal is a family of related approaches, rather than one fixed process. How much formal process it includes scales with team size, and with how much is at stake if the project fails.

Think About It

Scrum and Kanban: Both Have Boards

Here is a question to think about. Scrum and Kanban both make work visible on a board, yet they are treated as distinct frameworks. What is the real difference? It is not the board itself. It is how work moves across it. Scrum batches work into fixed iterations, each with a planned scope. Kanban treats work as a continuous stream, governed by work in progress limits rather than iteration boundaries.

Choosing

Which Fits Best?

None of these frameworks is objectively the best choice. Each fits certain situations more comfortably. Work that arrives unpredictably tends to fit Kanban's continuous flow better than fixed iterations. Teams that most need discipline in the code itself often lean toward X P's engineering practices. A team trying to cut waste out of an existing, inefficient process may find Lean more directly useful. Very small, low-risk projects, and large, high-stakes ones, are exactly what Crystal's scalable formality is designed for. And teams can combine ideas. A Scrum team, for example, commonly adopts several of X P's engineering practices.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. Scrum organizes work into fixed-length iterations, with defined roles and ceremonies. X P centers on technical practices meant to protect code quality under frequent change. Kanban organizes work as a continuous flow across a visual board, governed by work in progress limits. Lean, adapted from manufacturing, focuses on eliminating anything that does not add value for the customer. And Crystal is a family of approaches that scales formal process to team size and project risk.

Key Takeaways

What to Carry Forward

To pull this together. Scrum, X P, Kanban, Lean, and Crystal all express the same agile values, through different practical structures. Their defining ideas are fixed iterations, engineering practice, continuous flow, eliminating waste, and scalable formality. The right fit depends on how predictably work arrives, where a team most needs discipline, and the project's size and risk. And teams are free to combine ideas from more than one framework.

About Software Engineering at UPI Study

Software Engineering (Computer Science 301) is a self-paced online course of 103 video lessons in 15 chapters, from process models and agile to requirements, design, user interfaces, reliability, security and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take Software Engineering with UPI Study

How professional software gets builtSoftware Engineering covers how teams turn requirements into working, maintainable software: process models, agile, requirements, design, testing, reliability and project management. It is a core course in computer science and software degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Software Engineering carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Comparing Agile Process Frameworks

What are the most common agile frameworks?
Five widely used agile frameworks are Scrum, Extreme Programming (XP), Kanban, Lean, and Crystal. Scrum uses fixed-length iterations with defined roles and ceremonies. XP centers on engineering practices that protect code quality. Kanban manages a continuous flow of work with work-in-progress limits. Lean eliminates waste, and Crystal scales formal process to team size and project risk.
What is the difference between Scrum and Kanban?
The key difference is how work moves, not the board, since both make work visible on one. Scrum batches work into fixed-length iterations, each with a planned scope. Kanban treats work as a continuous stream across a visual board, governed by work-in-progress limits rather than iteration boundaries. That makes Kanban a natural fit when work arrives unpredictably.
What is Lean software development?
Lean software development is an approach adapted from lean manufacturing whose central idea is removing anything that adds no value for the customer. Examples of such waste include unnecessary handoffs, unfinished work sitting idle, and features nobody uses. Lean can be especially useful to a team trying to cut waste out of an existing, inefficient process.
How do you choose which agile framework to use?
No agile framework is objectively best, so the choice depends on the situation. Unpredictable incoming work fits Kanban's continuous flow. Teams needing discipline in the code often lean toward XP. Lean helps cut waste from an inefficient process, and Crystal scales formality for very small or high-stakes projects. Teams can also combine ideas, such as a Scrum team adopting XP practices.

About the Software Engineering course

How many college credits is Software Engineering?
Software Engineering (Computer Science 301) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Software Engineering cost and what is included?
$250, paid once, with lifetime access: all 103 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Software Engineering take?
It is self-paced with no deadlines. The 103 lessons total about 11 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Software Engineering.

103 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Software Engineering →Download the syllabusEvery course with PRO →
Software Engineering
3 credits · NCCRSEnroll →