As Simple As Possible,As Simple As Possible,But But NoNo Simpler Simpler

Sam GuckenheimerSam Guckenheimerhttp://lab.msdn.microsoft.com/vs2005/teamsystem/http://lab.msdn.microsoft.com/vs2005/teamsystem/

samgu@microsoft.comsamgu@microsoft.com

Simple Project ManagementSimple Project Management

Functionality

Quality

Resources

Time

““The Iron Triangle”The Iron Triangle”

(err… tetrahedron)(err… tetrahedron)

2121stst Century Mantra Century Mantra

Do more with less!Do more with less! But if your only variables are:But if your only variables are:

FunctionalityFunctionality QualityQuality Resources Resources Time Time

……then how are you going to do that? then how are you going to do that?

An Older TruthAn Older Truth

Happy families are all alike; every Happy families are all alike; every unhappy family is unhappy in its unhappy family is unhappy in its own way.own way.

Tolstoy, Tolstoy, Anna KareninaAnna Karenina

Все счастливые семьи похожи друг на друга, каждая несчастливая семья несчастлива по-своему.

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

CodeCode Some why-notsSome why-nots

Use managed codeUse managed code Use modern Use modern

frameworksframeworks Use service-Use service-

oriented oriented architecturearchitecture

Use available toolsUse available tools

TransparencyTransparency Responsible Responsible

costingcosting Visible resultsVisible results

Available toolsAvailable tools Unit testsUnit tests Code coverageCode coverage Static analysisStatic analysis Profiling Profiling

performanceperformance Source controlSource control Work item trackingWork item tracking Build automationBuild automation

Unit Tests and Code CoverageUnit Tests and Code Coverage

Unit Test Results

Code Under Test not covered during the test run

Code AnalysisCode Analysis

http://blogs.msdn.com/jason_anderson/archive/2004/09/05/225798.aspx

Code Analysis recommendations as build warnings

Direct jump to code from the warning

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

Product DefinitionProduct Definition

Personas and ScenariosPersonas and Scenarios Qualities of ServiceQualities of Service Capture implicit requirementsCapture implicit requirements

Kano analysisKano analysis

Stack rankingStack ranking

Continually challenge your assumptions!

Personas and Scenarios Personas and Scenarios

PM Starts New Portfolio Project

PM Enumerates Requirements in Excel

PM Schedules Work in MS Project

PM Monitors Project Status

PM Reviews Project Status

PM Promotes For Deployment

CEO Signs Contract

Architect Updates Design

Architect Adds Tasks & Checks In

Dev Writes Code

Dev Writes & Runts Unit Tests

Dev Reviews Work

Dev Runs Code Analysis

Dev Writes Load Tests

Dev Checks In Work

Dev Diagnoses & Fixes

Dev Checks In Work

Tester Checks Build Status

Tester Runs Load Test

Tester Reports Bug

Jacqui AckermanJacqui AckermanProject ManagerProject Manager

Art BensonArt BensonArchitectArchitect

Martin GainesMartin GainesDeveloperDeveloper

Renee DavisRenee Davis TesterTester

Qualities of ServiceQualities of Service PerformancePerformance

ResponsivenessResponsiveness ConcurrencyConcurrency Efficiency Efficiency Fault toleranceFault tolerance ScalabilityScalability

TrustworthinessTrustworthiness SecuritySecurity PrivacyPrivacy Conformance to Conformance to

standardsstandards InteroperabilityInteroperability

UsabilityUsability AccessibilityAccessibility AttractivenessAttractiveness CompatibilityCompatibility DiscoverabilityDiscoverability Ease of useEase of use LocalizabilityLocalizability

ManageabilityManageability AvailabilityAvailability ReliabilityReliability Installability and Installability and

uninstallabilityuninstallability MaintainabilityMaintainability MonitorabilityMonitorability RecoverabilityRecoverability TestabilityTestability SupportabilitySupportability

Kano AnalysisKano Analysis

Hinshitsu (Quality), The Journal of the Japanese Society for Quality Control , XIV:2, pp.39-48, April 1984

