項目起步內培

1、議程集成項目的實施風險與對策概述集成項目的實施方法論1集成項目實施的風險（1）管理風險業(yè)務需求在分析階段還不確定，拖延分析時間,更糟糕的是在整個工程階段還在不斷更改需求；多單位合作關系,沒有明確的分工和責任劃分; 應用開發(fā)團隊、系統(tǒng)集成團隊的建議和企業(yè)各部們之間欠配合;難以平衡業(yè)務集成需要和對短期績效的追求；過渡計劃啟動過遲；缺乏整體EAI/BPI戰(zhàn)略和計劃, 沒有高層推動和領導，資源和效率都得不到保障。應用系統(tǒng)項目實施的拖延影響到EAI/BPI的進度；2集成項目實施的風險應對（1）管理風險的對策業(yè)務需求在分析階段還不確定，拖延分析時間,更糟糕的是在整個工程階段還在不斷更改需求；必須確認業(yè)務需

2、要達到的目的,以業(yè)務部門的需求緩急，心理準備程度來安排業(yè)務整合項目的優(yōu)先次序，并對其有深入透徹和完整精確的需求理解分析，并獲得業(yè)務部門的共識，業(yè)務部門對共識做出承諾. 3集成項目實施的風險應對（2）管理風險的對策多單位合作關系,沒有明確的分工和責任劃分; 明確各單位在整個項目中的角色, 不同角色具有不同的權利和責任. 清晰確定各單位之間的接口. 組織結構先行, 具有組織就具有生命力.應用開發(fā)團隊、系統(tǒng)集成團隊的建議和企業(yè)各部們之間欠配合;組建項目管理團隊, 統(tǒng)一協(xié)調，培養(yǎng)相互尊重的過程文化和伙伴合作關系是項目成功的關鍵。項目成功是共同的成功, 失敗是共同的失敗.4集成項目實施的風險應對（3）管

3、理風險的對策難以平衡業(yè)務集成需要和對短期績效的追求規(guī)劃好工程的規(guī)模和實施順序，從而迅速地獲得最大程度的商業(yè)回報 .過渡計劃啟動過遲；過程伊始就把新舊系統(tǒng)過渡提到議事日程;在分析，設計階段要充分考慮解決方案的可移植性。在系統(tǒng)測試階段前必須制定新舊系統(tǒng)過渡方案，充分考慮新舊系統(tǒng)的差別，評估新舊系統(tǒng)移植的風險，制定新舊系統(tǒng)切割步驟。在系統(tǒng)測試階段，做過渡測試，仿真，做過渡試點;在上線前對作業(yè)人員作充分培訓，由專職機構，有效協(xié)調過渡計劃和作業(yè)。 5集成項目實施的風險應對（4）管理風險的對策缺乏整體EAI/BPI戰(zhàn)略和計劃高層領導推進非常關鍵。EAI/BPI項目會觸發(fā)一些困難的問題，而承擔責任的這位高級

4、管理人員就可以及時處斷 。企業(yè)建立管理小組, 必須制定企業(yè)EAI/BPI從啟動到上線維護的長期戰(zhàn)略和計劃，了解和指導EAI/BPI項目進程，規(guī)劃公司的未來。 應用系統(tǒng)項目實施的拖延影響到EAI/BPI的進度多個項目并行，項目之間相互關聯(lián)和依賴，涉及到多個業(yè)務領域和部門，并需要采用多種技術手段。 建議:采用分步分階段策略,降低管理復雜度和技術難度.6集成項目實施的風險（2）技術風險:實施團隊缺乏技術支撐；缺乏可行的EAI/BPI實施技巧；集成系統(tǒng)上的再集成；沒有充分發(fā)揮全新的集成信息的威力，對新系統(tǒng)不太適應7集成項目實施的風險應對（5）技術風險的對策實施團隊缺乏技術支撐要有技術保障方案和措施。不

5、嗇使用EAI技術專才，并訓練自己的技術人員。保證企業(yè)內部的業(yè)務尖子的參與。缺乏可行的EAI/BPI實施技巧 必須有一個適合業(yè)務流程開發(fā)特點的，容易掌握的，EAI/BPI實施技巧為項目指導。一個有效的管理小組來客戶化，制定實施指導規(guī)范，推行實施技巧。建議對實施每個環(huán)節(jié)都給出指導意見.8集成項目實施的風險應對（6）技術風險的對策集成系統(tǒng)上的再集成在選擇平臺時，公司應該首先考慮兼容性其架構整體性，平臺的開發(fā)要保證構架整體性，運行優(yōu)化必須始終是一個開發(fā)過程的衡量指標。 建議:選擇可靠的, 開放的, 靈活的, 可適應環(huán)境變化的集成基礎平臺.沒有充分發(fā)揮全新的集成信息的威力，對新系統(tǒng)不太適應EAI/BPI

6、項目30%的挑戰(zhàn)來自技術層面，而剩余的70%則來自人員和流程。全新的EAI/BPI技術會影響許多人員，他們需要培訓以掌握新的業(yè)務流程和操作工具。企業(yè)必須通過詳細計劃、試點試用、內部教育和風險分析等一系列手段，來減少這種情況發(fā)生的可能性.企業(yè)必須充分認識到項目上線最初的這段適應期的存在，如果執(zhí)行得當，那么這種負效果可以減低到最小，而且在最短的時間內消除。 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