ICT4GOV Project Management Essentials Training Notes

  • 2,076 views
Uploaded on

Training notes to facilitate discussion and activity in building competencies in managing ICT projects. The notes bring to attention the framework, methodology, process, template, tools and software …

Training notes to facilitate discussion and activity in building competencies in managing ICT projects. The notes bring to attention the framework, methodology, process, template, tools and software to structurally managed project justification, planning, implementation, control and closing.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,076
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ESSENTIALS OF ICT PROJECT MANAGEMENT Practitioner’s Notes on Standards and Practices (THE E-GOVERNMENT VERSION)
  • 2. TABLE OF CONTENTESSENTIALS OF ICT PROJECT MANAGEMENT ...................................................................................... 1TABLE OF CONTENT ................................................................................................................. 2Training Goal: ........................................................................................................................ 4Training Objectives: ................................................................................................................. 4A. Project Management Basic Definitions: ....................................................................................... 4 Description of e-Government ................................................................................................... 4 e-Government Maturity Framework ....................................................... Error! Bookmark not defined. Project ............................................................................................................................. 4 Project Valuation – ............................................................................................................... 5 Project Management ............................................................................................................. 5 Project Management Office..................................................................................................... 5 Project Manager .................................................................................................................. 6B. PROJECT MANAGEMENT COMPETENCIES: (Project Manager View) ........................................................ 7 ICT Project Management Domains ............................................................................................. 7 ICT Project Manager Categories of Skills...................................................................................... 7C. PROJECT MANAGEMENT MATURITY ASSESSMENT (Organizational View) ................................................. 8 ICT Project Management Failure Points ....................................................................................... 8 Presence Ranking................................................................................................................. 8 Project Management Capability Maturity Rubric............................................................................. 9D. PROJECT MANAGEMENT METHODOLOGY STANDARDS ..................................................................... 10 Project Management Life-Cycle Phases ..................................................................................... 10 Project Management Knowledge Areas...................................................................................... 10 Business Management Stages of the Project................................................................................ 11 Solution Development Management ......................................................................................... 14E. ICT PROJECT MANAGEMENT TEMPLATES .................................................................................... 16 Project Initial Definition and Planning ...................................................................................... 16 ICT Project Visioning and Scoping ........................................................................................... 18 ICT Project Business Case ..................................................................................................... 19 ICT Solution Development Project Scoping ................................................................................. 21 ICT Project Cost and Budget: Item Spreadsheet ........................................................................... 23 ICT Project Investment Requirement and Cost ............................................................................ 25 Project Organization: Roles Matrix .......................................................................................... 26F. ICT PROJECT MANAGEMENT OPEN STANDARD SOFTWARE ................................................................ 29 Project Documentation Software ............................................................................................ 29 Project Gantt chart Software................................................................................................. 29 Project Modeling Software .................................................................................................... 29 Project File Security Software ............................................................................................... 29
  • 3. Training Goal: Improve the leadership, management, and technical mindsets and practices behind the e- Government ICT project’s performance, methodology, justification, planning, implementation, control, evaluation and supportTraining Objectives: 1. Describe the knowledge, skills and attitudes requirements to manage the projects towards success 2. Explore the various references standards that defines the mindset, methodology and certification in managing projects 3. Build common understanding on the detailed processes, deliverable, templates and tools to manage ICT project for e-government and community development 4. Elaborate the use of project management tools to capture, store and analyze project data and generate project information and knowledge , and how to use project templates to document project management deliverable on each phase or stage of the ICT project 5. Discover, evaluate, and use open standard computer software and web based services to support the documentation, collaboration, communication, visualization, publication, and monitoring requirements of project management.A. Project Management Basic Definitions:Description of e-Government World Bank Definition: “It refers to the use by government agencies of information technologies (such as Wide Area Networks, the Internet, and mobile computing) that have the ability to transform relations with citizens, businesses, and other arms of government.” “These technologies can serve a variety of different ends: (1) better delivery of government services to citizens, (2) improved interactions with business and industry, (3) citizen empowerment through access to information, or (4) more efficient government management.” “The resulting benefits can be less corruption, increased transparency, greater convenience, revenue growth, and/or cost reductions.”Project • OGC PRINCE 2 -“A management environment that is created for the purpose of delivering one or more business products according to a specified Business Case.” “A temporary organization that is needed to produce a unique and predefined outcome or result at a pre-specified time using predetermined resource.” • PMI PMBOK - “A project is a temporary endeavour undertaken to create a unique product, service or result. It is performed by people, constrained by limited resources, planned, executed and controlled.” “Projects are different from operations because the latter are ongoing and repetitive activities, while projects are temporary and unique.”
  • 4. Project Valuation – Indicative areas to refer the value of a project • Quality of Experience • Cost Effectivity • Sustainability • GovernanceProject Management • Project management is the aapplication of principles, practices, and techniques to lead project teams and control project schedule, cost, and risks to deliver the results of a successful project to the delighted stakeholders. • Control: Scope, Time, Cost, Resources, Quality, Change, and Security • Agenda: Performance, Culture, People, Process, and Technology • Project management is a process with the following components: (PMBOK) 1. Inputs (documents, plans, designs, etc.) 2. Tools and Techniques (thinking tool applied to inputs) 3. Outputs (documents, products, etc.)Project Management Office • PMBoK Definition: • Shared and coordinated resources across all projects administered by the PMO • Identification and development of project management methodology, best practices, and standards • Clearinghouse and management for project policies, procedures, templates, and other shared documentation • Centralized configuration management for all projects administered by the PMO • Centralized repository and management for both shared and unique risks for all projects • Central office for operation and management of project tools, such as enterprise-wide project management software • Central coordination of communication management across projects • A mentoring platform for project managers • Central monitoring of all PMO project timelines and budgets, usually at the enterprise level • Coordination of overall project quality standards between the project manager and any internal or external quality personnel or standards organization.
  • 5. Project Manager • Responsibility Domains of Project Manager (From TenStep)A. PROCESS RESPONSIBILITIES B. PEOPLE RESPONSIBILITIES1. Define the project and build the work plan 1. Lead the identification and elaboration of the2. Supervise the implementation of the overall work project processes, and make sure that people plan, that the work is assigned and completed on follow the tasks directives. time, according to quality specifications and within 2. Lead the team to willingly follow your direction. budget. Leadership is about communicating a vision and3. Identify, track, and resolve the project issues. getting the team to accept it and strive to get4. Communicate proactively the project information there with you. to all stakeholders. 3. Set the reasonable, challenging and clear5. Identify, monitor, and mitigate the project risk. expectation of people, and holding them6. Ensure acceptable quality of the solution and accountable for meeting the expectations and project deliverables at every phase of the project. allow them to get enabling opportunities.7. Manage proactively the project scope by insuring 4. Facilitate team-building, so that people work that only what was agreed to is delivered, and the together well, and feel motivated to work hard for changes are approved through scope management. the sake of the project and other team members.8. Define the metrics and collect the data that set 5. Communicate proactively and clearly, both the proper view on how the project is progressing, verbally and written. and whether the production of the deliverables is 6. Realize good and active listening skills acceptable based on agreed specification, time and cost.
  • 6. B. PROJECT MANAGEMENT COMPETENCIES: (Project Manager View) ICT Project Management Domains 1. Business Management Business Case, Policy and Regulations, Acquisition and Procurement, Scope and Time, Cost and Budget, Plan and Implementation, Documentation and Communication, Human Resources, Contracts and Vendors, and Risk Mitigation 2. Solution Development Management Requirement, Approach, Standards, Architecture, Configuration, Technology, Skills, Construction, Control, Testing, Acceptance, Training, Integration, Security, Roll-Out, and Support ICT Project Manager Categories of Skills 1. Leadership Skills AttributesVISIONING Leads strategic management; defines, communicates, and leads goals and objectivesCONTROL Decides, implements and monitorsNEGOTIATION listens, builds consensus, and manages conflict 2. Management Skills AttributesPLANNING Gathers data, analyze information, look forward decision, design, and writeCONTROL Facilitates process initiation, execution, control and improvement, and lead decision makingDOCUMENTATION Captures and stores information for knowledge requirements 3. Technical Skills AttributesANALYSIS Captures information and apply appropriate thinking tool to build understanding, decision, and planned action.DESIGN Capturer requirements and performance specifications, and apply appropriate modeling toolBUILDING Defines and implements the development platform, and to control delivery and integration of work packages to comply with the project scope and outcome requirements
  • 7. C. PROJECT MANAGEMENT MATURITY ASSESSMENT (Organizational View) ICT Project Management Failure Points FAILURE CAUSES Presence Ranking RUSSEL D. ARCHIBALD (MPCM Survey)Frequent scope changes: 73%Unattainable deadlines: 51%Frequent scope changes: 73%Incorrect or incomplete Feasibility Study (or Business Case or Business Plan): 27%Precarious project management methods, tools and techniques: 22%Lack of resources (human, financial and material): 22%Insufficient or inadequate commitment from senior management: 22%Inadequate risk management: 22%Project managers with insufficient management skills: 20%Insufficient or inadequate IT team’s technical skills: 13%Insufficient or inadequate commitment from the involved user areas: 7%
  • 8. Project Management Capability Maturity Rubric (Based on OGC P3M3)Maturity Maturity Condition Descriptor Level 5 Optimized Process The organization runs continuous process improvement with proactive problem and technology management for projects in order to improve its ability to depict performance over time and optimize processes 4 Managed Process The organization obtains and retains specific measurements on its project management performance and run a quality management organization to better predict future performance 3 Defined Process The organization has its own centrally controlled project processes, and individual projects can flex within these processes to suit the particular project. 2 Repeatable Process The organization ensures that each project is run with its own processes and procedures to a minimum specified standard. There may be limited consistency or co-ordination between projects. 1 Initial Process The organization recognizes projects and run them differently from its ongoing business. Projects may be run informally with no standard process or tracking system.
  • 9. D. PROJECT MANAGEMENT METHODOLOGY STANDARDS The methodology standards help the project manager to define and manage the end-to-endstages, activities, requirements, and deliverables of both the business and product developmentcomponents of ICT project. The project team members and stakeholders are given the commonreferences on how to appraise and deliver the expectations defined for the project. The applicablemethodology standards provide the competencies and organization to project handling, and makeavailable the performance benchmark to validate the kind of input, tools, and deliverables enteredinto the project management.Project Management Life-Cycle Phases PMBOK PRINCE2 MSFProject Management Body of Project in Controlled Microsoft Solutions Knowledge Environment Framework1. Initiating 1. Starting Up a Project 1. Envisioning Phase2. Planning 2. Planning 2. Planning Phase3. Executing 3. Controlling a Stage 3. Developing Phase4. Controlling and Monitoring 4. Managing Product Delivery 4. Stabilizing Phase5. Closing 5. Managing Stage Boundary 5. Deploying Phase 7. Closing a ProjectProject Management Knowledge Areas PMBOK PRINCE2 SWEBOKProject Management Body of Project in Controlled Software Engineering Body Knowledge Environment of KnowledgeIntegration Management Business Case RequirementsScope Management Organization DesignTime Management Plans ConstructionCost Management Controls TestingQuality Management Management of Risks MaintenanceHuman Resource Management Quality in a Project EnvironmentCommunication Management Configuration ManagementRisk Management Change ControlProcurement Management
  • 10. Business Management Stages of the Project INITIATION PLANNING EXECUTION CONTROL CLOSING L Stages Tasks Results INITIATION Data gathering for the baseline information to define the need for the project, value justification of the project, solution and Research data and information requirements, the available options Approved business case Agreement on the project methodology, estimation tools, and financial valuation formula. Request for Proposal and Project Terms of Reference Elaboration of the needs, key performance indicators, critical success factors, financial Approved Project Proposal valuation metrics Project Contracts Formulation and approval of the business case Project Implementation Terms of Composition, approval and release of the request References for proposal with project terms of reference Project Manager Appointment Acceptance, review and approval of project proposal Composition, approval and release of the project contracts, and project implementation terms of reference based on the approved project proposal Setting up of the project organization and the appointment of the project manager
  • 11. PLANNING Definition of the tasks and requirements to be Work Breakdown Schedule planned for execution and utilization Organization Breakdown Schedule Elaboration and agreement on of the applicable input, procedures, methodology and tools to be Estimation Techniques use in planning the project development. Project Management Plan Composition of the Project Management Plan to integrated the following plans Issues and Problem Management Work Plan –work breakdown schedule, organization Plan breakdown schedules Change Management Organization Resource Plan – organization, skills needs, recruitment, people training, deployment schedules Procurement Plan – bills of materials, acquisition strategy, contract handling Communication Plan – reporting instruments, kinds of communications, audience definition and information needs Risk Management Plan – What if identification process and the mitigation and action requirements Budget Plan – Budget Items, Cost and Scheduling Quality Plan – Quality assurance procedures and tools specifications Training Plan – capability requirement matrix and training design, and schedules Technology Plan – technology items, approaches, standards, and delivery, installation, and configuration, and testing schedules Change Management Plan –request for changes as a result of problem, incident, etc…EXECUTION Definition of solutions requirement Process Model Design the solution model Information Model Create the solution model prototype Technology Model Verify and Validate solution model prototype Work Packages Build the beta version of the solution Delivery Report Internal Team verification and validation of beta Accomplishment Reports version of the solution Minutes of the Meeting Train users to test the beta version release User’s Approval, Sign-in and Sign- Test and Approve the beta version Off document Training Report
  • 12. Integration and normalization of the final Configuration Documentation version User’s Manual Test and approve the final version Release the final version Handle incident, problem and change requestCONTROL Institute and enforce compliance report Compliance Checklist Issues reporting and change management Issues Documentation handling Attendance Reporting Testing and Quality Assurance DocumentsCLOSURE Lessons Learned Lesson Learned Document Contracts closure Payment Handing over Project Acceptance Documentation Project document archived Turn-over Documentations
  • 13. VISIONING REQUIREMENT DESIGN BUILDING TESTING PLANNING DEFINITION INTEGRATION RELEASE SUPPORT MAINTENANCESolution Development Management Stages Tasks ResultsVISIONING & PLANNING Setting the goals, strategy, Project Work Plan approach, configuration, and plan of developing the solution based on the approved business case and project proposal of the project.REQUIREMENT ANALYSIS Elicitation and documentation Business, Information, of information to compose the Technology Configuration input, process, output, and Documentation technology architecture specifications of the proposed Functional and non-functional solution requirement checklists Analysis and definition of the functional and non-functional requirements of the proposed solution.SOLUTION DESIGN Visual drawing of the Process, application, data, and application, data, and technology models technology model, and prototype making of the Application conceptual model solution Database model Generate mock-ups and prototypes of processes, screen, Technology platform model reports Validation, verification and approval of the visual drawing and prototype.SOLUTION BUILDING Coding of the approved Work Packages application, data and technology prototype. Conformance Testing Report – Pass – Fail – Internal testing on the conformance of the coded Revision Report solution to approved design of the solution requirements
  • 14. SOLUTION TESTING Validation and verification of List of approved work packages the functional and non- functional requirements of the Change Requests alpha version of the application model and database tables Issues reporting and change requestSOLUTION INTEGRATION Putting together the Integrated work package beta functionally accepted modules, version databases, network services and security services to run the Testing report and change integrated version of the requests solution Integration testing to validate and verify the inter-operational performanceSOLUTION ACCEPTANCE Conduct of user’s training on Training Design using the functional beta version of the solution Testing Scripts Perform user’s testing and Testing Report acceptance of the completed solution version Change Request Solution business readiness List of accepted functional and assessment of the final solution non-functional features version for releaseSOLUTION RELEASE Normalization of the Final Release Version of the configuration requirements for work packages the solution final version release User manual Deploying by installing and List of location and users for configuring the release version deployment, and status of of the solution to business installation and configuration production area. Users training schedules Training of the production users.SOLUTION SUPPORT Setting up of the organization Service Desk and procedures for Incident, problem and change handling Accepting incident and problems for documentation, reporting, analysis and resolution
  • 15. E. ICT PROJECT MANAGEMENT TEMPLATES Project Initial Definition and Planning Logical Framework OBJECTIVES MEASURABLE MEANS OF IMPORTANT INDICATORS VERIFICATION ASSUMPTIONSGOAL: Wider problem Quantitative ways of Cost-effective methods External factorsthe project will help to measuring or and sources to quantify necessary to sustain inresolve qualitative ways of or assess indicators the long run judging timed achievement of goalPURPOSE: The Quantitative ways of Cost-effective methods External conditionsimmediate impact on measuring or and sources to quantify necessary if achievedthe project area or qualitative ways of or assess indicators project purpose is totarget group i.e. the judging timed contribute to reachingchange or benefit to be achievement of purpose project goalachieved by the projectOUTPUTS: These are Quantitative ways of Cost-effective methods Factors out of projectthe specifically measuring or and sources to quantify control which, ifdeliverable results qualitative ways of or assess indicators present could restrictexpected from the judging timed progress from outputsproject to attain the production of outputs to achieving projectpurpose purpose.ACTIVITIES: These are Quantitative ways of Cost-effective methods Factors out of projectthe tasks to be done to measuring or and sources to quantify control which, ifproduce the outputs. qualitative ways of or assess indicators present, could restrict judging timed progress from activities performance of the to achieving outputs activitiesINPUT: These are the Quantitative ways of Cost-effective methods Factors out of projectresources and budget to measuring or and sources to quantify control which, ifbe made available to qualitative ways of or assess indicators present, could restrictrealize the activities judging timed the provision of inputand to produce the performance of the Financial report as to initiate the activitiesoutputs. activities required by the project to achieving outputs fund sources
  • 16. Stakeholder Analysis The project stakeholders are individuals and organizations whose interests may be affected asa result of executing the project. They are either primary or secondary stakeholders who needs,knowledge, influences, resources, and regulatory functions are considered contributory to achieve theproject goal, and whose active engagement are considered critical success factors to the projectsuccess. The project manager has to initiate the activity of identifying the stakeholders, to perform thecritical evaluation of their situational stake, and manage their expectation and participation.Stakeholders are persons assigned to the project, the members or departments within the organization,the outside institutions with regulatory or supplier relationship with the organization, and individual orgroups considered as influencers. The results of stakeholder analysis provide the stand-point on how to communicate with thevarious interest groups of the project, and how to address differences and build consensus. 1. Stakeholder Analysis: Talking Points
  • 17. ICT Project Visioning and Scoping MSF v3.0 Project Visioning and Scoping BUSINESS SOLUTION SOLUTION DESIGN SCOPE OPPORTUNITY CONCEPT STRATEGYOpportunity Goals Feature/Functions ArchitecturalStatement List Design StrategyVision Statement Objectives Out of Scope Technical Design StrategyBenefit Analysis Assumptions Version Release Strategy Constraints Acceptance Criteria User Profile Operational Criteria Usage Scenario Business Requirements Users Requirements Operation Requirement Systems Requirements
  • 18. ICT Project Business Case Decision Points for E-Gov Project Justification DECISION POINTS INPUTProject Needs, Goals and Project Log FrameObjectives,Key Performance Indicators, Project Log FrameCritical Success Factors, andPerformance MetricsTarget Beneficiary and Stakeholder AnalysisStakeholdersMandate or Developmental Agency R.A., Medium Term Developmental Goals, IncumbentAgenda Alignment President Agenda, Approved Strategic PlanResulting Value to the Agency, Applied Information Economics, Balanced Score Card, EconomicCitizen, and Government Value Added, Economic Value Sourced, Portfolio Management, Real Option Valuation, Break Even Analysis,Technology Solution Options Enterprise Architecture, Information Systems Strategic Plan,and the Value of Choosing the Request for InformationOptionRisks Risk Analysis, Costs of Risk, Costs of Mitigation, Risk Probability and Impact,Timeframe Project Timelines, Work Breakdown ScheduleProject Requirements and Cost One-Time Development Expenses, One-Time Implementation Expenses, Capital Costs, Maintenance/Continuing CostFinancial Valuation Cost Benefit Analysis, Net Present Value, Payback, Total Cost of Ownership, Internal Rate of Return, Opportunity Cost, PaybackMaintenance and Sustainability Service Support Plan and Service Management, Business Continuity Plan, Business Plan
  • 19. LOGICAL PROJECT DEFINITION MATRIX JUSTIFICATION REQUIREMENT ACQUISITIONSTAKEHOLDERS NEEDS OBJECTIVES ICT SERVICES PRIMARY PRIMARY NON- SECONDARY SECONDARY DEVELOPMENT INPUT SUPPLIERWhose interest Problem, Measurable End- SOLUTION FUNCTIONAL FUNCTIONAL FUNCTIONAL NON- APPROACH or GOOD ANDwill be affected Improvement, Result to Solve Product REQUIREMENT REQUIREMENT REQUIREMENT FUNCTIONAL STRATEGY SERVICES Internal Regulation Problem, Deliverables to Core/Cutting Core/Cutting Serves REQUIREMENT Procedures External Improvement be Purchased or Across Across particular Serves Methods Targets, Constructed Tasks, Quality interest or particular Standards Compliance Information and Characteristics in handle special interest or Tools Registration for Results the Tasks, exceptions handle special Infrastructure the Stakeholders Information and exceptions Platforms Results Skills Organization
  • 20. ICT Solution Development Project Scoping PROJECT TASKS REQUIREMENTS PROJECT PHASES ACTIVITY DURATION SERVICES GOODS01. Business CasePreparation02. Business Case Reviewand Approval03. Budget RequirementPreparation, AllocationRequest Processing,Approval and ActualAllocation04. Request for ProposalPreparation and ProjectTerms of ReferenceDefinition05. Request for ProposalReview and Approval ofthe Project Terms ofReference06. ProcurementPreparation, Bidding,Evaluation, Awards,Contract Approval07. Activation of ProjectImplementationOrganization08. Detailed ProjectImplementation Planning,Scope BreakdownRefinement, BudgetAlignment, DeliverySchedules, responsibilitymatrix09. DevelopmentalPlatform Delivery,Installation andConfiguration10. Solution RequirementElicitation and DesignDefinition11.Solution PrototypeBuilding, Validation andVerification12. Solution Beta VersionCoding, Internal Testingand Integration13. Production PlatformDelivery, Installation andConfiguration14. User’s Training forSolution’s Beta VersionTesting15. Solution FirstProduction ReleaseVersion normalization16. User’s Approval ofProduction Version; andrelease of solution tothe users environment17. Service Support andMaintenance18. Project Closing andTurn-over
  • 21. ICT Project Cost and Budget: Item Spreadsheet SERVICES COST ITEMS AND BUDGET ESTIMATE PROJECT DELIVERABLES SERVICES DETAILS Expert & Skills Salary Total Total Travel, Insurance Requirement Rate Hours or Salary Accommodation HR/DAY Mandays Expenses01. Business Case02. Financial Work Plan,Budget Requirements andApproved Allocation02. Request for Proposal &Project Terms of References03. Reviewed and ApprovedBids04. Project Office and SkilledPersonnel05. Project Meetings andWorkshops and ProjectTraining06. Project Work Plan07. Development PlatformHardware, Software andBandwidth08. Approved RequirementDocumentation and SolutionDesign, Architecture andFunctional Models09. Validated and VerifiedSolution Prototype Program –application interfacesprototypes, database tables,and network interfaces10. Beta Version ProgramModule –working businessapplication, data, security,integration interfaces, andnetwork11. User’s Documentationand User’s Training12. User’s Testing andChange Documentation13. Normalized ProductionVersion of the Solution14. Solution Roll OutSupport.15. Incident Managementand Maintenance
  • 22. COMPUTER GOODS REQUIREMENT AND BUDGET ESTIMATE Project Management Office COMPUTER HARDWARE COMPUTER SOFTWARE BANDWIDTH Item Name No. & Total Software License Total Cost Capacity Duration Cost of Cost Type Number Cost UnitsWorkstation Operating SystemNetwork Hub Productivity ToolsServer Scheduling ProgramNetwork SecurityCables/Peripheral Software Solution Development Platform COMPUTER HARDWARE COMPUTER SOFTWARE BANDWIDTH Item Name No. & Total Software License Total Cost Capacity Duration Cost of Cost Type Number Cost UnitsWorkstation ModelerNetwork Hub EditorServer Application ServerNetwork DatabaseCables/Peripherals Server Network Server Business Production Roll-Out COMPUTER HARDWARE COMPUTER SOFTWARE BANDWIDTHItem Name No. & Total Cost Software License Total Cost Capacity Duration Cost of Type Number Cost Units Service Support Management COMPUTER HARDWARE COMPUTER SOFTWARE BANDWIDTH Item Name No. & Total Cost Software License Total Cost Capacity Duration Cost of Type Number Cost Units Service Desk Service Monitoring
  • 23. ICT Project Investment Requirement and Cost Investment Unit Duration Estimated Estimated Total Total Cost % Source of Fund Component Unit Cost CostSERVICES 000% Project TeamExternal Consultants Training Venues Transportation Accommodations Rentals Bandwidth Electricity, WaterGOODS 000% User’s Access Computer Computer Server Network Server Internet Server Application Server Database Server Security Server Backup Server Network Devices Cabling and Peripheral Software Installer and Licenses Office Supplies Other EquiptmentsMAINTENANCE 000% Computer Devices Network Devices Other Equiptments Software Building TOTAL INVESTMENT COST
  • 24. Project Organization: Roles Matrix PROJECT TASKS: ROLES MATRIXDate of First Draft: Version No. Current Version Date: PROJECT NAME PROJECT DURATION PROJECT OUTCOME PROJECT OWNER PROJECT BENEFICIARY SOURCING STRATEGYPROJECT DELIVERABLES PROJECT ROLES TASKS Responsible Accountable Expert Work
  • 25. PROJECT ACTIONS: RESPONSIBILITY MATRIXDate of First Draft: Version No. Current Version Date: PROJECT NAME PROJECT DURATION PROJECT OUTCOME PROJECT OWNER PROJECTBENEFICIARY SOURCING STRATEGY PROJECT RESPONSIBILITY MATRIX PROJECT ACTION ACTION APPROVING DECISION ANALYSIS, INTERNAL EXTERNAL ITEMS IMPLEMENTOR AUTHORITY PROVIDER EVALUATION & SUBJECT SUBJECT RECOMMENDATION MATTER MATTER MAKER EXPERT EXPERT
  • 26. REQUIREMENT TRACEABILITY MATRIXUnique Requirement Requirement Software Design Program Requirement Successful Modification RemarksNo. Statement Source Requirement Specification Module Test Test of Specification Document Name and Specification Verification Requirements or Reference Reference Document Functional Number Number Reference Requirement Number Document Reference Number
  • 27. F. ICT PROJECT MANAGEMENT OPEN STANDARD SOFTWAREProject Documentation Software 1. OpenOffice Writer 2. OpenOffice Calc 3. OpenOffice Draw 4. OpenOffice ImpressProject Gantt chart Software 1. OpenProjectProject Modeling SoftwareProject File Security Software 1. Antivirus 2. Unwanted File Cleaner 3. File Backup