1 / 33

… Concept to Completion

e-Government Project Life Cycle. … Concept to Completion. J Satyanarayana. Agenda. e-Government – Track Record Implementation Dynamics Project Development & Project Management Effective Project Management. Success & Failure Rate. 35 % of eGov projects are total failures

darrell
Download Presentation

… Concept to Completion

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. e-Government Project Life Cycle …Concept to Completion J Satyanarayana

  2. Agenda • e-Government – Track Record • Implementation Dynamics • Project Development & Project Management • Effective Project Management

  3. Success & Failure Rate • 35 % of eGov projects are total failures • Initiatives not implemented • Initiatives abandoned immediately • 50% of eGov projects are partial failures • Main stated goals not achieved • Initial success but failure after an year • Success for one group but failure for others • 15% of eGov projects are successes • All stakeholders benefited • No adverse results Most Failures are rooted in improper Project Development & Project Management

  4. Project Management Project Development Rollout Pilot Develop Evaluate Architect Conceptualize Enhance 5 7 6 4 3 2 1 7 Steps in Implementation

  5. Project Development Creativity Research & Analysis Consultation High-end Resources Project Management Planning Ability Field Work Coordination Medium Resources Project Development VsProject Management

  6. Principles of Project Management

  7. Project & Program A Project is an endeavour to create a unique Product, Service or Result that has inter-related activities and is progressively elaborated A Program is a group of projects managed in a coordinated way

  8. Components of Project Mgt. Integration Management Scope Management Time Management Cost Management Quality Management HR Management Communications Management Risk Management Procurement Management

  9. Triple Constraint of Project Mgt Quality Time Cost Scope

  10. Components of a Project Plan • Project Charter • Project Management Approach • Scope Statement • Work Breakdown Structure • Responsibility Chart • Major Milestones • Budget • Schedule • Resources • Change Control Plan • Project Management Baselines

  11. Conceptualize Architect Define Support • Study • AS IS • Best Practice • Stakeholder • Consultation • Develop • Vision • Mission • Objectives • Business Case Analysis • Functional • Architecture • Technology • Architecture • Process • Architecture • People • Architecture • Services • Roles & • Responsibilities • Service • Levels • Business • Model • RFP • POC • Bid Process Management • Evaluation • Project • Management • Assessment CADS Methodology of Project Development (NISG)

  12. Anatomy of Project Documentation … the 3 part approach

  13. Part I – Functional & Technical Specs • Vision, Mission, Objectives, Outcomes • National/ International Best Practices • Service Definition • Functional Architecture • Technology Architecture • Including Security Management Requirements • Process Architecture • Outcome of GPR • People Architecture

  14. Part II- Commercial & Bid Specifications • Prequalification Criteria • Technical Bid Formats • Commercial Bid Formats • Evaluation Criteria • Bidding Terms & Conditions

  15. Part III – Legal Specs & SLA • Roles & Responsibilities of parties • Scope of Work of Partner • Service Level Agreement • Consequences of Breach • Terms of Payment • Governance Structure • Exit Management

  16. About SLA • SLA= Service Level Agreement • Justification for SLA • Govt is buying services not hardware, software & networks • Specifies quantity & quality of services • Payments – part or full – are linked to performance against SLA • Contains rewards & penalties • Drives the partners – both public & private – to better performance

  17. Evaluation • Prequalification criteria • Turnover limit – in relation to Project size • Experience in e-Government project • Technical Criteria • Past Project Experience • Quality of Solution Offered • Implementation Plan • Key Project Personnel • Commercial Evaluation • Relative to Lowest Cost • Combined Score • Appropriate weightages between Technical & Commercial scores

  18. Scope of IS Audit of e-Gov Projects • To audit the functionality • Service Levels • Suitability • Accuracy • Interoperability • To audit IT infrastructure • To audit Quality as per ISO 9126 • Reliability • Availability • Data Integrity • Efficiency/ Performance • Usability • To Audit Security as per BS 7799/ ISO 17799

  19. Issues in Project Managementfor e-Government

  20. Issues in eGov Project Mgt. e-Government delayed is e-Government denied! Integration Management Scope Management Time Management Lack of team spirit No e-Champion Scope is not precise Scope creeps Delays in Decisions Delays in sign-offs Cost Management Quality Management HR Management No Flexibility Delays in payments Lack of Skills Lack of Institutional approach to QM Turnover of Key people Lack of PM Skills Communications Management Risk Management Procurement Management Too many meetings Too few decisions Risk Aversion One-sided contracts Vagueness in specifying requirements

  21. Improving Project Management • Empowerment • Empowered Committee for Major Decisions • Project Implementation Committee for operational decisions • Partial outsourcing of PM activities • Select a Professional Organization as PMU • Capacity Building in PM skills • Institutional Capacity • ‘Creating’ CIO & CTO • Sponsoring Key people for PMI Certification

  22. Conclusion • e-Government requires • Systematic development of the conceptinto a Project • Systematic Management of the Project • Project Development & Project Management are both specialized jobs. • There is a continuous need to build capacities in Project Development & Project Management

  23. Thank You ceo@nisg.org

  24. 1. Conceptualization • Develop a Vision • Bordering on the impossible ! • Define a Mission • A Slogan that motivates • Spell-out Objectives • Benefits to ALL Stakeholders • Stakeholder consultation • Define Services • Transformation • Lay down Specific Outcomes • Measurable Parameters

  25. 2. Architecture • Meets the Objectives • Is Sustainable • Scales to handle future demand • Accommodates future developments

  26. 2. Architecture (contd) • Process Architecture • Government Process Reengineering • Technology Architecture • Consultative Approach – e.g eBiz Architecture • People Architecture • Policy Level, e-Gov Champions, CIOs, CTOs Operational Level • Resource Architecture • Business Model, Viability, Sustainability, PPP, User Charges, SLA

  27. 3. Development • Functional Requirement Specification • System Requirement Specification • Coding • Testing • Deployment • Documentation, Version Management, ALM Spend Quality Time here

  28. 4. Pilot • Why Pilot? • A More thorough debugging • A more innovative product • Early course correction OR ‘Go-No-GO’ decision • A more reliable Business Model • Scope of the Pilot • Functionality • Geographical Coverage

  29. 5. Rollout • Phasing • Functionality • Geography • Resource Planning • Financial • Managerial • People • PPP • Stakeholder Consultation • Project Management

  30. Service-Orientation Efficiency User-Convenience Citizen-Centricity Technology Architecture & Standards Security Scalability Reliability Sustainability Organizational Commercial Legal Cost-effectiveness Replicability Functional Technological Commercial 6. Evaluate

  31. SLA Metrics of a G2B project (1/3)

  32. SLA Metrics of a G2B project (2/3)

  33. SLA Metrics of a G2B project (3/3)

More Related