项目起步内培

1、议程集成项目的实施风险与对策概述集成项目的实施方法论1集成项目实施的风险（1）管理风险业务需求在分析阶段还不确定，拖延分析时间,更糟糕的是在整个工程阶段还在不断更改需求；多单位合作关系,没有明确的分工和责任划分; 应用开发团队、系统集成团队的建议和企业各部们之间欠配合;难以平衡业务集成需要和对短期绩效的追求；过渡计划启动过迟；缺乏整体EAI/BPI战略和计划, 没有高层推动和领导，资源和效率都得不到保障。应用系统项目实施的拖延影响到EAI/BPI的进度；2集成项目实施的风险应对（1）管理风险的对策业务需求在分析阶段还不确定，拖延分析时间,更糟糕的是在整个工程阶段还在不断更改需求；必须确认业务需

2、要达到的目的,以业务部门的需求缓急，心理准备程度来安排业务整合项目的优先次序，并对其有深入透彻和完整精确的需求理解分析，并获得业务部门的共识，业务部门对共识做出承诺. 3集成项目实施的风险应对（2）管理风险的对策多单位合作关系,没有明确的分工和责任划分; 明确各单位在整个项目中的角色, 不同角色具有不同的权利和责任. 清晰确定各单位之间的接口. 组织结构先行, 具有组织就具有生命力.应用开发团队、系统集成团队的建议和企业各部们之间欠配合;组建项目管理团队, 统一协调，培养相互尊重的过程文化和伙伴合作关系是项目成功的关键。项目成功是共同的成功, 失败是共同的失败.4集成项目实施的风险应对（3）管

3、理风险的对策难以平衡业务集成需要和对短期绩效的追求规划好工程的规模和实施顺序，从而迅速地获得最大程度的商业回报 .过渡计划启动过迟；过程伊始就把新旧系统过渡提到议事日程;在分析，设计阶段要充分考虑解决方案的可移植性。在系统测试阶段前必须制定新旧系统过渡方案，充分考虑新旧系统的差别，评估新旧系统移植的风险，制定新旧系统切割步骤。在系统测试阶段，做过渡测试，仿真，做过渡试点;在上线前对作业人员作充分培训，由专职机构，有效协调过渡计划和作业。 5集成项目实施的风险应对（4）管理风险的对策缺乏整体EAI/BPI战略和计划高层领导推进非常关键。EAI/BPI项目会触发一些困难的问题，而承担责任的这位高级

4、管理人员就可以及时处断 。企业建立管理小组, 必须制定企业EAI/BPI从启动到上线维护的长期战略和计划，了解和指导EAI/BPI项目进程，规划公司的未来。 应用系统项目实施的拖延影响到EAI/BPI的进度多个项目并行，项目之间相互关联和依赖，涉及到多个业务领域和部门，并需要采用多种技术手段。 建议:采用分步分阶段策略,降低管理复杂度和技术难度.6集成项目实施的风险（2）技术风险:实施团队缺乏技术支撑；缺乏可行的EAI/BPI实施技巧；集成系统上的再集成；没有充分发挥全新的集成信息的威力，对新系统不太适应7集成项目实施的风险应对（5）技术风险的对策实施团队缺乏技术支撑要有技术保障方案和措施。不

5、啬使用EAI技术专才，并训练自己的技术人员。保证企业内部的业务尖子的参与。缺乏可行的EAI/BPI实施技巧 必须有一个适合业务流程开发特点的，容易掌握的，EAI/BPI实施技巧为项目指导。一个有效的管理小组来客户化，制定实施指导规范，推行实施技巧。建议对实施每个环节都给出指导意见.8集成项目实施的风险应对（6）技术风险的对策集成系统上的再集成在选择平台时，公司应该首先考虑兼容性其架构整体性，平台的开发要保证构架整体性，运行优化必须始终是一个开发过程的衡量指标。 建议:选择可靠的, 开放的, 灵活的, 可适应环境变化的集成基础平台.没有充分发挥全新的集成信息的威力，对新系统不太适应EAI/BPI

6、项目30%的挑战来自技术层面，而剩余的70%则来自人员和流程。全新的EAI/BPI技术会影响许多人员，他们需要培训以掌握新的业务流程和操作工具。企业必须通过详细计划、试点试用、内部教育和风险分析等一系列手段，来减少这种情况发生的可能性.企业必须充分认识到项目上线最初的这段适应期的存在，如果执行得当，那么这种负效果可以减低到最小，而且在最短的时间内消除。 9议程集成项目的实施风险与对策概述Vitria集成项目的实施方法论Vitria B2B成功案例海外推项目推动的建议风险与对策机制的预先建立三方公认的项目开展原则明确第一阶段目标10Implementation ApproachProject S

