[2016.11 Meetup #7] [TALK #2] Luís Faceira - Feature-driven development on the Enterprise

The best approach to embrace a true culture around DevOps and Continuous Delivery is to treat software development as a continuous pipeline of independent features, from specification to support. However, the Enterprise ecosystem presents many specific challenges that make it harder to achieve such continuous flow.In this talk, we'll present the challenges that we've faced in the past when helping other enterprise teams apply feature-driven development and approaches to tackle them effectively.

Transcript

1. Feature-driven development on the Enterprise
2. feature-driven development stage 1 - cyclic integration and delivery
3. feature-driven development stage 2 - continuous integration, cyclic delivery
4. feature-driven development stage 3 - continuous delivery Pipeline of versions through environments Pipeline of features / added-value
5. we do and help others do continuous delivery be.ubi provides consulting, training and custom development of solutions in the different themes and areas that are involved in applying continuous delivery practices: Clear and strict workflows Precise specification Feature isolation Behaviour-Driven Development Code branching and merging techniques Test automation Functional validation Static analysis Code-Review Controlled integration Continuous Security Operations automation Infrastructure as code Normalized environments Configuration management Auto-scaling Cadence management Subjective manual validation Dependency management Automated and continuous deployments Feature toggles Feature Factory Quality Assurance DevOps Delivery Management feature-driven development Consulting business unit established First project in 2013/14, applying continuous delivery to ubi-banking in the context of systems used by Crédito Agrícola for multiple core businesses (credit authorization, data mining, legal management, assets management, etc.)
6. Challenge: velocity aversion
7. feature-driven development Challenge: velocity aversion Greater speed may generate more risk and less quality... Velocity = Direction + Speed quick feedback improves direction which improves quality which improves speed which improves feedback ... ... but Quality is simultaneously a requirement and an output of CD
8. feature-driven development Challenge: velocity aversion Culture can’t be enforced, must be demonstrated Premature horizontal changes fail Vertical changes with increasing width: 1. Simple recent web project 2. Low-risk legacy project 3. Some parts of core-project Measure and promote the outcomes!
9. Challenge: environments complexity
10. feature-driven development Challenge: environments complexity Progress from the beginning of the pipeline (dev) to the end (prod) Use images for the most stable parts Reverse-engineer the most complex cases
11. Challenge: licensing per environment
12. feature-driven development Challenge: licensing per environment Abstract the usage of simpler/cheaper alternatives Progressively move complexity out of licensed services/tools Use new licensing options Abstract the usage of simpler/cheaper alternatives
13. Challenge: click-based programming
14. feature-driven development Challenge: click-based programming Develop through clicks - automate export/reset/import Split exports as much as possible, use text formats Develop manually to explore - then convert to code
15. Challenge: cross-project/department dependencies
16. feature-driven development Challenge: cross-project/department dependencies Micro-features specification Emulate common dependencies Feature-toggles to sync
17. Challenge: see it to believe it
18. feature-driven development Challenge: see it to believe it
19. luis.faceira@beubi.com Questions? Default answer: it depends!