The below is a first stab at the kind of high level information you require at the start of an Interwoven Upgrade project.

- Why are you doing the upgrade? What are the main drivers and benefits?

- What are the project timelines? Is there a “drop dead” date?

- What is the project budget and where are the perceived risks to exceeding this?

- How many people in the technical team for the Upgrade? Are their roles clearly defined?

- What versions of software are you currently using for TeamSite, LiveSite, OpenDeploy etc?

- What versions are you planning to upgrade to for each of the above?

- What other new products are you planning to introduce?

- Which other software platforms do you integrate with? Examples are Websphere, Weblogic, Sharepoint…

- What operating system is in use, including the version?

- Where are the current user profiles stored? Is it locally to the server or in LDAP or Active Directory?

- How many users are there in the current system? Please group them into “frequent users” and “occasional users”.

- Is the TeamSite backing stored going to be “migrated” or can the Editions simply be copied over for each branch to the new server?

- Where is the data stored? Is it in a database, filesystem or both?

- What do the current workflows do at a high level?

- What do the current deployments do? Are database deployments involved?

- What do the current data capture forms do? Any particular features of interest such as database callouts and use of FormAPI?

- What customisations are required for TinyMCE or Visual Format Editor?

- What customisations have been done or are planned for the User Interface?

- Do you currently have any scheduled nightly or weekend tasks that run on the servers?

This is a list of questions to ask a new project that is required to be delivered on an existing Interwoven platform.

The idea with asking these questions is to get an immediate feel for size, benefits and risks of the project and then to help set the clients expectations on timescales, budgets and quality of the deliverable.

- What date do you need to deliver the project?

- Who is the end customer for the project?

- Who will sign off the project for the business?

- Who will assist with testing?

- Who will assist with the requirements document?

- Is there more than one business unit involved?

- Is this a new website?

- Is a change needed to the CMS Service Level?

- Is there any 3rd Party Integration?

- Is there any integration with backend systems?

- Can we have a content freeze?

- Are Web Site analytics required?

- Are page Redirects required?

- Are there any additional CMS Support requirements?

- Is there a requirement for multi-language support?

- Do we need to create or update branches?

- Do we need to create or update workareas?

- Do we need to create or update deployments?

- Do we need to create or update data capture forms?

- Do we need to create or update presentation templates?

- Do we need to create or update components?

- Do we need to create or update workflows?

- Do we need to create or update menu items?

- Do we need to create or update users or groups on the servers?

- Will content need to be regenerated?

- Will content need to be migrated?

- Do we need to create or update a cron job?

- Is this a global code change or specific to a project?

- What other technical teams are involved?

- What is the availability of the other technical teams for the dates?

- What dates will we need to raise Change Requests on?

- Which team will own the project once it is in Production?