TEAM方法(英文)PPT演示模板

1、TEAM方法(英文)PPT演示模板TEAM方法(英文)PPT演示模板The IBM Signature Selling Method and TeAMethod are based upon alignment with the customer buying processThe IBM Signature Selling MethSignature Selling Method:OutcomesSellCycle Verifiable Outcomes Customer and IBM agreement to the value of a relationship. Customer-d

2、emonstrated interest in working with IBM. Customer-stated business need,buying vision and agreement to support IBM access to Power Sponsor. Customer Power Sponsor and IBM agreement to go forward with a preliminary solution. Customer Power Sponsors conditional approval of proposed solution. Customer

3、and IBM sign a contract. Customer acknowledges the value of the IBM solution. ldentifiedValidatedQualifiedProposedWonCompletedSignature Selling Method:OutcoTEAM:Work Product FormatTitlePurposeSIMethod work product enabledDescriptionCreating the work productSample work productTEAM:Work Product Format

4、TitleTEAM:Work product Dependency DiagramTEAM:Work product Dependency DTEAM:Task FormatTitlePurposeSIMethod task enabledDescriptionAssociated work products/technique papersTEAM:Task FormatTitlePhase/Activity/Task(GSMethod Task)/Work Products(GSMethod Work Products)PlanEvaluate Customers Business Env

5、ironmentDefine Business Context, Validate Business Issues and Goals(Define Business Context & Validate Business Issues and Goals)Business Context Diagram(Same name)Envisioned Goals and Issues(Envisioned TO-Be Business Goals)Describe Current Organization(Describe Current Organization)Current Organiza

6、tion(none)Develop Plan Linked to Customers Business InitiativesDocument I/T Standards(Document I/T Standards)Information Technology Standards(Same name)Analyze Current IT Infrastructure(Analyze Current IT Infrastructure)Current IT Environment(Current IT Infrastructure, more detailed)Phase/Activity/T