7、tructureOur implementation approach consists of five project stages:Initiate Communicate project goals, methodology and team structure, establish project charter, and determine business requirements.Analyze Bridge the gap, if any, between customer requirements and Vitria Cleanorder capabilities, as

8、well as defining business processes and interfaces.Design/Build Functional and technical development and realization of the systems architecture and configurationIntegrate Rigorous testing and in preparation for the deployment.Deploy Successfully executed implementation and operations support.Each s

9、tage is defined in terms of key tasks, deliverables, tools and techniques and customer benefits 11Implementation Approach Implementation PlanInitiateAnalyzeDesign/Build Integrate DeployDana ParallelTestProject Weeks 1 2 3 4 5 6 7 8 9 10 11 12Initiate Establish project charter Confirm/identify requir

10、ements Set up the technical environmentAnalyze Use case analysis Connectivity and mapping analysis Test plan developmentDesign/Build System design Data transformation/mapping System implementationIntegrate Test preparation Test execution Test acceptanceDeploy Procedure/script preparation System depl

11、oyment12Implementation Approach Implementation - InitiateKey TasksDeliverablesTools and TechniquesBenefits Confirm the project scope Define roles and responsibilities Create project work plan and staffing plan Create communication plan Define high-level requirements Setup the technical environment D

12、etailed project work plan Project approach orientation Skill matrix of Fast Forward team High-level business/user and system/performance requirementsChange management procedure Project/deliverable standards and templates Project management toolkit including: Estimating tools Work plans and status re

13、ports Issue resolution protocol VIP methodology Upfront buy-in and agreement to project structure, expectations and approach Confirm scope and requirements early in the project Early setup of the technical environmentThe initiate stage focuses on communicating the project goals, methodology, and tea

14、m structure, establishing project charter and determining business requirements.InitiateAnalyzeDesign/BuildIntegrateDeploy13Implementation Approach Implementation AnalyzeKey TasksDeliverablesTools and TechniquesBenefitsAnalyze business processes (incl. exceptions) Analyze data validation requirement

15、s Analyze application connectivity requirements Analyze data transformation requirements Analyze reporting and audit information Develop and document use cases Develop test strategy and test plan Requirements specification document Sequence diagrams/collaboration models Data models fit/gap analysis

16、summary Interface specifications Documentation of system requirements Test strategy and test plan checklist Enterprise production checklist Fit/gap analysis tools Pre built process baseline models Pre Built Mapping Guides Test plan / execution checklist Early identification of risks and issues Exten

17、sive hands-on business owner/user participation fosters system ownershipPre built baseline reduces overall implementation timeframe.The analyze stage focuses on bridging the gap, if any, between customer requirements and the BusinessWare capabilities, as well as defining business processes and inter

18、faces.InitiateAnalyzeDesign/BuildIntegrateDeploy14 Unit-tested components (process models, connectors, reports, etc.) Data transformation maps (5) Testing environment checklist Design specification documentProject suggested standards documentSystem ready for integration testing (BPM, EDI Documents,

19、Transformations, Error Handling, Audit Control, Configuration).Implementation Approach Implementation Design/BuildKey TasksDeliverablesTools and TechniquesBenefits Load and configure process models and channel architecture Load and configure connection models and system reports Configure trading par

20、tner relationship Create data transformation maps Document system design specifications Unit test all componentsInitiateAnalyze Pre-built process modelsLogical Mapping guidesBusinessWare Tools and Best Practice Methods Incremental UML based (VIP) methods Shorter development cycle resulting from pre-

21、built baseline processing models.Extensive domain expertise Knowledge transfer with customer involvementDesign/BuildThe design/build stage focuses on the functional and technical development and realization of the systems architecture and configuration.IntegrateDeploy15Implementation Approach Implem

22、entation IntegrateKey TasksDeliverablesTools and TechniquesBenefits Develop test objectives and test plan Develop test cases and generate test data Setup the test environment Conduct system and integration testing Prepare the deployment environmentInitiateAnalyze Test checklist, test cases and sampl

23、e test data System and integration test results Deployment plan and readiness checklistSupport through testing Test plan template documents Stress & load test planner Test data samples Deployment readiness checklist Continued transfer of knowledge through user/operator participation in testing proce

24、ssThoroughly tested application provides solid foundation for deploymentConfirmation that system is ready to accept/send valid documentsDesign/BuildIntegrateDeployThe integrate stage focuses on rigorous testing and in preparing for the deployment.16Implementation Approach Implementation DeployKey TasksDeliverablesTools and TechniquesBenefits Identify operations procedures Develop operations support scripts Review the operations procedures and scripts with the application support staff Monitor performance and tune accordinglyInitiateAnalyze Operati