+ All Categories
Home > Documents > Audit of Public access point to the Polish e-Administration

Audit of Public access point to the Polish e-Administration

Date post: 24-Nov-2021
Category:
Upload: others
View: 3 times
Download: 0 times
Share this document with a friend
16
Audit of Public access point to the Polish e-Administration April 2009, و ا
Transcript

Audit of Public access point to the Polish

e-Administration

April 2009, ا��و��

Algorithm Approach

• Idea: EUROSAI IT Working Group - 2005– shortcuts to help in e-Government audit– useful set of auxiliary materials– visual guide– as simple as possible

• Presented: ISCITA – 2006

Algorithm Structure

Level I

• Programme• Strategy• Key actors• Key projects• Dependencies

Level II

• Project• Frameworks

(Methodologies)

• Effects

Level III

• Application• ISO • COBIT

Algorithm Structure – Documents

• Definitions• Analysis• Guide• Read• Links

Project

• ‘Public access point to the Polish e-Administration’

• web solution giving an easy access to Government e-Services

• to be completed in 2013• benefits:

- comfort to citizens- government‘s activities coordinated- information registered and safe

Audit

• April-November 2008• Follow-up of 2005 e-Government audit• 46 auditees and 2588 questionnaires sent

• Ex post approach

• Ex ante conclusions

• Report in March 2009

Start at Level II

• Reason: audit focused on a project• Step: Choose one of well known

frameworks• Issue: quality of implementation• Step: Analyse project effects• Issue: quality of indicators

– output and outcome – project indicators– impact – back to Strategy

Return to Level I

• Does the strategy really exist?• Issues:

– level of precision – awareness of expected benefits– dependencies among central and regional systems

• Impact restraints:– all results foreseen?– branch and regional interest– dimensions of user’s comfort– personal data– users overburdened with requirements

Level III

• Functionality• Technology

– Service-Oriented Architecture (SOA)– What should participant-offices know and do?– Interfaces – user or computer?– Is SOA an instrument of power?– Information broker?– IT Architecture – back to Strategy

Issue: Frameworks vs Public Procurement• Methodologies (frameworks):

– business oriented– support reasonable change even revolutionary one– responsibility management: ‘Win or die’

• Public procurement system:– decency oriented– defends first concept– responsibility management:

‘You start, others complete’

Issue: Public Body Investment Potential

• Illusion of ‘All happy by outsourcing’• Strength on both sides is required

– supplier:• responsible marketing• understanding of public service reality

– public body:• long term goals determination• methodologies skilled top management• IT project partner’s skills

Lessons: e-Government Project Coordination• Benefits management• Project dependencies • Stakeholders management• Do not suppress local and regional

activities

Lessons: Algorithm

• Keep it as simple as possible - processes’ description can be an endless work.

• Use the audited project’s framework as the basic tool – to speak the same language as the auditee. Then translate it to plain language.

• Development of effects analysis – esp. project’s results assessment may require to overcome internally defined goals and indicators.

• New step: strategic choices test? (SOA or Broker Issue)


Recommended