…Concept to Completion

J Satyanarayana

e-Government Project Life Cycle

Agenda

• e-Government – Track Record

• Implementation Dynamics

• Project Development & Project Management

• Effective Project Management

Most Failures are rooted inimproper

Project Development&

Project Management

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

7 Steps in Implementation

Conceptualize1

Architect2 Develop

3

Pilot4

Rollout5Evaluate

6Enhance

7

Project Development

Project Management

Project Development VsProject Management

Project Development

• Creativity

• Research & Analysis

• Consultation

• High-end Resources

Project Management

• Planning Ability

• Field Work

• Coordination

• Medium Resources

Principles of Project Management

Project & Program

A Project is an endeavour to create a unique Product, Service or Result that has inter-related activitiesand is progressively elaborated

A Program is a group of projects managed in a coordinated way

Components of Project Mgt.

Integration Management

Scope Management

Time Management

Cost Management

Quality Management

HR Management

Communications Management

Risk Management

Procurement Management

Triple Constraint of Project Mgt

QualityCostTim

e

Scope

Components of a Project Plan

1. Project Charter2. Project Management Approach3. Scope Statement4. Work Breakdown Structure5. Responsibility Chart6. Major Milestones7. Budget8. Schedule9. Resources10. Change Control Plan11. Project Management Baselines

CADS Methodology of Project Development (NISG)

• Study•AS IS

• Best Practice• Stakeholder Consultation• Develop

•Vision•Mission

• Objectives• Business Case Analysis

Conceptualize

• Functional Architecture •Technology Architecture •Process Architecture •People Architecture

Architect

• Services • Roles & Responsibilities • Service Levels •Business Model

• RFP

Define

• POC • Bid Process Management

•Evaluation

• Project Management

• Assessment

Support

Anatomy of Project Documentation

… the 3 part approach

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

Part II- Commercial & Bid Specifications

• Prequalification Criteria

• Technical Bid Formats

• Commercial Bid Formats

• Evaluation Criteria

• Bidding Terms & Conditions

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

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

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

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

Issues in Project Managementfor e-Government

Issues in eGov Project Mgt.

Integration Management

Scope Management

Time Management

Cost Management

Quality Management

HR Management

Communications Management

Risk Management

Procurement Management

Scope is not preciseScope creeps

Lack of team spiritNo e-Champion

Delays in DecisionsDelays in sign-offs

Turnover of Key peopleLack of PM Skills

No FlexibilityDelays in payments

Too many meetingsToo few decisions

Risk AversionOne-sided contracts

Vagueness in specifying

requirements

Lack of Skills Lack of Institutional

approach to QM

e-Government delayedis

e-Government denied!

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

Conclusion e-Government requires

Systematic development of the concept into 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

Thank Youceo@nisg.org

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

2. Architecture

• Meets the Objectives

• Is Sustainable

• Scales to handle future demand

• Accommodates future developments

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

3. Development

• Functional Requirement Specification

• System Requirement Specification

• Coding

• Testing

• Deployment

• Documentation, Version Management, ALM

Spend Quality Time here

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

5. Rollout

• Phasing• Functionality• Geography

• Resource Planning• Financial• Managerial• People• PPP

• Stakeholder Consultation• Project Management

6. Evaluate

• Service-Orientation• Efficiency• User-Convenience• Citizen-Centricity

• Technology• Architecture &

Standards• Security• Scalability• Reliability

• Sustainability• Organizational• Commercial• Legal

• Cost-effectiveness

• Replicability• Functional• Technological• Commercial

SLA Metrics of a G2B project (1/3)

BaselineLower

performanceHigher

performance Breach

Service Metrics Parameters Metric Credit Metric Credit Metric Credit Metric

I- Service-related, Citizen-facing (65)            

1.Average wait-period at Service CentrePeak dates , Peak hours <15 min 15

15-25 min 10

 < 12 min 20 >30 min

2.Average wait-period at Service CentrePeak dates, Non-Peak hours

< 10 min 12

10 -15 min 8 < 8 min 16 >20 min

3.Average wait-period at Service CentreNon-Peak dates , Peak hours < 5 min 9

5-10 min 6 No additional credit

( No incentive)>10 min

4.Average wait-period at Service CentreNon-Peak dates , Non- Peak hours

No waiting 7

0 – 3 min 5

5.Average time for service at B1 Service

Counter -Peak dates, peak

hours <4 min 9 4-5 min 6  < 2 min 12  >6 min

BaselineLower

performanceHigher

performance Breach

Service Metrics Parameters Metric Credit Metric Credit Metric Credit Metric

6.Average time for service at Service Counter -Peak dates, Non-peak hours

<2min 5 2-4 min 3< 1min 7 >5 min (-) 3

7.Availability of agreed services over the Internet 99.0% 5

99..0 to 98.0% 3

 No credit for

higher performance

  

<95.0% (-) 3

8.Average Portal page loading 7 sec 3

7 to 10 sec 1 >15 sec (-) 1

SLA Metrics of a G2B project (2/3)

  Baseline Lower performanceHigher

performance Breach

Technology Metrics Parameters Metric Credit Metric Credit Metric Credit Metric Debit

II-Technological, performance-related(15)  

No toleration for lower performance. No credit will be given for performance below baseline.

No extra credit for higher performance. Baseline performance is mandatory.

   

9. Capacity of the Application Server

Equivalent of capacity to handle 10000 service transactions per hour 6

< 6000 transactions per hour (-) 6

10. Capacity of the Database Server

Equivalent of capacity to handle 10000 service transactions per hour 6

< 6000 transactions per hour (-) 6

 11. Concurrent connects to Application Server  >750  3  < 500   (-) 3

III-Technological, maintenance-related (20)      

 12. Uptime of Data Centre > 99% 8   < 96%  (-) 8

13. Uptime of Service Centre > 98% 4 < 95% (-) 4

14. Time to restore Data Centre from failure < 1 hour 5 < 3 hours (-) 5

15. Time to restore Service Centre from failure < 2 hours 3 < 5 hours (-) 3

SLA Metrics of a G2B project (3/3)