Skip to content
BENIBIX Learn

XP, Lean and Scrumban

Level 5 Β· Other methods and scale

Three more agile ways to work. One is a set of strict coding habits. One is a war on waste. The last mixes Scrum events with a Kanban board.

Course contentsLesson 18 of 19

After this lesson you can

  • Name the habits of Extreme Programming
  • Spot waste the Lean way
  • Say what Scrumban keeps from each side

12 mincovers 3 glossary entries

Worth reading first: Story Maps and Releases

What XP, Lean and Scrumban each add

Scrum and Kanban are the most used agile methods, but not the only ones. Extreme Programming, or XP, is a set of strict coding habits. Lean software development is about cutting waste. Scrumban mixes Scrum and Kanban. Kent Beck shaped XP in the late 1990s, and Mary and Tom Poppendieck set out Lean software in a 2003 book.

XP takes good habits and turns them all the way up. Programmers work in pairs, two at one screen. They write a test before the code it checks. Everyone merges their work into one shared copy many times a day. Releases are small and frequent, and the design is kept simple.

XP's habits run on feedback loops of different lengths. A test answers in seconds. A partner answers in minutes. Merging answers in hours. A small release answers the customer in weeks. XP names five values, including feedback, courage and respect.

Lean comes from car factories and asks one question. What adds value for the user? Everything else is waste. Waiting, half-done work, extra features nobody asked for and passing work from hand to hand all count. Its seven principles start with cutting waste.

Scrumban keeps some Scrum habits, like regular planning and retrospectives. It adds Kanban's board, its WIP limits and its pull. Planning often happens when the to-do column runs low, not on a fixed day. Many Scrum teams move to it when their work arrives in a steady stream.

These methods mix well. Plenty of Scrum teams use XP's coding habits and Lean's eye for waste. Scrum's own guide leaves room for that, because it says nothing about how to write code or track the work.

The common mistake is picking a method by its name instead of its fit. A support team with work arriving all day fights sprints. A team building one product to a launch date may want them. Choose for the shape of the work.

Three more agile methods

MethodMain ideaWhat it adds
Extreme Programming (XP)Strict coding habitsPairs, tests first, many merges a day
Lean software developmentCut wasteA habit of asking what adds value
ScrumbanScrum events on a Kanban boardPull and WIP limits, with regular planning
XP's habits are loops of feedback, from seconds to weeks. The smaller the loop, the cheaper each mistake.

Worked example

Lucy's team moves to Scrumban

Lucy's team fixes problems for 300 shops, and new work arrives every day. In 2-week sprints, urgent fixes keep breaking the plan.

They move to Scrumban. The board has a limit of 5 in doing. A planning session starts when to do drops below 8 cards. A review of how they work happens every 2 weeks. Urgent fixes now wait 2 days on average, not 8.

The words for this lesson3

Check yourself

In Lean, what is the name for work that adds no value for the user?

Finished this lesson?

Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.