You’ve got a great idea for transforming software development or IT processes in your organization, but you’re not sure how to get buy-in from key stakeholders, or how to change your company culture.
In this session, Microsoft MVP Ike Ellis will draw on his experience as a consultant and leader in software development to give you real-world tips to define, shape, and share your pitch successfully. Whether you are launching a revolutionary new initiative or expanding an existing effort to improve your software development, Ike’s tips will help you create a plan to effect change in your teams.
How to Pitch a Software Development Initiative and Ignite Culture Change
1. How to Pitch a Software
Development Initiative and
Ignite Culture Change
2. Ike Ellis @ike_ellis
www.ikeellis.com
Microsoft MVP
Chairperson of the San Diego TIG
Book co-author – Developing Azure Solutions
Upcoming course on Azure Databricks
Crafting Bytes
We’re hiring Data Experts!
www.craftingbytes.com
3. The challenges of culture change
• Personal
• Team
• Company
• Societal
21. Every leader I’ve ever met has the same
few things in common:
• A lingering project
• A lingering problem
• A publicly embarrassing event
22. So tune in to the radio station and
calm their fear
• We can deliver faster
• We’ll deliver more frequently
• We’ll have fewer bugs
• We’ll have more success
26. Phrases of Fear
• We tried that and we failed
• That will never work here
• This is just the latest fad,our processes are tried and true
• Our company is always 10 years behind the industry
• I have too much to do and this will slow me down
• Just another kitchy program that will eat up all our time
27. But we can address their fears and slowly
introduce change so that they are
comfortable with it
28. Steps to developing new habits:
Step 1: Focus on One New Habit at a time
Step 2: Form a new habit? Commit to 30 days per new habit
Step 3: Anchor Your New Habit to an Established Habit.
Step 4: Take Baby Steps. Don’t be too hard if you misstep or
step backward…stay determined to baby step forward
Step 5: Make a Plan for Obstacles.
Step 6: Create Accountability for Your Habit.
Step 7: Reward Important Milestones.
Step 8: Build a New Identity.
38. Culture TIP: Bathroom signs
LEARN ON THE LOO!
• Teach DevOps Best Practices
• Teach how to use Source Control
• Teach good testing techniques
• Teach culture
39. Standardizing source code only
Pros
• Provides audit trail of
development changes
• Manages collaboration
of team members
• Standardizes coding
practices
Cons
• Manual database code
validation, testing, and
deployments
• Requires a custom process
to prevent environment drift
42. SQL Provision adds speed & safety
• Rapidly refresh development databases with
real-world datasets
• Easily support dedicated environments that
isolate changes made in branches and allow
experimentation
• Mask sensitive data upon image creation
43. Should monitoring be in your initial project?
Pros
• Visibility into production
health
• SQL Monitor shows when
deployments have occurred,
making it easy to track
customer impact (good and
bad) of changes
Cons
• If an external team in
your organization already
controls monitoring,
proposing a change may
be tricky
44.
45. In a supported POC, ask for
guidance from Redgate
• Crafting executive summary
• Industry standards for success criteria
• Sample schedules & help keeping the team on track
46. Elements of a technical project pitch
• Executive Summary
• Business Need
• Solution to be Proven
• Success Criteria and
Long-Term Gains
• Prerequisites
• Schedule
• Team
• Other Resources
• Risks
47. Project Schedule
Keeps your team moving in sync
Helps key stakeholders understand
• Target project duration
• Key milestones
• Proof of concept schedule and core meetings
48. Identify and approach potential
sponsors
Who might this project resonate with in your organization?
• C-Level
• Executive & Senior Managers
• Department Heads
49.
50. Key actions for a sponsor
• Help build a coalition of managers and peers
• Be visible to employees throughout the project
• Communicate the ‘why’ of the change to employees
https://www.prosci.com/resources/articles/change-sponsor-checklist
51. Messages from sponsors
Engage with employees with face-to-face messaging
• Video and recordings work when in-person isn’t possible,
these are more effective than emails alone
Answer questions about the business issues
• “Why is this change happening?”
• “What is the risk of not changing?”
https://www.prosci.com/resources/articles/change-management-communication-checklist
52. The goal of a Proof of Concept is
demonstrating that the tools achieve your
success criteria
53. Choose your technical champions
This team will:
• Explore methodologies to standardize database code
and choose the best approach for your teams
• Set up a proof of concept (POC), safely outside of
production
• Explore and test automation for provisioning, builds
(code validation) and change deployment
54. A rule for any POC
• It must be safe for the team to make a big
mess during the process
•
It must be safe to fail and start over and try
again
55. Avoid these anti-patterns
• Causes of failed proof-of-concepts
• Not a joint venture
• Key stakeholders not involved
• Think it will be more labor
intensive than it is
• Developers leading without
manager buy-in
• Too much focus on tech benefit vs
business benefit
• Biting off too much at a time
58. A POC doesn’t take 2 months of
sustained work
The two-three month timeline applies if:
• Your internal point team has other duties
• You only get a few hours of their time each week
Dedicated resource teams have completed Standardize,
Automate & Protect POCs in two weeks
60. Support practices to map
• What team on-call rotations are needed?
• How to avoid single-points of failure in the team?
• How/when to escalate to subject matter experts?
61. Shifting change approval left
• Shifting change review and approval to earlier in
the development cycle speeds you up
• First steps: can standard (pre-approved) changes
help get you started?
• Sponsorship: this is one place where a sponsor
who can help you build a coalition will help
62. Completing your Proof of Concept
• Collate results from POC and implementation plan
• Finalize licensing
• Set target implementation date and schedule first call
and support session
• Internal presentations about business benefits
63. When an executive sponsor has been
involved from the start, POC sign-off and
completion goes very smoothly
64. Any questions?
Ike Ellis @ike_ellis
www.ikeellis.com
Microsoft MVP
Chairperson of the San Diego TIG
Book co-author – Developing Azure Solutions
Upcoming course on Azure Databricks
Crafting Bytes
We’re hiring Data Experts!
www.craftingbytes.com