An agile journey - Scania Connected Services at Meetup Go Agile - Stockholm (2015-08-12)
•Transferir como PPTX, PDF•
3 gostaram•1,689 visualizações
A agile journey from Scania with tips on working practices and pitfalls. Cultural and technical ones. Was arranged by Meetup: Go Agile! - Stockholm at the 3 office, 2015-08-12.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a An agile journey - Scania Connected Services at Meetup Go Agile - Stockholm (2015-08-12)
Semelhante a An agile journey - Scania Connected Services at Meetup Go Agile - Stockholm (2015-08-12) (20)
Último
Último (20)
An agile journey - Scania Connected Services at Meetup Go Agile - Stockholm (2015-08-12)
- 1. An agile journey Pitfalls and working practices Anders Lundsgård Scania Connected Services Go Agile! – Stockholm, 2015-08-12
- 2. Smartphone access to driver/vehicle data Scania Connected Services FMP Communication Servers Web Servers Monitoring Report Email and SMS remiders/ alarms Fleet Management Portal Remote Diagnosis Current status message every minute Web Service Interface FMP MPMP 50+ engineers 2 TB of data .NET AngularJS
- 3. About me Anders Lundsgård Senior Engineer (Developer, Architect) Scania Connected Services @anderslundsgard 2003 2008 2015 Small Startup Big Enterprise
- 4. Disclaimer #1 The opinions expressed in this presentation and on the following slides are solely those of the presenter and not necessarily those of Scania as a whole.
- 5. Disclaimer #2 Tools are only random selected. Scania does not value these more than those not mentioned.
- 6. Started to automate manual tasks Short summary 2008 2015 MAJOR release failure 2010 20122009 2011 2013 2014 Started to do Continuous Integration (as we thought) Started to do Continuous Integration (as we think ) Integration Driven Development No Projects! Continuous Deployment DevOps Microservices iOSS Model Agile > Scrum No test team! Best lead times from commit to Prod 3-12 months 1-2 month 1-14 days
- 7. Why Agile?
- 10. Why Agile? 65%
- 11. Limit Work In Progress CODE IN PROD PENDING CODE NEW FEATURS Value
- 12. Continuous Delivery (Do not talk about the unicorns)
- 14. Waterfall
- 15. Water-Scrum-Fall
- 18. Continuous Integration Quality over new features Version everything Everyone work on Main branch Automation everything http://codingfast.devops.vision
- 19. Automation – Deployment Pipeline Version Control Pull & Push several times a day Continuous Integration Server - Build - Test - Package Deploy Server Target Servers (Dev, Staging, Prod) Version Everything - Code - Tests - Configuration - Database - Infrastructure
- 20. Feature Branch Dev Branch #1 Main Release Branch #1 Dev Branch #2
- 22. Release != Deploy One appliance, one database table with one column, 0.01 % of all users, thanks to feature toggles. @auriorai
- 23. Always On
- 24. DB Web1 Web2 Load balancer 1. Add new schema 2. Write to both schemas 3. Backfill historical data 4. Read from new schema 5. Remove writes to old schema 6. Remove old schema
- 26. When do you have a Monolith?
- 27. GUI Database Infra Business Logic Networking Storage OS Integration Monolith Service 1 Service 2 Service 5 Service 7 Service 8 Service 10 Service 12 Service 14 Service 3 Service 4 Service 6 Service 9 Service 11 Service 15 Middleware Service 13 User Interface Security Monitoring Even with Continuous Integration. Fast delivery is hard with 50+ engineers and a large codebase.
- 28. All Infra needs User Interface Service 1 Service 2 Service 5 Service 7 Service 8 Service 10 Service 12 Service 14 Service 3 Service 4 Service 6 Service 9 Service 11 Service 15 Service 13 Microservices All Infra needs All Infra needs All Infra needs All Infra needs All Infra needs All Infra needs All Infra needs GUI Database Infra Business Logic Why Microservices? 1. Autonomous teams 2. Build, Test, Deploy SPEED
- 29. Need for DevOps I want change!! I want stability.
- 30. We at infra need to be an enabler for developers. Enable automatic deployments and roll-backs. Creating tools/dashboards with relevant KPI’s so that the developer can fast and easily see the consequences of a deployment. - Mattias Järnhäll, Group manager Scania IT DevOps definition
- 31. ITOps DevOps Version Control I need a new web site for my front end code ”xxx”
- 33. Level 1 Level 2+3 Infrastructure As A Service Infra/ Operations Feature Team Feature Team Feature Team Feature Team GUI Business Logic Database Virtual Machine Integration Network Change Management Database Monitoring Forward
- 34. Infrastructure As A Service Infra/ Operations Feature Team Feature Team Feature Team Feature Team GUI Business Logic Database Virtual Machine Web server Load Balancer Change Management Monitoring You build it You run it! Infrastructure as code Cultural Technical
- 35. Database tests (FeatureToggle MS) 1. Create SQL Server 2. Create empty database 3. Run delta scripts 4. Run Integration tests 5. Delete Server 6. Result in Team City Check-in Why is this nice? No available is server required to run the tests Everything needed is created from source
- 36. 3 awesome infra
- 37. 11,6
- 40. Autonomous Engineers (minimal handovers for fast time to market)
- 41. CodeTest Design Deploy Idea Operate How engineer centric is your company culture?
- 42. Quiz Who is best suited to press the deploy button?
- 43. Inspired by Martin Fowler Jez Humble Adrian Cockcroft Agile Manifesto Continuous Integration Continuous Delivery Lean Enterprise DevOps Microservices
- 44. Contact Anders Lundsgård anders.lundsgard@scania.com @anderslundsgard - #DevOps, #NoEstimates
Notas do Editor
- http://theagileadmin.com/what-is-devops/
- http://theagileadmin.com/what-is-devops/
- http://theagileadmin.com/what-is-devops/
- http://www.infoq.com/news/2011/12/water-scrum-fall-is-the-norm/
- Short iterations gives more quality: http://whatgivesquality.devops.vision
- http://theagileexecutive.com/2010/01/11/standish-group-chaos-reports-revisited/
- http://theagileadmin.com/what-is-devops/
- What is CD? How to do CD? Who does CD?
- Water – Defines the upfront project planning process that typically happens between IT and the business. Scrum – An iterative and adaptive approach to achieving the overall plan that was first laid out in the 'Water' stage. Fall – A controlled, infrequent production release cycle that is governed by organizational policy and infrastructure limitations. (From: http://www.infoq.com/news/2011/12/water-scrum-fall-is-the-norm)
- Water – Defines the upfront project planning process that typically happens between IT and the business. Scrum – An iterative and adaptive approach to achieving the overall plan that was first laid out in the 'Water' stage. Fall – A controlled, infrequent production release cycle that is governed by organizational policy and infrastructure limitations. (From: http://www.infoq.com/news/2011/12/water-scrum-fall-is-the-norm)
- http://theagileadmin.com/what-is-devops/
- You have still automation to do if… You can’t have a dev environment up and running with one single command Someone does manual regressions Prepare test data on test environment You have to order a server Anyone have to log in to a server Someone does manual installations
- ”It’s a trade from code complexity to operational complexity” Martin Fowler: https://www.youtube.com/watch?v=wgdBVIX9ifA http://martinfowler.com/articles/microservices.html Adrian Cockcroft: https://www.youtube.com/watch?v=nMTaS07i3jk&feature=youtu.be Gene Keen, Randy Shoup http://youtu.be/MRa21icSIQk 43:00 Randy Shoup: http://gotocon.com/dl/goto-cph-sept-2014/slides/DeanWampler_and_EvaAndreasson_and_KevlinHenney_and_RandyShoup_WheresCaptainKirkChartingACourseThroughEnterpriseArchitecturePartI.pdf
- http://theagileadmin.com/what-is-devops/
- What is Chaos Monkey? Chaos Monkey is a service which runs in the Amazon Web Services (AWS) that seeks out Auto Scaling Groups (ASGs) and terminates instances (virtual machines) per group. The software design is flexible enough to work with other cloud providers or instance groupings and can be enhanced to add that support. The service has a configurable schedule that, by default, runs on non-holiday weekdays between 9am and 3pm. In most cases, we have designed our applications to continue working when an instance goes offline, but in those special cases that they don't, we want to make sure there are people around to resolve and learn from any problems. With this in mind, Chaos Monkey only runs within a limited set of hours with the intent that engineers will be alert and able to respond. Zerg demo http://zerg.erlangonxen.org/
- http://theagileadmin.com/what-is-devops/
- Other inspirers: Eric Ries, Gene Kim, Randy Shoup, …