|
Home | Project startup
Project startup
Having successfully produced a Business case it is necessary to start addressing some of the detailed project planning which will help deliver a successful WARP. This section of the Toolbox provides help and assistance on the following topics:
-
Establish review board
-
Create project plan
-
Create security policy
-
Create website
-
Recruit team
-
Sign-up members
1. Establish review board
Like any good project you need to use sound project management principles to deliver a successful WARP. A project review board is an important component, which also needs to understand and agree its terms of reference. The following example was used by one of the existing WARPs.
  Terms of reference for a WARP project board (V1.0 June 2004)
Back to top
2. Create project plan
Clear roles and responsibilities with agreed deliverables and milestones are also essential ingredients for good project management. The following workpackage definition for the Filtered Warnings Service can be used as a model for the other two services.
Workpackage definition for a WARP Filtered Warnings Service (V1.0 June 2004)
Back to top
3. Create security policy
One aspect of developing a WARP that spreads across all three services is the need to define a robust security policy. There may well be a security policy that can be adopted from a parent organisation. The following document is intended to cover very briefly the areas that should be addressed, particularly if the Filtered Warnings Application is to be operated.
Outline security policy for a WARP service (V3.0 July 2006)
The following is a case study example of a WARP information security policy.
Case study - Information Security Policy for MYWARP (MYSWARP) (V1.1 July 2005)
Back to top
4. Create website
Whilst it is not the case that every WARP will run the Filtered Warnings Application, all WARPs will require a website to support their operations.
One important aspect of commissioning the website will be choosing and obtaining the domain name, in which you are likely to want to include the term "WARP". Generally there will be three formats you could choose from:
- A new domain creating a distinct entity for the WARP e.g. mywarp.org
- A sub domain of the WARP's parent domain, this may well appeal to WARPs that are closely allied to a parent organisation. e.g. warp.myorg.gov.uk
- A new root directory within an existing website structure. e.g. www.myorg.com/warp
Choosing a domain that you are not going to change is important for a number of reasons, not least of which being that you want to be sure the WARP members have a consistent place to find the service. One important factor that is closely linked to the domain name is the requirement for an SSL certificate for the server that will serve the WARP website as this is also required for the Filtered Warnings Application.
As all three WARP services require the sharing of information in a trusted environment, it makes both technical and psychological sense to implement SSL on the WARP website. Certificates can be obtained from a number of sources, and must be renewed annually.
Back to top
5. Recruit team
The WARP can be resourced by using a virtual team from people who are already working in your organisation, or from the WARP members themselves. Alternatively you may wish to recruit a full time resource. The following documents were used by a WARP to help recruit a Technical Analyst and provide a good indication of the job description and skills required.
Technical analyst - job description (V1.1 June 2004)
Technical analyst - person specification (V1.1 June 2004)
Example job advertisement for a WARP technical analyst (V1.1 June 2004)
Back to top
6. Sign-up members
It is important to make a formal agreement with your WARP members. This can be done in several ways but a simple way is to ask WARP members to complete a registration form and you confirm acceptance. The following is an example of a WARP member registration form.
Registration form for WARP membership (V1.1 June 2004)
The following is a case study example of a WARP member registration form.
Case study - Registration form for membership of MYWARP (MYSWARP)
It is also important to agree the level of service with your WARP members. The following is a case study example of a WARP service agreement for all WARP services, based on the service definition for the Filtered Warnings service.
Case study - Service agreement for MYWARP (MYSWARP) services (V1.1 July 2005)
Next step – Service requirements will take you through the next step in the process. In this next stage you will have an opportunity to check that the three core WARP services meet the requirements of your own community by conducting a Requirements capture and Requirements analysis.
Back to top
|
