TEAM方法課件可編輯

TEAM方法2024/7/1TEAM方法TheIBMSignatureSellingMethodandTeAMethodare

baseduponalignmentwiththecustomerbuyingprocessTEAM方法SignatureSellingMethod:OutcomesSellCycle

VerifiableOutcomes

CustomerandIBMagreementtothevalueofa

relationship.Customer-demonstratedinterestinworkingwithIBM.Customer-statedbusinessneed,buyingvisionandagreementtosupportIBMaccesstoPowerSponsor.CustomerPowerSponsorandIBMagreementtogoforwardwithapreliminarysolution.CustomerPowerSponsor’sconditionalapprovalofproposedsolution.CustomerandIBMsignacontract.CustomeracknowledgesthevalueoftheIBMsolution.

ldentifiedValidatedQualifiedProposedWonCompletedTEAM方法TEAM:WorkProductFormatTitlePurposeSIMethodworkproductenabledDescriptionCreatingtheworkproductSampleworkproductTEAM方法TEAM:WorkproductDependencyDiagramTEAM方法TEAM:TaskFormatTitlePurposeSIMethodtaskenabledDescriptionAssociatedworkproducts/techniquepapersTEAM方法Phase/Activity/Task(GSMethodTask)/WorkProducts

(GSMethodWorkProducts)PlanEvaluateCustomer’sBusinessEnvironmentDefineBusinessContext,ValidateBusinessIssuesandGoals(DefineBusinessContext&ValidateBusinessIssuesandGoals)BusinessContextDiagram(Samename)EnvisionedGoalsandIssues(EnvisionedTO-BeBusinessGoals)DescribeCurrentOrganization(DescribeCurrentOrganization)CurrentOrganization(none)DevelopPlanLinkedtoCustomer’sBusinessInitiativesDocumentI/TStandards(DocumentI/TStandards)InformationTechnologyStandards(Samename)AnalyzeCurrentITInfrastructure(AnalyzeCurrentITInfrastructure)CurrentITEnvironment(CurrentITInfrastructure,moredetailed)TEAM方法Execute(part1)DevelopCustomerInterest,EstablishBuyingVisionObtainorDevelopBusinessRoadmap(BusinessProcessModel)BusinessProcessRoadmap(Usesdifferentnotation)GainSponsorship(none)ProjectDescription(ProjectGoals,ProjectEstimatesandRiskAssessment)DemonstrateBusinessBenefits,Capabilities,QualifyOpportunityOutlineSolutionRequirements(Defineandcategorizerequirements,Developarchitectureoverview,Establishsystemcontext,IdentifyKeyusecases)Non-FunctionalRequirement(Samename)SystemContextDiagram(Samename)ArchitecturalDecisions(Samename)UseCaseModel(Samename)AssessInitialViability(AssessInitialViability)ViabilityAssessment(Samename)Phase/Activity/Task(GSMethodTask)/WorkProducts

(GSMethodWorkProducts)TEAM方法Execute(part2)DevelopSolutionwithCustomerDevelopArchitectureOverview(Samename)ArchitectureaLDecisions(Samename)ArchitectureOverviewDiagram(Samename)SurveyAvailableAssets(Samename)AvailableAssetList(CandidateAssetList)DevelopHighLevelComponentModel(Samename)ComponentModel(Samename)DevelopOperationalModelOperationalModel(Samename)RefineViabilityAssessment(RefineViabilityAssessment)UpdatedViabilityAssessment(Samename)RefineSolution,ResolveConcerns,CloseSaleAssessBusinessImpact(Samename)UpdatedViabilityAssessment(Samename)EnsureClientCommitment(Samename)UpdatedProjectDescription&UpdatedViabilityAssessment(ProjectGoals,ProjectEstimatesandRiskAssessment)EvaluateIntegratedSolution(EvaluateIntegratedSolution,CreateTechnicalPrototype)UpdatedProjectDescription&UpdatedViabilityAssessmentbytheSolutionReviewrecommendations,andtheresultsfromaprototype,POC,orperformancetestPhase/Activity/Task(GSMethodTask)/WorkProducts

(GSMethodWorkProducts)TEAM方法ImplementMonitorSolutionImplementation,EnsureExpectationsAreMetMonitorPilot(None)UpdatedViabilityAssessment(Samename)Evaluatesuccess(None)UpdatedViabilityAssessment(Samename)HarvestAssets(None)Phase/Activity/Task(GSMethodTask)/WorkProducts

(GSMethodWorkProducts)TEAM方法ValueofTeAMethod

