Evolve - Staying relevant at cloud speed

  • Published on
    06-Dec-2014

  • View
    832

  • Download
    0

Embed Size (px)

DESCRIPTION

EvolveStaying relevant at cloud speed

Transcript

  • 1. The IT Department

2. IT considered acost centerHub of ITTechnical decisionsmade by IT 3. IT deploymentsdriven by businessneedTechnical directiondriven bymanagementStill a cost center 4. Carefullyplanned ITinvestmentsCustomer drivenPotential profitcenter 5. Windowsand the PCarestandardbusinesstools 6. Consumersembrace theInternet as afundamentalpart of theirlives 7. Mobiledevicesbecome thetool forInternetaccess 8. Theemployeesworking forus 9. Questions? 10. 73823,681,882 804717,000,000 11. Creates conflicting prioritiesDevDiv:among stakeholdersServant of Should force a discussion of single backlogThreeAt divisional level, reconciledMasterslargely through resourcing 12. Conways LawDysfunctional WasteTribalismThe best and brightestDont ask, dont tell Easy creditAutonomy, job rotation, No interest charge for debtpromotion Schedule chickenThe currency of loveMetrics are for othersHeadcount Our tribe is betterOur customers are different 13. VS 2005 Bug Step@Beta 1Deferral common(see top line)Teams carry undone work(both functional and ility)Endgame hard to predict 14. Second wave amplified flow of valueNow its time to focus on cycle timeIn parallel, we start to delivercontinuous services in parallel toon-premise product 15. Focus of MQGet CleanStay Clean Understand our DebtMeasure our Quality(Milestone Test Automation Product Code BugsQuickly & ConsistentlyAnytime, Anywhere Test Case Bugsfor Quality) Test Infrastructure BugsQuality earlier in the cycle Put our Debt on the TableMake life easier Cost our Debt Eliminate the Debt 16. End-to-End Scenarios, Value Props, Experiences, Features 17. Scrum Team (FeatureCrew) Delivers 1FeaturesTeam responsible for producing afeatureWork together as a team to hit FeatureCompleteSmall Interdisciplinary Team (63) 18. Engineering Principles 19. Changes 20. First wave addressed technical debtNow its time to focus on cycle timeIn parallel, we start to delivercontinuous services in parallel toon-premise product 21. Focus on the flow 22. Information burnersmake all work and riskvisible 23. First wave addressed technical debtSecond wave amplified flow of valueIn parallel, the we start to delivercontinuous services in parallel toon-premise product 24. Engineering Principles Redux High-value exploratory testing; Test features not stories; Fix bugs immediatelyTests run everywhere in rolling builds with ility tests; Devs write most of regression suite Finish 2-3 stories / team / week; Push for one piece flow Use Story branches; Integrate done, not complete; Keep main ship ready 25. ScenariodefinitionClearly express thecustomer promise 26. ScenariostoryboardsWhat we will do todeliver on thecustomer promise 27. ScenariomeasurementAre we building: the right product? the product right? customer value? 28. ScenariomeasurementAre we building: the right product? the product right? customer value? 29. First wave addressed technical debtSecond wave amplified flow of valueNow its time to focus on cycle time 30. Priorities User ExperienceCode & TestsLive SiteTesting 31. Ideas User ExperienceCode & TestsLive SiteTesting 32. IdeasPriorities User ExperienceLive SiteTesting 33. CodingFeedbackLoop 34. IdeasPriorities User ExperienceCode & TestsLive Site 35. http://procl.files.wordpress.com/2011/06/map-of-north-america-1806.jpg 36. http://procl.files.wordpress.com/2011/06/map-of-north-america-1806.jpg 37. IdeasPriorities User ExperienceCode & TestsTesting 38. Reduction of WasteContinuous BusinessTrustworthy ImprovementTransparencyContinuous Increased Flow ofFeedback Value Shortened CycleTime 39. Theres noplace likeproduction 40. Where tostart? 41. Prioritize work 1..nRuthlessly increase the granularity 42. Make the work visibleAttend the sprint review, put hands on the product, hold the team accountable