BEING A PROJECT MANAGER

369 views
313 views

Published on

Responsibilities and components to manage.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
369
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

BEING A PROJECT MANAGER

  1. 1. BEING A PROJECT MANAGERMy value as an ICT project manager is measured in terms of my CAPABILITY to deliver the PROJECT RESULTS successfullyaccording to the QUANTITY and QUALITY of EXPERIENCE expected by my STAKEHOLDERS and solution USERS.My capability is CONSTRAINED by the defined and agreed SCOPE based on SPECIFIED REQUIREMENTS. REQUIREMENT viewed asstrategic and tactical conditions in order to FILL GAPS or to ACTUALIZE OPPORTUNITIES for improvement or development.My capability is LIMITED by TIME expectation, which prescribed the START DATE and END DATE to happen in order for the resultsof the project to have IMMEDIACY and RELEVANCE.My performance is CONDITIONED by the kind of available RESOURCES to support WORK and MATERIALS, and the BUDGETED COSTallocated as INVESTMENT that will bring social and financial RETURNS.My results in RESTRICTED by required METRICS that speaks of numbers and quality. I have to comply with competency, processand technology standards which are used to benchmark the value of project methods, analytics, models, documentation,hardware, software, products and people.My decision is BOUND by rules, policies, procedures, decision-flow, inter-relationship and responsibility matrix.To get started, I must understand my project by filling up the thinking matrix to initiate, plan, execute, control and close myICT PROJECT.
  2. 2. Tell the story of your project 01 PROJECT NAME Code Name or Descriptive Title 02 Problem or Needs Gaps to be filled up . to Address Opportunities to be exploited 03 Stakeholders Whose interests are affected by the project 04 Goals State or condition to be achieved 05 Outcomes Objective results to be experienced 06 Critical Success What are to be made available Factors 07 Critical Assumptions Considered to be true 08 Competency People, Process, Technology and Culture 09 Methods Management, Analysis, Valuation, Modeling, Data Gathering, Evaluation, Control and Monitoring 10 Standards Procedures, Tools, Results, Metrics, Documentation, Financial, Templates 11 Risks What if – consequences and mitigation
  3. 3. 12 Governance Responsibility, Accountability, Expert and Work 13 Major Tasks Scope of Work – Work Breakdown 14 Main Output Products, Artifacts, Deliverables 15 Duration Timeline, schedule 16 Resource Input – Time and Material Requirement 17 Sourcing Strategy Acquisition and Procurement 18 Control and Metrics Checkpoint, Quality and Quantity Standards Checklist 19 Cost Budget 20 Fund Source Organization, Appropriation, AssistancePermission is granted for free use:ICT Project Thinking MatrixJohn Macasiojohn@onecitizen.net

×