Your SlideShare is downloading. ×
KEAP Project Plan 1a
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

KEAP Project Plan 1a

375
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
375
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 KEAP - PROJECT PLAN Project Project Acronym KEAP Project ID Project Title KCL Enterprise Architecture Project Start Date 01/01/2008 End Date 31/12/2008 Lead Institution KCL, Centre for e-Research Project Director Dr. Mark Hedges Project Manager & Dr. Mark Hedges contact details Centre for e-Research King's College London 26 - 29 Drury Lane LONDON, WC2B 5RL Tel: 0207 848 1985 Fax: 0207 848 1989 Email: mark.hedges at kcl.ac.uk Partner Institutions (None) Project Web URL TBD Programme Name (and JISC Circular 02/07: Appendix D, Enterprise Architecture Group Pilot Call number) Programme Manager Myles Danson Document Document Title Project Plan Reporting Period n/a Author(s) & project role Dr. Mark Hedges, Project Manager Date 28/02/2008 Filename keap-project-plan-1a2341.doc URL n/a Access   Project and JISC internal  General dissemination Document History Version Date Comments 0a 01/01/2008 Initial draft (rough) 1a 25/02/2008 First draft with all sections included Page 1 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 2. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 JISC Project Plan Overview of Project 1. Background In support of the College’s Strategic Plan for 2006-2016, Information Systems and Services (ISS) at King’s College London (KCL) is carrying out a five-year programme, "Connected Campus" (CC), to create a comprehensive framework for the support of institution-wide teaching, research and administration. To support this programme, KCL has established the Centre for e-Research (CeRch), part of whose role will be to develop an integrated e-infrastructure to support research processes across the College, a three-year (2008-10) project that forms part of the overall CC programme. The Centre plans to take a service-orientated approach to developing this infrastructure, and also is likely to play a significant role in developing an overall service-oriented architecture for the College. The KEAP project will thus form part of a broader programme at KCL. 2. Aims and Objectives The broad aim of the project is to pilot an Enterprise Architecture approach to the CC programme, by applying and evaluating the TOGAF approach to the work. The project will address the specific domain of research, although project experience will be spread to other parts of ISS to enable the approach to be applied in other domains if appropriate (although this will be outside the scope of the project). The research infrastructure project, and the CC programme of which it forms a part, will continue beyond 2008. If, as we hope, the TOGAF methodology proves appropriate to the work, KCL will continue to employ the approach during the programme, and to this end we aim to spread knowledge of TOGAF among selected IT staff at KCL. 3. Overall Approach Although the College aims to apply a service-orientated approach broadly within its overall CC programme, it would clearly be infeasible to address this within the constraints of the current project. Instead, the project will restrict its scope to those components of the infrastructure that lie within the remit of the Centre for e-Research, namely those that support research processes within the College, together with the interfaces between this e-research infrastructure and other components. Furthermore, within the scope of the project the methodology will be applied in detail only to a selected set of business processes within the research domain. The project staff will not directly address the application of the methodology outside the research domain. However, to supplement this detailed application of EA/TOGAF to the research domain, the project team will seek to involve other ISS staff, who will be encouraged to apply the approach while not working directly under the aegis of the project. Knowledge gained from training courses, and the experience of both KEAP and other projects in the programme, will be passed on to these staff, who will also be encouraged to make use of the training material available from the Open Group. This will be facilitated via the existing Team Leaders Development Forum (see Section 12). Within the research domain, the project will take the following approach: • Gather and specify requirements for the business processes required to carry out and to support research within KCL. For convenience, these will be broken down into five categories: research planning and administration, research collaboration and communication, scholarly publishing and open access, management of research data and other digital material, digital preservation. • Identify the legacy systems at KCL (external to the research domain) with which research processes will need to interact, and specify the interfaces for these interactions; • Apply TOGAF to: (i) analysis of selected business processes (and data) in the research domain; Page 2 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 3. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 (ii) specification of an SOA for the applications and technology required to support these business processes. • Document and evaluate the utility of TOGAF as applied during the project. 4. Project Outputs The tangible deliverables are expected to be: Output Timescale Comments 31 March 2008 Quarterly progress reports 30 June 2008 30 September 2008 Final report 31 December 2008 Project Website 1 March 2008 until 31 December 2008 Ongoing, from 31 Documents will be issued in Outputs arising from applying the TOGAF March 2008 until 31 draft form as they are methodology, including business process, December 2008. produced. Final versions will application, data and technology models, both “as be created for the end of the project. is” and “to be”. This may include additional material containing guidance on developing service-oriented architectures and enterprise architectures. Ongoing, from 31 Documents will be submitted Contributions to the e-Framework, possibly March 2008 until 31 to the e-Framework team including the following: domain maps and models, December 2008. once internally reviewed. Creation of final versions good practice and process models, service-based may extend beyond the end composite applications, SUMs and Services, of the project, depending on the e-Framework team’s supporting scenarios. timescales. 31 December 2008 Case study, evaluating the project and making recommendations based on the project’s findings A less tangible output will be a body of knowledge and experience regarding enterprise and service- orientated architectures and their applicability in HE environments, and in particular the use of the TOGAF methodology to develop such architectures. This knowledge and experience will be disseminated among KCL staff, and (via JISC, Open Group, and the other projects in the Enterprise Architecture programme) to the wider HE community, so that:: • KCL staff can continue to apply the methodology (or parts of it) after the project is complete; • the methodology can be applied to components of KCL’s architecture that are not the responsibility of CeRch or of the KEAP project (that is to say, components that lie outside the research domain); • KCL’s experience as an early adopter can help to support wider take-up in the HE community. 5. Project Outcomes The Connected Campus programme will have impact on all communities throughout KCL, whether in research, teaching, learning or administration. Consequently, any advantages gained from applying the TOGAF methodology during the project will have similarly extensive impact. Page 3 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 4. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 By the end of the project, KCL will have started a process of developing a service-orientated e- infrastructure for the College, a process that will continue after project completion. At this stage of the project, of course, it cannot be guaranteed that the methodology will be appropriate; indeed, evaluating the approach in the context of an HE institution is one of the purposes of the project. Even if applying the full methodology to the programme proves to be not entirely successful, however, the project is still expected to bring benefits to the institution. It is very likely that some form of service- orientated approach is appropriate to KCL’s institutional architecture, and using a formal approach to such an implementation will produce a more robust and effective result. The project will also improve the understanding of SOAs, their potential and shortcomings, and cost issues (including cost-benefit tradeoffs) among IT staff and senior management. The experience and knowledge gained from the project will also be useful to the wider community, both to other HE institutions who are considering applying a similar Enterprise Architecture approach to their own systems, and to JISC who will be able to use the project outputs to inform future developments and funding programmes. In summary: • The project is evaluating the TOGAF methodology – the comprehensive suitability of TOGAF is not a criterion of success. • We anticipate and hope that:: • At least some components of the methodology will prove useful. • We will apply the methodology in detail to selected business processes within the research domain • We will gain sufficient knowledge and experience to apply the methodology to other processes and domains within the wider CC programme. 6. Stakeholder Analysis Stakeholder Interest / stake Importance KCL Chief Information Officer and the Senior Overall responsibility for High Management Team at KCL information strategy. Direct and explicit interest in the success of the project. Significant financial investment in the CC. Research community within KCL Providers of information and High users of the systems and information. Teaching and learning communities within KCL Providers of information and High users of the systems and information. Professional Services community Providers of information and High within KCL users of the systems and information. CeRch Leaders of research and High development for the CC. JISC, particularly the JISC/DEST e- A case study into the High Framework Programme applicability of Enterprise Architectures in HE. Services, SUMs and Guides contributed to the e-Framework by the project. Other benefits, as in Paragraphs D7 and D8 of the call. Corresponding communities in other institutions Results of project may influence Medium adoption of methodology in other institutions. Page 4 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 5. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 Open Group Case study of applying the Medium TOGAF methodology in an HE institution that is at an early stage of implementing a cross- institution service-orientated architecture 7. Risk Analysis Risk Probability Severity Score Action to Prevent/Manage Risk (1-5) (1-5) (P x S) Staffing Problems (inability to 1 3 3 – The proposed senior staff are attract and retain staff with already employed by CeRch. The appropriate skills and junior staff member will be part of the experience) new core team CeRch, and the recruitment process has already begun (interviews early Jan. 2008). Relevant expertise is spread among a number of other CeRch staff. – Spread project experience to other CeRch staff. Create a clear project plan and document current work to ensure knowledge is not lost. Difficulties getting staff to buy 1 3 3 – The TOGAF framework is a good fit into the TOGAF framework for much of the planned KCL e- and the Open Group infrastructure. approach. – The plan has the full support of key KCL staff: Karen Stanton, Chief Information Officer & College Librarian, and Prof. Keith Hoggart, Vice-Principal (Arts & Sciences). – Use the ISS Team Leaders Development Forum (see Para. 3.4) to involve relevant staff with TOGAF approach. A complete solution cannot be 2 3 6 – The absence of a complete solution devised using the selected is not a failure, as one aspect of the approach within the project project is to investigate potential time constraints. problems. – Liaise closely with the JISC programme support, Open Group working groups (in particular the new HE Working Group), and the mentor representative from Open Group. – While keeping in mind the broader view, attempt at least to achieve a solution in a subset of the problem space. Failure to meet project 1 2 2 – Produce project plan with clear milestones. objectives. – Assess project continually and reschedule when necessary. Delays in getting e-Framework 2 1 2 The project team will continue to be components approved by the employed at KCL beyond the end of e-Framework team. the project, and will continue to work Page 5 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 6. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 on e-Framework components as part of their work. External dependencies – 1 3 3 Liaise closely with JISC programme problems with getting required management. support from JISC. Time limitations – training for 3 2 6 – Select a subset of business TOGAF is only being supplied processes to analyse using TOGAF. in mid-April (over 25% of the way through the project). 8. Standards The use of standards is critical to the proposed work, and we will keep in mind the standards in the JISC Standards catalogue (http://standards-catalogue.ukoln.ac.uk/index/JISC_Standards_Catalogue), as well as other standards, throughout the project. That said, it would be inappropriate at this stage to limit ourselves to specific standards; this section will be updated as the project progresses, as particular standards are deemed appropriate. Given the objectives of the project, standards related to service-orientated architectures (e.g. WSDL, SOAP, UDDI) are likely to be particularly relevant. We will use open, non-proprietary standards wherever possible. 9. Technical Development The project will apply the TOGAF methodology in its implementation of an EA/SOA for the research domain at KCL. At the current stage of the project, it is not possible to specify the particular technologies that will be used. However, open source components and open standards will be used as far as possible, although we may be constrained in this by the need to integrate existing proprietary components. This section will be updated in later versions of the document as more information becomes available. 10. Intellectual Property Rights IPR in all documents produced will be retained by the authors and KCL, except in so far as they incorporate other material that affects this status. They will be made freely available on an open- source licence, except where they contain commercially confidential information. Any software created by the project will be made available to the community on an open-source basis on the GPL licence. We will respect the licence model of all third party software incorporated – as far as possible, only software made available under open source licences will be used in this way. Any non-open source third-party material to be used will be listed here at a later date, along with how we will obtain permission to use it, and any legal implications for the project outputs. Project Resources 11. Project Partners None. Page 6 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 7. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 12. Project Management Project team: Mark Hedges Deputy Director of Centre for e-Research, King’s College London Project role: Project Manager, nominated senior staff member for project (see Paras D24-D26 of call) 0.3 FTE, 0.05 FTE of which will be spent on project management activities mark.hedges@kcl.ac.uk 020-7848-1970 Sheila Anderson Director of Centre for e-Research, King’s College London Project role: Consultant 0.05 FTE 7nders.anderson@kcl.ac.uk 020-7818-1981 Omar Radwan Systems Analyst, Centre for e-Research, King’s College London Project role: Activities in Para. D27 of call. 0.4 FTE Programme Support Cohort: Programme Manager Myles Danson Open Group David Rose e-Framework Phil Nicholls and Alex Hawker CETIS Scott Wilson Case Study Coordination & Synthesis Gaynor Backhouse & Paul Anderson (JISC TechWatch) InfoNet Interest Patrick Bellis (JISC Infonet) TOGAF Trainer TBA Evaluation TBA UCISA Interest TBA Training needs: The project team will require training in TOGAF. It is anticipated that JISC will supply this (see Para. D28 of call). Management framework: Mark Hedges will be Project Manager. The Systems Analyst will report to the Project Manager, who will in turn report to the Director of CeRch, Sheila Anderson. The Director of CeRch (who will act as consultant on the project) will be responsible for liaison with ISS as a whole regarding the project. She is part of the ISS Leadership Team which has responsibility for strategic level decision making, developing and leading strategic projects, collaborative working across teams within ISS, and discussing and deciding on future developments. The Leadership Team meets on a monthly basis and the project will be a regular item for reporting and discussion, in particular, to discuss how the outputs from the project are integrated into future planning and decision making. Colleagues from across ISS will be involved and cross-team collaborations will be formed as appropriate, to action outcomes from the project work. The Leadership Team will establish a cross ISS Working Group to discuss and implement the problems questions and decisions arising from the project. The planning process will be an integrated part of the CC implementation plan and will inform both current activity and future plans. Regular Page 7 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 8. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 reports on the outcomes of the project will be provided to the CC Programme Board to help inform their decision making, and to provide guidance back to the project on further developments. ISS has a Team Leaders Development Forum that brings together team leaders responsible for running services and implementing strategic decisions and plans. This Forum will be used to inform and provide training for Team Leaders (and their staff where appropriate) in the TOGAF methodology and the resulting architecture. This will ensure that as an enterprise architecture is developed for King’s, staff are fully briefed on the impact and the requirements for its further development and implementation, and are involved in the decision making process. 13. Programme Support Support will be required from the JISC programme, as specified in para D28 of the call. To recap, this support will include: • Additional funding (over and above the project funding) for KCL to take out Open Group Silver Membership for one year (additional 10,000 euros); • Additional funding (over and above the project funding) for the attendance for two people at two Open Group Conferences; • A training course on TOGAF methodology; • Workshops in Enterprise Architecture and process modelling methods and tools; • Software licences for Enterprise Architecture tools; • Access to a senior Open Group representative for support and mentoring; • Access to a working group of HE peers participating in the TOGAF initiative (the new HE specialist Working Group); • Support in the development of case studies; • An evaluator who will work with the institutions and synthesise their findings and recommendations into a final evaluation report. Additional support required (from JISC and/or Open Group) • Detailed case studies of applying TOGAF in practice, which the project could use as “worked examples”. • Advice on specific tools to be used. 14. Budget There are no changes to the budget included in the proposal. Detailed Project Planning 15. Workpackages See Appendix B. 16. Evaluation Plan Indicate how you will evaluate the quality of the project outputs and the success of the project. List the factors you plan to evaluate, questions the evaluation will answer, methods you will use, and how success will be measured. Expand as appropriate on how you will conduct the evaluation. Timing Factor to Evaluate Questions to Address Method(s) Measure of Success Ongoing Quarterly reports Internal project review End of Case Study Internal project project review Ongoing Documentation arising Internal project from applying TOGAF review methodology. Page 8 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 9. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 Ongoing e-Framework Internal project components (SUMs review etc.) Review by e- Framework team (when submitted) End of Contribution of project Internal KCL project and TOGAF review methodology to CC project as a whole. 17. Quality Plan Explain the quality assurance procedures you will put in place to ensure that project deliverables meet quality expectations and acceptance criteria. Complete the table below for each of the major deliverables providing as much detail as possible. Repeat the table as many times as necessary to accommodate all deliverables. Output Quarterly Reports & Final Report Timing Quality QA method(s) Evidence of Quality Quality tools criteria compliance responsibilities (if applicable) When Accurately - Internal project - Record of internal MH complete represents review. review. progress of - Review by JISC. - Acceptance by project to JISC. date. Output Case Study Timing Quality QA method(s) Evidence of Quality Quality tools criteria compliance responsibilities (if applicable) When Utility for - Internal project - Record of internal MH/OR complete other review. review. institutions. - Review by JISC. - Acceptance by Comprehensi JISC. bility. Clarity. TOGAF output documentation Timing Quality QA method(s) Evidence of Quality Quality tools criteria compliance responsibilities (if applicable) When Fitness for - Internal project - Record of internal MH/OR complete purpose review. review. - Review by JISC. - Acceptance by JISC. When Fitness for Review by e- Acceptance by e- MH/OR submitted purpose Framework team (in Framework team to e- relevant cases). Framewo rk. Output e-Framework components Timing Quality QA method(s) Evidence of Quality Quality tools criteria compliance responsibilities (if applicable) When Fitness for Internal project Review MH/OR complete purpose review documentation When Fitness for Review by e- Acceptance by e- MH/OR submitted purpose Framework team Framework team to e- Page 9 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 10. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 Framewo rk. 18. Dissemination Plan Timing Dissemination Activity Audience Purpose Key Message Ongoing Project website and blog. - Other projects in Provide frequent the EA Programme. updates on project - Wider JISC progress and community experience. Ongoing Participation in JISC JISC community Spread experience programme events of applying TOGAF approach to HE. Ongoing Participation in Open Group - Open Group Spread experience events - TOGAF of applying TOGAF community (& approach to HE. potential users) Ongoing Presentations and papers Wider IT and HE Spread experience at other conferences and communities of applying TOGAF workshops. approach to HE. End of Case Study - JISC community Provide evaluation project - Open Group of TOGAF with - TOGAF respect to its community (& suitability to an HE potential users) environment. 19. Exit and Sustainability Plans Project Outputs Action for Take-up & Embedding Action for Exit Knowledge and expertise - Project staff will continue to - Ensure knowledge & expertise is acquired by project staff implement and advise on SOA at KCL. documented. - Projects staff will document their - Ensure knowledge & expertise knowledge and experience as far as spread among other KCL staff so possible, to enable dissemination to that they can in turn apply it in other institutions. their work. Documentation Make publicly available, e.g. on CeRch and JISC websites e-Framework components Submit contributions to e-Framework Ensure components website Project Outputs Why Sustainable Scenarios for Taking Issues to Address Forward Case study Useful to other - Make case study available. institutions considering - Presentations at workshops use of TOGAF. and conferences e-Framework Useful to other Include in e-Framework components institutions website. implementing an SOA (whether or not using TOGAF). Appendixes Appendix A. Project Budget As in proposal (unchanged). Page 10 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 11. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 Appendix B. Workpackages Month 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 WORKPACKAGES J F M A M J J A S O N D 1: Project Management 2: External Liaison 3: Requirements 3: EA / TOGAF Implementation 4: EA / TOGAF Evaluation Workpackage and activity Earliest Latest Outputs (deliverables in bold) Milestone Responsibility start date completion date YEAR 1 WORKPACKAGE 1: Project 01-01-08 31-12-08 Management Objective: To manage and coordinate activities; to report; to assess risks and opportunities as the project progresses; to liaise with stakeholders within ISS. 1.1 Develop a detailed project plan with timescales, Project Plan Version 1a delivered. MH deliverables, and milestones 01-01-08 29-02-08 1.2 Create website and JISC web template Website MH/OR 01-01-08 31-03-08 JISC web template Page 11 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 12. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 1.3 Periodically update website as project progresses Website updates MH/OR 01-01-08 31-12-08 5.1 Case study (Sections 1 and 2) Case study (Sections 1 and 2) MH 01-03-08 31-03-08 1.4 Quarterly report for JISC, covering January to Progress Report 1 MH March 2008. 01-03-08 31-03-08 1.5 Quarterly report for JISC, covering April to June Progress Report 2 MH 2008. 01-06-08 30-06-08 1.6 Quarterly report for JISC, covering July to Progress Report 3 MH September 2008. 01-09-08 30-09-08 1.7 Final report for JISC. Final Report MH 01-12-08 31-12-08 WORKPACKAGE 2: External Liaison 25-02-08 31-12-08 Objective: Liaison external to project: KCL/ISS, JISC and JISC-supported groups (e.g. EA programme and e-Framework), Open Group 4.1 Liaison with other KCL/ISS groups to spread MH/SA knowledge. 14-04-07 31-12-08 2.1 JISC events See timeline in Appendix C. MH/OR 25-02-08 31-12-08 2.2 Open Group / TOGAF events See timeline in Appendix C. MH/OR 25-02-08 31-12-08 Note: requirements documentation may WORKPACKAGE 3: Requirements 01-02-08 30-07-08 pass through several iterations in liaison with research & research-support staff. Objective: To gather and analyse requirements for Page 12 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 13. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 the research domain at KCL. 3.1 Interviews with targeted research and research- Interview notes. MH/OR/SA support staff. 01-02-08 30-07-08 3.2 Focus groups addressing requirements, involving Focus group notes. MH/OR/SA CeRch and research/research-support staff. 01-02-08 30-07-08 3.3 Requirements for interaction with legacy systems. Requirements documentation. MH/OR/SA 01-02-08 30-07-08 3.4 Requirements for research planning and ditto MH/OR/SA administration. 01-02-08 30-07-08 3.5 Requirements for research collaboration and ditto MH/OR/SA communication. 01-02-08 30-07-08 3.6 Requirements for scholarly publications and open ditto MH/OR/SA access. 01-02-08 30-07-08 3.7 Requirements for data management and ditto MH/OR/SA processing 01-02-08 30-07-08 3.8 Requirements for long-term preservation of digital ditto MH/OR/SA resources. 01-02-08 30-07-08 3.9 Identify set of key business processes for further List of business processes. MH/OR/SA analysis. 01-05-08 30-07-08 WORKPACKAGE 4: EA/TOGAF 14-04-07 30-09-08 Implementation Objective: To apply an EA/TOGAF approach to designing an SOA for the KCL research domain. 4.1 Apply TOGAF to analysis of selected business TOGAF modelling outputs MH/OR processes. 14-04-07 30-09-08 Page 13 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 14. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 4.2 Apply TOGAF to design of SOA to support TOGAF modelling outputs MH/OR selected business processes. 14-04-07 30-09-08 4.3 Produce e-Framework components (both existing e-Framework components (which may MH/OR e-Framework and upper level knowledge base). 14-04-07 30-09-08 include the outputs from 4.1 and 4.2). WORKPACKAGE 5: EA/TOGAF 01-08-08 31-12-08 Evaluation Objective: To evaluate the application of EA/TOGAF within the KCL research domain. 5.2 Evaluation of EA/TOGAF application. Evaluation outputs. MH/OR 01-08-08 08-12-08 5.3 Case study (full) Case study (full) MH/OR 01-10-08 08-12-08 5.4 Case study (full + requested revisions) Case study (final) MH/OR 09-12-08 31-12-08 Page 14 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 15. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 Appendix C. Timeline Date: Week beginning 25/2/08 Participants: Project staff (2) plus entire support cohort Task: Programme Kick Off Meeting Duration: 1 day Location: London Aims: Group familiarisation, expectations, aspirations, complete key dates, present projects and work plans Date: 29/2/08 Milestone: Project Plan delivered to Programme Manager according to JISC Template Milestone: Project Web Site in place Milestone: JISC Web Site Template delivered to Programme Manager Date: Week beginning 31/3/08 or week beginning 7/4/08 Participants: Project staff (2), support cohort for day 1 Task: TOGAF Training Duration: 3 or 4 days anticipated Location: TBA Aims: Training course to meet needs of projects with opportunity to certify Date: 31/3/08 Milestone: First quarterly project report delivered to Programme Manager Date: 20/4/08 – 25/4/08 (starts Sunday evening) Participants: Project Staff (2), support cohort Task: Open Group Conference Duration: 3 – 4 days Venue: Glasgow Radisson SAS Hotel Aims: Opportunity to meet others active in the field. Opportunity to undertake group work. Open Group to arrange agenda in consultation with projects and cohort Date: Week beginning 12/5/08 Participants: e-Framework staff, Project Staff (2) plus Programme Manager Task: E-Framework workshop project staff Duration: 1 Day Location: TBA Aims: Familiarisation with e-Framework, identification of project linkages and opportunities, engagement with EF, agree dates for further input between projects and EF Staff Date: Week beginning 23/6/08 Duration: Up to 3 days Participants: Project staff (2), support cohort for day 1 Task: Bespoke Workshop: According to needs analysis Location: TBA Aims: Trainer to scope with projects and support cohort Date: 30/6/08 Milestone: Second quarterly progress report delivered to Programme Manager Date: 17/7/08 Duration: 1 day Participants: Project staff (2) plus entire cohort Task: Mid point gathering Page 15 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10
  • 16. Project Acronym: KEAP Version: 1a Contact: Mark Hedges Date: 28 February 2008 Location: TBA Aims: Show and tell / present on progress and issues arising Date: 30/9/08 Milestone: Third Quarterly Progress Report delivered to Programme Manager Date: Week beginning 6/10/08 Duration: 1 day Participants: Project staff (2) plus entire cohort Task: Peer evaluation Location: Birmingham Aims: Address quality of approaches and outputs. One day of preparation work expected. Date: 19/10/08 – 22/10/08 Duration: 3 days Participants: Project staff (2), Open Group, Programme Manager Task: Open Group Conference Venue: Munich Aims: Networking / training opportunity. Projects and support cohort to determine. Date: 10/12/08 Duration: 1 day Participants: Project staff (2) plus entire cohort Task: Wrap up meeting Aims: Final wrap up meeting – progress reports and case studies / synthesis discussions and agreements Date: 31/12/08 Milestone: Final deliverables due Page 16 of 16 Document title: keap-project-plan-1a2341.doc Last updated: 8-Jun-10