Scrum : when the reqs are changing or any other change is done in the

projects everyone is aware of it. Everyone gets a update on the change right
away. in scrum development team works very close together. (Ear to ear with
each other).
Kanban
Visualize the workflow
Split the work into pieces, write each item on a card and put on the wall
Use named columns to illustrate where each item is in the workflow.
Limit WIP (work in progress) assign explicit limits to how many items may be in
progress at each workflow state.
Measure the 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.
Similarities of Scrum and Kanban
Both are Lean and Agile
Both use pull scheduling
Both limit WIP
Both use transparency to drive process improvement
Both focus on delivering releasable software early and often
Both are based on self-organizing teams
Both require breaking the work into pieces
In both, release plan is continuously optimized based on empirical data (velocity /
lead time)
Differences Scrum and Kanban
Scrum:
Pre-defined roles of Scrum master, Product owner and team member
Time boxed sprints
Work is pulled through the system in batches (the sprint backlog)
No changes allowed mid-sprint

Velocity
More appropriate in situations where work can be prioritized in batches that can be
left alone
Burndown chart prescribed
WIP limited indirectly (per sprint)
A sprint backlog is owned by one specific team
Timeboxed iterations prescribed.
Kanban:
No arranged roles
Continuous Delivery
Work is pulled through the system (single piece flow)
Changes can be made at any time
Cycle time
More appropriate in operational environments with a high degree of variability in
priority
No particular type of diagram is prescribed
WIP limited directly (per workflow state)
A kanban board may be shared by multiple teams or individuals
Timeboxed iterations optional. (Can have separate cadence for planning,
release, and process improvement. Can be event-driven instead of
timeboxed.)

Scrum master: Project manager who manage the sprints and requirements
listed under each Scrum Master is the facilitator of the scrum team. He / she
make sure that the scrum team is productive and progressive. In case of any
impediments, scrum master follows up and resolves them for the team.
sprint. Mini life cycle Sprint is a predefined interval or the time frame in
which the work has to be completed and make it ready for review or ready
for production deployment. This time box usually lies between 2 weeks to 1
month. In our day to day life when we say that we follow 1 month Sprint
cycle, it simply means that we work for one month on the tasks and make it
ready for review by the end of that month.
Product backlog: Product backlog is a kind of bucket or source where all
the user stories are kept. Product backlog maintained by Product owner.

Product backlog can be imagined as a wish list of the product owner who
prioritizes it as per business needs.

Advantages of Scrum

Advantages of Kanban

Transparency

Flexibility

Improved credibility with clients

Focus on continuous delivery

High product quality

Increased productivity and quality

Product stability

Increased efficiency

Team members reach sustainable pace

Team members have ability to

focus

Allows client to change priorities and requirements Reduction of wasted work/wasted

quickly
time

Scrum is more prescriptive than Kanban

Prescriptive means more rules to follow and adaptive means fewer rules to
follow. 100% prescriptive means you dont get to use your brain, there is a rule for
everything. 100% adaptive means Do Whatever, there are no rules or constraints at
all.
Scrum gives you more constraints, and thereby leaves less options are open. For
example
Scrum prescribes the use of timeboxed iterations, Kanban doesnt.

Scrum prescribes 3 roles: Product Owner (sets product vision &

priorities), Team (implements the product) and Scrum Master
(removes impediments and provides process leadership).
Kanban doesnt prescribe any roles at all.
That doesnt mean you cant or shouldnt have a Product Owner role
in Kanban! It just means you
dont have to. In both Scrum and Kanban you are free to add
whatever additional roles you need.