Maximo project approach using prince2
1 like1,600 views
The document outlines the methodology for upgrading a Maximo system using PRINCE2 project processes. It describes the 7 PRINCE2 processes: starting up a project, directing a project, initiating a project, controlling a stage, managing product delivery, managing stage boundary, and closing a project. Each process includes activities and management products. The methodology then applies these processes to the phases of the Maximo upgrade project: initiation, gap analysis, design, build, data migration, testing, training, and closing.
Maximo project approach using prince2
- 1. Project Methodology Using PRINCE2 (Maximo Upgrade Project) Balasubramanian.C
- 2. Project Process in PRINCE2 1) Starting Up a Project 2) Directing a Project 3) Initiating a Project 4) Controlling a Stage 5) Managing Product Delivery 6) Managing Stage Boundary 7) Closing a Project A) Project Mandate
- 3. A) Project Mandate A.1)Project Mandate Input to Project Startup produced by Corporate or Program Management
- 4. 1) Starting Up a Project 1.A)Activities Involved 1.A.1)Appoint the Executive and Project Manager 1.A.2) Capture previous lessons 1.A.3) Design and appoint the project management team 1.A.4) Prepare the outline Business Case 1.A.5) Select the project approach and assemble the Project Brief 1.A.6) Plan the initiation stage 1.B)Management Products 1.B.1)Daily Log created 1.B.2)Lessons Log created 1.B.3)Outline Business Case created 1.B.4)Project Product Description created 1.B.5)Project Brief created 1.B.6)Initiation Stage Plan created DP1
- 5. 2) Directing a Project Authorize Initiation Authorize Project Authorize Stage Plan or Exception Plan Give Adhoc Direction Authorize Project Closure 1.C)Activities Involved DP1 DP2 DP3 DP4 DP5 Project Board Activities (Senior User + Senior Supplier + Executive)
- 6. 3) Initiating a Project 1.D)Activities Involved 1.D.1) Prepare the Risk Management Strategy 1.D.2) Prepare Configuration Management Strategy 1.D.3) Prepare Quality Management Strategy 1.D.4) Prepare Communication Management Strategy 1.D.5) Set up Project Controls 1.D.6) Create the project Plan 1.D.7) Refine the Business Case 1.D.8) Assemble the Project Initiation Documentation 1.E)Management Products 1.E.1) Risk Management Strategy Created 1.E.2) Configuration Management Strategy Created 1.E.3) Communication Management Strategy Created 1.E.4) Project Plan Created 1.E.5) (Detailed) Business Case Created 1.E.6) Risk Register created 1.E.7) Configuration Items Records Created 1.E.8) Issue Register Created 1.E.9) Quality Register Created 1.E.10) Benefits Review Plan Created 1.F)Themes : Plan 1.F.1) Product Breakdown Structure Created 1.F.2) Product Descriptions Created 1.F.3) Product Flow Diagram Created DP2 DP4
- 7. 4) Controlling a Stage 1.G)Activities Involved 1.G.1)Authorize a Work package 1.G.2)Review Work Package status 1.G.3)Receive completed Work Packages 1.G.4)Review the stage status 1.G.5)Report Highlights 1.G.6)Capture and examine issues and risks 1.G.7)Escalate issues and risks 1.G.8)Take corrective action 1.H)Management Products 1.H.1) Work Packages created 1.H.2) Highlight Report(s) created 1.H.3) Issue Report(s) created 1.H.4) Exception Report(s) created 1.H.5) Stage Plan updated 1.H.6) Configuration Item Records updated 1.H.7) Risk Register updated 1.H.8) Issue Register updated 1.H.9) Quality Register updated 1.H.10) Work Package(s) updated 1.H.11) Lessons log updated 1.H.12) Issue Report updated 1.H.13) Daily Log updated DP4
- 8. 5) Managing Product Delivery 1.I)Activities Involved 1.1.1) Accept a Work Package 1.1.2) Execute a Work Package 1.1.3) Deliver a Work Package 1.J)Management Products 1.J.1) Quality Register updated 1.J.2) Configuration Item Records updated 1.J.3) Team Plan created 1.J.4) Checkpoint Reports created
- 9. 6) Managing Stage Boundary 1.K)Activities Involved 1.K.1) Plan the next stage 1.K.2) Update the Project Plan 1.K.3) Update the Business Case 1.K.4) Report stage end 1.K.5) Produce an Exception Plan 1.L)Management Products 1.L.1) Project Initiation Documentation updated 1.L.2) Configuration Item Records updated 1.L.3) Risk Register updated 1.L.4) Issue Register updated 1.L.5) Quality Register updated 1.L.6) Project Plan updated 1.L.7) Business Case updated 1.L.8) Benefits Review Plan updated 1.L.9) Stage or Exception Plan created 1.L.10) Product Descriptions (next stage) created 1.L.11) End Stage Report created 1.L.12) Lessons Report created DP3 DP4
- 10. 7) Closing a Project 1.M)Activities Involved 1.M.1) Prepare planned closure 1.M.2) Prepare premature closure 1.M.3) Hand over products 1.M.4) Evaluate the project 1.M.5) Recommend project closure 1.N)Management Products 1.N.1) Follow-on action recommendations created 1.N.2) Lessons Report created 1.N.3) Project Initiation Documentation updated 1.N.4) Project Plan updated 1.N.5) Issue Register updated 1.N.6) Configuration Item Records updated 1.N.7) Benefits Review Plan updated 1.N.8) Risk Register closed 1.N.9) Issue Register closed 1.N.10) Quality Register closed 1.N.11) Daily Log closed 1.N.12) Lessons Log closed DP5
- 11. Maximo Upgrade using PRINCE2 Project Process Starting Up a Project 1.1) Appoint Executive and Project Manager 1.2) Capture Previous Lessons 1.3) Design and Appoint Project Management Team 1.4) Prepare Outline Business Case 1.5) Select Project Approach and Assemble the Project Brief 1.6) Plan the Initiation Stage DP1 A.1)Project Mandate Input to Project Startup produced by Corporate or Program Management
- 12. Directing a Project 2.2) Authorize Project 2.3) Authorize Stage or Exception Plan 2.4) Give Adhoc Direction 2.5) Authorize Closure 2.1) Authorize Initiation DP1 DP2 DP3 DP4 DP5 Project Board Activities (Senior User + Senior Supplier + Executive)
- 13. Initiating a Project DP2 DP4 3.2) Core Team Assembly 3.3) Product Orientation 3.4) Training Strategy 3.5) Cutover Strategy 3.1) Kickoff Meeting 3.D.1) Prepare the Risk Management Strategy 3.D.2) Prepare Configuration Management Strategy 3.D.3) Prepare Quality Management Strategy 3.D.4) Prepare Communication Management Strategy 3.D.5) Set up Project Controls 3.D.6) Create the project Plan 3.D.7) Refine the Business Case 3.D.8) Assemble the Project Initiation Documentation
- 14. Controlling a Stage- Gap Analysis 4.1) Business Process Review 4.2) Fit Gap Analysis 4.3)Data Source Review 4.4) Initial Data Mapping 4.5) New Requirements Carry Out Managing Stage Boundary Process DP3 DP4
- 15. Controlling a Stage – Design 5.1) Design CRP(Conference Room Pilots) 5.2) Workflow Analysis and Design 5.3) SOP Development 5.4) Data Mapping Carry Out Managing Stage Boundary Process DP3 DP4
- 16. Controlling a Stage- Build 6.1) Server Infrastructure Build 6.2) Maximo Install 7.x 6.3) Maximo Configuration 6.4) Customization 6.5) Reports / KPI’s 6.6) Security 6.7) Workflow Development Carry Out Managing Stage Boundary Process DP3 DP4
- 17. Controlling a Stage – Data Migration 7.1) Legacy Data Migration 7.2) Integration Framework 7.3) Data Load Development 7.4) Data Testing Carry Out Managing Stage Boundary Process DP3 DP4
- 18. Controlling a Stage - Testing 8.1) System Integration Testing 8.2) Data Migration Testing 8.3) Performance Testing 8.4) User Acceptance Testing 8.5) Cutover to Production Testing DP3 DP4 Carry Out Managing Stage Boundary Process
- 19. Controlling a Stage - Training 9.1) End User Training 9.2) Systems Administrator Training 9.3) Reports Developer Training DP3 DP4 Carry Out Closing a Project Process
- 20. Closing a Project 10.1) Execute Cutover Plan 10.2) Data Migration 10.3) Go Live 10.4) Stabilization 10.5) Post Implementation Review DP5