guidelines for ict strategic planning in...
TRANSCRIPT
Annexes
Annex 1: Outline of Strategy Document
PART I: CURRENT SITUATIONParliament institutional context
• Mandate & Responsibilities• institutional areas
• General organizational structure by area (organigramme)
Services, processes & systems• <AREA>
• Services• Processes• Enabling (ICT) environment
<AREA>..
<AREA>
ICT services & support in parliamentICT department (OR unit OR office OR group OR external contractor)
ServicesRoles and responsibilityGovernance, policies and standardsICT Systems & Infrastructure
Communication and Information Dissemination services & support in parliamentLegislative Information Centre or Library (OR unit OR office OR group OR external contractor)
ServicesRoles and responsibilityGovernance, policies and standards
PART II: THE FUTUREThe vision statement
• Vision statement for the Parliament• Vision statements by institutional area
Strategic goals and objectives• <AREA>
• Goal• Objectives:
▪ Services▪ Processes▪ Systems
<AREA>..
<AREA>
PART III: THE CHALLENGES <AREA>
gap analysis<AREA>
..
ChallengesSummary of Gap analyses over all AreasChallenges
PART IV: ACTION PLANS
ACTION PLAN FOR ICTRecommendations
• Overview of recommendations• Mapping challenges recommendations
• Recommendation – detail descriptions• <RECOMMENDATION>
• <ACTIVITY>• <STAKEHOLDER>
Action Plan• Roadmap• Overview activities – priority – stakeholder – planning• Activity based budget
ACTION PLAN FOR COMMUNICATION AND INFORMATION DISSEMINATION Recommendations
• Overview of recommendations• Mapping challenges recommendations
• Recommendation – detail descriptions• <RECOMMENDATION>
• <ACTIVITY>• <STAKEHOLDER>
Action Plan• Roadmap• Overview activities – priority – stakeholder – planning• Activity based budget
Annex 2: Project evaluation questionnaire
To be signed by all the stakeholders involved in the project evaluation and lessons learned process
Project Lessons Learned questionnaire Yes No N/AImpact
Low High1 2 3 4 5
Place your cursor in the appropriate boxes and type an X. (Insert additional rows as needed.)
Yes = the project team agrees with the statementNo = the project team does not agree with the statementN/A = this statement does not apply to the projectImpact = the extent to which this factor had an impact on your project
Add a >comment to any question where supporting detail would be helpful
Project Planning
• Project Objectives were specific, measurable, attainable, resultsfocused and timelimited >
• Product concept was appropriate to Project Objectives >
• Project Plan and Schedule were welldocumented, with appropriate structure and detail >
• Project Schedule encompassed all aspects of the project >
• Tasks were defined adequately >
• Stakeholders (e.g., Sponsor, Customer) had appropriate input into the project planning process >
• Requirements were gathered to sufficient detail >
• Requirements were documented clearly >
• Specifications were clear and welldocumented >
• Test Plan was adequate, understandable, and welldocumented >
• External dependencies were identified, agreements signed >
• Project budget was well defined >
• End of Phase Criteria were clear for all project phases >
• Project Plan had buyin from the stakeholders >
Project Lessons Learned questionnaire Yes No N/AImpact
Low High1 2 3 4 5
Place your cursor in the appropriate boxes and type an X. (Insert additional rows as needed.)
Yes = the project team agrees with the statementNo = the project team does not agree with the statementN/A = this statement does not apply to the projectImpact = the extent to which this factor had an impact on your project
Add a >comment to any question where supporting detail would be helpful
Project Planning
• Stakeholders had easy access to Project Plan and Schedule >
Project Execution and Delivery
• Project stuck to its original goals >
• Changes in direction that did occur were of manageable frequency and magnitude >
• Project baselines (Scope, Time, Cost, Quality) were wellmanaged (e.g., changed through a formal Change Control Process) >
• Design changes were wellcontrolled >
• Basic project management processes (e.g., Risk Management, Issue Management) were adequate >
• Project tracked progress against baselines and reported accurate status >
• Procurement (e.g., RFP, Contract with vendor) went smoothly >
• Contracted vendor provided acceptable deliverables of appropriate quality, on time, and within budget >
• Stakeholders were satisfied with the information they received >
• The project had adequate Quality Control >
• Requirements – specifications – Test Plan were wellmanaged (e.g., Requirements Management System was used) >
• Risks were manageable >
Human Factors
• Project Manager reported to the appropriate part of the organization >
• Project Manager was effective >
Project Lessons Learned questionnaire Yes No N/AImpact
Low High1 2 3 4 5
Place your cursor in the appropriate boxes and type an X. (Insert additional rows as needed.)
Yes = the project team agrees with the statementNo = the project team does not agree with the statementN/A = this statement does not apply to the projectImpact = the extent to which this factor had an impact on your project
Add a >comment to any question where supporting detail would be helpful
Project Planning
• Project Team was properly organized and staffed >
• Project Manager and staff received adequate training >
• Project Team’s talent and experience were adequate >
• Project team worked effectively on project goals >
• Project team worked effectively with outside entities >
• There was good communication within the Project Team >
• Management gave this project adequate attention and time >
• Resources were not overcommitted >
• Resources were consistently committed to project aims >
• Functional areas cooperated well >
• Conflicting departmental goals did not cause problems >
• Authority and accountability were well defined and public >
Overall
• Initial cost and schedule estimates were accurate >
• Product was delivered within amended schedule >
• Product was delivered within amended budget >
Project Lessons Learned questionnaire Yes No N/AImpact
Low High1 2 3 4 5
Place your cursor in the appropriate boxes and type an X. (Insert additional rows as needed.)
Yes = the project team agrees with the statementNo = the project team does not agree with the statementN/A = this statement does not apply to the projectImpact = the extent to which this factor had an impact on your project
Add a >comment to any question where supporting detail would be helpful
Project Planning
• Overall Change Control was effective >
• External dependencies were understood and wellmanaged >
• Technology chosen was appropriate >
• The project was a technological success >
• Customer’s needs/requirements were met >
• Customer was satisfied with the product >
• Project Objectives were met >
• Business Objectives were met >
Annex: Steps 14: outline of Strategy Document
PART I: CURRENT SITUATION Parliament institutional context
• Mandate & Responsibilities• institutional areas
• General organizational structure by area (organogram)
Services, processes & systems <AREA>
Services Processes
Enabling (ICT **) environment
Information systems ++
Communication channels and mechanisms ++
• <AREA>
• ..• <AREA>
•ICT services & support in parliament **
• ICT department (OR unit OR office OR group OR external contractor)• Services• Roles and responsibility• Governance, policies and standards• ICT Systems & Infrastructure
Communication and Information Dissemination Services & Support in parliament ++
• Department responsible for communication and information dissemination (OR unit OR office OR group OR external contractor)
• Services• Roles and responsibility• Governance, policies and standards• ICT Systems & Infrastructure
PART II: THE FUTUREThe vision statement
• Vision statement for the Parliament• Vision statements by institutional area
Strategic goals and objectives <AREA>
Goal Objectives:
ServicesProcessesICT Systems **Information systems ++
Communication channels and mechanisms ++
• <AREA>..
• <AREA>PART III: THE CHALLENGES
<AREA>• gap analysis
<AREA>• ..
Challenges• Summary of Gap analyses over all Areas• Challenges
PART IV: ACTION PLANSRecommendations
• Overview of recommendations• Mapping challenges recommendations
• Recommendation – detail descriptions• <RECOMMENDATION>
• <ACTIVITY>• <STAKEHOLDER>
Action Plan Roadmap Overview activities – priority – stakeholder – planning Activity based budget
** Specific when also producing an Action Plan for ICT++ Specific when also producing an Action Plan for Communication and Information Dissemination
Annex: Step 1 – Mapping services, processes and systems
Area: Product or Service
Client(s) ProcessProcess Owner
Sub Area: ..
..
..
..
Mapping of ICT systems and applications on parliamentary research processes (1st step)
Area:
Product or Service
Client(s) ProcessProcess owner
System:..
System:..
System:..
System:..
System:..
System:..
Sub Area:
Mapping of ICT systems and applications on parliamentary research processes (2nd step)
Annex: Step 1 SWOT Analysis
Strength WeaknessPerformance within the institutional areasCommunication & Information Dissemination
Services, processes & systemsLegislative draftingParliamentary reportingParliamentary researchLibrary servicesICT infrastructureIntranetinternetRemote connectivitySecurityICT organizationStructured roles & responsibilitiesIndependent budget & resourcesICT servicesUser support & helpdeskPC supportData & Network operationsSystems managementSystems developmentProject managementICT governanceEnterprise wide policies and proceduresEnterprise wide planning
Strengths and Weaknesses
Dimensions of the external environment
Opportunities Threats
Social & economicalPoliticalLegalTechnological
Opportunities and Threats
Annex: Step 3 – Fit/Gap Analysis and Challenges
AREA:
Sub Area: Fit (already have) Gap (not yet have)
Service
Process
System
Human Resources
ICT service & support
ICT governance, policies and procedures
..
..
Fit/Gap analysis by Area and SubArea
Nr. Institutional area Challenge Type Impact
.. .. .. .. ..Challenges by area and type, indicating their impact
Annex : Step 4 – Formulating actions and the action plan for ICT
ICT Systems (→)
Sys- Sys- Sys- Sys- Sys- Sys- Sys- Sys- Sys- Sys- Sys-
Processes ( )
: existing and operational: new systems
Processes supported by new systems
Issues and challenges Impact Strategic Recommendation Priority
Mapping recommendations and challenges
Recommendation: ..Action Key
stakeholdersOutcomes Priority
Recommendation and its activities
Action Stakeholders Resources / Inputs Needed
Priority Year 1 Year 2 Year 3
Quarter Quarter Quarter
1 2 3 4 1 2 3 4 1 2 3 4
Recommendation: ..
Action Stakeholders Resources / Inputs Needed
Priority Year 1 Year 2 Year 3
Quarter Quarter Quarter
1 2 3 4 1 2 3 4 1 2 3 4
Recommendation: ..
Recommendation: ..
Action Plan for ICT
Annex: Evaluation & midterm review
Project Lessons Learned checklist Yes No N/AImpact
Low High1 2 3 4 5
Yes = the project team agrees with the statementNo = the project team does not agree with the statementN/A = this statement does not apply to the projectImpact = the extent to which this factor had an impact on your project
Project Planning
• Project Objectives were specific, measurable, attainable, resultsfocused and timelimited >
• Product concept was appropriate to Project Objectives >
• Project Plan and Schedule were welldocumented, with appropriate structure and detail >
• Project Schedule encompassed all aspects of the project >
• Tasks were defined adequately >
• Stakeholders (e.g., Sponsor, Customer) had appropriate input into the project planning process >
• Requirements were gathered to sufficient detail >
• Requirements were documented clearly >
• Specifications were clear and welldocumented >
• Test Plan was adequate, understandable, and welldocumented >
• External dependencies were identified, agreements signed >
• Project budget was well defined >
• End of Phase Criteria were clear for all project phases >
• Project Plan had buyin from the stakeholders >
• Stakeholders had easy access to Project Plan and Schedule >
Project Execution and Delivery
Project Lessons Learned checklist Yes No N/AImpact
Low High1 2 3 4 5
Yes = the project team agrees with the statementNo = the project team does not agree with the statementN/A = this statement does not apply to the projectImpact = the extent to which this factor had an impact on your project
Project Planning
• Project stuck to its original goals >
• Changes in direction that did occur were of manageable frequency and magnitude >
• Project baselines (Scope, Time, Cost, Quality) were wellmanaged (e.g., changed through a formal Change Control Process) >
• Design changes were wellcontrolled >
• Basic project management processes (e.g., Risk Management, Issue Management) were adequate >
• Project tracked progress against baselines and reported accurate status >
• Procurement (e.g., RFP, Contract with vendor) went smoothly >
• Contracted vendor provided acceptable deliverables of appropriate quality, on time, and within budget >
• Stakeholders were satisfied with the information they received >
• The project had adequate Quality Control >
• Requirements – specifications – Test Plan were wellmanaged (e.g., Requirements Management System was used) >
• Risks were manageable >
Human Factors
• Project Manager reported to the appropriate part of the organization >
• Project Manager was effective >
• Project Team was properly organized and staffed >
• Project Manager and staff received adequate training >
• Project Team’s talent and experience were adequate >
Project Lessons Learned checklist Yes No N/AImpact
Low High1 2 3 4 5
Yes = the project team agrees with the statementNo = the project team does not agree with the statementN/A = this statement does not apply to the projectImpact = the extent to which this factor had an impact on your project
Project Planning
• Project team worked effectively on project goals >
• Project team worked effectively with outside entities >
• There was good communication within the Project Team >
• Management gave this project adequate attention and time >
• Resources were not overcommitted >
• Resources were consistently committed to project aims >
• Functional areas cooperated well >
• Conflicting departmental goals did not cause problems >
• Authority and accountability were well defined and public >
Overall
• Initial cost and schedule estimates were accurate >
• Product was delivered within amended schedule >
• Product was delivered within amended budget >
• Overall Change Control was effective >
• External dependencies were understood and wellmanaged >
• Technology chosen was appropriate >
• The project was a technological success >
Project Lessons Learned checklist Yes No N/AImpact
Low High1 2 3 4 5
Yes = the project team agrees with the statementNo = the project team does not agree with the statementN/A = this statement does not apply to the projectImpact = the extent to which this factor had an impact on your project
Project Planning
• Customer’s needs/requirements were met >
• Customer was satisfied with the product >
• Project Objectives were met >
• Business Objectives were met >
Project Lessons learned checklist