15. Lesson #1
Get all the players involved early on.
Use new things as a catalyst to question
everything. Nothing is sacred.
5 Whys.
Let teams think. Don’t control via
crippled tools.
19. Lesson #4
Come up with a ToS for “going fast”.
Approve a process for auto-approving
frequent change instead of manually
approving all changes.
20. Lesson #5
Personify your software – think of
Facebook for Apps.
What does it mean to:
• Interact with an app’s wall
• Like an app
• Friend request an app
• See an app’s friends list
21. Lesson #6
Store meta data about your software.
Be able to query and filter.
DISCUSS: What are some interesting
data points? To deploy? To support?
22. Challenge #3
We now have the means to push quickly and
frequently… but some are scared to do so.
DISCUSS: Why are teams scared of pushing to
production? How do we build confidence?
23. Lesson #7
Make small changes and push
frequently.
Go from “don’t make mistakes” to
“recover very quickly”
Use blue / green deployments.
Pilot with low risk applications and
ramp up.
24. Lesson #8
Have good leaders. Get them onboard.
Celebrate learning what doesn’t work – aka
saving money.
Don’t overreact to first production issue under
new processes. Avoid new “operational scars”.
25. Challenge #4
Users can create new orgs or sign up
for Pivotal Tracker in minutes online.
DISCUSS: Why does this take days at
The Home depot?
26. Lesson #8
Remove all barriers to entry for
collaborative tools.
Enable self-provisioning.
Running out of licenses is a good thing!
Bypassing change management
Finding new ways to be SOX compliant
Bypassing change management
Finding new ways to be SOX compliant
1CD to production
Makes stakeholders really consider change at scale
Bypassing change management
Finding new ways to be SOX compliant
Make it easy and free.
If not, teams will avoid it.
Avoiding it builds risk and monolithic changes with sweeping impacts.
“You Can Go Fast” terms of service for teams
- Certain aspects of your app are pre-approved unless they change.
- most sensitive classification of data
set of shared resources accessed or provided
Agile methodology (1-3 week iterations), testing done in iteration, peer reviewed / approved, change log, etc
Get rid of knowledge transfers, runbooks, etc
Get rid of knowledge transfers, runbooks, etc
Bypassing change management
Finding new ways to be SOX compliant
Get rid of knowledge transfers, runbooks, etc
Bypassing change management
Finding new ways to be SOX compliant
AD groups
Requesting access
Worried about licensing