Information Commissioner's Office
|
|
- Beverley Shaw
- 8 years ago
- Views:
Transcription
1 Information Commissioner's Office Review of the Agile process used to develop the ICE system Ian Falconer Partner T: E: Last updated 15 March 2013 Will Simpson Senior Manager T: E: Simon Edwards Associate Director T: E: Distribution Timetable For action Fieldwork completed 14 December 2012 Daniel Benjamin Director of Corporate Draft report issued 16 January 2013 Services Simon Entwistle Director of Operations Management comments 1 February February 2013 For information Christopher Graham Information Commissioner Audit Committee Final report issued 22 February 2013
2 Contents Sections 1 Executive Summary 1 2 Detailed Findings 4 A Internal audit approach 10 B Definition of internal audit ratings 13 C Overview of Methodologies 14 This report is confidential and is intended for use by the Management and Directors of The Information Commissioner's Office only. It forms part of our continuing dialogue with you. It should not be made available, in whole or in part, to any third party without our prior written consent. We do not accept responsibility for any reliance that third parties may place upon this report. Any third party relying on this report does so entirely at its own risk. We accept no liability to any third party for any loss or damage suffered or costs incurred, arising out of or in connection with the use of this report, however such loss or damage is caused. It is the responsibility solely of The Information Commissioner s Office management to ensure that there are adequate arrangements in place in relation to risk management, governance and control.
3 Glossary General terms Capita ICO ICE IT Project Board Agile Waterfall ICO's current IT service provider Information Commissioner's Office ICO Customer Engagement (replacement for Data Protection Notification System) Information Technology Body responsible for representing ICO, monitoring progress and providing authorisation to project on decisions Software development methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration between selforganising, cross-functional teams (see Appendix C) Software development methodology based on a sequential process of requirements analysis, design, implementation, testing (validation), integration, and maintenance. Often referred to as "Traditional" (see Appendix C) Waterfall development terms FRS NFRS SRS Functional Requirements Specification Non Functional Requirements Specification System Requirements Specification UAT RC User Acceptance Testing - final stage before release Release Candidate potential live version of software Agile development terms Epic Requirement for a piece of software typically covering a number of business processes and made up of a large number of Stories eg web site to enable customers to maintain their registration Story A new or upgraded capability of the software able to be delivered within 1-2 weeks by a small number of team members. For each Story an estimate is made of the number of units of work, eg days or hours. Sprint A group of Stories to be delivered together within a 2-6 week period. Scrum Velocity Backlog Done Daily team meeting also known as stand-up meeting The number of units of work completed in a certain interval e.g one week. Outstanding Stories Acceptance criteria for a completed Story
4 1 Executive Summary 1.1 Background The ICE project is designed to replace the ICO's main customer facing system, including the registration of organisations and individuals under the Data Protection Act, and to create a website for self service. Currently the systems used to manage complaints and investigations are excluded from the scope of the project, although it is anticipated that the ICE system will be extended to cover these functions at a later date. The initial business objective was to replace the system in The project began in 2010 and Capita was appointed as the main contractor, but with some specialist work such as the website subcontracted to other companies. The project was developed using a methodology known as 'Waterfall' (see Appendix C) and a detailed Functional Requirement Specification was agreed that is still being used as the basis for the system requirements. In mid-2012 the project began to slip against its original schedule and estimates for testing the software underpinning the new and untested system became unaffordable. In order to address the emerging issues, and improve the speed and cost of managing the systems changes and improvements required, the Project Board decided to adopt a new development methodology, "Agile" (see Appendix C). It formed an Agile team comprising members of management, users and IT Development and based them in the Operations area close to the Registration team who will be early users of the new system. 1.2 Scope The objective of our review was to identify any significant risks associated with the use of the Agile approach to develop a new system. The key subrisks we considered were that: the revised scope and approach to the project may not meet all of the ICO's original business objectives, and/or its use of an Agile methodology may lead to a loss of focus on those business objectives; the ICO may not be ready to adopt an Agile development methodology, leading to development delays or disruption to its business as usual operations; and the ICO may not apply sufficient rigour to the testing phase to ensure a usable system is available to users and/or excessive bugs remain in the system resulting in additional rework and expense to resolve the operational issues. Further details of our scope and approach can be found in Appendix A. 1
5 1.3 Audit Opinion Our focus during this phase of the audit has been on the revised scope of the project, whether the adoption of Agile will affect future success of the project, and the robustness of the approach to testing etc adopted by the ICO to date. Design effectiveness Overall, we have concluded that, except for the specific weaknesses identified by our audit, in the areas examined, the risk management activities and controls are suitably designed to achieve the risk management objectives required by management. The Agile approach has only been partially adopted and the controls within the Agile methodology are not yet fully in place. ICO is still trying to work in a sequential "Waterfall" methodology. This could delay progress on the ICE project. Operating effectiveness Except for the controls listed below those activities and controls that we examined were operating with sufficient effectiveness to provide reasonable assurance that the related risk management objectives were achieved during the period under review. Management needs to ensure that ICO fully adopts the Agile approach across all functions affected by the ICE system, to ensure that the initial release and subsequent enhancements to the system are delivered, implemented and supported successfully. Further details of our findings and recommendations are provided in Section 2. Amber Amber 1.4 Key findings The following table details the key findings from our review. Further details of our findings and recommendations are provided in Section 2. Risk / Process High Medium Low Improve't Meeting original objectives ICO not ready to adopt Agile Sufficiently robust testing approach Total Refer to Appendix B for definitions of internal audit recommendation ratings. We have made no high priority recommendations and four medium priority recommendations. Each aims to help the ICO to establish an appropriate approach using the Agile methodology in the future. Our four medium rated findings are as follows: The Project team is responsible for determining priorities for the Backlog (outstanding work) but has no clear business priorities to support its decision making. The Project team has not documented the benefits, tests and acceptance criteria against each requirement. The ICO has only partially implemented the Agile methodology, with only limited testing of work in progress, no planning to adapt its operational IT support arrangements once ICE has gone live, nor to alter IT processes to accommodate the more frequent releases of software that the new methodology will generate. Some ICO teams who are key to the ultimate success of the ICE project are currently not directly represented on the Agile team, nor are they operating within the Agile methodology. 1 2
6 1.5 Basis of opinion The ICO has adopted an Agile development methodology and established a multi-disciplined team to apply it. The team is working cohesively to develop software in relatively short periods of time, i.e within two to six weeks (these short development phases are known as Sprints). A appropriate team working dynamic is in place within an environment that allows collaborative working. Staff are able to operate as a virtual team and are being allowed to concentrate on Agile matters which will enable an effective operating model to develop. The key areas that have yet to be established are arrangements for complete testing within each development phase and preparations to allow a wider community within the ICO to operate with the Agile methodology once the project has gone live. 1.6 Acknowledgement We would like to take this opportunity to thank the staff involved in for their co-operation during this internal audit. 3
7 2 Detailed Findings 2.1 Meeting original objectives 1. Medium Business priorities not clear to the project team Finding and Implication Proposed action Agreed action (Date / Ownership) The project's current objectives are related to the need to replace the Management to establish clear business Existing backlog reviewed to ensure current system that will become unsupported in the future and to reflect priorities for the ICE project future business benefits clearly prioritised. the potential changes to Data Protection requirements of the European development, and the criteria to be used by Union. the Agile team when deciding which stories to work on next. Complete - December 2012 To deliver this, the ICO needs to establish a set of criteria to allow the Agile team to determine priorities for development. Therefore, when determining what is next for development, it is unclear how this will be done when management delegates the authority to the Agile team to determine priorities based upon a common agreed criteria, in line with Agile methodology. Other business priorities exist but are not clearly stated and used when the team prioritises the Backlog (outstanding functionality) of Stories (discrete software functionality to be delivered) e.g. Longer term, set up an agile steering group to support our agile team by identifying priority areas for system development and articulating business benefits to be realised Taken forward by Simon Entwisle February 2013 Customer service Cost Time Saving Reduction in postage and paper The implication is that future system enhancements will not necessarily lead to an improvement in business performance, as described by the benefits, as business priorities will not be formally considered when the Agile team decides what to do next. 4
8 2. Low Existing ICO project reporting ineffective on the ICE project Finding and Implication Proposed action Agreed action (Date / Ownership) There is a disconnect between Agile project controls and existing ICO project reporting which is more geared to the Waterfall methodology. The gap is being filled by project team management trying to control in one way and report in another. Management to resolve the problems with the Agile reporting and use this to control the project going forward. Project reporting/demonstrations now utilise further agile sprint information from Team Foundation Server dashboards to add further project controls. This problem is compounded by the uncertainty of completeness at the end of each sprint, and delays to testing. This results in difficulties in controlling time and cost Complete - January 2013 Longer term as part of the steering group set-up the ICO is planning to review its project management approach with a view to implementing an agile approach. Review to begin in May Steering group 5
9 2.2 ICO not ready to adopt Agile 3. Medium Functional Requirements have not been defined in full Story format Finding and Implication Proposed action Agreed action (Date / Ownership) As a consequence of the change in methodology mid-project, the Management to ensure that all new Review of user stories carried out and redefined to include full story format including existing Functional Requirements Specification continues to be used as requirements are fully documented in Story the reference for many of the requirements. However, the FRS does format and contain benefits, tests and acceptance criteria. All future requirements not contain all of the information required to follow the Agile acceptance criteria. to be articulated in full user story format. methodology, particularly; Benefits Tests Acceptance Criteria (Done) The consequence is that the absence of test and acceptance criteria makes it time consuming to specify system test requirements and has delayed testing until later Sprints. Complete December
10 4. Medium Agile team skills and working methods Finding and Implication Proposed action Agreed action (Date / Ownership) The current team includes all the skills required to develop and test each Sprint. The team is strongly linked to the business function and gives regular demonstrations, building trust and effective sharing of information. Team working and communication within the team appears good. Management to ensure that all functions necessary for the success of the project are directly represented on the team and operating in Agile methodology. However, the team does not include the skills to be able to migrate data and go-live. These need to become part of the team as soon as possible to encourage a one-team approach, essential for Agile. Two key individuals, the Scrum Master and one of the testers, are leaving the team shortly. This will leave a gap, particularly the Scrum Master who is the person most able to communicate across all areas of the project, technical, business, and management. Test resource returned to the project full time; scrum master retained part-time. The data migration resource had been managed at arms-length by the scrum master; however this resource is now working as part of the agile project team. Going forward agile teams will be adequately resourced including long-term assignment of scrum master and product owner; additional resources such as data migration expertise will be bought in for specific sprints/activities. Complete January Low Agile process not fully integrated into business Finding and Implication Proposed action Agreed action (Date / Ownership) The current team is strongly linked to the business function it is directly supporting, but business functions not on the project team are not yet fully aware of, or following the Agile methodology. It is difficult to work in both Agile and non-agile ways at the same time. Management to educate all areas of the business on the new way of working with IT, and what people can expect if they are involved in an Agile project. Working in a matrix management style is also not fully understood and appreciated by all functions impacted by the project. This is the normal way of working with an Agile methodology where the project team changes over time as the project looks at new functions and processes. It is felt that matrix management and cross office working is a well-established working practice at the ICO. However, longer term as part of the steering group set-up the ICO is planning to review its project management approach with a view to implementing an agile approach which will include education on the agile approach and lessons learned from ICE. There is potential for creating barriers between functions working in different ways, and some resistance to new ways of working Review to begin in May Steering group 7
11 2.3 Sufficiently robust testing approach 6. Medium Main Agile controls and methods not fully implemented Finding and Implication Proposed action Agreed action (Date / Ownership) Under the Agile methodology it is assumed that the completion of a 1/As per finding 2 above, management to 1/All new requirements now fully Sprint means all Stories in that Sprint have been completed, are ready ensure that all new requirements are fully documented in Story format and contain a for use, subject only to final checks and data migration, and that a documented in Story format and contain definition of done. release to production will be undertaken at the end of every Sprint. benefits, tests and acceptance criteria. However, in the ICE project: there is no agreed definition of "Done" for the project, and test and acceptance criteria are missing from the initial FRS documentation and also from new Stories too much testing remains at the end of each Sprint a full system test of all completed Stories has not yet been undertaken whereas Agile would require this to be done frequently full testing is not possible except in the production environment which was only available late in the project, and once live can no longer be used for testing product demonstrations show the systems operating but the level of completeness of testing and readiness for release is misleading no planning for Agile support post go-live has been undertaken the current release process is not designed to support regular releases of new Stories The implication is that the main Agile measure of progress, "Velocity", does not fully reflect actual progress on the project and therefore end date estimates are not reliable. 2/Management to provide an environment that allows full end to end testing including interfaces at any time. This will be required on a permanent basis to support testing of both maintenance Stories and new Stories 3/Management to plan post go-live support under Agile. 4/Management to review the calculation of Velocity and assumptions made, and agree a reliable measure of progress. Complete December 2012 Accepted. We have production, staging and development environments for both the CRM and web components. These will carry over as the service goes live and be permanently available. The level of testing that can be carried out in each environment is different and subject to some restrictions. The staging environment is a very close replica of live with the exception that it does not interface automatically to the external components. Where full end to end testing is considered necessary from the staging environment to any external component then manual processes/steps and controls will be put in place to transfer data. It is considered that the small number of changes likely to require full end to end testing are low, the external components are loosely coupled and do not require immediacy of data transfer and can be handled with manual intervention without impact the testing schedule or the confidence in testing Closed January /Post go live support has been agreed 8
12 6. Medium Main Agile controls and methods not fully implemented Finding and Implication Proposed action Agreed action (Date / Ownership) with Capita through to July 2013 for CRM, support for the servers and SQL databases. Support of the ICE configurations will lie with the Agile development team through a post go live support period. More detailed planning will take place through March and April to agree how the CRM and Agile team handle both support and new developments. Owner :- Head of Corporate services and Operations. April /As part of the steering group set-up the ICO is planning to review its project management approach with a view to implementing an agile approach which will include a review of the calculation of velocity and agreement on a reliable measure of progress. Review to begin in May Steering group 9
13 A Internal audit approach Approach and Scope The objective of the review was to identify significant risks when adopting Agile approach to developing a new system, for future phases and projects. We focussed on the following sub risks: the revised scope and approach to the project may not meet all of the ICO's original business objectives, and/or the use of an Agile methodology may lead to a loss of focus on those business objectives; the ICO is not ready to adopt an Agile development methodology, leading to development delays or disruption to business as usual operational; and the ICO may not apply sufficient rigour to the testing phase to ensure a usable system is available to users and/or excessive bugs remain in the system resulting in additional rework and expense to resolve the operational issues. Our internal audit approach is based upon the underlying principles of the UK Corporate Governance Code (2010) guidelines on internal control that require management to identify, assess and manage the risks that are significant to the achievement of the organisation s overall business objectives. Our role as internal auditor is to provide objective and independent assurance to the Audit Committee and management that it is doing this successfully for each of the areas being audited. Our audit was carried out in accordance with the guidance contained within the Government s Internal Audit Standards (2011) and the Auditing Practices Board s Guidance for Internal Auditors. We also have regard to the Institute of Internal Auditors guidance on risk based internal auditing (2005). In accordance with our agreed internal audit plan, we agreed to undertake a review of the agile process applied to the Information Commissioner's Office's ICE project to replace key systems within ICO. This review will further inform our on-going understanding of ICO's governance and risk management activities. We achieved our audit objectives by: meeting with key staff to gain an understanding of the arrangements in place, building upon the information we have already gained through our audit planning process; assessing the effectiveness of the control mechanisms in place to mitigate identified risks; discussion of key findings with management and preparation of a draft report. The findings and conclusions from this review will support our annual opinion to the Audit Committee on the adequacy and effectiveness of internal control arrangements. 10
14 Responsibilities It is the responsibility of management to ensure that there are adequate controls and activities in place to ensure that the ICO's business objectives can be met and that the risks to the ICO are minimised. Based on the work we have carried out, we provide an objective assessment of the adequacy and effectiveness of controls and activities established by management to manage the identified risks to the ICO. During the course of our review we have conducted interviews and, where necessary, testing/verification work to support our assessment of the adequacy and effectiveness of current arrangements. It is our reporting protocol to balance our reporting of positive practice with areas for attention. This enables the ICO to build upon its strengths, whilst focusing upon key findings and associated recommendations, which if acted upon, should enhance the control environment and improve the management of key risks. Please refer to our letter of engagement for full details of responsibilities and other terms and conditions. Additional information Client staff The following people were consulted as part of this review: Daniel Benjamin, Director of Corporate Services Simon Entwistle Director of Operations David Wells, Head of IT Paul Arnold, Head of Customer Contact Agile Team Members Emma Dean Uno Smith Traci Shirley Andrew Jarvis Julia Harrison Ian Campbell Richard Bennett Vijay Deshpande Brian McCone Simon Mackel Locations The Wilmslow Office was visited during the course of this review: 11
15 Documents The following documents were reviewed during the course of this engagement: Changes - user journey.docx Deploying Microsoft Dynamics CRM Solutions from Development through Test and Production Environments.pdf Development progress tracking spreadsheet xlsx ICE - Operational readiness backlog v0.1.xlsx ICE Backlog pre TFS.xlsx Non Functional Requirements - V1.0.docx ICE project weekly update meeting - agenda and actions.msg Indigo ICE project roles.docx Indigo_CRM_Functional design specification_v61 - ICO.docx IRCICERegParticularsPaperJuly2012v1 0.docx Microsoft Word - ICE Reqirements Final v1.0.pdf MicrosoftDynamicsCRM2011-ImplementationGuide-Planning.pdf Ops readiness plan Jan-Apr 2013.pdf Ops readiness timeline Jan-Apr 2013.pdf P ICE - Plan - Budget.xls P ICE - Plan - Project Initiation Document.docx PB update msg Registration Application - user journey.docx Renewals - user journey.docx Service transformation summary Sept12.docx Simplified NoW requirement.docx Sprint 6 and 7 outstanding.xlsx Sprint five backlog.docx Sprint four backlog.docx Sprint one backlog - pre TFS.xlsx Sprint one backlog.docx Sprint summary - sprint five.docx Sprint summary - sprint four.docx Sprint summary - sprint one and two.docx Sprint summary - sprint three.docx Sprint summary - sprint zero further update to docx Sprint summary - sprint zero interim to docx Sprint three backlog.docx Sprint two backlog.docx 12
16 B Definition of internal audit ratings Internal audit opinion Design effectiveness Opinion Operating effectiveness Rating We have not been able to form an opinion on whether the internal controls examined have been designed to achieve the risk management objectives required by management Overall, we have concluded that, in the areas examined, the risk management activities and controls are suitably designed to achieve the risk management objectives required by management Overall, we have concluded that, except for the specific weaknesses identified by our audit, in the areas examined, the risk management activities and controls are suitably designed to achieve the risk management objectives required by management. Overall, we have concluded that, in the areas examined, the risk management activities and controls are not suitably designed to achieve the risk management objectives required by management. No opinion can be given Green Amber Red We have not been able to form an opinion on whether the internal controls examined were operating to provide reasonable assurance that the related risk management objectives were achieved during the period under review Those activities and controls were operating with sufficient effectiveness to provide reasonable assurance that the related risk management objectives were achieved during the period under review Except for the controls listed below those activities and controls that we examined were operating with sufficient effectiveness to provide reasonable assurance that the related risk management objectives were achieved during the period under review. Those activities and controls that we examined were not operating with sufficient effectiveness to provide reasonable assurance that the related risk management objectives were achieved during the period under review No opinion can be given Green Amber Red Audit issue rating Within each report, every audit issue is given a rating. The ratings are summarised in the table below. Rating Description Features High Medium Low Improvement Findings that are fundamental to the management of risk in the business area, representing a weakness in control that requires the immediate attention of management Important findings that are to be resolved by line management. Findings that identify non-compliance with established procedures. Items requiring no action but which may be of interest to management or best practice advice Key control not designed or operating effectively Potential for fraud identified Non compliance with key procedures / standards Non compliance with regulation Impact is contained within the department and compensating controls would detect errors Possibility for fraud exists Control failures identified but not in key controls Non compliance with procedures / standards (but not resulting in key control failure) Minor control weakness Minor non compliance with procedures / standards Information for department management Control operating but not necessarily in accordance with best practice 13
17 C Overview of Methodologies Waterfall (traditional) systems development methodology Waterfall development methodology generally start with a business analyst designing the new or revised business process, followed by production of a Functional Requirements Specification (FRS) detailing all functional capabilities of the new or revised system to support the business process. This FRS is signed off by the user departments as the start of the development. General system features such as performance, user access, security and other non-functional requirements are documented and approved in a Non-Functional Requirements Specification (NFRS). Following selection of the technology to be used, a development team produces a System Design and takes the FRS and NFRS documents and turns them into System Requirements Specifications (SRS). Each part of the system is then built and tested individually by the development team against these SRS documents. The parts of the system are then assembled into one release for testing by the user departments. Following initial user testing, bugs and change requests are fed back to the development team which either reworks the system, or moves change requests into a later release. Once an acceptable level of functionality has been achieved, and migration of live data has been tested, User Acceptance Testing (UAT) of a release candidate (RC) is undertaken. Once the RC has successfully completed a final (UAT), the system is handed over to production, users are trained, migration of live data is undertaken and the new or upgraded system goes live. The process then repeats for further releases. The key features of this process are: extensive formal documentation of exactly what is required, produced well in advance, and signed off by the recipients. a series of handovers between several different departments and business functions. testing and acceptance generally done at the end of the process releases to production done infrequently typically every few months missing or incomplete requirements identified during development often have to wait until later releases. Agile development methodology Software development methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organising, cross-functional teams. The team (often located into one area of an office) is created with all key skills required to deliver and implement a completed system including business analysis, design, end-user experience and knowledge, end-user management, project management, development, testing, training, migration and IT operations. 14
18 Initial meetings clarify the overall scope of the new or revised system and processes, documented as one or more Epics. In parallel, User Journeys are documented, the typical routes through a system by end users. For each Epic, workshops create Stories of the following form: As a...role I want.capability so that... BENEFIT. how will I know...test. I am satisfied if.done.. Most stories are driven by user roles and relate to business or functional requirements. However, Stories can also relate to non-functional requirements and support for the work of the team members. A Story should be as self-contained as possible and at a level of complexity which can be fully developed and tested with a couple of weeks. The Stories are added to a Backlog which becomes a prioritised list of outstanding Stories, and records progress on completing Stories. The key features of this process are: documentation produced on an as required basis no handovers as all key skills are in the same team testing and acceptance done all the way through the process rather than at the end control of scope and end dates down to the skill of the Scrum Master who must have technology, business and project skills missing or incomplete requirements identified at every stage and simply added to the Backlog no distinction between a development project and maintenance; maintenance requests are simply more Stories added to the Backlog The team is led by a Scrum Master who acts in the role of team facilitator and project manager. The team meets each day for a short meeting, called the daily Scrum, often undertaken standing up to reinforce the need for a short meeting. Anyone in the organisation can attend a Scrum as an observer. The Scrum Master prioritises the Backlog and agrees at a Scrum a number of Stories to work on over the next period, known as a Sprint. A Sprint will last for between 2 and 6 weeks, and at end of the Sprint the outcome is normally a group of new or changed system capabilities, tested and ready for release. Team members take responsibility for a specific Stories and can talk to other team members and request support at any time. The Scrum reviews new Stories, progress and issues each day. The Scrum Master maintains an updated Backlog, and uses Velocity, a measure of the number of Stories and effort expended per period, and the size of the Backlog to estimate time and cost for the project. 15
19 Grant Thornton UK LLP. All rights reserved. "Grant Thornton" means Grant Thornton UK LLP, a limited liability partnership. Grant Thornton UK LLP is a member firm within Grant Thornton International Ltd ('Grant Thornton International'). Grant Thornton International and the member firms are not a worldwide partnership. Services are delivered by the member firms independently. This publication has been prepared only as a guide. No responsibility can be accepted by us for loss occasioned to any person acting or refraining from acting as a result of any material in this publication.
Information Commissioner's Office
Information Commissioner's Office Internal Audit 2013-14: Follow up Last updated 4 July 2014 Distribution For action Senior Corporate Governance Manager Timetable Fieldwork completed 21 May 2014 Draft
More informationInformation Commissioner's Office
Information Commissioner's Office IT Procurement Review Ian Falconer Partner T: 0161 953 6480 E: ian.falconer@uk.gt.com Last updated 18 June 2012 Will Simpson Senior Manager T: 0161 953 6486 E: will.g.simpson@uk.gt.com
More informationInformation Commissioner's Office
Phil Keown Engagement Lead T: 020 7728 2394 E: philip.r.keown@uk.gt.com Will Simpson Associate Director T: 0161 953 6486 E: will.g.simpson@uk.gt.com Information Commissioner's Office Internal Audit 2015-16:
More informationInformation Commissioner's Office
Information Commissioner's Office Ian Falconer Partner T: 0161 953 6480 E: ian.falconer@uk.gt.com Internal Audit 2011-12: Business Continuity Review Last updated 6 February 2012 Will Simpson Senior Manager
More informationInternal Audit Monitoring Report. Audit Report status Assurance. Payroll Final Limited
Appendix 1 Internal Audit Monitoring Report Audit Report status Assurance Payroll Final Limited The Payroll system was reviewed to seek assurance that processes and procedures are operating effectively
More informationSOUTH NORTHAMPTONSHIRE COUNCIL. 11/31 ICT Capacity Management FINAL REPORT. June 2011
SOUTH NORTHAMPTONSHIRE COUNCIL 11/31 ICT Capacity Management FINAL REPORT June 2011 This report and the work connected therewith are subject to the Terms and Conditions of the contract dated 18/06/07,
More informationDacorum Borough Council Final Internal Audit Report. IT Business Continuity and Disaster Recovery
Dacorum Borough Council Final Internal Audit Report IT Business Continuity and Disaster Recovery Distribution list: Chris Gordon Group Manager Performance, Policy and Projects John Worts ICT Team Leader
More informationInternal Audit - progress report 2015-16 and 2016-17 plan
Audit Committee, 16 March 2016 Internal Audit - progress report 2015-16 and 2016-17 plan Executive summary and recommendations Introduction Grant Thornton have prepared the attached report which sets out
More informationVale of Glamorgan. Overview Report: Review of HR and Workforce Planning. November 2011
Vale of Glamorgan Overview Report: Review of HR and Workforce Planning November 2011 Content 1 Introduction 1 2. Review Findings 3 3. The Way Forward 17 2012 Grant Thornton UK LLP. All rights reserved.
More informationCapital Projects. Providing assurance over effective delivery of projects
Capital Projects Providing assurance over effective delivery of projects Governance and oversight Project Scope and change Reporting and communication Project risk and success factors Delivery Major projects
More informationClinical Risk Management: Agile Development Implementation Guidance
Document filename: Directorate / Programme Document Reference NPFIT-FNT-TO-TOCLNSA-1306.02 CRM Agile Development Implementation Guidance v1.0 Solution Design Standards and Assurance Project Clinical Risk
More informationLloyd s Managing Agents FSA Solvency II Data Audit
Lloyd s Managing Agents FSA Solvency II Data Audit Working in partnership with you to provide the independent assurance that your Data Audit Report fulfils Lloyd s and FSA Solvency II requirements Lloyd
More informationAGILE BUSINESS INTELLIGENCE
AGILE BUSINESS INTELLIGENCE OR HOW TO GIVE MANAGEMENT WHAT THEY NEED WHEN THEY NEED IT Evan Leybourn Author Directing the Agile Organisation Melbourne, Australia evan@theagiledirector.com INTRODUCTION
More informationGUIDELINE NO. 22 REGULATORY AUDITS OF ENERGY BUSINESSES
Level 37, 2 Lonsdale Street Melbourne 3000, Australia Telephone.+61 3 9302 1300 +61 1300 664 969 Facsimile +61 3 9302 1303 GUIDELINE NO. 22 REGULATORY AUDITS OF ENERGY BUSINESSES ENERGY INDUSTRIES JANUARY
More informationUnderstanding Agile Project Management
Understanding Agile Project Management Author Melanie Franklin Director Agile Change Management Limited Overview This is the transcript of a webinar I recently delivered to explain in simple terms what
More informationData Quality - A Review of the Audit Committee
AGENDA ITEM 6 TRANSPORT FOR LONDON AUDIT COMMITTEE SUBJECT: DATA QUALITY REVIEW 2007/08 DATE: 25 NOVEMBER 2008 1 PURPOSE AND DECISION REQUIRED 1.1 As part of its assessments of TfL, the Audit Commission
More informationShared service centres
Report by the Comptroller and Auditor General Cabinet Office Shared service centres HC 16 SESSION 2016-17 20 MAY 2016 4 Key facts Shared service centres Key facts 90m estimated savings made to date by
More informationQUICK FACTS. Providing Application Development and Data Migration Support for a Leading Healthcare Company
[ Healthcare Services, Application Development ] TEKsystems Global Services Customer Success Stories Client Profile Industry: Healthcare Revenue: Private Employees: Over 400 Geographic Presence: Locations
More informationNetwork Rail Infrastructure Projects Joint Relationship Management Plan
Network Rail Infrastructure Projects Joint Relationship Management Plan Project Title Project Number [ ] [ ] Revision: Date: Description: Author [ ] Approved on behalf of Network Rail Approved on behalf
More informationConfident in our Future, Risk Management Policy Statement and Strategy
Confident in our Future, Risk Management Policy Statement and Strategy Risk Management Policy Statement Introduction Risk management aims to maximise opportunities and minimise exposure to ensure the residents
More informationBridgend County Borough Council. Corporate Risk Management Policy
Bridgend County Borough Council Corporate Risk Management Policy December 2014 Index Section Page No Introduction 3 Definition of risk 3 Aims and objectives 4 Strategy 4 Accountabilities and roles 5 Risk
More informationThe style is: a statement or question followed by four options. In each case only one option is correct.
AGILE FOUNDATION CERTIFICATE SAMPLE FOUNDATION QUESTIONS WITH ANSWERS This document is a set of sample questions, in the style of the Agile Foundation Certificate Examination, which is a 60 question, 1
More informationInvestment Management Standard. A guide for Victorian government departments and agencies
Investment Management Standard A guide for Victorian government departments and agencies The Secretary Department of Treasury and Finance 1 Treasury Place Melbourne Victoria 3002 Australia Telephone: +61
More informationSuccessful CRM. Delivered. Prepare for CRM Success. Our How to start right and stay right!
Successful CRM. Delivered. Prepare for CRM Success Our How to start right and stay right! ConsultCRM: Prepare for CRM Success Introduction ConsultCRM has years of experience in the area of Customer Relationship
More informationAberdeen City Council IT Disaster Recovery
Aberdeen City Council IT Disaster Recovery Internal Audit Report 2014/2015 for Aberdeen City Council January 2015 Terms or reference agreed 4 weeks prior to fieldwork Target Dates per agreed Actual Dates
More informationFINAL. Internal Audit Report. Employees Travel and Subsistence Expenses 2014/15
FINAL Internal Audit Report Employees Travel and Subsistence Expenses 2014/15 Document Details: Reference: 2.14/2014.15 Senior Manager, Internal Audit & Assurance: ext. 6567 Engagement Manager: Audit Assistant
More informationInforming the audit risk assessment Enquiries to those charged with governance Calderdale Council. Year ended 31 March 2013
Informing the audit risk assessment Enquiries to those charged with governance Calderdale Council This version of the report is a draft. Its contents and subject matter remain under review and its contents
More informationBirmingham Women s NHS Foundation Trust
Birmingham Women s NHS Foundation Trust Data protection audit report Executive summary January 2015 1. Background The Information Commissioner is responsible for enforcing and promoting compliance with
More informationWhite Paper On Pilot Method Of ERP Implementation
White Paper On Pilot Method Of ERP Implementation Rod Clarke Rod Clarke provides guidance, advice and support to businesses in successfully applying IS/IT in support of their business goals. He brings
More informationThe Audit Plan for West Mercia Energy Joint Committee
The Audit Plan for West Mercia Energy Joint Committee Year ended 31 March 2015 16th February 2015 Jon Roberts Partner T 0121 232 5410 E jon.roberts@uk.gt.com Andrew Davies Manager T 0121 232 5417 E andrew.davies@uk.gt.com
More informationDacorum Borough Council Final Internal Audit Report
Dacorum Borough Council Final Internal Audit Report ICT Change Management Distribution list: Chris Gordon Group Manager Neil Telkman - Information, Security and Standards Officer Gary Osler ICT Service
More informationAuditing data protection a guide to ICO data protection audits
Auditing data protection a guide to ICO data protection audits Contents Executive summary 3 1. Audit programme development 5 Audit planning and risk assessment 2. Audit approach 6 Gathering evidence Audit
More informationAudit Committee, 28 November. HCPC Project Risk Management. Executive summary and recommendations. Introduction
Audit Committee, 28 November HCPC Project Risk Management Executive summary and recommendations Introduction At its meeting on 29 September 2013 the Committee agreed that it would receive the Education
More informationSouth Northamptonshire Council Contract Assurance: Leisure Contract
South Northamptonshire Council Contract Assurance: Leisure Contract FINAL Internal Audit Report 2012/2013 January 2013 Contents 1. Executive summary 4 2. Background and scope 5 3. Detailed current year
More informationThe Annual Audit Letter for West Mercia Police and Crime Commissioner and Chief Constable
The Annual Audit Letter for West Mercia Police and Crime Commissioner and Chief Constable Year ended 31 March 2015 October 2015 John Gregory Director and Engagement Lead T +44 (0)121 232 5333 E john.gregory@uk.gt.com
More informationRISK MANAGEMENT STRATEGY
RISK MANAGEMENT STRATEGY 1 Introduction The purpose of this document is to outline a which facilitates the effective recognition and management of risks facing the University. The Combined Code on Corporate
More information2.0 RECOMMENDATIONS Members of the Committee are asked to note the information contained within this report.
REPORT TO: SCRUTINY COMMITTEE 25 JUNE 2013 REPORT ON: REPORT BY: INTERNAL AUDIT REPORTS CHIEF INTERNAL AUDITOR REPORT NO: 280-2013 1.0 PURPOSE OF REPORT To submit to Members of the Scrutiny Committee a
More informationEntitlements Management System (EMS) Technology Update Project Health Check Review
Entitlements Management System (EMS) Technology Update Project Health Check Review February 2010 Final This report and PricewaterhouseCoopers deliverables are intended solely for the Department of Finance
More informationWest Dunbartonshire Council. Follow-up data protection audit report
West Dunbartonshire Council Follow-up data protection audit report Auditors: Lee Taylor (Audit Team Manager) Jonathan Kay (Engagement Lead Auditor) Data controller contacts: Michael Butler (Data Protection/Information
More informationArgyll and Bute Council
Argyll and Bute Council 3 June 2009 Contents Page 1 Executive Summary 1 Appendices A B Action plan Progress in implementation of prior year recommendations 1 1 Executive Summary 1.1 Introduction The Council's
More informationDRAFT. Report to Governors on the Quality Report 2015/16. Royal United Hospitals Bath NHS Foundation Trust] Year ended 31 March 2016 16 May 2016
Report to Governors on the Quality Report 2015/16 This version of the report is a draft. Its contents and subject matter remain under review and its contents may change and be expanded as part of the finalisation
More informationIT REVIEW OF THE DISASTER RECOVERY ARRANGEMENTS
NOTTINGHAM CITY HOMES IT REVIEW OF THE DISASTER RECOVERY ARRANGEMENTS Report issued: February 2011 Audit Plan: The matters raised in this report are only those that came to the attention of the auditor
More informationProject, Programme and Portfolio Management Delivery Plan 6
Report title Agenda item Project, Programme and Portfolio Management Delivery Plan 6 Meeting Performance Management and Community Safety Panel 27 April 2009 Date Report by Document number Head of Strategy
More informationAberdeen City Council
Aberdeen City Council Internal Audit Report Final Contract management arrangements within Social Care & Wellbeing 2013/2014 for Aberdeen City Council January 2014 Internal Audit KPI Targets Target Dates
More informationScrum in a Large Project Theory and Practice
Scrum in a Large Project Theory and Practice Agile World 2012 Munich, July 12, 2012 Dr. Sebastian Stamminger Scrum in Large Projects Agenda Theory Case Study Teams Our Process Challenges Lessons Learned
More informationStatistics New Zealand is Agile Continued Implementation of AGILE Process at Statistics NZ
Distr. GENERAL WP.22 17 May 2011 ENGLISH ONLY UNITED NATIONS ECONOMIC COMMISSION FOR EUROPE (UNECE) CONFERENCE OF EUROPEAN STATISTICIANS EUROPEAN COMMISSION STATISTICAL OFFICE OF THE EUROPEAN UNION (EUROSTAT)
More informationChange Management Office Benefits and Structure
Change Management Office Benefits and Structure Author Melanie Franklin Director Agile Change Management Limited Contents Introduction 3 The Purpose of a Change Management Office 3 The Authority of a Change
More informationCumbria Constabulary. Business Continuity Planning
Cumbria Constabulary Business Continuity Planning 0 Cumbria Shared Internal Audit Service Images courtesy of Carlisle City Council except: Parks (Chinese Gardens), www.sjstudios.co.uk, Monument (Market
More informationPROJECT MANAGEMENT FRAMEWORK
PROJECT MANAGEMENT FRAMEWORK DOCUMENT INFORMATION DOCUMENT TYPE: DOCUMENT STATUS: POLICY OWNER POSITION: INTERNAL COMMITTEE ENDORSEMENT: APPROVED BY: Strategic document Approved Executive Assistant to
More informationCourse Title: Managing the Agile Product Development Life Cycle
Course Title: Managing the Agile Product Development Life Cycle Course ID: BA25 Credits: 28 PDUs Course Duration: 4 days (with optional Executive session) Course Level: Intermediate/Advanced Course Description:
More informationBusiness Operations. Module Db. Capita s Combined Offer for Business & Enforcement Operations delivers many overarching benefits for TfL:
Module Db Technical Solution Capita s Combined Offer for Business & Enforcement Operations delivers many overarching benefits for TfL: Cost is reduced through greater economies of scale, removal of duplication
More informationAberdeen City Council. Performance Management Process. External Audit Report o: 2008/19
Aberdeen City Council Performance Management Process External Audit Report o: 2008/19 Draft Issued: 11 February 2009 Final Issued: 6 April 2009 Contents Pages Pages Management Summary Introduction 1 Background
More informationA flexible approach to outsourcing in the financial services sector
A flexible approach to outsourcing in the financial services sector A White Paper produced by Eversheds in association with Serco Global Services - February 2015 A flexible approach to outsourcing in the
More informationCouncil, 14 May 2015. Information Governance Report. Introduction
Council, 14 May 2015 Information Governance Report Introduction 1.1 The Information Governance function within the Secretariat Department is responsible for the HCPC s ongoing compliance with the Freedom
More informationReview of Financial Planning and Monitoring. City of York Council Audit 2008/09 Date
Review of Financial Planning and Monitoring City of York Council Audit 2008/09 Date Contents Introduction and Background 3 Audit approach 4 Main conclusions 5 Financial Planning Findings 6 Financial Monitoring
More informationHow Silk Central brings flexibility to agile development
How Silk Central brings flexibility to agile development The name agile development is perhaps slightly misleading as it is by its very nature, a carefully structured environment of rigorous procedures.
More informationColeg Gwent Internal Audit Report 2012/13 Assets and Inventory. Assurance Rating:
Coleg Gwent Internal Audit Report 2012/13 Assets and Inventory Assurance Rating: Distribution List: Draft Report: Principal Vice Principal, (Finance, Estates and Information Services) Clerk to the Corporation
More informationUpdate on HR/Payroll and Recruitment System Implementation
GOVERNANCE COMMITTEE Agenda Item 102 Brighton & Hove City Council Subject: Date of Meeting: 27 April 2010 Report of: Update on HR/Payroll and Recruitment System Implementation Director of Strategy and
More informationHead of Internal Audit:
Head of Internal : Opinion on the effectiveness of the system of Internal Control at Northern Devon Healthcare NHS Trust for the year ended 31 March 2010 Roles and responsibilities The whole Board of Directors
More informationManchester City Council
Manchester City Council Accounts Audit Plan 2009/10 18 December 2009 Contents Page 1 Introduction 2 2 Approach and audit risks 3 3 Administration 13 4 Planned outputs 16 Appendices A B IFRS Action Plan
More informationInternal Audit. Audit of HRIS: A Human Resources Management Enabler
Internal Audit Audit of HRIS: A Human Resources Management Enabler November 2010 Table of Contents EXECUTIVE SUMMARY... 5 1. INTRODUCTION... 8 1.1 BACKGROUND... 8 1.2 OBJECTIVES... 9 1.3 SCOPE... 9 1.4
More informationProject Management Toolkit Version: 1.0 Last Updated: 23rd November- Formally agreed by the Transformation Programme Sub- Committee
Management Toolkit Version: 1.0 Last Updated: 23rd November- Formally agreed by the Transformation Programme Sub- Committee Page 1 2 Contents 1. Introduction... 3 1.1 Definition of a... 3 1.2 Why have
More informationSCHEDULE 16. Exit Plan. sets out the strategy to be followed on the termination (including Partial Termination) or expiry of this Agreement; and
SCHEDULE 16 Exit Plan 1. Scope 1.1 This schedule: (A) sets out the strategy to be followed on the termination (including Partial Termination) or expiry of this Agreement; and requires the Service Provider
More informationIT Operations Management: A Service Delivery Primer
IT Operations Management: A Service Delivery Primer Agile Service Delivery Creates Business Value Today, IT has to innovate at an ever- increasing pace to meet accelerating business demands. Rapid service
More informationCost effective methods of test environment management. Prabhu Meruga Director - Solution Engineering 16 th July SCQAA Irvine, CA
Cost effective methods of test environment management Prabhu Meruga Director - Solution Engineering 16 th July SCQAA Irvine, CA 2013 Agenda Basic complexity Dynamic needs for test environments Traditional
More information1.1 To provide highlight reports for all the Council s corporately significant projects, covering the period up to the end of June 2006.
The Executive Agenda item: On 12 September Report Title: Programme Highlight Report June 2006 Forward Plan reference number (if applicable): Report of: The Chief Executive Wards(s) affected: All Report
More informationAudit of Business Continuity Planning
Cumbria Office of the Police & Crime Commissioner Audit of Business Continuity Planning 0 Cumbria Shared Internal Audit Service Images courtesy of Carlisle City Council except: Parks (Chinese Gardens),
More informationHow To Plan An Agile Project
GAO Scheduling Best Practices Applied to an Agile Setting by Juana Collymore and Brian Bothwell April 15, 2015 Outline Why is scheduling important? GAO Schedule Assessment Guide Overview Status of the
More informationScotland s Commissioner for Children and Young People Records Management Policy
Scotland s Commissioner for Children and Young People Records Management Policy 1 RECORDS MANAGEMENT POLICY OVERVIEW 2 Policy Statement 2 Scope 2 Relevant Legislation and Regulations 2 Policy Objectives
More informationInternal Audit at the University of Cambridge.
Internal Audit at the University of Cambridge. Contents Introduction to Deloitte 1 Our team 2 What is Internal Audit? 4 Our approach to Internal Audit 5 Authority and reporting lines 7 Planning 8 Ad Hoc
More informationGateway review guidebook. for project owners and review teams
Gateway review guidebook for project owners and review teams The State of Queensland (Queensland Treasury and Trade) 2013. First published by the Queensland Government, Department of Infrastructure and
More informationTaking the first step to agile digital services
Taking the first step to agile digital services Digital Delivered. Now for Tomorrow. 0207 602 6000 mbailey@caci.co.uk @CACI_Cloud 2 1. Background & Summary The Government s Digital by Default agenda has
More informationPage 5. The Adult Social Services and Health Committee. The Strategic Director of Adult Social Services, Housing and Health
Page 5 Agenda Item 5 Report to: The Adult Social Services and Health Committee Date: 20 th November 2012 Report of: The Strategic Director of Adult Social Services, Housing and Health Ward Location: All
More informationSHAREPOINT SERVICE DEFINITION. G-CLOUD Commercial-in-Confidence. civil.lockheedmartin.co.uk
SHAREPOINT SERVICE DEFINITION G-CLOUD Commercial-in-Confidence civil.lockheedmartin.co.uk SECTION 1 LOCKHEED MARTIN S SHAREPOINT CAPABILITY Lockheed Martin offers a full end to end service, delivering
More informationAudit Report for South Lakeland District Council. People and Places Directorate Neighbourhood Services. Audit of Grounds Maintenance
Audit Report for South Lakeland District Council People and Places Directorate Neighbourhood Services Audit of Grounds Maintenance Cumbria Shared Internal Audit Service: Internal Audit Report 7 th November
More informationTable of contents. Performance testing in Agile environments. Deliver quality software in less time. Business white paper
Performance testing in Agile environments Deliver quality software in less time Business white paper Table of contents Executive summary... 2 Why Agile? And, why now?... 2 Incorporating performance testing
More informationIntegrating PRINCE2 and Scrum for successful new product development
1 Goal Professional Services Pty Ltd 2 Renewtek Pty Ltd Integrating PRINCE2 and Scrum for successful new product development Rankins G J 1 and Kearns M 2 This paper was presented at the Australian Institute
More informationGravesham Borough Council
Gravesham Borough Council Report to: Finance & Audit Committee Date: 21 February 2008 Reporting officer: Subject: Senior Auditor Audit Opinion of Unsatisfactory Council Tax Purpose and summary of report:
More informationBusiness Continuity Business Impact Analysis arrangements
Aberdeen City Council Internal Audit Report 2012/2013 for Aberdeen City Council May 2013 Business Continuity Business Impact Analysis arrangements Final Report Contents Section Page 1. Executive Summary
More informationSTL Microsoft Dynamics CRM Consulting and Support Services
STL Microsoft Dynamics CRM Consulting and Support Services STL Technologies Equis House Eastern Way Bury St Edmunds Suffolk IP32 7AB Service Description and Pricing Specialist Cloud Services www.stl.co.uk
More informationBuilding Software in an Agile Manner
Building Software in an Agile Manner Abstract The technology industry continues to evolve with new products and category innovations defining and then redefining this sector's shifting landscape. Over
More informationBusiness Solutions Manager Self and contribution to Team. Information Services
POSITION DESCRIPTION Position Title: Responsible To: Responsible For Agile Test Analyst Business Solutions Manager Self and contribution to Team Position Purpose: The Agile Test Analyst is responsible
More informationAxe in the Agile World
Axe in the Agile World WHITE PAPER Executive Summary This paper explains the way in which Axe (Odin s Enterprise Test Automation Platform) allows the automated testing to take place in a range of project
More informationNHS DORSET CLINICAL COMMISSIONING GROUP GOVERNING BODY INFORMATION GOVERNANCE TOOLKIT REPORT
NHS DORSET CLINICAL COMMISSIONING GROUP GOVERNING BODY INFORMATION GOVERNANCE TOOLKIT REPORT 9.7 Date of the meeting 15/07/2015 Author Sponsoring Clinician Purpose of Report Recommendation J Green - Head
More informationMANAGING DIGITAL CONTINUITY
MANAGING DIGITAL CONTINUITY Project Name Digital Continuity Project DRAFT FOR CONSULTATION Date: November 2009 Page 1 of 56 Contents Introduction... 4 What is this Guidance about?... 4 Who is this guidance
More informationAgile Scrum Workshop
Agile Scrum Workshop What is agile and scrum? Agile meaning: Able to move quickly and easily. Scrum meaning: a Rugby play Agile Scrum: It is an iterative and incremental agile software development framework
More informationThe University s responsibilities and its arrangements for internal audit Internal audit protocol 2014/15 to 2016/17
The University s responsibilities and its arrangements for internal audit Internal audit protocol 2014/15 to 2016/17 Summary This paper sets out the University s current obligations and arrangements for
More informationAgile for Project and Programme Managers
Agile for Project and Programme Managers Author Melanie Franklin Director Agile Change Management Limited Introduction I am involved in a mixture of assignments for different organisations across Europe
More informationDigital Marketplace Services Service Definition
Digital Marketplace Services Service Definition Arrk Limited Manchester Science Park Pencroft Way Manchester M15 6JJ Tel: +44 161 227 9900 Fax: +44 016 227 9966 www.arrkgroup.com Registered In England
More informationRapid software development. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 1
Rapid software development Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 1 Objectives To explain how an iterative, incremental development process leads to faster delivery of
More informationAUDIT COMMITTEE 10 DECEMBER 2014
AUDIT COMMITTEE 10 DECEMBER 2014 AGENDA ITEM 8 Subject Report by MANAGEMENT OF INFORMATION RISKS DIRECTOR OF CORPORATE SERVICES Enquiries contact: Tony Preston, Ext 6541, email tony.preston@chelmsford.gov.uk
More informationAudit Committee, 20 March 2014. Internal Audit Report Partners Expenses. Executive summary and recommendations. Introduction
Audit Committee, 20 Internal Audit Report Partners Expenses Executive summary and recommendations Introduction Mazars have undertaken a review of the HCPC s controls and processes for ensuring partners
More informationInternal Audit Strategic and Annual Plans 2015/16
Internal Audit Strategic and Annual Plans 2015/16 Financial Scrutiny and Audit Committee 10 February 2015 Agenda Item No 8 Summary: This report provides an overview of the stages followed prior to the
More informationProject Management Guidebook
METHOD 12 3 empowering managers to succeed Project Management Guidebook ISBN 0-473-10445-8 A bout this e-book This e-book was created by Method123 (see www.method123.com) to help provide you with a simple
More informationDSDM DSDM. CONSORTiUM. CONSORTiUM. AgileBA. The Handbook for Business Analysts. Extract The Requirements Lifecycle In An Agile Project. www.dsdm.
DSDM CONSORTiUM DSDM CONSORTiUM AgileBA The Handbook for Business Analysts Extract The Lifecycle In An Agile Project www.dsdm.org This Extract from AgileBA, The Lifecycle in an Agile Project, is based
More informationAberdeen City Council IT Security (Network and perimeter)
Aberdeen City Council IT Security (Network and perimeter) Internal Audit Report 2014/2015 for Aberdeen City Council August 2014 Internal Audit KPIs Target Dates Actual Dates Red/Amber/Green Commentary
More informationInternal Audit Annual Report 2011/12
1 Introduction 1.1 In accordance with the Code of Practice for Internal Audit in Local Government in the United Kingdom, the Internal Audit Annual Report 2011/12 for Cheshire East contains the following:
More informationAgile extreme Development & Project Management Strategy Mentored/Component-based Workshop Series
Overview This is a 15-day live facilitator-led or virtual workshop is designed to prompt your entire team to work efficiently with Microsoft s Application Lifecycle Management solution based around Visual
More informationTEC Capital Asset Management Standard January 2011
TEC Capital Asset Management Standard January 2011 TEC Capital Asset Management Standard Tertiary Education Commission January 2011 0 Table of contents Introduction 2 Capital Asset Management 3 Defining
More informationSCHEDULE 3 Generalist Claims 2015
SCHEDULE 3 Generalist Claims 2015 Nominal Insurer And Schedule 3 (Claims) Page: 1 of 23 Contents Overview... 3 1. Scope of Services... 4 1.1 Claims Services... 4 1.2 Claims Process... 5 1.3 Assessment
More information