Challenging AssumptionsChallenging Assumptions

Customer in usability lab

Customer’s desktop

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

ArchitectureArchitecture

Service-Oriented ArchitectureService-Oriented Architecture Infrastructure ArchitectureInfrastructure Architecture LegacyLegacy

Service OrientationService OrientationBuild Build systemssystems using using autonomous autonomous servicesservices that adhere to the four that adhere to the four tenets of Service Orientation:tenets of Service Orientation:

1.1. Boundaries are explicitBoundaries are explicit

2.2. Services are autonomousServices are autonomous

3.3. Services share schema and Services share schema and contract, not classcontract, not class

4.4. Service compatibility is determined Service compatibility is determined based on policybased on policy

http://msdn.microsoft.com/msdnmag/issues/04/01/Indigo/default.aspx

Application DesignerApplication Designer

Service-OrientedArchitecture modelService-Oriented

Architecture model

Port Details editorPort Details editor

Infrastructure ArchitectureInfrastructure Architecture

Points of FailurePoints of Failure Points of ObservationPoints of Observation Points of AttackPoints of Attack ManageabilityManageability

Logical Infrastructure Logical Infrastructure DesignerDesigner

Services assignedto logical infrastructure

Services assignedto logical infrastructure

Architecture validatedagainst operational

settings and constraints

Architecture validatedagainst operational

settings and constraints

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

Build AutomationBuild Automation Nightly buildNightly build

Project heartbeatProject heartbeat PrePre check-in tests check-in tests

Validation of code prior against current Validation of code prior against current base prior to check-inbase prior to check-in

Variant is continuous integrationVariant is continuous integration Build verification testsBuild verification tests

Functional tests (from unit tests)Functional tests (from unit tests) Component integration testsComponent integration tests

Build reportingBuild reporting Against backlog, by check-in/changesetAgainst backlog, by check-in/changeset

Build ReportingBuild Reporting

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

VersionsVersions

Track versions for each ofTrack versions for each of SourceSource TestsTests Executables and other runtimes you Executables and other runtimes you

createcreate XML, HTML, images, docs & databasesXML, HTML, images, docs & databases

Environmental/deployment componentsEnvironmental/deployment components BugsBugs

Report them together & relate themReport them together & relate them

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

EnvironmentEnvironment

Production environmentProduction environment Test environmentTest environment Capturing environmentCapturing environment ToolsTools

Microsoft Virtual PCMicrosoft Virtual PC Microsoft Virtual Server Microsoft Virtual Server

Maintain lab imagesMaintain lab images

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

SecuritySecurity

The core problemThe core problem Threat modelingThreat modeling Code analysisCode analysis Security testingSecurity testing

Michael Howard, Writing Secure Code, 2003J.D. Meier et al., Improving Web Application Security, 2003

Security: Core ProblemSecurity: Core Problem

Odds of securing a single level is 1 / Odds of securing a single level is 1 / ∞∞ Bad guy has to find only one vulnerability Bad guy has to find only one vulnerability Infinite time Infinite time

Microsoft as exampleMicrosoft as example 100’s of different IT environments100’s of different IT environments 2,500 unique attacks per day2,500 unique attacks per day 125,000 incoming virus-infected e-mails per month125,000 incoming virus-infected e-mails per month

Need to secure at every levelNeed to secure at every level DesignDesign DefaultDefault DeploymentDeployment

Multiple layers of defense neededMultiple layers of defense needed

Threat ModelingThreat Modeling

Analyze the design for vulnerabilityAnalyze the design for vulnerability Model data flowsModel data flows

SS - Spoofing Identity- Spoofing Identity TT - Tampering with Data- Tampering with Data RR - Repudiation- Repudiation II - Information Disclosure- Information Disclosure DD - Denial of Service- Denial of Service EE - Elevation of Privilege- Elevation of Privilege

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

PerformancePerformance Deployment configurationDeployment configuration

Model performance as part of product Model performance as part of product definitiondefinition

Replicate environment in labReplicate environment in lab Test it as part of developmentTest it as part of development Fix it where it hurtsFix it where it hurts

