微軟項(xiàng)目管理課件

MicrosoftSolutionFramework

(Overview)微軟（中國）開發(fā)合作部軟件開發(fā)首席專家李東方MicrosoftSolutionFramework

AgendaOverviewTeamModelRiskManagementProcessVisionapprovedmilestoneProjectplanapprovedmilestoneScopecompletemilestoneReleasemilestoneAgendaOverviewProjectFailureRatesApplicationDevelopmentProjectsChallengedSucceededFailed28%46%26%ProjectFailureRatesApplicati“Whenprojectsfail,it’srarelytechnical.”JimJohnson,TheStandishGroupRootCausesofFailureSeparationofgoalandfunctionSeparationofbusinessandtechnologyLackofcommonlanguageandprocessFailuretocommunicateandactasateamProcessesthatareinflexibletochange“Whenprojectsfail,it’srareAgendaOverviewTeamModelRiskManagementProcessVisionapprovedmilestoneProjectplanapprovedmilestoneScopecompletemilestoneReleasemilestoneAgendaOverviewLesson2:

TeamModelforApplicationDevelopment

Ahigh-leveloverviewoftheteammodelrolesandresponsibilitiesinanapplicationdevelopmentprojectLesson2:TeamModelforAppliTeamGoalsforSuccessSatisfiedcustomersDeliverywithinprojectconstraintsDeliverytospecificationsthatare

basedonuserrequirementsReleaseafteraddressingallknownissuesEnhanceduserperformanceSmoothdeploymentandongoingmanagementTeamGoalsforSuccessSatisfieTeamofPeersIsateamwhosemembersrelateasequalsHasspecificrolesandresponsibilitiesforeachmemberEmpowersindividualsintheirrolesHoldsmembersaccountableforthesuccessoftheirrolesDrivesconsensus-baseddecision-makingGivesallteammembersastakeinthesuccessoftheprojectTeamofPeersIsateamwhosemProgramManagementDevelopmentTestingLogisticsManagementUserEducationProductManagementTeamModelforApplicationDevelopmentCommunicationProgramDevelopmentTestingLogisProductManagementRoleActsascustomeradvocatetotheteamActsasteamadvocatetothecustomerDrivessharedprojectvisionManagescustomerexpectationsDevelops,maintains,andexecutesthebusinesscaseDrivesfeatureidentificationandprioritizationDevelops,maintains,andexecutesthecommunicationsplanProductManagementProductManagementRoleActsasProgramManagementRoleDrivestheoverallprocessManagesresourceallocationManagestheprojectscheduleandreportsprojectstatusManagestheproductscopeandspecificationFacilitatesteamcommunicationandnegotiationDrivesoverallcriticaltrade-offdecisionsProgramManagementProgramManagementRoleDrivesDevelopmentRoleBuildsandtestsfeaturestomeetthespecificationandcustomerexpectationsParticipatesindesignEstimatestimeandefforttocompleteeachfeatureServestheteamasatechnologyconsultantDevelopmentDevelopmentRoleBuildsandtesTestingTestingRoleDevelopstestingstrategy,plans,andscriptsManagesthebuildprocessConductsteststoaccuratelydeterminethestatusofproductdevelopmentParticipatesinsettingthequalitybarTestingTestingRoleDevelopsteUserEducationRoleActsasteamadvocatetotheenduserActsasend-useradvocatetotheteamParticipatesindefininguserrequirementsParticipatesindesigningfeaturesDesignsanddevelopsusersupportsystemsDrivestheusabilityprocessUserEducationUserEducationRoleActsasteaLogisticsManagementLogisticsManagementRoleActsasteamadvocatetooperationsActsasoperationsadvocatetotheteamPlansandmanagesproductdeploymentParticipatesindesign,focusingonmanageability,supportability,anddeployabilitySupportstheproductduringbetatestingTrainsoperationsandhelpdeskpersonnelforproductreleaseLogisticsLogisticsManagementTeamandGoalAlignmentTeamroleProductmanagementProgrammanagement

Development

Testing

