Skip to main content link. Accesskey S
  • Log In
  • Help
  • IBM Logo
  • WebSphere Portal Family wiki
  • All Wikis
  • All Forums
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • IBM Redbooks
Community Articles Product Documentation Learning Center IBM Redbooks This category IBM Redbooks: Building a Sample Website Using IBM Web Content Manager 7.0 IBM Redbooks: Building and Implementing a Social Portal IBM Redbooks: Developing Exceptional Multi-Channel Web Experiences V7: IBM Web Content Manager Product Documentation V7: IBM WebSphere Portal Enable for z/OS Product Documentation V7: IBM WebSphere Portal Express Product Documentation V7: WebSphere Portal Product Documentation V8: IBM Web Content Manager Product Documentation V8: IBM WebSphere Portal Express Product Documentation V8: IBM WebSphere Portal Product Documentation (includes z/OS) Custom Search Scope...
Search
Community Articles > IBM Web Content Manager > Best Practices for Web Content Manager > Guide to running a WCM Requirements Workshop
  • New Article
  • Share Show Menu▼
  • Subscribe Show Menu▼

About the Original Author

Melissa Howarth
Contribution Summary:
  • Articles authored: 15
  • Articles edited: 52
  • Comments Posted: 7

Recent articles by this author

Creating an Intranet using WCM - Part 4 - Design

The attached document presents the highlevel technical design solution for the Department Template Intranet site. It uses IBM Lotus Web Content Management (WCM) and IBM WebSphere Portal (WP) to provide an integrated solution from content management and life cycle management to the site ...

Creating an Intranet using WCM - Part 3 - Creative

The creative phase of a WCM Project varies from project to project. It may involve very little time with existing graphics being utilised or many months in which an entire site is designed with new branding. The team who carries out the creative design also varies. It may be an internal team or ...

Creating an Intranet using WCM - Part 2 - Project Planning

Many projects have failed due to poor project planning. The following article gives an overview of the typical phases of a wcm project and what items should be considered when implementing a project plan.

Creating an Intranet using WCM - Part 1 - Analysis

Starting with good requirements is essential to the success of any project! It saves time, money and creates a more maintainable site. Coming up with good requirements requires thorough analysis. The most common problem in the requirements analysis phase is that customers have only a vague idea of ...

Creating an Intranet using Lotus Web Content Management

Introduction   This article is the first in a multiplepart series that is going to follow a typical Lotus Web Content Management (WCM) project. It will cover the various phases of the project and the deliverables output from each. It will not focus on the low level technical how to – as this ...

Community articleGuide to running a WCM Requirements Workshop

Added by Melissa Howarth | Edited by IBM contributor Craig Lordan on October 22, 2009 | Version 20
  • Edit
  • More Actions Show Menu▼
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars
expanded Abstract
collapsed Abstract
No abstract provided.
Tags: 6.0, 6.1, planning, WCM, Project Management
Document Purpose


This article is designed to assist a consultant in defining a WCM workshop agenda to discuss the requirements for designing a web site and the implementation of an infrastructure to support that web site.

It provides examples of issues and questions that should be considered during the requirements phase for a lotus web content management (wcm) solution. This is specifically targeted at a technical audience who are familiar with web content management terminology and have a good understanding of both software and infrastructure.

Generating Specific Workshop Agendas

When developing an agenda for a specific workshop, the consultant will need to his/her existing knowledge of the environment and the user requirements to determine which areas of content within each section of the potential agenda modules in the next section will be relevant and important.
The timing should be given for each agenda module in the next section and will be based on the customer either already having the required information to hand or actions being generated for people to research the information off-line rather than lengthy discussions taking place during the workshops.
One way to use these modules would be to spend a couple of hours with the key customer contact explaining what could be covered in each section of a workshop and discussing who within the customer organization might have the required information or would require consultation on decisions made. This should help to identify the likely attendees for the workshops.
If specific sections have very distinct attendee lists, this also may lead to a decision to split the agenda into more than one workshop so that attendees do not get bored sitting through agenda sections in which they do not have an interest.

Requirements workshops:
Typical requirements workshops can be 2 – 4 days. For large implementations, they can be split into logical chunks such as Content Life Cycle, Presentation (Look and Feel) and Infrastructure.

Participants for the requirements workshops could comprise: authors, web master, content governance representatives, graphic designers, WCM architect, infrastructure architect, business analyst. Some participants will be required to attend all workshops, but some such as the graphic designers do not.

Technical design workshops:
A similar 2 – 4 days (if not more) will also be required for the technical design workshops. Based on the information gathered during the requirements workshops, construct a series of usage scenarios and authoring scenarios. Modify the list of questions to suit your particular requirements. Use these scenarios in a series of walk-through against the modified questions during the design workshops.

Participants are: business analyst, web masters, graphic designers, WCM architect, infrastructure architect, security specialist (optional).

Modules are defined in the attached document

Related Content

Redbook: Information Architecture and Site Design

Attachments


  • Edit
  • More Actions Show Menu▼


expanded Attachments (1)
collapsed Attachments (1)
Edit the article to add or modify attachments.
File TypeSizeFile NameCreated On
application/msword 177 KB WCM requirement workshops Guidev1.1.doc 10/21/08 1:07 AM
expanded Versions (15)
collapsed Versions (15)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (20)Oct 22, 2009 4:19:11 PMCraig Lordan  IBM contributor
19Nov 18, 2008 11:46:02 PMMelissa Howarth  IBM contributor
18Nov 18, 2008 11:35:53 PMMelissa Howarth  IBM contributor
17Oct 23, 2008 12:57:51 AMMelissa Howarth  IBM contributor
16Oct 23, 2008 12:51:12 AMMelissa Howarth  IBM contributor
15Oct 23, 2008 12:24:26 AMMelissa Howarth  IBM contributor
14Oct 22, 2008 10:23:21 PMMelissa Howarth  IBM contributor
13Oct 22, 2008 7:57:47 PMMelissa Howarth  IBM contributor
12Oct 22, 2008 4:13:00 AMMelissa Howarth  IBM contributor
11Oct 22, 2008 2:29:00 AMMelissa Howarth  IBM contributor
10Oct 22, 2008 2:16:28 AMMelissa Howarth  IBM contributor
9Oct 22, 2008 2:01:57 AMMelissa Howarth  IBM contributor
8Oct 22, 2008 1:33:02 AMMelissa Howarth  IBM contributor
7Oct 22, 2008 12:32:56 AMMelissa Howarth  IBM contributor
5Oct 21, 2008 9:38:36 PMMelissa Howarth  IBM contributor
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedHelpAbout
  • IBM Collaboration Solutions wikis
  • IBM developerWorks
  • IBM Software support
  • Twitter LinkIBMSocialBizUX on Twitter
  • FacebookIBMSocialBizUX on Facebook
  • ForumsLotus product forums
  • BlogsIBM Social Business UX blog
  • Community LinkIBM Collaboration Solutions
  • Wiki Help
  • Forgot user name/password
  • Wiki design feedback
  • Content feedback
  • About the wiki
  • About IBM
  • Privacy
  • Accessibility
  • IBM Terms of use
  • Wiki terms of use