团队建设综合论述英文版

1、团队建设综合论述英文版The IBM Signature Selling Method and TeAMethod are based upon alignment with the customer buying processTEAM:Work Product FormatTitlePurposeSIMethod work product enabledDescriptionCreating the work productSample work productTEAM:Work product Dependency DiagramTEAM:Task FormatTitlePurposeS

2、IMethod task enabledDescriptionAssociated work products/technique papersPhase/Activity/Task(GSMethod Task)/Work Products(GSMethod Work Products)PlanEvaluate Customers Business EnvironmentDefine Business Context, Validate Business Issues and Goals(Define Business Context & Validate Business Issues an

3、d Goals)Business Context Diagram(Same name)Envisioned Goals and Issues(Envisioned TO-Be Business Goals)Describe Current Organization(Describe Current Organization)Current Organization(none)Develop Plan Linked to Customers Business InitiativesDocument I/T Standards(Document I/T Standards)Information

4、Technology Standards(Same name)Analyze Current IT Infrastructure(Analyze Current IT Infrastructure)Current IT Environment(Current IT Infrastructure, more detailed)Execute(part1)Develop Customer Interest,Establish Buying VisionObtain or Develop Business Roadmap(Business Process Model)Business Process

5、 Roadmap(Uses different notation)Gain Sponsorship(none)Project Description(Project Goals, Project Estimates and Risk Assessment)Demonstrate Business Benefits,Capabilities,Qualify OpportunityOutline Solution Requirements(Define and categorize requirements,Develop architecture overview,Establish syste

6、m context, Identify Key use cases)Non-Functional Requirement(Same name)System Context Diagram(Same name)Architectural Decisions(Same name)Use Case Model(Same name)Assess Initial Viability(Assess Initial Viability)Viability Assessment(Same name)Phase/Activity/Task(GSMethod Task)/Work Products(GSMetho

7、d Work Products)ImplementMonitor 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)/Work Products(GSMethod Work Products)Valu

8、e of TeAMethodWork Productsfor SWITAsThe Value of TeAMethodHelps you break a large project into manageable chunksGives you time to thinkHelps transition to other SWITAs, IGS,ITS,AIM Services & Solution AssuranceHelps you remember where you left off with a customer!BUSINESS CONTEXT DIAGRAM:Helps defi

9、ne the scope of the projectHelps you understand the customers business processes, leading to a better solutionHelps you understand the relationships between the target business entities and processes and other entities/processesIdentifies potential system interfaces BUSINESS PROCESS ROADMAP:Helps yo

10、u understand the customers current and proposed business processes, leading to a better solutionHelps 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 cu

11、stomers business objectivesIT 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 assetsCURRENT IT

12、 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 environmentUSE CASE MODEL

13、:Provides functional requirements for development of your solutionProvides a process for 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

14、systems responsibilities.NON-FUNCTIONAL REQUIREMENTS:Documents 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 requirementsARCHITECTURAL DECIS