7、ask(GSMethod TExecute(part1)Develop Customer Interest,Establish Buying VisionObtain or Develop Business Roadmap(Business Process Model)Business Process Roadmap(Uses different notation)Gain Sponsorship(none)Project Description(Project Goals, Project Estimates and Risk Assessment)Demonstrate Business

8、Benefits,Capabilities,Qualify OpportunityOutline Solution Requirements(Define and categorize requirements,Develop architecture overview,Establish system context, Identify Key use cases)Non-Functional Requirement(Same name)System Context Diagram(Same name)Architectural Decisions(Same name)Use Case Mo

9、del(Same name)Assess Initial Viability(Assess Initial Viability)Viability Assessment(Same name)Phase/Activity/Task(GSMethod Task)/Work Products(GSMethod Work Products)Execute(part1)Phase/Activity/TExecute(part2)Develop Solution with CustomerDevelop Architecture Overview(Same name)ArchitectureaL Deci

10、sions(Same name)Architecture Overview Diagram(Same name)Survey Available Assets(Same name)Available Asset List(Candidate Asset List)Develop High Level Component Model(Same name)Component Model(Same name)Develop Operational ModelOperational Model(Same name)Refine Viability Assessment(Refine Viability

11、 Assessment)Updated Viability Assessment(Same name)Refine Solution, Resolve Concerns, Close SaleAssess Business Impact(Same name)Updated Viability Assessment(Same name)Ensure Client Commitment(Same name)Updated Project Description & Updated Viability Assessment(Project Goals,Project Estimates and Ri

12、sk Assessment)Evaluate Integrated Solution(Evaluate Integrated Solution,Create Technical Prototype)Updated Project Description & Updated Viability Assessment by the Solution Review recommendations, and the results from a prototype, POC, or performance testPhase/Activity/Task(GSMethod Task)/Work Prod

13、ucts(GSMethod Work Products)Execute(part2)Phase/Activity/TImplementMonitor Solution Implementation, Ensure Expectations Are MetMonitor Pilot(None)Updated Viability Assessment(Same name)Evaluate success(None)Updated Viability Assessment(Same name)Harvest Assets(None)Phase/Activity/Task(GSMethod Task)

14、/Work Products(GSMethod Work Products)ImplementPhase/Activity/Task(GValue of TeAMethodWork Productsfor SWITAsValue of TeAMethodWork ProducThe Value of TeAMethodHelps you break a large project into manageable chunksGives you time to thinkHelps transition to other SWITAs, IGS,ITS,AIM Services & Soluti

15、on AssuranceHelps you remember where you left off with a customer!The Value of TeAMethodHelps yoBUSINESS CONTEXT DIAGRAM:Helps define the scope of the projectHelps you understand the customers business processes, leading to a better solutionHelps you understand the relationships between the target b

16、usiness entities and processes and other entities/processesIdentifies potential system interfaces BUSINESS CONTEXT DIAGRAM:HelpsCURRENT ORGANIZATION:Helps qualify the opportunity:are we in at the right level of the organization?Identifies(potential)sponsors,power sponsors,and enemiesIdentifies perso

17、ns who should be involved in the sales process and what their roles should be Identifies additional opportunitiesHelps identify system interfacesCURRENT ORGANIZATION:Helps quaBUSINESS PROCESS ROADMAP:Helps you understand the customers current and proposed business processes, leading to a better solu

18、tionHelps you build credibility with the customer by demonstrating an understanding of their key business processesHelps you more effectively communicate with the customer and the client team regarding the customers business objectivesBUSINESS PROCESS ROADMAP:HelpsENVISIONED GOALS & SSUES:Documents

19、you agreement with the customer on their goals, issues, and CSFsProvides a basis for assessing the success of the projectProvides high-level functional requirements for your use in designing the solutionHelps It see the big picture (theyre usually focused on immediate deliverables)ENVISIONED GOALS &

20、 SSUES:DocumIT STANDARDS:Provides“givens” to be considered in your solutionHelps you eliminate unfeasible options up frontIdentifies competitors and opportunities for competitive“replacements”(e.g.Oracle-DB2 UDB)Helps ID skills and education requirementsHelps ID current assetsIT STANDARDS:Provides“g

21、ivens” CURRENT IT ENVIRONMENT:Guides you architecture decisionsIdentifies candidates for re-useProvides a starting point for the to-be architecture pictureIdentifies system integration requirementsHelps define transition/release strategy to minimize riskHelps determine the sophistication of environm

22、entCURRENT IT ENVIRONMENT:Guides PROJECT DESCRIPTION:Communicates the projects goals to all parties; answers the question:“what are we doing on this project and why?”Helps ensure agreement to the project goalsIdentifies issues early on in the projectProvides a basis for development of the architectu

23、rabas solutionPROJECT DESCRIPTION:CommunicatSYSTEM CONTEXT DIAGRAM:Identifies scope boundariesDefines interface requirementsHelps identify potential interface solutionsSYSTEM CONTEXT DIAGRAM:IdentifUSE CASE MODEL:Provides functional requirements for development of your solutionProvides a process for

24、 validating a proposed solution Helps in planning a PoCPrioritizes/categorizes system capabilitiesHelps define release strategyIdentifies user and system interfacesUse Case Description helps describe(in text)the systems responsibilities.USE CASE MODEL:Provides functiNON-FUNCTIONAL REQUIREMENTS:Docum

25、ents critical requirements like performance, security, and availability that must be met by the proposed solutionHelps validate the proposed solutionProvides a basis for estimating the size and cost of the proposed systemFirst sign of potential software product requirementsNON-FUNCTIONAL REQUIREMENT

26、S:DoVIABILITY ASSESSMENT:Helps you determine the probability of success for a proposed solutionHighlights issues and risks early on, when they are more easily resolvedVIABILITY ASSESSMENT:Helps youARCHITECTURAL DECISIONS:Provides your rationale for including IBM content in the solutionLets you posit

27、ion IBM content to customers within an architectural contextCommunicates the foundation for your choices to the implementors such as IGSARCHITECTURAL DECISIONS:ProvidARCHITECTURE OVERVIEW DIAGRAM:Communicates the architecture solution“vision”to all partiesIdentifies the IBM and third-party elements of the proposed solutionProvides input to follow-on design and implementation workThis is where themagichappensUse several views depending on the audienceARCHITECTURE OVERVIEW DIAGRAM:AVAILABLE ASSET LIST:Helps you justify your choices to customers and other partiesHelps you ke