LKIN 17: Kanban: An Alternate Path to Enterprise Agility - Kamini

Kanban: An Alternate Pathto Enterprise Agility

Kamini Milind Godbole

16- Sept-2017

A Definite Answer for Effective Project Execution in Uncertainties

www.leankanbanindia.com

© 2017 Persistent Systems — Confidential 2www.leankanbanindia.com

Agenda

Shortfall of Waterfall model 01

Benefits of Agile02

Agility and its parameters03

Problem faced in a project 04

How Kanban helped?05


Why is Waterfall model fading away?

Phases are sequential.

Product is available at the end.

Requirement changes of any type can impact cost, efforts, schedules.

Completion delays of a phase can have cascading effect on schedule and effort

Evolving customer requirements can not be supported.

Customer involvement oscillates during phases

WA

TER

FALL

Requirements

Design

Implementation

Verification

Documents Documents Unverified Code Software

AG

ILE


Benefits of Agile

Vision driven

Multiple approaches to implement Agile

Shorter development cycles

Minimum viable product available at the end of each cycle

Evolving customer requirement can be supported

Maximum involvement of stakeholders

Impact on cost , schedule, efforts due to changes can be controlled

Minimized defect leakage


What is Enterprise Agility?

Ability of a business to respond to changes in the

most positive way possible with its available

resources.

Agility is adopted to achieve

Faster ROI

Better profit margins

Quick and multiple launch of products in short duration

Capturing larger consumer market share

Support planning of dynamic business needs

Make timely decisions

Craft product to meet end user needs


Can failure occur although being Agile?

Less market research on competitors approach,

trends of consumer need

Diversion of assigned funds

Naïve and ineffective resource, time management

Priority differences

Distraction from periodic goals

Lack of commitment

No lessons learnt

Can he ever understand the

priorities?


Which factors can improve Agility index?

The rules, ceremonies, deliverables, roles agreed by

a project help us define and know Agility index for

an engagement

Result oriented

Self awareness of strengths

Innovative approach

People oriented

Quality focusedCommitment

Capability

Courage

Clarity


What was the problem statement?

Customer organization is a media giant in Maharashtra but unaware of impact on delivery due to not setting definite process of functioning; had pre-conceived notion of Agile

Too many stakeholders

Stakeholder conflicts on business priorities

Frequent non-concluding timeless meetings

Customer losing trust due to not being able to see much progress on the work

Requirements were succinct with implicit sub requirements

Communication gaps amongst the stakeholders

Too many changes during a release

Schedule slippages



How we approached it?

Carried out stakeholder analysis

Realized and agreed on unavoidable constraints on Business Agility and Technology

Trained for Agile and its methodologies

Defined, agreed on the common problem statement “How might we ensure to support business agility with quality and be on schedule.”

Kanban properties

Visualize the workflow

Flexibility of WIP

No fixed release duration

Eliminating distractions on other items

Latents

Keep satisfied

Promoters

Manageclosely

Monitor

Apathetics

Keep informed

Defenders

Pow

er

Interest


Kanban Boards

Stories were written

User stories prioritization

Capacity planning which took careof buffer time


Kanban Implementation

Snapshots of board was shared to broadcast status after regular interval



14© 2017 Persistent Systems — Confidential

Liberal use of colorful post-its was doneto mark blockers

Introduced fast lane




Use of paper callouts for status reporting

Quick decision on movement of blocker user stories , changing of priorities

Reinforcing the process


What extra was done to support?


Guidelines were created

Roles and responsibilities, POCs identified

Instructed all what to do, when to do,

why to do, how to do

Agreed on time boxing for various activities

Defined DoR, DoD

Decided on the number of WIP

user stories/tickets

Bring activities on track for deviations, if any


What difference Kanban got for all?


Kanban offered

Transparency on status

Reduction in wasteful non-productive meetings

More customer engagement

Quicker decisions on blockages, priority changes

Deliveries at agreed interval and of features

Increase in client’s trust

Effective handling of release


What’s next?


Use of weave.conteneo.co tool

https://weave.conteneo.co/weave/

Explore the tool for Kanban

Train stakeholders

Try on one succinct release


https://weave.conteneo.co/weave/

Q & A


[email protected]

Kamini Milind Godbole, Senior Project Manager

Thank You!

Persistent Systems Limited, Pune, India


mailto:[email protected]

Education

LKIN 17: Kanban: An Alternate Path to Enterprise Agility - Kamini