IBM-CRM实施方法论1

DesignReviewWorkshop“TheStepstoSignoff”PEforCRMforBusinessDomainPractitionersFile:L080–DesignReviewWorkshopOverview.pptInitiateLaunchPhasePrepare&ConductDiscoveryWorkshopPrepare&ConductFit-GapWorkshopPrepare&ConductDesignReviewConductDesignValidation(optional)ObtainscopedocumentsDefineteams/rolesConductthelaunchkickoffEducatethecoreteamPresentthescenarios,processdefinition,andfunctionalrqmtstootherconstituenciesIdentifyissues/additionstotakebacktocoreteam/sponsorValidatethescopeDraftthescenariosDraftthestrawmanprocessdefinition(OLP)withcoreteamDocumentfunctionalrequirementrequestsUpdatethescenariosValidateandupdatetheprocessdefinition(OLP)withextendedteamIdentifyhigh-levelfunctionalrequirementsFinalizethescenariosValidateandfinalizetheprocessdefinitionPrioritizethehgh-levelfunctionalrequirementsObtainclientsignoffIntheDesignReviewwefinalizethescenariosandprocess,prioritizetheautomationrequirements,andobtainclientsignoffWeconducttheDesignReviewsessionessentiallythesamewaywedidtheFit-GapsessionFit-GapDesignReviewParticipantsIBMteamClientcoreteamClientextendedteam(SMEs)IBMteamClientcoreteamClientexecutivesWorkshopLeadership50/50IBM/Client20/80IBM/ClientWorkProductsDetailedscenario(s)Detailedprocessdefinition(OLP)Proposedhigh-levelconfigurationrqmts(FRs)Finalscenario(s)Finalprocessdefinition(OLP)Prioritizedhigh-levelconfigurationrqmts(FRs)ClientsignoffWhat'sdifferent:Thestartingpoint–westartwiththeresultsoftheFit-GapworkshopThelevelofdetailwereach--wemovefrom“detailedto“finalThelevelofclientparticipation–theclientcoreteamnowhasthelead,workingwiththeclientexecstoachievesign-offDesignReviewOverview•WhatisDesignReview?–Theopportunitytopresentthenew“Siebelized”businessdesigntoanaudienceofkeydecisionmakersandobtainapprovaloftheprocessmodelandrequirements–Mechanically,it’sanotherfit/gap•Whoistheaudience?–Themanagementorexecutiveteamthatcancommittomakingthenewbusinessmodelhappen•Whoisthepresenter?–TheBusinessCoreTeamWeuseseveralstrategiestoeliminateFRs•ComparetheFRstotheagreedcriteria–IstheFRwithinprojectscope?–CantheclientoperatewithouttheFR?–WillitcostsignificantlymoretooperatewithouttheFR?–Isthereisalegal/regulatoryrequirementfortheFR?–WilllackoftheFRharmcustomersatisfaction?•Demonstrateawork-aroundfortheFR–WillSiebeldeliverthisfunctionisafuturerelease?•IdentifytheprojectimpactoftheFR–Projectcostandtimeline–Developmentcomplexity(high,medium,low)•RemindtheclientthattheyowneveryFR–MustdriveFRstomid-andlow-level–MustdocumentbusinessjustificationforFRsTheDesignReviewresultsinsignoffClientsignoffendstheLaunchworkshops•Signoffindicates:–Agreementthattheprocessmapscaptureandwillsupportbusinessrequirements–AuthorizationtoproceedtotheConfigurationphase–Commitmenttomoveforward•Signoffdoesnot:–GuaranteetechnicalfeasibilityoftheFRs–Eliminatetheneedfortechnicalreviewsinfollow-onphasesNowwe’rereadytomoveontoConfiguration•Ifneeded,conductDesignValidationsessionstocommunicatethenewdesigntootherclientgroups–Maybeconductedforlargemulti-siteprojects•FinalizeLaunchphasedocumentation–Businessscenarios–Processmaps(OLPs)–Configurationrequirements(FRs)–Signoff•TurnoverdocumentationtoConfigurationphaseteamFinalizingthedocumentationmayincludeadditionalworktodriveFRsto“mid-level”LaunchPhaseConfigurePhaseDiscoveryWorkshopFit-GapWorkshopDesignReviewLaunchWorkshopsPhaseCompletionDetailedDesignHighLevelMidLevelLowLevelClientcoreteammemberscontinuetoowntheFRsIBMteammembersmayassisttheclientindetailingtheFRs