UsereducationLogisticsmanagementGoalSatisfiedcustomersDeliverywithinprojectconstraintsDeliverytoproductspecificationsReleaseafteraddressingallknownissuesEnhanceduserperformanceSmoothproductdeploymentTeamandGoalAlignmentTeamroNotaTraditionalOrganizationalChartTestingDeveloperProjectManagerLogisticsDeveloperAnalystUserEducationNotaTraditionalOrganizationCoordinationwithExternalTeamsTechnologyFocusBusinessFocusEndUsersBusiness

ArchitectsandPlannersCustomerTechnologyArchitectsandSteeringCommitteesOperationsandSupport

GroupsEndUsersProjectTeamUserEducationDevelopmentTestingLogisticsManagementProductManagementProgramManagementCoordinationwithExternalTeaLesson3:

UnderlyingTeamModelPrinciples

SomeoftheprinciplesandpracticesthatmaketheteammodelsuccessfulLesson3:UnderlyingTeamModePrinciplesofaSuccessfulTeamSharedprojectvisionProductmindsetZero-defectmindsetCustomer-focusedmindsetWillingnesstolearnPrinciplesofaSuccessfulTeaWhatitmeansClearlyunderstandingproject

goalsandobjectivesUnderstandingandbuyingintoavisionthatisheldbyallteammembersandthecustomerWhyitisimportantProvidestheteamauniformsenseofpurposeResolvesconflictingandcontradictoryvisionsClarifiesprojectgoalsandobjectivesEnsuresthatteammembersareworkingtowardthesamegoalSharedProjectVisionWhatitmeansSharedProjectViProductMindsetWhatitmeansTreatingallworkaspartofaprojectTreatingthefinaldeliverableofthe

projectasaproductWhyitisimportantFocusestheteamonexecutionrather

thanprocessEnablestheteamtouseproductdevelopmenttechniquesIncreasesteamidentityandaccountabilityProductMindsetWhatitmeansZero-DefectMindsetWhatitmeansCommittingtoqualityPerformingworkatthehighest

possiblelevelofqualityFocusingonachievingthequalitybarsetbytheteamWhyitisimportantIncreasesproductstabilityIncreasesschedulepredictabilityImprovesaccountabilityZero-DefectMindsetWhatitmeaCustomer-FocusedMindsetWhatitmeansCommittingtounderstandingand

solvingthebusinessproblemFocusingonthealignmentofbusinessandtechnologyInvolvingthecustomerthroughouttheprocessWhyitisimportantIncreasesfocusoncustomerneeds,whichimprovesabilitytosolvethebusinessproblemFocusesinnovationonsolvingthebusinessproblemCustomer-FocusedMindsetWhatiWillingnesstoLearnWhatitmeansCommittingtoimprovementthroughgatheringandsharingknowledgeInstitutionalizinglearningthroughsuchtechniquesasreviewsandpostmortemsWhyitisimportantAllowsteammemberstobenefitfrommistakesHelpsteammemberstorepeatsuccessesMandatestimefortheteamtolearnWillingnesstoLearnWhatitmeLesson4:

ScalingtheTeamModel

HowtoscaletheteammodeltoaccommodateprojectsofvaryingsizesLesson4:ScalingtheTeamModScalingforSmallProjectsProgramManagementDevelopmentTestingLogisticsManagementUserEducationProductManagementProgramManagementDevelopmentTestingLogisticsManagementUserEducationProductManagementNoNPossiblePUnlikelyUPPPPPPPPPPUUUUUUUUNNNNNNNNNNNNScalingforSmallProjectsProgProductManagementExample:CombinedRolesProgramManagementDevelopmentTestingLogisticsManagementUserEducationProductExample:CombinedRolesScalingforLargeProjectsDividelargeteamsintosmallerteams,whichhaveLowerprocessoverheadLowermanagementoverheadLowercommunicationoverheadFasterimplementationCreatefeatureteams—multidisciplinarysubteamsorganizedaroundproductfeaturesetsCreatefunctionteams—unidisciplinarysubteamsorganizedbyfunctionalroleScalingforLargeProjectsDiviExample:FeatureTeamsDevelopmentTestingUserEducationProgramManagementDevelopmentTestingUserEducationProgramManagementDevelopmentTestingUserEducationProgramManagementProgramManagementDevelopmentTestingLogisticsManagementUserEducationProductManagementLeadTeamUI

