Integrated project management and solution delivery process 10082017 dt
•
2 likes•259 views
The document presents a proposed process for project management and solution delivery. It discusses the benefits of using defined processes, including consistency, productivity, and risk reduction. It outlines the key phases of the solution delivery process, including planning, design, implementation, testing, and support. It also describes the major components of project management, such as initiation, scope, communication, risks/issues. The document provides many templates that can be used to document requirements, designs, plans, issues, and other elements of the process. Feedback is sought on the proposed process before full implementation.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Integrated project management and solution delivery process 10082017 dt
Similar to Integrated project management and solution delivery process 10082017 dt (20)
Recently uploaded
Recently uploaded (20)
Integrated project management and solution delivery process 10082017 dt
- 1. PROJECT MANAGEMENT AND SOLUTION DELIVERY PROCESS Daniel Thuraiappah
- 2. • Process Introduction • Solution Delivery and Project Management Processes • Solution Delivery • Project Management • Using the Process • Using the Template Documents • Feedback and Process Development AGENDA
- 5. Benefits • Consistency • Speed • Drives Delivery • Ensures Acceptance • Productivity • Reuse • Professionalism • Customer Confidence • Speed • Accuracy • Audit Trail • Cost Saving • Risk Management and Reduction • Change Management and Additional Work • Formal Project Closure Potential Disadvantages • Time to Adopt • Suitability • Too Comprehensive • Cost of Use • Not Currently In Use • Risk PROJECT AND SOLUTION DELIVERY PROCESS
- 6. • Deliver defined objective/solution • Must have a defined start and end • Project management is concerned about delivering what has been committed PROJECT
- 7. • Increase credibility • Increase visibility of the customer engagement • Improving customer confidence and facilitating smoother engagements • Improve profitability by customising pre-defined proven processes rather than developing new ones • Reduce risk through improve planning • competitors have them • Eliminate surprises WHY USE PROCESSES?
- 8. Structure and mechanism for knowledge capture and reuse • A means for the retention and application of company knowledge • Reuse encouraged and will become the normal practice, with significant reduction in the development of non-reusable collateral Adaptive and creative • Allowing personnel to follow a structure and focus on adding value • New and developing resources are brought up to speed more quickly Resource Management • Better understanding and definition of required skills • Training based around methodologies, standard techniques, and tools WHY USE PROCESSES?
- 9. • Initially painful • Can seem to be longwinded • They really do help • Add value WHY USE PROCESSES?
- 10. • Methodology without process is meaningless • Process without usage is pointless Methodology (General Framework) Process (Actualises the Methodology) Use the Process (Achieve the Benefits) METHODOLOGY AND PROCESSES
- 11. SOLUTION DELIVERY AND PROJECT MANAGEMENT PROCESSES
- 12. • Two processes running in parallel • Solution Delivery – delivery of the solution to the customer • Project Management – management of the delivery of the solution • Processes must work together • Processes supported by document templates • Templates used to capture and document information • Templates provide a framework for management and control PROJECT AND SOLUTION DELIVERY PROCESSES
- 13. • Full set of project template documents Project Management - • PMOPROJECT MANAGEMENT • Solution Delivery • PMOSOLUTION DELIVERY DOCUMENT TEMPLATES
- 14. Planning and Analysis Detailed Design Implementation and Installation Testing Training and Handover Support, Administration and Maintenance Initiation Scope Quality Communication Risks, Issues and Decisions Closure Project Management Solution Delivery
- 15. • Tailor process to suit project • Agree in advance how project is to be handled: • Project management • Solution delivery • Use process appropriate for • Project size • Project complexity • Number of participants • role • Customer USE OF PROCESSES
- 17. • Match project scope and solution design to what is delivered • Ensure delivery matches what is committed • Requirement drive delivery and closure • Must identify and document requirements • Must deliver on requirements • Requirements may change during the life of the project • Additional revenue V LIFECYCLE APPROACH
- 18. • Planning and Analysis – customer requirements are captured and documented • Detailed Design – the proposed solution is documented is detail • Implementation and Installation – the solution is installed • Testing – the solution is tested • Training and Handover – the solution is handed over to the customer and training is provided • Support, Administration and Maintenance – the solution is transferred to support SOLUTION DELIVERY PHASES
- 19. • Document requirements • Confirm requirements • Design solution to meet requirements • High level and detailed design • Confirm solution design • Implement solution • Test solution and confirm requirements are met • Handover solution and provide training SOLUTION DELIVERY PROCESS
- 20. • Initiation – the project is formally initiated • Scope – project scope is managed and changes are captured • Quality – project quality is managed • Communication– project communications are managed and documented • Risks, Issues and Decisions – project issues, risks and decisions are managed and documented • Closure – the project is closed and moved to maintenance PROJECT MANAGEMENT PHASES
- 21. • Not sequential • Controlling the project will lead to changes in project planning and execution Initiate Plan Execute Control Close PI E Cn Cl PROJECT MANAGEMENT
- 23. Final Requirements Checklist.doc This is a checklist to validate requirements. Functional Specification.doc This describes the functionality of the solution being delivered. Infrastructure Requirements Checklist.doc This is a checklist to infrastructure requirements. Non-Functional Requirements Checklist.doc This is a checklist to non-functional or operational requirements. Objectives and Requirements Specification.doc This documents the customer’s objectives and requirements. Requirements Traceability Log.doc This logs requirements to provide traceability to ensure they are delivered. SOLUTION DELIVERY – PLANNING AND ANALYSIS
- 24. Detailed Design.doc This documents the actual solution design in detail. High Level Design.doc This documents the actual solution design at a high level. Proposed Solution.doc This defines the concept of the solution SOLUTION DELIVERY – DETAILED DESIGN
- 25. Installation Plan.doc This documents how the solution will be installed. SOLUTION DELIVERY - IMPLEMENTATION AND INSTALLATION
- 26. Acceptance Test Package.doc This defines the approach to testing of the solution. Acceptance Test Specification.doc This details the set of tests to be performed to validate the solution. Fault Report Log.doc This is a log of any faults discovered during testing. Fault Report.doc This documents a fault discovered during testing. System Test Plan.doc This defines the plan for performing testing. Test Execution Log.doc This logs the testing performed. SOLUTION DELIVERY - TESTING
- 27. User Documentation Manual.doc This documents the solution. SOLUTION DELIVERY – TRAINING AND HANDOVER
- 28. Operational Support Plan.doc This documents a plan to provide operational support. Service Level Agreement.doc This defines the service level to be provided. Solution Support Plan.doc This documents the level of support to be provided. Transfer to Support.doc This documents the transfer of the solution to support. SOLUTION DELIVERY - SUPPORT, ADMINISTRATION, AND MAINTENANCE
- 30. Project Initiation Document (PID).doc This initiates the project. Statement of Work (SOW).doc This defines the scope of the work to be done. Project Organization Chart.ppt This describes the project organisation. PROJECT MANAGEMENT - INITIATION
- 31. Issue Resolution Request.doc This documents an issue that has been raised that needs to be responded to. Change Request Log.doc This logs requests for changes. Change Request.doc This is used to document a request for a change. Solution Delivery Plan.mpp This is the project plan for delivering the solution. PROJECT MANAGEMENT - SCOPE
- 32. Quality Log.doc This documents results of testing for quality logging. Quality Plan.doc This is a plan for managing project quality. PROJECT MANAGEMENT - QUALITY
- 33. Communication Distribution Plan.doc This documents project communication. Communication Log.doc This logs communications. Customer Monthly Status Report.doc This is a sample monthly report. Customer Status Report Presentation.ppt This is a sample status report presentation Delay Notification Log.doc This is a log of delays that have occurred in the project. Delay Notification.doc This is a formal notification of a project delay. Information Request Log.doc This is a log of requests for information. Information Request.doc This is a request for information Meeting Agenda and Minutes.doc This is used to record meeting minutes. Project Monthly Report.doc This is an internal project report. Project Weekly Status Report.doc This is a sample weekly report. Steering Committee Meeting Agenda.doc This is a document for use with a project steering committee. PROJECT MANAGEMENT - COMMUNICATION
- 34. Actions-Issues-Decisions Log.doc This is a log of actions, issues and decisions. Decision Request.doc This documents a project decision. Issue Report.doc This documents a project issue. PROJECT MANAGEMENT - RISKS, ISSUES, AND DECISIONS
- 35. Project Closeout Report.doc This documents project closure. Project Sign-off.doc This is used to record formal project signoff by the customer. PROJECT MANAGEMENT - CLOSURE
- 37. • Effective project and solution delivery steps • 1 – Initiation • 2 – Requirements • 3 – Project Planning • 4 – Solution Design • 5 – Delivery and Testing • 6 – Training and Handover • 7 – Closure and Move to Maintenance USING THE PROCESS
- 38. • Gather and define requirements: • Objectives and Requirements Specification.doc • Final Requirements Checklist.doc • Infrastructure Requirements Checklist.doc • Non-Functional Requirements Checklist.doc • Manage requirements through life of project • Requirements Traceability Log.doc • Complete functional specification – defines what is to be done (not how) • Functional Specification.doc PROJECT AND SOLUTION PROCESS - REQUIREMENTS
- 39. Requirements Definition REQUIREMENTS DEFINITION AND DOCUMENTATION GATHER ANALYSE REVIEW Requirements Management CAPTURE ASSESSCHANGE
- 40. • Gather – Tasks relating to the initial gathering of requirements • Analyse – Analysing and categorising requirements and specifying them • Review – Agreeing (with the customer) exactly what the requirements are. Modify if necessary to reach agreement. REQUIREMENTS DEFINITION
- 41. • Business – objectives and goals to be delivered as a result of the solution • Functional – what it does • Technical – operational and procedural constraints • Implementation – how the solution will be implemented • Project – requirements of the project REQUIREMENTS CLASSIFICATION
- 42. • Financial (Market share increase) • Customer-related (On-time delivery) • Business Processes (Business cycle times) • Innovation and Learning Measures (Speed of completing transactions) • Regulatory Requirements (Adherence to regulations) BUSINESS REQUIREMENTS
- 43. • Inputs • Outputs • Actions • Responses • Outcomes • Usage FUNCTIONAL REQUIREMENTS
- 44. • Performance (Response times, transaction throughput rates, batch job durations.) • Volumes (Data capacity, network bandwidth, business units) • Availability (Required uptime, daytime periods for which the system must be available) • Resilience(No single point of failure, MTBF of components, switchover times) • Recoverability(Backup times, tolerable data loss, offsite needs, recovery timescales) • Scalability (How the solution will deal with more users/data, capability for predicted growth) • Integrity (Degree of problems tolerated, problem detection needs) • Interfaces (Internal and external, user, hardware, software, communications) • IT Management (Event handling and classification, detection needs, management roles and processes) TECHNICAL REQUIREMENTS
- 45. • Timescales (What are the desired target dates) • Disruption and Impact (What levels of disruption can be tolerated) • Data Conversion(What data needs to be migrated, how, and with what constraints) • Supportability (What levels of support will be needed) • Training (What staff require what new skills) • Handover (Process of transfer of control, parallel run) • Support • Warranty (Coverage during warranty) • Post-Warranty • Operation IMPLEMENTATION REQUIREMENTS
- 46. • Implementation • Testing • Facilities PROJECT REQUIREMENTS
- 47. • Capture – Ensure that the new requirements or change requests are captured • Assess – Consider whether the changes will be actioned. Approve or reject • Change – Undertake the changes REQUIREMENTS MANAGEMENT
- 48. Complete first draft of project plan PROJECT AND SOLUTION PROCESS – 3 – PROJECT PLANNING AND MANAGEMENT
- 49. • Standard project plan structure • Initiation • Planning • Executing • Project Management • Closing • Customise detail for individual project PROJECT PLANNING AND MANAGEMENT
- 50. • Changes during the course of a project are inevitable and can affect the scope, cost, delivery, and nature of the deliverables as well as the functioning of the project team • Change Management is a systematic process that allows for changes and at the same time aims to minimise the negative consequences of these changes • Change process must be included in the project initiation material and published to the customer MANAGING CHANGE
- 51. FIRST DRAFT CHANGE PROCESS INITIATE REVIEW APPROVE EVALUATION EVALUATE REVIEW, NEGOTIATE, APPROVE IMPLEMENT REVIEW AND VALIDATE CLOSECLOSE CLOSE NO NO YES YES
- 52. • WIP • Issue Resolution Request.doc – document issues • Change Request Log.doc – maintain log of change requests • Change Request.doc – document change request and document outcome CHANGE CONTROL TEMPLATES
- 53. • Risk • All projects have risks • Need to identify and manage • Action can be taken to mitigate/circumvent risks • Minimise the negative risk impacts • Risk management steps • Risk Management Planning – determine the approach to risk management • Risk identification - identify all known project risks • Risk Analysis - perform an assessment of the probability of occurrence and potential impact • Risk Response Planning - create action plans to manage the identified risks • Risk Monitoring and Control – monitor, review and update risk status and plans • Risk Closeout – document lessons learned • Take appropriate approach to managing risk RISK MANAGEMENT
- 54. • Issue management • Identifying, tracking, resolving, and communicating to project stakeholders the issues that arise out of day-to-day project execution • ongoing process, from start to closure of any project and it is a critical component of project monitoring and control activities • Steps • Identify Project Issues • Establish Issue Tracking • Evaluate the Issue • Determine Issue Resolution • Implement Issue Resolution • Close the Issue • Take appropriate approach to managing risk ISSUE MANAGEMENT
- 55. • WIP: Project Management50 Risks, Issues and Decisions • Actions-Issues-Decisions Log.doc • Decision Request.doc • Issue Report.doc RISK AND ISSUE MANAGEMENT TEMPLATES
- 56. • Complete solution design using documents contained in Solution Delivery20 Detailed Design • High Level Design.doc • Detailed Design.doc • Proposed Solution.doc • Not always necessary to use all documents • Depends on project size and approach • Could have single design document PROJECT AND SOLUTION PROCESS – 4 – SOLUTION DESIGN
- 57. • Define communication structure during initiation • Status reports • Frequency - weekly, fortnightly, monthly • Content/agenda • Meetings • Frequency - weekly, fortnightly, monthly • Content/agenda • Levels – project team, project steering group PROJECT REPORTING
- 58. • Use documents in Project Management40 Communication • Document how communication is handled - Communication Distribution Plan.doc • Log communications - Communication Log.doc • Meetings • Meeting Agenda and Minutes.doc • Steering Committee Meeting Agenda.doc • Reports • Customer Monthly Status Report.doc • Customer Status Report Presentation.ppt • Project Monthly Report.doc • Project Weekly Status Report.doc • Other communications • Delay Notification Log.doc • Delay Notification.doc • Information Request Log.doc • Information Request.doc PROJECT REPORTING
- 59. • Deliver solution • Solution Delivery30 Implementation and Installation • Testing • Solution Delivery40 Testing • Acceptance Test Package.doc • Acceptance Test Specification.doc • Fault Report Log.doc • Fault Report.doc • System Test Plan.doc • Test Execution Log.doc • Test against requirements • Log results of tests to establish audit trail PROJECT AND SOLUTION PROCESS – 5 – DELIVERY AND TESTING
- 60. • Project Management30 Quality • Quality Log.doc • Quality Plan.doc • Ensures that quality is built into project from the start • Delivers real benefits • Reduced testing • Reduced rework • Increased customer satisfaction • Increased project profitability PROJECT QUALITY
- 61. • Handover • 50 Training and Handover PROJECT AND SOLUTION PROCESS – 6 – TRAINING AND HANDOVER
- 62. • Closure and Move to Operations • Project Management60 Closure • Project Closeout Report.doc • Project Sign-off.doc • Solution Delivery60 Support, Administration and Maintenance • Operational Support Plan.doc • Service Level Agreement.doc • Solution Support Plan.doc • Transfer to Support.doc PROJECT AND SOLUTION PROCESS – 6 – CLOSURE AND MOVE TO OPERATIONS