1 / 37

Turning Walls Into Bridges

Turning Walls Into Bridges. Sam Guckenheimer samgu@microsoft.com Microsoft Corporation. All Processes Are Rooted In Fear. (Kent Beck). The ‘90s: Basic Tools. Early tools focused on isolated tasks, such as source control. Dev. Dev. Dev. Dev. Dev. Dev. Dev. Dev. Dev. Dev.

quamar-sexton
Télécharger la présentation

Turning Walls Into Bridges

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Turning Walls Into Bridges Sam Guckenheimer samgu@microsoft.com Microsoft Corporation

  2. All Processes Are Rooted In Fear (Kent Beck)

  3. The ‘90s: Basic Tools • Early tools focused on isolated tasks, such as source control Dev Dev Dev Dev Dev Dev Dev Dev Dev Dev

  4. The ‘00s: Value Up Software Engineering • Trustworthy Transparency bridges the team Devs DB Test PM Arch PM Devs DB Test Arch

  5. Flow of Value → Working software Quality first Lean Application Lifecycle Changing the Paradigm Reduction of Waste → Small batches Short cycles

  6. Changing the Paradigm Work Down Value Up Plan Task 1 Task 2 Task 3 Task 4 Remaining Work Value Traditionally, we decompose tasks and measure completion This is the cost accounting tradition Alternatively, we account for customer value incrementally delivered This is the Lean Manufacturing and Theory of Constraints model

  7. How Far Can We Get In The Available Time? Work planned Work completed

  8. What Is Our Software Quality? Test rates (pass, inconclusive, fail) shown in bars Against code coverage, … code churn, … and active bugs

  9. A Venerable Truth Happy families are all alike; every unhappy family is unhappy in its own way. Tolstoy, Anna Karenina Всесчастливыесемьипохожидругнадруга, каждаянесчастливаясемьянесчастливапо-своему.

  10. Signs Of Unhappiness • Underestimating • Uneven Task Decomposition • Solution Stuck in Testing • Development Practices Too Loose • Inadequate Unit Testing • Tests Passing; Solution Doesn’t Work • Too Little Testing • Build Failures • Scope Creep • Resource Leaks

  11. Underestimating Slow progress leading to cuts in planned work, but not enough cuts Steady rates of progress, but slope too shallow

  12. Solution Stuck In Testing Bulge in resolved → Insufficient resources or inadequate quality from dev

  13. Development Practices Too Loose Growing “Fault Feedback Ratio” – bugs requiring multiple handling

  14. Inadequate Unit Testing Fewer Passing and More Inconclusive Tests Falling Code Coverage Rising Code Churn

  15. Scope Creep “Dark matter” emerging during iteration Planned work is squeezed out

  16. Process Enacted By Tooling

  17. Process Enacted In Cycles

  18. What Code Hasn’t Been Tested? Unit tests for both application and database tiers The lines in question Uncovered code by method

  19. Down To The Individual Check-In Check-in dialog captures the workitems resolved with the code(and tests) delivered Policy makes sure that the association is made(and unit tests and code analysis have been run)

  20. And Up To The Team Build Build Verification Test results as part of the build process Who checkedin what? Automated release note: Why the work was delivered

  21. Identify Performance Under Load In Time To Act… Load test captures both test-generated data and metrics on the servers under test Running the test with profiling pinpoints hotspots in code

  22. Supporting Heterogeneous Development Web Access Client for NON-development roles Eclipse integration as partner solution for heterogeneous environments

  23. We Document For The Auditor Capturing evidencedoes not have to be a manual process, ... …because there is a complete audit trail on all the tasks, code and tests…

  24. How Microsoft Uses VSTS

  25. Actual Feature Flow In Orcas (VS 2008) Beta 1 planning review Initial planning spike Beta 2 review Additional tightening @ Beta 2 Tightened process rules @ Beta 1 reduce WIP

  26. Quality Gates Quality Gates act as extended check-in policies, governing the quality of feature delivery into the main source code branch

  27. Value Props, Experiences, And Features Features are designed from Value Propositions and Experiences

  28. Drilldown: Value Prop → Feature Status review rolls up features and experiences back into value props to assess release readiness Drilldown from value prop shows detailed feature status

  29. Others Prefer To Review In VS… Same value prop…

  30. Or In Excel…. Same value prop…

  31. Value Up: How It Feels

  32. Looking Forward: The ‘10s • The right thing • Done right • In the right way Business Analyst PMO Customers Operations Designers Test Arch Devs PM DB PM Arch Test Devs DB PMO Operations Designers Customers Business Analyst

  33. How It Feels • The Wall Becomes a Bridge

  34. Visual Studio Team System

  35. For More Information… Naked Self-Promotion

More Related