TeamPrinting

TeamCore

TeamExample:FeatureTeamsDevelopExample:FunctionTeamGroupProductManagementEvangelismPublicRelationsMarketingProductPlanningProductManagementExample:FunctionTeamGroupPrAgendaOverviewTeamModelRiskManagementProcessVisionapprovedmilestoneProjectplanapprovedmilestoneScopecompletemilestoneReleasemilestoneAgendaOverviewLesson2:

RiskManagementOverview

TheMSFapproachtoriskmanagementLesson2:RiskManagementOverRetiredRisksRiskAssessmentDocumentTop103.Plan5.Control2.Analyze1.IdentifyRiskStatements4.TrackRiskManagementProcessTheongoingdeliverableofthisprocessisalivingriskassessmentdocumentRetiredRisksRiskAssessmentDAgendaOverviewTeamModelRiskManagementProcess

VisionapprovedmilestoneProjectplanapprovedmilestoneScopecompletemilestoneReleasemilestoneAgendaOverviewLesson1:

ProcessModelfor

ApplicationDevelopment

Ahigh-leveloverviewoftheMSFprocessmodelforapplicationdevelopmentLesson1:ProcessModelfor

AProcessModelsLifecyclemodelsestablishtheorderforprojectactivitiesTwomodelsarepopularThewaterfallmodelThespiral(orrapidapplicationdevelopment)modelMSF’sprocessmodelforapplicationdevelopmentcombinesthebenefitsofbothMilestone-basedprocessFlexibleanditerativeprocessProcessModelsLifecyclemodeProcessModelforApplicationDevelopmentIENVSOGINNIPLANIGNNDEVLOPIGENSTABILZNGIIVisionApprovedProjectPlanApprovedScopeCompleteReleaseProcessModelforApplicationMilestone-DrivenAccountabilityMilestoneVisionapprovedProjectplanapprovedScopecomplete

ReleasePrimarydriverProductmanagementProgrammanagementDevelopmentand

usereducationTestingand

logisticsmanagement

Milestone-DrivenAccountabilitPrinciplesofaSuccessfulProcessCreatinglivingdocuments

Usingversionedreleases

Makingprojecttrade-offsResourcesFeaturesSchedulePrinciplesofaSuccessfulProBenefitsofVersionedReleasesForceclosureonprojectissuesSetclearandmotivationalgoalswithallteammembersManagetheuncertaintyandchangeinprojectscopeEncouragecontinuousandincrementalfeaturedeliveryEnableshortertimetomarketBenefitsofVersionedReleasesMakingProjectTrade-offsResourcesFeaturesScheduleMakingProjectTrade-offsResouProjectTrade-offMatrixConstrainOptimizeAcceptScheduleFeaturesResourcesResourcesFeaturesScheduleProjectTrade-offMatrixConstrAgendaOverviewTeamModelRiskManagementProcessVisionapprovedmilestoneProjectplanapprovedmilestoneScopecompletemilestoneReleasemilestoneAgendaOverviewEnvisioningPhase

AchievingthevisionapprovedmilestoneEnvisioningPhase AchievingthEnvisioning

Creatingahigh-levelviewoftheproject’sgoalsandconstraints

ServesasanearlyformofplanningHelpstheteampulldifferentperspectivesintoacommonunderstandingProvidesthebasisforfutureplanningCaptureswhatthecustomerandkeystakeholdersdeemessentialforsuccessEnvisioning Creatingahigh-leDefiningtheScopeResourcesFeaturesScheduleEnvisioningDefiningtheScopeResourcesFeaVisionApprovedMilestoneIENVSOGINNIPLANIGNNDEVLOPIGENSTABILZNGIIProjectPlanApprovedReleaseVisionApprovedScopeCompleteSignalsagreementonThereasonforthe

projectTheexpected

outcomeProject

feasibilityProjectgoalsand

