Change with a Capital C by Aruni Wijetilleke
20
-
Upload
excella-consulting -
Category
Technology
-
view
254 -
download
1
Transcript of Change with a Capital C by Aruni Wijetilleke
Innovation and change
The world hates change, yet it is the only
thing that has brought progress
–Charles Kettering (American inventor, engineer, businessman, and the holder of 186 patents)
Do you remember when?
Back to the future
Most of us didn’t grow up with today’s technology, we evolved
our behaviors and adopted them into our lives
Change is hardA
do
pti
on
“I heard about this new thing called a smart phone”
“I get what I can do with the smart phone”
“I plan to buy a smart phone”
“I use my smart phone every day”
Time
Change: shift an entire organization (as a whole and individually) from the old to the new
Change is even harder across an organization
Your success in life isn’t based on your ability
to simply change. It is based on your ability to
change faster than your competition,
customers and business
–Mark Sanborn (Leadership speaker)
Changing rapidly to stay ahead
…and it is rapid.
10 versions
Today’s BA needs to embrace and drive change- new
processes, services and innovations-early and often
There is no “magic pill” to adopt change across an
organization.
“It takes a village” and cross-functional collaboration
to promote adoption across new processes, services
or innovations
Mid-point Takeaways?
How can we promote adoption?
Our change management client stories with Agile adoptions
or applications
Change with a capital “C”
Change.
Coaching
Commitment
Culture
Communications
Case Study #1
Issue: Client is managing websites but
changes were given at random across
the development team
Business Results:
Created clear understanding and expectations to deliver
Approach:
• Agile lead collaborated with customer
on work
Set priority based on highest
business value per Agile
• Set expectations for initial results
Invited customer to regular Sprint
Review meeting for product demo
Case Study #2
Issue: Client is introducing automated
testing for quality assurance across the
development team but the code was
“buggy”
Business Results:
Improved key skills and increased understanding to improve delivery
Approach:
• Created better understanding of tool
Provided brown bag lunches
• Promoted Agile commitment across
the development team
Offered Agile-in-a-day session
• Identified additional training needs
Submitted needs to sponsor
Now, you “4C” it!
16
Case Study #3
Issue: Federal Civilian client is introducing
a new agency customer system as a pilot
but faced an unanticipated badging
verification issue.
Business Results:
Identified issue early and re-focused to ensure secure system delivery
Approach:
• Moved away from detailed project plan
across task teams to focus on
messaging, testing and support
Support team for known issues
Tutorial for proper set-up
• Created transparency across
messaging
Provided issue updates during
demos
Case Study #4
Issue: Federal client wanted to adopt Agile
across matrixed IT organization but faced
pushback from a traditionally PMO
environment.
Business Results:
Demonstrated Agile results to improve delivery
Approach:
• Created wins to promote Agile buy-in
Two pilots with Agile coaches
reduced deployment delays
Ability to pivot and “fail fast” to
meet client needs
• Balancing PM needs
Re-focused documentation on
working software vs. weekly status
reports
Don’t forget to “4C” and proactively respond to
change in your organization
Identify problems and readjust priorities early
and often
Be Agile and stay ahead
Final Takeaways?
Aruni [email protected]