Three-tiered problemThree-tiered problem SystemSystem ComponentsComponents CodeCode

System and ComponentSystem and Component

Performance measures of test and Systems Under Test

Alerts and warnings on Systems Under Test

Code PerformanceCode Performance

Timeline of memory consumption

Suspect functions, drillable to code

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

ManageabilityManageability

Operations documented and current Operations documented and current for every service or applicationfor every service or application

Service level agreement in placeService level agreement in place Security scanning in placeSecurity scanning in place Proactively monitor and fixProactively monitor and fix Reactive and proactive problem Reactive and proactive problem

managementmanagement

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

Testing Mission & ApproachTesting Mission & Approach Marick’s FrameworkMarick’s Framework

Different missions and approaches Different missions and approaches apply for each quadrantapply for each quadrant

Technology Technology FacingFacing

Business Business FacingFacing

Support Support ProgrammingProgrammingCritique Critique ProductProduct

http://www.testing.com/cgi-bin/blog/2003/08/21#agile-testing-project-1

Let the punishment fit the Let the punishment fit the crime!crime!

A good test approach is:A good test approach is: DiversifiedDiversified Risk-focusedRisk-focused Product-specificProduct-specific PracticalPractical DefensibleDefensible

Fit the technique and its data to its Fit the technique and its data to its purpose in the quadrantpurpose in the quadrant

Gilbert & Sullivan, The Mikado

Kaner, Bach & Pettichord, Lessons Learned in Software Testing, 2002

Testing Mission & ApproachTesting Mission & ApproachRepresentative techniquesRepresentative techniques

Technology Technology FacingFacing

Business Business FacingFacing

Support Support ProgrammingProgramming

Unit testing, code Unit testing, code coverage, code analysiscoverage, code analysis

Test-Driven DevelopmentTest-Driven Development

Granularity matches Granularity matches code code

Discrete scenariosDiscrete scenarios

Example-driven dataExample-driven data

Realistic 80% casesRealistic 80% cases

Prioritized regression Prioritized regression testingtesting

Critique Critique ProductProduct

Specialize by QoSSpecialize by QoS

Model-driven testsModel-driven tests

Generated dataGenerated data

Exploratory testingExploratory testing

Soap operasSoap operas

Test CoverageTest Coverage

Identify the Scenario, QoS or Code Identify the Scenario, QoS or Code that the test teststhat the test tests If they’re newly discovered, capture themIf they’re newly discovered, capture them If you can’t name them, question the If you can’t name them, question the

value of the testvalue of the test

Measure coverage against these Measure coverage against these dimensionsdimensions

Test Automation and Its Test Automation and Its DiscontentsDiscontents

Technology FacingTechnology Facing Business FacingBusiness Facing

Support Support ProgrammingProgramming Lowest costLowest cost

Critique ProductCritique Product Highest costHighest cost

ROI= ΣΣtt (Value of Information) - (Value of Information) - ΣΣtt (Cost to Maintain) (Cost to Maintain) ΣΣtt (Cost to Implement) (Cost to Implement)

(adjusted for net present value and risk)

Test Automation and Its Test Automation and Its DiscontentsDiscontents

Value depends on contextValue depends on context Automation is a programming exerciseAutomation is a programming exercise Opportunity cost high due to resource Opportunity cost high due to resource

constraintsconstraints Options theory problemOptions theory problem

Very sensitive to volatilityVery sensitive to volatility Often incalculableOften incalculable

ROI= ΣΣtt (Value of Information) - (Value of Information) - ΣΣtt (Cost to Maintain) (Cost to Maintain) ΣΣtt (Cost to Implement) (Cost to Implement)

Testing Web ApplicationsTesting Web Applications

View of content as rendered

Content validation

http request & response

Performance breakdown

Data substitution

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

MetricsMetrics Consider many dimensions at onceConsider many dimensions at once

Single metrics easily misleadSingle metrics easily mislead Test resultsTest results Bug ratesBug rates Code churnCode churn Code coverageCode coverage Requirements coverageRequirements coverage