constraintsOpportunitiesandrisksProjectstructureVisionApprovedMilestoneIENVSTestingstrategies;acceptancecriteria;implicationsTeamFocusDuringEnvisioningProductmanagementProgrammanagementDevelopmentUsereducationTestingLogisticsmanagementVisiondocumentDesigngoals;solutionconcept;projectstructurePrototypes;developmentoptions;implicationsDeploymentimplications;supportimplicationsUserperformanceneedsandimplicationsRoleFocusTestingstrategies;acceptanceSuggestedInterimMilestonesRiskAssessmentDocumentDraftedVisionDocumentDraftedVisionApprovedArevisibleattheteamlevelProvideanopportunityforteammemberstosynchronizetheirworkProvideanopportunityforteammemberstoassessprojectprogressandstatusCoreTeamFormedSuggestedInterimMilestonesRiDeliverablePurposeVisiondocument

RiskassessmentdocumentProjectstructuredocumentDescribeswhatyouwanttodoandhowyouplantodoitDescribestheriskstheprojectentails

Describestheproject’sorganizationalstructureDeliverablesforVisionApprovedOwnerProductmanagement

Programmanagement

ProgrammanagementDeliverablePurposeVisiondocumContentPurposeProblemstatementVisionstatementSolutionconceptUserprofiles

BusinessgoalsDesigngoals

WhyyouwanttodoitWhatyouwanttheproducttobeWhatyouwilldoWhowillusetheproduct

WhatyouwanttoaccomplishHowyouplantoaccomplishitContentsoftheVisionDocumentContentPurposeProblemstatemenRiskAssessmentDocument

AssessingpreliminaryprojectrisksandplanningtheirmanagementIscreatedduringthefive-stepriskmanagementprocessIstheinitialassessmentofprojectriskLaysthegroundworkforongoingriskmanagementProvidesabasisforschedulinganddecision-makingRiskAssessmentDocument AssesProjectStructureDocument

Describingtheproject’s

organizationalstructureand

projectmanagementprocessListsinformationonteammembersIncludesteamlogisticalinformationDescribesteamprocessesActsasarepositoryforprojectdocumentationtemplatesProjectStructureDocument DesAgendaOverviewTeamModelRiskManagementProcessVisionapprovedmilestoneProjectplanapprovedmilestoneScopecompletemilestoneReleasemilestoneAgendaOverviewLesson1:

PlanningPhase

AchievingtheprojectplanapprovedmilestoneLesson1:PlanningPhase AchieImportanceofPlanningRepairCostofDesignDefectsbyPhase10080604020EnvisioningPlanningDevelopingStabilizingImportanceofPlanningRepairCFurtherDefiningtheScopeResourcesFeaturesSchedulePlanningFurtherDefiningtheScopeResoProjectPlanApprovedMilestoneIENVSOGINNIPLANIGNNDEVLOPIGENLSTABIZNGIIVisionApprovedProjectPlanApprovedScopeCompleteReleaseSignalsagreementonProjecttrade-off

strategyProjectrisksWhatwill

bebuiltWhenitwillbebuiltHowitwillbebuiltWhowillbuilditProjectPlanApprovedMilestonTeamFocusDuringPlanningProductmanagementProgrammanagementDevelopmentUsereducationTestingLogisticsmanagementRoleFocusDesign;communicationsplanandscheduleDesign;functionalspecification;masterprojectplanandmasterprojectscheduleDesign;developmentplanandschedule;proofofconceptdevelopmentDesignevaluation;testingplanandscheduleDesignevaluation;logisticsplanandscheduleDesign;userperformancesupport;usereducationplanandscheduleTeamFocusDuringPlanningProdSuggestedInterimMilestonesFunctionalSpecificationDraftedProjectPlanApprovedMasterProjectScheduleDraftedMasterProjectPlanDraftedSuggestedInterimMilestonesFuDesignProcessOverviewLogicalDesignConceptualDesignScenariosPhysicalDesignComponents,UserInterface,and

PhysicalDatabaseObjectsandServices,UserInterface,and

