Personalization5.

R: Anna Wilkins

Maintenance6.

R: Peter McIntosh

Content3.

R: Peter McIntosh

General1.

R: John Williams

Generic2.1.

Ease of use2.4.

Search2.5.

Look and feel2.3.

Navigation2.2.

Website performance4.1.

Platform4.2.

Measurement4.3.

Technical4.

R: Sarah Johnson

The career site should be created in labourmarket 'look and feel'2.3.2.

5 R: Walter Swift

The website should be appealing to itstarget audiences2.3.1.

1 R: Walter Swift

Product branding should be visible onrelevant webpages2.3.3.

3 R: Anna Wilkins

Selected product logo's should be visible on theproduct website2.3.4.

3 R: Walter Swift

Scrolling should always support contentaccess2.1.1.

2 R: Walter Swift

The website interface should also bestructured on industry type and markets(besides products & applications)

2.1.2.

2 R: Ben Millar

URLs should become user friendly2.1.3.

Document URLs stay intact after Go Live4.4.

R: Bradley Evans

CRStech

Usability2.

R: Anna Wilkins

?

XLS exit: collaborating on requirements using mindmap concepts

Table hell

Organizing requirements into a spreadsheet and trying to discuss them

with stakeholders. The huge spreadsheet makes your audience

lose context, facilitates a discussion only on individual requirements, and decision making is made a tedious practice. To improve this process

we came up with an approach to handle requirements in a visual way using mindmap

concepts.

Layered categorization

The layered categorization ensures

you don’t get thrown down to the lowest level, but

drill down gradually.

Design vs implementation

Not all phases are equal. A mindmap is difficult to fit in

a developers’ workflow while a

.xls is not.

Visual metadata

Visual metadata, like question marks,

thumbs up/down, agile phase and completion,

helps logging the discussion.

Relations between

requirements

Any brought in requirements that are

conflicting can be linked to each

other, facilitating discussion.

Attachments

Direct access to the source of

the requirement by attaching the source (xls, ppt, email, links)

providing better insight

Contextual content

Include prioritization, logging of stakeholders, timetracking (start date, due date, duration) and

link rich media

Facilitation of communication

Adding requirements including prioritization,

(stakeholder) logging and contextual content is a perfect

fit. It makes it easy to bring a discussion to the right level and point out gaps

within the defined needs.

Jeroen Grit@JeroenGrit

jeroen@gridd.nl

A structured overview while providing the possibility of a detailed dive in

3?

R: