Cloud foundry, Lessons Learned at The Home Depot
Download as PPTX, PDF7 likes7,795 views
Cloud Foundry has helped The Home Depot build better software and identify opportunities to improve their development processes. Some key lessons learned include getting all stakeholders involved early in new initiatives, applying new processes to existing work, reducing deployment costs so going to production is easy, and establishing processes to allow for frequent small changes rather than infrequent large deployments. Cloud Foundry has also highlighted areas where internal tools and procedures create barriers preventing teams from working quickly and collaboratively.
Cloud foundry, Lessons Learned at The Home Depot
- 1. Cloud Foundry & The Home Depot What tools can teach us about our people and processes.
- 2. greetings the mission a plan the reality the challenges & lessons Agenda
- 3. Greetings 14 years Anthony McCulley Manager, App Platforms & Dev Tools The Home Depot anthonymcculley Startups
- 4. The Mission Build better software.
- 5. A Plan how do I build better software?
- 6. A Plan Do some research
- 7. A Plan Drink from the hydrant
- 8. A Plan Get some help
- 9. A Plan Get some tools
- 10. The Reality – In the Beginning We turned this…
- 11. The Reality – Going to Production … into this! #facepalm
- 12. The Challenges & Lessons What Cloud Foundry is teaching us about our company.
- 13. Challenge #1 cf push == deploy in minutes DISCUSS: Why do you think it took us 4.5 hours?!?
- 14. Oh yea – these people.
- 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.
- 16. Lesson #2 Apply new processes to old things. Look for low-hanging fruit.
- 17. Challenge #2 So teams can push quickly now. DISCUSS: Why don’t teams push more frequently?
- 18. Lesson #3 Drive deployment costs down until going to prod is free.
- 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!
Editor's Notes
- #15: Bypassing change management Finding new ways to be SOX compliant
- #17: Bypassing change management Finding new ways to be SOX compliant
- #18: 1CD to production Makes stakeholders really consider change at scale
- #19: Bypassing change management Finding new ways to be SOX compliant
- #20: Make it easy and free. If not, teams will avoid it. Avoiding it builds risk and monolithic changes with sweeping impacts.
- #21: “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
- #22: Get rid of knowledge transfers, runbooks, etc
- #23: Get rid of knowledge transfers, runbooks, etc
- #24: Bypassing change management Finding new ways to be SOX compliant
- #25: Get rid of knowledge transfers, runbooks, etc
- #27: Bypassing change management Finding new ways to be SOX compliant
- #28: AD groups Requesting access Worried about licensing