relax time > JISC Bid Document > Project Management1.1 About this section
1.1.1 Strong project management is fundamental to the success of any project. In this section we will describe how the project partners will manage the operational issues of resourcing, scheduling, quality and risk. Matters of post-funding sustainability, dissemination and intellectual property rights will also be discussed.
1.2.1 An outline of the strengths of all three partners are provided below.
1.2.2 Emerald Group Publishing Limited
Emerald is actively involved in the library and information science community through its participation in the work of bodies such as UKSG, BBSLG and IFLA and is in regular attendance at industry conferences. Emerald actively supports industry standards such as Athens, COUNTER, OpenURL and DOIs. It has been involved in many research projects, including JISC. Emerald has its own excellent IT resource capability for projects including database, programming and project management (PRINCE 2) skills.
1.2.3 NCWBL capabilities
About the NCWBL
1.2.4 OU capabilities
About the OU
1.3 Roles and responsibilities
1.3.1 The team involved in the day-to-day management of the project are outlined in the table below.
| Name | Partner | Role | Responsibilities |
| Paul Evans | Emerald | Project manager | Smooth running of the project. |
| Paul Coyne | Emerald | Technical developer - publisher | Development of the software component for the publisher. |
| Skip Baisel | NCWBL |
|
|
| Alan Durrant | NCWBL |
|
|
Note: Brief CVs for the above individuals are available in Appendix n.
1.4.1 The proposed project timeline is outlined in the Gantt chart below.
Mini gantt chart goes here
1.5.1 A section about how the project will ensure quality throughout it’s duration
1.6.1 The potential risks associated with the project along with mitigating measures are outlined in the table below.
| Risk | Impact | Probability | Mitigating Measures |
| Project team absence | High | Medium | Each partner organisation will identify a suitable deputy in the case of extended absence. Contingency is built in to the project plan. |
| Lack of cooperation for the audit study | Medium | Low | Select enough libraries to visit to mitigate lack of cooperation from a few. |
| Inadequate monitoring of the project | High | Low | Instigate regular reviews. |
| Technical risk | High | Medium | Utilise proven technologies and technical environments familiar to project developers, and for which knowledge is available either in the Open Source community or via consultancy. |
| Time risk | High | Low | We believe this project is sufficiently tightly scoped to ensure that the envisaged timescales will be met. |