Epic Breakdown

All Agile Infographic Posters - Courtesy Dandypeople.com

Problem with Gartner's "Combine Design Thinking, Lean and Agile" Diagram

1. Problem Solving happens before Execution, thus indicating a Big Upfront Planning. 
2. Each sub process is indicative of a functional silo with handover between them

Overall, this appears Waterfallish.

Scrum vs. Kanban (Henrik Kniberg)

Scrum and Kanban Summary

=================

Scrum

====

1. Split your organization into small, cross functional, self organizing teams.
2. Split your work into a list of small, concrete deliverables. Sort the list by priority and estimate the relative effort of each item.
3. Split time into short fixed-length iterations (1-4 weeks) with potentially shippable code demonstrated after each iteration. 
4. Optimize the release plan and update priorities in collaboration with the customer, based on insights gained by inspecting the release after each iteration. 
5. Optimize the process by having a retro after each iteration.

Kanban

=====

1. Visualize the workflow. 
1. Split the work into pieces, write each item on a card and put them on a wall. 
2. Use named columns to illustrate where each item is in the workflow.
2. Limit WIP. Assign explicit limits to how many items may be in progress at each workflow state.
3. Measure lead time -- average time to complete one item, sometimes called cycle time. Optimize the process to make lead time as small and predictable as possible.

Scrum vs. Kanban

==========