WorkProductsforSWITAsTEAM方法TheValueofTeAMethodHelpsyoubreakalargeprojectintomanageable‘chunks’GivesyoutimetothinkHelpstransitiontootherSWITAs,IGS,ITS’,AIMServices&SolutionAssuranceHelpsyourememberwhereyouleftoffwithacustomer!TEAM方法BUSINESSCONTEXTDIAGRAM:HelpsdefinethescopeoftheprojectHelpsyouunderstandthecustomer’sbusinessprocesses,leadingtoabettersolutionHelpsyouunderstandtherelationshipsbetweenthetargetbusinessentitiesandprocessesandotherentities/processesIdentifiespotentialsysteminterfacesTEAM方法CURRENTORGANIZATION:Helpsqualifytheopportunity:areweinattherightleveloftheorganization?Identifies(potential)sponsors,powersponsors,andenemiesIdentifiespersonswhoshouldbeinvolvedinthesalesprocessandwhattheirrolesshouldbeIdentifiesadditionalopportunitiesHelpsidentifysysteminterfacesTEAM方法BUSINESSPROCESSROADMAP:Helpsyouunderstandthecustomer’scurrentandproposedbusinessprocesses,leadingtoabettersolutionHelpsyoubuildcredibilitywiththecustomerbydemonstratinganunderstandingoftheirkeybusinessprocessesHelpsyoumoreeffectivelycommunicatewiththecustomerandtheclientteamregardingthecustomer’sbusinessobjectivesTEAM方法ENVISIONEDGOALS&SSUES:Documentsyouagreementwiththecustomerontheirgoals,issues,andCSFsProvidesabasisforassessingthesuccessoftheprojectProvideshigh-levelfunctionalrequirementsforyouruseindesigningthesolutionHelpsItseethebigpicture(they’reusuallyfocusedonimmediatedeliverables)TEAM方法ITSTANDARDS:Provides“givens”tobeconsideredinyoursolutionHelpsyoueliminateunfeasibleoptionsupfrontIdentifiescompetitorsandopportunitiesforcompetitive“replacements”(e.g.Oracle->DB2UDB)HelpsIDskillsandeducationrequirementsHelpsIDcurrentassetsTEAM方法CURRENTITENVIRONMENT:GuidesyouarchitecturedecisionsIdentifiescandidatesforre-useProvidesastartingpointfortheto-bearchitecturepictureIdentifiessystemintegrationrequirementsHelpsdefinetransition/releasestrategytominimizeriskHelpsdeterminethesophisticationofenvironmentTEAM方法PROJECTDESCRIPTION:Communicatestheproject’sgoalstoallparties;answersthequestion:“whatarewedoingonthisprojectandwhy?”HelpsensureagreementtotheprojectgoalsIdentifiesissuesearlyonintheprojectProvidesabasisfordevelopmentofthearchitecturabassolutionTEAM方法SYSTEMCONTEXTDIAGRAM:IdentifiesscopeboundariesDefinesinterfacerequirementsHelpsidentifypotentialinterfacesolutionsTEAM方法USECASEMODEL:ProvidesfunctionalrequirementsfordevelopmentofyoursolutionProvidesaprocessforvalidatingaproposedsolutionHelpsinplanningaPoCPrioritizes/categorizessystemcapabilitiesHelpsdefinereleasestrategyIdentifiesuserandsysteminterfacesUseCaseDescriptionhelpsdescribe(intext)thesystem’sresponsibilities.TEAM方法NON-FUNCTIONALREQUIREMENTS:Documentscriticalrequirementslikeperformance,security,andavailabilitythatmustbemetbytheproposedsolutionHelpsvalidatetheproposedsolutionProvidesabasisforestimatingthesizeandcostoftheproposedsystemFirstsignofpotentialsoftwareproductrequirementsTEAM方法VIABILITYASSESSMENT:HelpsyoudeterminetheprobabilityofsuccessforaproposedsolutionHighlightsissuesandrisksearlyon,whentheyaremoreeasilyresolvedTEAM方法ARCHITECTURALDECISIONS:ProvidesyourrationaleforincludingIBMcontentinthesolutionLetsyoupositionIBMcontenttocustomerswithinanarchitecturalcontextCommunicatesthefoundationforyourchoicestotheimplementorssuchasIGSTEAM方法ARCHITECTUREOVERVIEWDIAGRAM:Communicatesthearchitecturesolution“vision”toallpartiesIdentifiestheIBMandthird-partyelementsofthepropose