LogicalDatabaseDesignProcessOverviewLogicalRelationshiptoPlanningProjectPlanApprovedPhysicalDesignBaselineConceptualDesignLogicalDesignPhysicalDesignVisionApprovedLogicalDesignBaselineConceptualDesignBaselineRelationshiptoPlanningProjecMSFApplicationModelBusiness

ServicesUser

ServicesDataServicesApplication1Application2MSFApplicationModelBusinessDeliverablePurposeFunctionalspecification

Masterprojectplan

Masterprojectschedule

Revisedmasterriskassessmentdocument

Describeswhatwillbebuilt

Describeshowitwillbebuilt

Describeswhenitwillbebuilt

Describesanyissuesinbuildingit

DeliverablesforProjectPlanApprovedOwnerProgrammanagement

Programmanagement

Programmanagement

Programmanagement

DeliverablePurposeFunctionalsContentsoftheFunctionalSpecificationContentPurposeVisionsummary

Designgoals

RequirementsUsage

summaryFeaturesDependencies

SchedulesummaryIssues

AppendixesWhatyouwanttheproducttobe,justificationforit,andkeyhigh-levelconstraintsWhatyouwanttoachievewiththeproductWhatyourequirefromtheproductWhentheproductwillbeusedandwhowilluseitWhatexactlytheproductdoesOtherfactorstheproduct

dependsonKeydatesanddeliverablesWhatrisksmightimpacttheprojectDesignprocessoutputContentsoftheFunctionalSpeMasterProjectPlan

Consolidatingfeatureteamand

roleworkplansDescribeshowfeatureteamsand

roleswillexecutetheirtasksSynchronizestheplansacrosstheteamIncludesDevelopmentplanTestplanTrainingplanUsersupportplanCommunicationsplanDeploymentplan MasterProjectPlan ConsolidatMasterProjectSchedule

Consolidatingfeatureteamand

roleworkschedulesDescribeswhenfeatureteamsandroleswill executetheirtasksSynchronizestheschedulesacrosstheteamIncludesProductshipdateDevelopmentscheduleTestscheduleTrainingscheduleUsersupportscheduleCommunicationsscheduleDeploymentscheduleMasterProjectSchedule ConsolMasterRiskAssessmentDocument

Consolidatingfeatureteamand

roleriskassessmentsProvidesanoverallviewofprojectriskSynchronizestheassessmentsacross

theteamDriveshigh-leveldecision-makingandprioritizationofeffortMasterRiskAssessmentDocumenLesson3:

SchedulingPrinciples

SomeoftheprinciplesandpracticesthathelpmakeschedulingmoreaccurateLesson3:SchedulingPrinciplePrinciplesofAccurateSchedulingBottom-upestimatingFixed–shipdatemindsetRisk-drivenschedulingSchedulingforan

uncertainfutureAddingbuffertimeUsinginterimdevelopmentmilestonesUsingdiscretetasksPrinciplesofAccurateSchedulBottom-upEstimatingWhatitmeansHavingthosewhodothe

workestimatetheeffortRollinguptask-levelestimatesRecognizingthatexperienceisthebestestimatingtechniqueWhyitisimportantIncreasestheaccuracyoftheestimateFostersteambuy-inofthescheduleMotivatesefficientworkBottom-upEstimatingWhatitmeFixed–ShipDateMindsetWhatitmeansTreatingaproject’sprojected

shipdateasunchangeableCommittingtoashipdate

becauseit’srealisticWhyitisimportantForcescreativitybyremovingtheoptionofdelayingtheshipdateEmpowerstheteambygivingitaneffectivedecision-makingtoolProvidesamotivationalteamgoalFixed–ShipDateMindsetWhatit

WhatitmeansPrioritizingtasksbased

onthelevelofriskinvolvedPrioritizingfeaturesbasedontheir

importancetokeystakeholdersWhyitisimportantMinimizeswastedeffortAllowsthegreatestamountofreaction

timeforriskmitigationManagescustomerexpectationsmoreproductivelyEncouragesearlyproof-of-conceptprototypesRisk-DrivenSchedulingWhatitmeansRisk-DrivenScheSchedulingforanUncertainFutureWhatitmeansRecognizingthatthefuturereally

