e-Government

1
e-Government the Art of Project Management

• J Satyanarayana

2
Agenda

• e-Government - Critical Success Factors
• Implementation Dynamics
• Project Development Project Management
• Principles of Project Management
• Capacity Building for Project Management

3
Managing e-Government
4
Success Failure Rate
Most Failures are rooted in improper Project
Development Project Management

• 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

5
7 Steps in Implementation
6
Project Development VsProject Management

• Project Development
• Creativity
• Research Analysis
• Consultation
• High-end Resources

• Project Management
• Planning Ability
• Field Work
• Coordination
• Medium Resources

7
Principles of Project Management
8
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
9
Components of Project Mgt.
Integration Management
Scope Management
Time Management
Cost Management
Quality Management
HR Management
Communications Management
Risk Management
Procurement Management
10
Triple Constraint of Project Mgt
Quality
Time
Cost
Scope
11
Components of a Project Plan

1. Project Charter
2. Project Management Approach
3. Scope Statement
4. Work Breakdown Structure
5. Responsibility Chart
6. Major Milestones
7. Budget
8. Schedule
9. Resources
10. Change Control Plan
11. Project Management Baselines

12
CADS Methodology of Project Development (NISG)
13
Issues in Project Managementfor e-Government
14
Issues in eGov Project Mgt.
e-Government delayed is e-Government denied!
Integration Management
Scope Management
Time Management
Scope is not precise Scope creeps
Lack of team spirit No e-Champion
Delays in Decisions Delays in sign-offs
Cost Management
Quality Management
HR Management
Turnover of Key people Lack of PM Skills
No Flexibility Delays in payments
Lack of Skills Lack of Institutional approach
to QM
Communications Management
Risk Management
Procurement Management
Too many meetings Too few decisions
Risk Aversion One-sided contracts
Vagueness in specifying requirements
15
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
• in NIC/CDAC/STQC/NISG
• Creating CIO CTO
• Sponsoring Key people for PMI Certification

16
Thank You

• ceo_at_nisg.org

17
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

18
2. Architecture

• Meets the Objectives
• Is Sustainable
• Scales to handle future demand
• Accommodates future developments

19
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

20
3. Development
Spend Quality Time here

• Functional Requirement Specification
• System Requirement Specification
• Coding
• Testing
• Deployment
• Documentation, Version Management, ALM

21
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

22
5. Rollout

• Phasing
• Functionality
• Geography
• Resource Planning
• Financial
• Managerial
• People
• PPP
• Stakeholder Consultation
• Project Management

23
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

24
SLA for e-Government projects

• Justification for SLA
• Govt is buying services
• not hardware, software networks
• Captures the Roles Responsibilities
• Specifies quantity quality of services
• Payments linked to performance
• Contains rewards penalties
• Drives the partners to better performance

25
SLA Metrics of a G2B project (1/3)
Baseline Baseline Lower performance Lower performance Higher performance Higher performance Breach Breach
Service Metrics Parameters Metric Credit Metric Credit Metric Credit Metric
I- Service-related, Citizen-facing (65)            
1.Average wait-period at Service Centre Peak dates , Peak hours lt15 min 15 15-25 min 10  lt 12 min 20 gt30 min
2.Average wait-period at Service Centre Peak dates, Non-Peak hours lt 10 min 12 10 -15 min 8 lt 8 min 16 gt20 min
3.Average wait-period at Service Centre Non-Peak dates , Peak hours lt 5 min 9 5-10 min 6 No additional credit ( No incentive) No additional credit ( No incentive) gt10 min
4.Average wait-period at Service Centre Non-Peak dates , Non- Peak hours No waiting 7 0 3 min 5 No additional credit ( No incentive) No additional credit ( No incentive) gt10 min
5.Average time for service at B1 Service Counter - Peak dates, peak hours lt4 min 9 4-5 min 6  lt 2 min 12  gt6 min
26
SLA Metrics of a G2B project (2/3)
Baseline Baseline Lower performance Lower performance Higher performance Higher performance Breach Breach
Service Metrics Parameters Metric Credit Metric Credit Metric Credit Metric
6.Average time for service at Service Counter - Peak dates, Non-peak hours lt2min 5 2-4 min 3 lt 1min 7 gt5 min (-) 3
7.Availability of agreed services over the Internet 99.0 5 99..0 to 98.0 3   No credit for higher performance       No credit for higher performance     lt95.0 (-) 3
8.Average Portal page loading 7 sec 3 7 to 10 sec 1   No credit for higher performance       No credit for higher performance     gt15 sec (-) 1
27
SLA Metrics of a G2B project (3/3)
  Baseline Baseline Lower performance Lower performance Higher performance Higher performance Breach 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 toleration for lower performance. No credit will be given for performance below baseline. No extra credit for higher performance. Baseline performance is mandatory. 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 No toleration for lower performance. No credit will be given for performance below baseline. No toleration for lower performance. No credit will be given for performance below baseline. No extra credit for higher performance. Baseline performance is mandatory. No extra credit for higher performance. Baseline performance is mandatory. lt 6000 transactions per hour (-) 6
10. Capacity of the Database Server Equivalent of capacity to handle 10000 service transactions per hour 6 No toleration for lower performance. No credit will be given for performance below baseline. No toleration for lower performance. No credit will be given for performance below baseline. No extra credit for higher performance. Baseline performance is mandatory. No extra credit for higher performance. Baseline performance is mandatory. lt 6000 transactions per hour (-) 6
 11. Concurrent connects to Application Server  gt750  3 No toleration for lower performance. No credit will be given for performance below baseline. No toleration for lower performance. No credit will be given for performance below baseline. No extra credit for higher performance. Baseline performance is mandatory. No extra credit for higher performance. Baseline performance is mandatory.  lt 500   (-) 3
III-Technological, maintenance-related (20)   No toleration for lower performance. No credit will be given for performance below baseline. No toleration for lower performance. No credit will be given for performance below baseline. No extra credit for higher performance. Baseline performance is mandatory. No extra credit for higher performance. Baseline performance is mandatory.    
 12. Uptime of Data Centre gt 99 8  No toleration for lower performance. No credit will be given for performance below baseline. No toleration for lower performance. No credit will be given for performance below baseline. No extra credit for higher performance. Baseline performance is mandatory. No extra credit for higher performance. Baseline performance is mandatory.  lt 96  (-) 8
13. Uptime of Service Centre gt 98 4 No toleration for lower performance. No credit will be given for performance below baseline. No toleration for lower performance. No credit will be given for performance below baseline. No extra credit for higher performance. Baseline performance is mandatory. No extra credit for higher performance. Baseline performance is mandatory. lt 95 (-) 4
14. Time to restore Data Centre from failure lt 1 hour 5 No toleration for lower performance. No credit will be given for performance below baseline. No toleration for lower performance. No credit will be given for performance below baseline. No extra credit for higher performance. Baseline performance is mandatory. No extra credit for higher performance. Baseline performance is mandatory. lt 3 hours (-) 5
15. Time to restore Service Centre from failure lt 2 hours 3 No toleration for lower performance. No credit will be given for performance below baseline. No toleration for lower performance. No credit will be given for performance below baseline. No extra credit for higher performance. Baseline performance is mandatory. No extra credit for higher performance. Baseline performance is mandatory. lt 5 hours (-) 3