Download/display Word Perfect


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • A pre-defined route map through the standard lifecycle and non-lifecycle Phases of Method abc. Designed to work with any type of project and provide benefit whether using some or all ONSide techniques Perhaps some projects will simply benefit from the use of collaborative techniques e.g. Facilitated workshops run by a trained facilitator. This is NOT a job for anyone: Greatest productivity gains will be made when using trained, qualified personnel to work on or mentor the project Products and approach should be adapted to suit project and client requirements The pathway can be applied right at the outset of any piece of work, whether it be a business idea or an ITT The pathway can be applied during Phase 9.1 Starting a Project The techniques and approach can be applied at any point ONSide is in place now within IM. ALL projects whether Development or Operational or Strategic MUST FOLLOW ONSide This will bring the control and rigour necessary for IM to bring the required quality of service to ONS. Each stage has entry / exit criteria these will by enforced by the IMMT via the Programme office to ensure that ONSIDE is being followed correctly. There isn’t an alternative to ONSIDE! Within the SMP the use of ONSIDE has been mandated by Caren Walker - SMP Programme Director (she has already accepted the roles of EXEC Sponsor and Visionary for SMP) She will chair the SMP delivery board and will report into Karen Dunnel who chairs the main Programme Board. ONSide is more than a collection of techniques and templates it is a process which must be followed and it is important that following this training course you look in the getting started folder
  • Download/display Word Perfect

    1. 1. Evolving Governance and Process to meet the IT Development Challenges at ONS Keith Jones MSIS - May 2009
    2. 2. Outline <ul><li>Rationale for Reorganisation </li></ul><ul><li>Description of Organisation </li></ul><ul><li>Current Development Process </li></ul><ul><li>Future Direction </li></ul>
    3. 3. Background to Reorganisation – Infrastructure Issues (1) <ul><li>In 2006 ONS carried out a review of its Infrastructure Services. The major issues were: </li></ul><ul><li>Data Centres were substandard with little disaster recovery capability which left data at risk. </li></ul><ul><li>ONS needed to make improvements to its storage and backup of data capability </li></ul><ul><li>There were security risks under the current system. </li></ul><ul><li>We had an ageing estate with applications up to 20 years old based on unsupported technology </li></ul>
    4. 4. Background to Reorganisation – Infrastructure Issues (2) <ul><li>ONS made the decision to outsource Infrastructure through Public Sector Flex </li></ul><ul><li>A highly scaleable shared service delivered by Fujitsu Services </li></ul><ul><li>Framework and Commercial terms can be used by any UK public sector entity without need for procurement process </li></ul>
    5. 5. Public Sector Flex – Advantages for ONS <ul><li>A “Core Shared Service” offering best value for money available to the public sector </li></ul><ul><li>Security accredited service </li></ul><ul><li>Access to ITIL- compliant support through a shared service desk </li></ul>
    6. 6. Background to Reorganisation – Other Drivers for Change <ul><li>ONS was focussing on delivering change through a series of smaller projects rather than a major Modernisation Program </li></ul><ul><li>Information Management Directorate (IMD) needed to be able to respond in and agile fashion whilst ensuring solutions aligned with corporate aims and objectives </li></ul>
    7. 7. Services Business Partners Business Systems Development Solutions Design Build Run Improve Delivery IMG Lifecycle and Customer Engagement Business analysis Architecture Strategic alignment Business case Methodology Business Area Projects Major Programmes Service Levels Standard Change Request Service Request Request for Change Service Improvements
    8. 8. <ul><li>Role </li></ul><ul><ul><li>To make sure the I.T. services required by the business are available when they need them </li></ul></ul><ul><ul><li>To deliver excellent Customer focussed I.T. services </li></ul></ul><ul><ul><li>To meet or exceed Service Level Agreements </li></ul></ul><ul><li>Who we are </li></ul><ul><ul><li>Service Management Professionals working to best practice who continually look to improve I.T. service and value </li></ul></ul><ul><li>What we do </li></ul><ul><ul><li>Align I.T. provision with the needs of the business now and in the future </li></ul></ul><ul><ul><li>Ensure costs are managed and quality of service is optimised through continuous service improvements </li></ul></ul><ul><ul><li>Supplier Management - Manage internal and external relationships </li></ul></ul><ul><ul><li>IMG Financial Management </li></ul></ul><ul><ul><li>IMG Communications </li></ul></ul>Services
    9. 9. Solutions Design Centre <ul><li>Role </li></ul><ul><ul><li>To design business solutions in partnership with our customers </li></ul></ul><ul><ul><li>- early engagement with customers to explore solution options </li></ul></ul><ul><ul><li>- joint development of business cases </li></ul></ul><ul><ul><li>- a holistic view of business change </li></ul></ul><ul><ul><li>- designing information assurance into solutions </li></ul></ul><ul><ul><li>- aligning solutions to corporate aims and objectives </li></ul></ul><ul><ul><li>To lead the development of the IM capability </li></ul></ul><ul><ul><li>To provide expertise on Information Assurance </li></ul></ul><ul><li>Who we are </li></ul><ul><ul><li>Business & Systems Analysts </li></ul></ul><ul><ul><li>Enterprise, Data and Solution Architects </li></ul></ul><ul><ul><li>Information Assurance experts </li></ul></ul><ul><ul><li>Professional testers </li></ul></ul><ul><li>What we do </li></ul><ul><ul><li>Solution Design Centre shapes business solutions at the pre-project stage </li></ul></ul><ul><ul><li>Provide a pool of IT professionals to be engaged on ONS projects and programmes </li></ul></ul>Solutions
    10. 10. IT Project Portfolio Delivery <ul><li>Role </li></ul><ul><ul><li>Deliver IT business solutions that create and support valued services that our Customers can use </li></ul></ul><ul><li>Who we are </li></ul><ul><ul><li>IT Professionals with significant experience in developing and delivering IT solutions; </li></ul></ul><ul><ul><li>IT Project Managers </li></ul></ul><ul><ul><li>IT Project Office </li></ul></ul><ul><li>What we do </li></ul><ul><li>Work with our project sponsors and their teams to deliver solutions; </li></ul><ul><li>Engagement with customers to explore delivery options </li></ul><ul><li>Manage the project pipeline </li></ul><ul><li>Ensuring appropriate resources are assigned </li></ul><ul><li>Delivery of IM project commitments to time, cost and quality </li></ul><ul><li>Gain approval for new services to be deployed into live </li></ul>Business Area Projects Major Programmes
    11. 11. Business Systems Development <ul><li>Role (as part of IM Delivery) </li></ul><ul><ul><li>Deliver IT business solutions that create and support valued services that our Customers can use </li></ul></ul><ul><li>Who we are </li></ul><ul><ul><li>Business Systems developers and service support teams with a wide range of statistical knowledge and technical skills, including; </li></ul></ul><ul><ul><ul><li>Web solutions </li></ul></ul></ul><ul><ul><ul><li>Java, Oracle, SAS </li></ul></ul></ul><ul><ul><ul><li>Ingres, Openroad </li></ul></ul></ul><ul><ul><ul><li>VB, M204 </li></ul></ul></ul><ul><ul><ul><li>Blaise and Statistical Tools </li></ul></ul></ul><ul><ul><ul><li>Environment Management </li></ul></ul></ul><ul><li>What we do </li></ul><ul><li>Responsible for building new business solutions/ services as part of delivery project teams </li></ul><ul><ul><li>Delivering against planned development commitments </li></ul></ul><ul><ul><li>Providing development resources across new and legacy platforms </li></ul></ul><ul><li>Responsible for delivering great support for existing services </li></ul><ul><ul><li>Fully meeting agreed customer service support commitments </li></ul></ul><ul><ul><li>Enabling the production of existing statistical outputs </li></ul></ul><ul><ul><li>Making approved small scale changes to existing services </li></ul></ul>Business Area Projects Application Support
    12. 12. Why we needed a standard Development Process <ul><li>To ensure everyone on the project understands their role and responsibilities </li></ul><ul><li>To have clear deliverables at each stage to make monitoring progress more effective </li></ul><ul><li>To be able to follow industry best practice adapted for use in our organisation </li></ul>
    13. 13. ONSide – ONS Integrated Delivery Environment <ul><li>ONSide is a framework which provides a rich set of predefined products, processes and templates aimed to support successful project delivery. </li></ul><ul><li>It guides , not dictates, the type and level of information that should be produced. </li></ul><ul><li>It is a framework which can be tailored, refined and adapted to different project requirements </li></ul>
    14. 14. What is ONSide? Solution Design Situation Definition Solution Shaping High Level Solution Analysis & Design Detailed Solution Analysis & Design Solution Delivery Transformation Preparation Consolidation Project Brief Project Brief PID 2nd Iteration PID etc Stage Plans End Stage Reports End Project Report Management / Non-Lifecycle Products Project / Lifecycle Phases = Potential Project Entry Points Iterative & Incremental Phases Pre-Project Feasibility Study Business Study Functional Model Iteration Design & Build Iteration Implementation = Prince Products
    15. 15. Situation Definition : Purpose <ul><li>A pre-project phase where a business idea is developed into something which can move into either Solution shaping or project start-up activities </li></ul><ul><li>To understand how the business operates currently and what problems, issues and opportunities exist. </li></ul><ul><li>To find out exactly what benefits and business performance improvements the business expects to gain from a project and why these are important or necessary </li></ul>
    16. 16. Situation Definition : Key Deliverables <ul><li>Initial Findings and Recommendations Report </li></ul><ul><ul><li>Provides high-level view of the background to the request for work and a recommendation as to whether the project should proceed to delivery IFRR </li></ul></ul><ul><li>Project Brief </li></ul><ul><ul><li>Outline of project following PRINCE2 guidelines </li></ul></ul>
    17. 17. Solution Shaping : Purpose <ul><ul><li>To define a preferred approach for taking the business forward </li></ul></ul><ul><ul><li>To define the core components that will form the solution that will deliver the above business architecture. </li></ul></ul>
    18. 18. Solution Shaping : Key Deliverables <ul><li>Feasibility Report </li></ul><ul><ul><li>Enables the project steering committee to decide not only which option to choose for the way forward but also whether or not the project should proceed beyond the Feasibility Study </li></ul></ul><ul><li>Feasibility Prototype </li></ul><ul><ul><li>Prototypes provide a mechanism to enable users to ensure the detail of the requirements is correct. </li></ul></ul>
    19. 19. High Level Solution Analysis and Design (HLSAD) : Purpose <ul><li>Produces the definition of the client’s solution at a high level, including the application and all it’s supporting components </li></ul>
    20. 20. High Level Solution Analysis and Design : Key Deliverables for Development <ul><li>Business Area Definition </li></ul><ul><ul><ul><li>Articulates the business problem that is to be addressed. It defines the business processes that are to be supported and describes the recommended solution - BAD </li></ul></ul></ul><ul><ul><ul><li>Main elements: Business Process Model and descriptions; Business Domain Model; Use Case Model </li></ul></ul></ul><ul><ul><li>Systems Architecture Document </li></ul></ul><ul><ul><ul><li>Defines the high level architecture, infrastructure and technical design of the solution – SAD </li></ul></ul></ul><ul><ul><ul><li>Overview of solution - components to be used (eg built or reused); identifies risk areas for early prototyping; explains the development, test and operational environments </li></ul></ul></ul>
    21. 21. High Level Solution Analysis and Design : Key Deliverables for Development <ul><li>Prioritised Requirements List </li></ul><ul><ul><li>Outlines the requirements of the system to be built. Lists and prioritises the requirements (functional and non-functional) – PRL </li></ul></ul><ul><li>Development Plan </li></ul><ul><ul><li>Provides a more detailed plan for activities within Build and Test. </li></ul></ul><ul><ul><li>It provides the development Strategy ie how the solution is to be developed </li></ul></ul>
    22. 22. Detailed Solution Analysis and Design (DSAD) : Purpose <ul><li>To define the solution in enough detail to enable construction of it </li></ul><ul><li>Depending on the approach taken DSAD and Solution Delivery could either be done as one block or done as a series of iterations (timeboxes) beginning with the most architecturally significant Use Cases. </li></ul>
    23. 23. Detailed Solution Analysis and Design – Key Deliverables for each timebox <ul><li>System Requirement Specification SRS </li></ul><ul><ul><li>Details descriptions of Use Cases and supplementary specifications; </li></ul></ul><ul><li>Software Architecture Document SoAD </li></ul><ul><ul><li>Provides a comprehensive architectural overview of the system from different perspectives: Use Case; Logical; Implementation; Process; Deployment </li></ul></ul><ul><ul><li>Specifies the sub systems, mechanisms, performance characteristics and sizings, etc and should be updated for each timebox / iteration for architecturally significant changes </li></ul></ul><ul><li>Technical Architecture Definition TAD </li></ul><ul><ul><li>Details the hardware and networks that will be used to meet the system requirements (only required for divergence from Corporate TAD) </li></ul></ul>
    24. 24. Detailed Solution Analysis and Design – Key Deliverables for each timebox <ul><ul><li>Data Architecture Document DAD </li></ul></ul><ul><ul><ul><li>Logical Data Model, Entity Descriptions, Business CRUD </li></ul></ul></ul><ul><ul><li>User Interface Prototype </li></ul></ul><ul><ul><ul><li>Prototype of User Interface to confirm / refine requirement </li></ul></ul></ul><ul><ul><li>Use Case Analysis </li></ul></ul><ul><ul><ul><li>Sequence Diagram per Use Case Flow of Events. </li></ul></ul></ul><ul><ul><ul><li>View of Participating Classes (VoPC) Class Diagram for the collaborating classes. </li></ul></ul></ul><ul><ul><ul><li>The Boundary-Controller-Entity analysis pattern is used to produce Analysis Classes, which are stored in the Analysis Model (which itself is a subset of the Design Model).    </li></ul></ul></ul>
    25. 25. Detailed Solution Analysis and Design – Key Deliverables for each timebox <ul><li>Use Case Design </li></ul><ul><ul><li>A Sequence diagram per Use Case Flow of Events . </li></ul></ul><ul><ul><li>View of Participating Classes (VoPC) Class Diagram for the collaborating classes. </li></ul></ul><ul><ul><li>Uses output from Use Case analysis, applying standard mechanisms / patterns as necessary. </li></ul></ul><ul><ul><li>Interface specifications will be produced for all sub systems </li></ul></ul><ul><ul><li>All above to be stored within Design model </li></ul></ul>
    26. 26. Solution Delivery <ul><li>To deliver the solution in terms of tested software </li></ul>
    27. 27. Solution Delivery – Key deliverables <ul><li>Physical Database Design </li></ul><ul><ul><li>Refinement of Physical data model (updating DAD ), Creation / Update of physical database </li></ul></ul><ul><li>Sub system design </li></ul><ul><ul><li>Within each subsystem identify / design classes required to meet requirement and update design model </li></ul></ul><ul><li>Class Design / Development </li></ul><ul><ul><li>Design classes and produce / document code to meet requirement </li></ul></ul><ul><ul><li>Produce Unit Tests to be run as part of build and regression tests which can also be run automatically when changes are made </li></ul></ul>
    28. 28. Consolidation <ul><li>Warranty period ensuring all documentation is complete </li></ul><ul><li>Covers the Post Implementation Review </li></ul>
    29. 29. Transformation Preparation <ul><li>Business Continuity planning </li></ul><ul><li>Business Change – planning and execution </li></ul><ul><li>Operational Acceptance Testing </li></ul><ul><li>Acceptance into Service </li></ul>
    30. 30. Adoption of Standard Toolset <ul><li>We have an integrated toolset (IBM Rational) for: </li></ul><ul><ul><li>capturing of requirements </li></ul></ul><ul><ul><li>production and documentation of analysis and design artefacts </li></ul></ul><ul><ul><li>version control of these artefacts plus source code </li></ul></ul><ul><ul><li>defect raising and tracking </li></ul></ul>
    31. 31. Adoption of Standard Toolset (2) <ul><li>This has given us full traceability of requirements through to code </li></ul><ul><li>We are able to monitor progress more closely through correct use of tools, and produce accurate release notes automatically outlining the functionality and defect fixes in any release. </li></ul>
    32. 32. As a Result ….. <ul><li>We have improved the business confidence in our ability to deliver within individual projects. </li></ul><ul><li>For each new project we look whether we have </li></ul><ul><ul><li>Are there common requirements in the form of high level business requirements or lower level Use Cases? </li></ul></ul><ul><ul><li>Can we use common patterns for implementing similar requirements? </li></ul></ul><ul><ul><li>Can we implement common design / code for building the solution? </li></ul></ul>
    33. 33. Future Direction <ul><li>We are now considering the move towards a Service Oriented Architecture (SOA) and the implications for organisation and process within development and support. </li></ul><ul><li>We believe, if we can successfully implement SOA it will lead to quicker development times and decreased support costs </li></ul>
    34. 34. Implication of the change <ul><li>We will then have the ability to share solutions both internally within ONS, and also across organisations not just in terms of software, but also requirements, patterns and design. </li></ul><ul><li>We can also look at reusing services developed by other organisations </li></ul>
    35. 35. Finally…. <ul><li>Our major challenges for the coming months </li></ul><ul><li>Convincing the rest of the organisation that this is the right approach </li></ul><ul><li>Making it work while continuing to deliver projects within budget. </li></ul><ul><li>. </li></ul>