Never use metrics for reward or Never use metrics for reward or punishmentpunishment

Flow of value, not completion of tasksFlow of value, not completion of tasks Planned Planned andand unplanned work unplanned work

Robert Austin, Measuring and Managing Performance In Organizations, 1996

Which Component is Healthiest? Which Component is Healthiest?

Contrast two views of project dataContrast two views of project data

Fewest bugs Highest test pass rate

Which Component is Healthiest?Which Component is Healthiest? Conclusions:Conclusions:

Tests are staleTests are stale Highest risk hereHighest risk here

Lowest code coverage

Highest code churn

Focus on Flow of Focus on Flow of ValueValue

David J. Anderson, Managing with Cumulative Flow, 2004www.agilemanagement.net/Articles/Papers/BorConManagingwithCumulat.html

Cumulative Flow

020406080

100120140160180200220240

10-F

eb

17-F

eb

24-F

eb

2-Mar

9-Mar

16-M

ar

23-M

ar

30-M

ar

Time

Fea

ture

s

Backlog Started Designed Tested Complete

Control height of work in progress

Value measured on completion

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

Processes Differ for Good Processes Differ for Good Reasons…Reasons… EconomicsEconomics

RegulationRegulation LiabilityLiability

Plan-Driven vs. AdaptivePlan-Driven vs. Adaptive Iteration lengthIteration length Documentation requiredDocumentation required Sign-off gatesSign-off gates Time tracking requirementsTime tracking requirements

InfrastructureInfrastructureArchitectArchitect

Project Project ManagerManager DeveloperDeveloper

TesterTesterSolutionSolutionArchitectArchitect

Business Business StakeholderStakeholder

……and for Bad Reasonsand for Bad Reasons……and for Bad Reasonsand for Bad Reasons

Solution is TransparencySolution is Transparency

InfrastructureInfrastructureArchitectArchitect

SolutionSolutionArchitectArchitect

Project ManagerProject Manager

DeveloperDeveloper

TesterTester

End UserEnd User

TransparencyTransparency

Single product backlogSingle product backlog Task-aware versioningTask-aware versioning Project portalsProject portals Process handbookProcess handbook

Single Product BacklogSingle Product BacklogSingle backlog of all Work Items (Reqts, Tasks, Bugs, etc.)

Queries to filter, view, report

Details for each entry

Complete change history

Task-aware VersioningTask-aware Versioning

Source files to check in …

…with Work Items done…

…and Check-in Notes and Policy Status

Project PortalProject Portal

Process HandbookProcess Handbook

http://workspaces.gotdotnet.com/msfv4

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

CultureCulture Productivity and predictabilityProductivity and predictability Responsibility over assignmentResponsibility over assignment Team and individualTeam and individual Product mentalityProduct mentality

13 Symptoms of Unhappiness13 Symptoms of Unhappiness It’s the code, stupid!It’s the code, stupid! Actually it’s the requirements!Actually it’s the requirements! No, the problem is that you neglected the architecture!No, the problem is that you neglected the architecture! Architecture, schmarchitecture. I just want a working build.Architecture, schmarchitecture. I just want a working build. What good is that the way we mix up versions?!What good is that the way we mix up versions?! Not code versions, but the environments, don’t you get it?Not code versions, but the environments, don’t you get it? Ever heard of security?!Ever heard of security?! Yeah, but you ignored performance, duh!Yeah, but you ignored performance, duh! So what if it worked in the lab -- it’s still unmanageable!So what if it worked in the lab -- it’s still unmanageable! Oh, and did we mention testing?Oh, and did we mention testing? Since you’re not measuring it, you can’t manage it anyway!Since you’re not measuring it, you can’t manage it anyway! With a process like that, what do you expect?With a process like that, what do you expect? It’s our culture – you’ll never change that.It’s our culture – you’ll never change that.

Sam GuckenheimerSam Guckenheimerhttp://lab.msdn.microsoft.com/vs2005/teamsystem/http://lab.msdn.microsoft.com/vs2005/teamsystem/

samgu@microsoft.comsamgu@microsoft.com