Curing the Agile Hangover

Download Curing the Agile Hangover

Post on 23-Jan-2015




3 download

Embed Size (px)


In this talk we Sandro Mancuso and Mashooq Badar (Directors at UBS) discuss their experiences in how they are trying to find the right balance between technical practices and processes. Empowered professional software engineers, well defined testing strategy, process automation, high investment in people development, requirements management and strong emphasis on quality have been the key areas of their focus.


<ul><li> 1. with Software Craftsmanship</li></ul> <p> 2. Requirements Dev Test Release 3. ProjectManagers Developers Testers/ Analysts 4. Dev Team 1 Dev Team 2 Dev Team 3 Component 1Component 2Component 3 5. Product Scrum DevelopersOwner Master QA BA 6. Team 1 Team 2Team 3 Component 3 Component 2 Component 1 7. Mountain Stagnant ofSkillset Technical DebtRequirementsLow MoralLack ofnot well andtechnical understood Motivationexpertise Long UnreliablerunningRelease buildsProcess Inefficient Develop/Debu Unstableg/Deploy Unreliable andLatesystem cycles costly testsdiscovery of bugs 8. Bad Quality Poor ROI SoftwareTheHangover IsolatedUs and ThemDevelopersAttitudes 9. Well CraftedPoor ROI Software The Hangover Isolated Us and ThemDevelopers Attitudes 10. Well CraftedSteadily Add Value Software The Hangover Isolated Us and ThemDevelopers Attitudes 11. Well CraftedSteadily Add Value Software The HangoverCommunity ofUs and ThemProfessionalsAttitudes 12. Well Crafted Software Steadily Add Value Software Craftsmanship Community ofProductive Partnership Professionals 13. Low Moral CareerLack of and paths for technicalMotivationevery Role expertise Empowered Professionals Role Equality 14. Longrunning Late buildsdiscoveryUnreliable and of bugs costly testsUnit Component Integration System 15. Unit Component IntegrationSystem 16. Mountain Inefficient ofDevelop/Debug/DTechnicaleploy cycles Boy Scout Rule DebtEmbrace Automated Legacy Testing Emphasis onQuality ContinuousTDD IntegrationPair UnstableProgrammingsystem 17. Unreliable Release ProcessRequirementsDev /Test Release Late Unstablediscoverysystem of bugs 18. Dev Prod Zero DowntimeIntegrationDeploymentContinuous DeliveryContinuousProcess AutomationDeployment 19. Low MoralStagnantCoaching and and SkillsetMentoringMotivationProfessional Communities Swap of Practice High Investmentin PeopleVendor ExternalRelationship Communities HiringProcess 20. ContinuousIntegrationPairGeneralizing ProgramingSpecialists AutomatedCode Reviews TestingContinuousBDD ImprovementSpecification WhereTesting at the By Exampleright levelwe are 21. Automated Release andUBS wide Deployment Zero downtimeimprovements Continuous Centre ofDisaster Excellence RecoveryPractice DistributedLocalSource ControlCommunitiesand Social of Practice CodingWhere SimpleRegionalMentorswe want Applicationsto be 22. Sandro MancusoMashooq @mashooq </p>