isuncertainCreatingschedulesthataredesigned

toadjusttotheunexpectedWhyitisimportantCreatesamoreaccurateschedulebybuildinginbuffertimetoaccommodatetheunknownCreatesamoreaccurateschedulebybreakinglargeprojectsintosmallersubprojectsthroughinterimdevelopmentmilestonesCreatesamoreaccurateschedulebyusingdiscretetasksforincreasedvisibilitySchedulingforanUncertainFuAddingBufferTimeRecognizethecriticalneedforbuffertimeUseconfidenceinteamestimatestohelpdeterminetheamountofbufferExternallycommunicatethemilestonedate,nottheteam-estimateddateKeepbufferownershipattheprogrammanagementlevelDevelopmentTimeBufferTimeTeam-EstimatedDateMilestoneAddingBufferTimeRecognizethInternalRelease1InternalRelease26to8weeksFeatureDevelopment2to4weeks2to3weeksTestingandStabilizingBufferTimeAcceptanceTestingMilestoneReviewUsingInterimDevelopmentMilestonesSegmentlargefeaturesetsintosmallerchunksMakethechunksasindependentaspossibleAssessprogressatinterimmilestonesandadjustforplanvariationsTreateachinterimmilestoneasapracticereleaseInternalRelease1InternalRelUsingDiscreteTasksHaveteamleadsbreakdownandprioritizeproductfunctionalityandassociatedtasksDefinetasksclearly,withabeginningandendpoint,asingleoutput,andasingleownerLimittasksizetoeffortsthatrequireonetotwoweeksHaveteammembersusebottom-upestimatingtodeterminetaskdurationAssessestimatedandactualtaskdurationsandmakenecessarycoursecorrectionsUsingDiscreteTasksHaveteamAgendaOverviewTeamModelRiskManagementProcessVisionapprovedmilestoneProjectplanapprovedmilestoneScopecompletemilestoneReleasemilestoneAgendaOverviewLesson1:

DevelopingPhase

AchievingthescopecompletemilestoneLesson1:DevelopingPhase AchSignalsagreementonTheplanned

featuresetWhetherthe

plannedfeature

sethas

been

developedBaselinedmaterials

tosupportuserperformanceThestabilizationprocess,includingbetasandtestingIENVSOGINNIPLANIGNNDEVLOPIGENSTABILZNGIIVisionApprovedProjectPlanApprovedScopeCompleteReleaseScopeCompleteMilestoneSignalsagreementonIENVSOGINNTeamFocusDuringDevelopingProductmanagementProgrammanagementDevelopmentUsereducationTestingLogisticsmanagementRoleFocusCustomerexpectationsmanagement;communicationplanexecution;betaplanningProjecttracking;teamcommunicationandcoordination;betaplanningFeaturedevelopment;testingTestspecifications,cases,andscriptsdevelopment;testingOperationalsupportdocumentation;betaplanning;internalteamsupportUserperformancesupportdevelopmentandtesting;betaplanning;productusabilitytestingTeamFocusDuringDevelopingPrSuggestedInterimMilestonesScopeCompleteInternalReleasenInternalRelease...InternalRelease2InternalRelease1SuggestedInterimMilestonesScInternalReleases

GettingtheproducttoaknownstateandincrementallybuildinguponitInternalRelease1InternalRelease26to8weeksFeatureDevelopment2to4weeks2to3weeksTestingandStabilizingBufferTimeAcceptanceTestingMilestoneReviewInternalReleases GettingtheDeliverablePurposeDescribesproduct

trade-offsandtheplannedfeaturesetDescribestheissues

Baselinestheproduct

Baselinesthematerials

thatsupportusersDescribeshowtheproduct

wasandwillbetestedDescribeswhat’sbeen

donetodateandremainingplansDeliverablesforScopeCompleteRevisedfunctionalspecification

RevisedmasterriskassessmentdocumentSourcecodeandexecutablesUserperformancesupportelementsTestingelements

RevisedmasterprojectplanandrevisedmasterprojectscheduleOwnerProgrammanagement

