Evolve - Staying relevant at cloud speed

751 views
643 views

Published on

Evolve Staying relevant at cloud speed

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
751
On SlideShare
0
From Embeds
0
Number of Embeds
350
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Evolve - Staying relevant at cloud speed

  1. 1. The IT Department
  2. 2. IT considered acost centerHub of ITTechnical decisionsmade by IT
  3. 3. IT deploymentsdriven by businessneedTechnical directiondriven bymanagementStill a cost center
  4. 4. Carefullyplanned ITinvestmentsCustomer drivenPotential profitcenter
  5. 5. Windowsand the PCarestandardbusinesstools
  6. 6. Consumersembrace theInternet as afundamentalpart of theirlives
  7. 7. Mobiledevicesbecome thetool forInternetaccess
  8. 8. Theemployeesworking forus
  9. 9. Questions?
  10. 10. 73823,681,882 804717,000,000
  11. 11. Creates conflicting prioritiesDevDiv: among stakeholdersServant of Should force a discussion of single backlogThree At divisional level, reconciledMasters largely through resourcing
  12. 12. Conway’s Law Dysfunctional Waste TribalismThe best and brightest Don’t ask, don’t tell Easy credit Autonomy, job rotation, No interest charge for debt promotion Schedule chickenThe currency of love Metrics are for others Headcount Our tribe is better Our customers are different
  13. 13. VS 2005 Bug Step@Beta 1Deferral common(see top line)Teams carry undone work(both functional and ‘ility)Endgame hard to predict
  14. 14. Second wave amplified flow of valueNow it’s time to focus on cycle timeIn parallel, we start to delivercontinuous services in parallel toon-premise product
  15. 15. Focus of MQ Get Clean Stay Clean Understand our Debt Measure our Quality(Milestone Test Automation Product Code Bugs Quickly & Consistently Anytime, Anywhere Test Case Bugsfor Quality) Test Infrastructure Bugs Quality earlier in the cycle Put our Debt on the Table Make life easier Cost our Debt Eliminate the Debt
  16. 16. End-to-End Scenarios, Value Props, Experiences, Features
  17. 17. Scrum Team (FeatureCrew) Delivers ≥1FeaturesTeam responsible for producing afeatureWork together as a team to hit FeatureCompleteSmall Interdisciplinary Team (6±3)
  18. 18. Engineering Principles
  19. 19. Changes
  20. 20. First wave addressed technical debtNow it’s time to focus on cycle timeIn parallel, we start to delivercontinuous services in parallel toon-premise product
  21. 21. Focus on the flow
  22. 22. Information burnersmake all work and riskvisible
  23. 23. First wave addressed technical debtSecond wave amplified flow of valueIn parallel, the we start to delivercontinuous services in parallel toon-premise product
  24. 24. Engineering Principles Redux High-value exploratory testing; Test features not stories; Fix bugs immediately Tests 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. 25. ScenariodefinitionClearly express thecustomer promise
  26. 26. ScenariostoryboardsWhat we will do todeliver on thecustomer promise
  27. 27. ScenariomeasurementAre we building: the right product? the product right? customer value?
  28. 28. ScenariomeasurementAre we building: the right product? the product right? customer value?
  29. 29. First wave addressed technical debtSecond wave amplified flow of valueNow it’s time to focus on cycle time
  30. 30. Priorities User ExperienceCode & Tests Live SiteTesting
  31. 31. Ideas User ExperienceCode & Tests Live SiteTesting
  32. 32. IdeasPriorities User Experience Live SiteTesting
  33. 33. CodingFeedback Loop
  34. 34. IdeasPriorities User ExperienceCode & Tests Live Site
  35. 35. http://procl.files.wordpress.com/2011/06/map-of-north-america-1806.jpg
  36. 36. http://procl.files.wordpress.com/2011/06/map-of-north-america-1806.jpg
  37. 37. IdeasPriorities User ExperienceCode & TestsTesting
  38. 38. Reduction of WasteContinuous Business Trustworthy Improvement Transparency Continuous Increased Flow of Feedback Value Shortened Cycle Time
  39. 39. There’s noplace likeproduction
  40. 40. Where tostart?
  41. 41. Prioritize work 1..nRuthlessly increase the granularity
  42. 42. Make the work visibleAttend the sprint review, put hands on the product, hold the team accountable

×