You Can't be Agile When you are Knee Deep in Mud
•
77 likes•21,350 views
This document discusses concepts related to agile software development practices. It covers topics like Scrum, extreme programming (XP), test-driven development (TDD), refactoring, continuous integration, continuous delivery, and transitioning from projects to product-focused organizations. The document suggests that being truly agile requires more than just adopting certain practices - it means establishing an organizational culture aligned around continual delivery of value to customers.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to You Can't be Agile When you are Knee Deep in Mud
Similar to You Can't be Agile When you are Knee Deep in Mud (20)
More from Thoughtworks
More from Thoughtworks (20)
Recently uploaded
Recently uploaded (20)
You Can't be Agile When you are Knee Deep in Mud
- 1. @ r a c h e l l a y c o c k YOU CAN’T BEAGILE When you are knee deep in mud
- 2. 2
- 3. I WANT CONTINUOUS DELIVERY 3 Architecture Quality Assurance Continuous Integration Configuration Management Data Management Environments & Deployment
- 13. REFACTORING 13 Refactoring is a controlled technique for improving the design of an existing code base. http://martinfowler.com/books/refactoring.html
- 15. CONTINUOUS INTEGRATION 15 Everyone Commits To the Mainline Every Day Mainline Server Develop Build Build pull Local Workstation Build push ✔ Done!
- 16. WATER - SCRUM - FALL 16
- 17. CONTINUOUS DELIVERY 17 Software always production ready Releases tied to business needs, not operational constraints Customer Delivery team Constant flow of new features into production
- 18. MORE THAN JUST DEVOPS 18 Organisational Alignment Release Management Architecture Quality Assurance Continuous Integration Configuration Management Data Management Environments & Deployment
- 19. BALLS OF MUD 19
- 20. Reckless Prudent Deliberate Inadvertent “We don’t have time for design” “What’s Layering?” “We must ship now and deal with consequences”
- 21. Good Design No Design Design Payoff Line Cumulative Functionality time
- 22. “We don’t have time for design” “What’s Layering?” “We must ship now and deal with consequences” “Now we know how we should have done it” Reckless Prudent Deliberate Inadvertent
- 23. QUALITY ISSUES (TECHNICAL) 23 Code quality Design quality Automated testing Technical debt reduction …is what your business partners hear! BLAH BLAH BLAH
- 27. CAN’T JUST LIFT AND SHIFT 27
- 29. MICROSERVICES 29 A monolithic application puts all its functionality into a single process… … and scales by replicating the monolith on multiple servers A microservices architecture puts each element of functionality into a separate service… … and scales by distributing these services across servers, replicating as needed.
- 30. REFACTORING 30
- 31. COMPONENTS 31 Component Library Service Libraries and Services are two forms of component Components are units of software that can be independently replaced and upgraded Libraries run within a single process, communicating through language function call mechanisms Services run in separate processes, communicating with networking mechanisms such as HTTP or TCP/IP
- 32. COUPLING AND COHESION 32 code artifact afferent efferent
- 33. FROM PROJECTS 33 BUSINESS PROJECTS OPERATIONS Many ‘good’ ideas - WE NEED $$$! We’re working - GIVE US $$$! That doesn’t work - NEED MORE $$$! Humble, Molesky, O’Reilly, Lean Enterprise: How High Performance Organizations Innovate At Scale
- 34. TO PRODUCTS 34 PRODUCTS / SERVICES OPERATIONS Customers Service DeskOps Management Cross-Functional Product Teams Teams Push Changes Continuously Product Teams for IaaS / PaaS Infrastructure / Platform-As-A-Service Humble, Molesky, O’Reilly, Lean Enterprise: How High Performance Organizations Innovate At Scale
- 35. YOU NEED TO BE THIS TALL TO BE AGILE 35