ProgrammanagementDevelopment

Usereducation

Testing

ProgrammanagementDeliverablePurposeDescribesprLesson2:

Zero-DefectMindset

Alookattheconceptofazero-defectmindsetandtheroleitplaysinqualityLesson2:Zero-DefectMindset Zero-DefectMindset

CommittingtothehighestpossiblelevelofqualitywithinprojectconstraintsTeammembersmustunderstandtherequiredqualitylevelfortheirworkWorkisnotcompleteuntilitreachesthatlevelofqualityThezero-defectmindsetisembodiedinTaskdeliverablesMilestonesZero-DefectMindset CommittingBenefitsofaZero-DefectMindsetIncreasesaccountabilityforthequalityoftheproductIncreasesstabilityoftheproductImprovesschedulepredictabilityDecreasesthecostofaddressingissuesAllowstestingtoshiftfocustoqualityassuranceRewardsqualitydevelopersBenefitsofaZero-DefectMindCodeReviews

AssessingcodetoimproveitsqualityandtoimprovethecapabilitiesofthedevelopmentteamSomewaystoconductcodereviews Acomprehensive,formalreviewAmorecasual,peer-basedreviewAnindependent,third-partyreview CodeReviews AssessingcodetoBenefitsofaCodeReviewImprovesthequalityofthecodeIncreasesthespeedofdevelopmentProvidesawaytotraindevelopersLowersthecostofresolvingdefectsMakesassumptionsexplicitIncreasesthemaintainabilityofthecodeEnforcesdevelopmentpracticesandstandards BenefitsofaCodeReviewImproDailyBuild

Buildingtheproductinanexecutable

formonadailybasis ApublicdailybuildisAstrongindicatorthatateamisfunctionalAwaytomaketheproductanditsprogressvisibleTheheartbeatofthedevelopmentprocess DailyBuild BuildingtheproduBenefitsoftheDailyBuildExposesunanticipateddesigndefectsMakesdiagnosingdefectseasierSynchronizesteameffortsMinimizesintegrationrisksIncreasesqualitySupportsthemonitoringofprogressImprovesteamandcustomermoraleBenefitsoftheDailyBuildExpLesson3:

TestingOverview

Ahigh-levellookatthetestingprocessduringthedevelopingphaseLesson3:TestingOverview AhTesting

Ensuringthattherightthingsare

donerightattherighttimeUncoversissuessotheycanbeaddressedValidatesthattheteamisdoingtherightthingsVerifiesthattheteamisdoingthemrightSupportsbusinessdecisionsandtrade-offsWatchestheprocess,notjusttheproductTesting EnsuringthattherighOngoingProcessofTestingDEVLOPIGENSTABILZNGIIProjectPlanApprovedScopeCompleteReleaseInternalRelease1InternalRelease2InternalRelease...TestPlanTestSpecificationComplete/AlphaBetasReleaseCandidatesGoldenReleaseReleaseInternalReleasenZero-BugReleaseOngoingProcessofTestingDEVLCategoriesofTestsCoveragetestingAttemptstothoroughlytest

everyfeatureoftheproductAttemptstothoroughlytestthecode

baseoftheproductIsusedprimarilyduringthedevelopingphaseUsagetestingAttemptstosuccessfullycomplete

usagescenariosAttemptstotesttheproductinits

expectedenvironmentIsusedprimarilyduringthestabilizingphaseCategoriesofTestsCoverageteTypesofCoverageTestingUnittestsFunctionaltestsCheck-intestsBuildverificationtestsRegressiontestsTypesofCoverageTestingUnitTypesofUsageTestingConfigurationtestsCompatibilitytestsStresstestsPerformancetestsDocumentationandhelpfiletestsAlphaandbetatestsTypesofUsageTestingConfigurLesson4:

BugManagement

AlookatbugsandhowtheycanbemanagedtoimprovequalityLesson4:BugManagement AlooSuccessfulBugManagementRequiresaformalizedbugtrackingprocessRequiressomeformofclassificationtodetermineprioritiesRequiresmorethanjustfixingthemEmpowersdecision-mak