[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-usability
Subject: KPlato Usability Report
From: Robert Watkins <robert_maria () yahoo ! com>
Date: 2001-08-17 11:15:30
[Download RAW message or body]
Here's my report on KPlato. Since this project is
in the very early stages, there isn't a user-base
to gather comments from. So what I've done is
gather comments of pitfalls people want to avoid
as well as wishlist-types of comments.
Any and all comments are welcome.
Thanks,
Robert
=====
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
["kplato-2001-08-16.html" (text/html)]
<!--
KDE Usability Study Report Framework
Jono Bacon jono@kde.org
This document is licenced under the GNU Public Licence.
-->
<html>
<head>
<title>KDE Usability Report</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" \
marginheight="0" link="#3399FF" vlink="#CCCCCC" alink="#FFFFFF">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="5%" bgcolor="#0000FF" rowspan="5">
<div align="center"><font size="6" color="#FFFFFF"><b>1</b></font></div>
</td>
<td width="95%" bgcolor="#000099"> </td>
</tr>
<tr>
<td width="95%" bgcolor="#000099" height="5">
<div align="center"><font face="Arial, Helvetica, sans-serif"><b><font \
color="#FFFFFF" size="+2">
<!-- Enter your application name here --> KPlato <!-- End --> Usability
Report</font></b></font></div>
</td>
</tr>
<tr>
<td width="95%" bgcolor="#000099">
<div align="center"><font color="#FFFFFF" face="Arial, Helvetica, sans-serif" \
size="2">
<!-- Enter the date -->
1 January 2001
<!-- End -->
</font></div>
</td>
</tr>
<tr>
<td width="95%" bgcolor="#000099">
<div align="center"></div>
</td>
</tr>
<tr>
<td width="95%" bgcolor="#000099" height="2"><font color="#FFFFFF" face="Arial, \
Helvetica, sans-serif" size="2"><b>Resources:</b>
<a href="http://usability.kde.org/">KDE Usability Study</a> - <a \
href="http://www.kde.org/">KDE
Homepage</a></font></td>
</tr>
<tr>
<td width="5%" bgcolor="#000099" height="3"> </td>
<td width="95%" align="left" valign="top" height="3">
<table width="100%" border="0" cellspacing="0" cellpadding="10">
<tr>
<td>
<p><font face="Arial, Helvetica, sans-serif" size="3"><b><font \
size="2">Written
by: </font></b><font size="2"> <!-- Add your name and email address \
details -->
<a href="mailto:robert_maria@yahoo.com">Robert Watkins</a> <!-- End --> \
</font><b><font size="2"><br>
</font></b>
</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2"><b>C O N T E N T \
S</b></font></p>
<!-- Contents -->
<a name="contents"></a>
<table width="100%" border="0" cellspacing="0" cellpadding="2">
<tr bgcolor="#000099">
<td width="9%">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">ID</font></b></font></div> </td>
<td width="91%">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">Item</font></b></font></div> </td>
</tr>
<!-- Add an item to the contents -->
<tr>
<td width="9%"><font face="Arial, Helvetica, sans-serif" size="2">
<!-- ID Number --> #1-1 <!-- End --> </font></td>
<td width="91%"><font face="Arial, Helvetica, sans-serif" size="2">
<a href="#1">End User Scenarios</a></font></td>
</tr>
<!-- End --> <!-- Add an item to the contents -->
<tr>
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> <!-- ID Number --> #1-2 <!-- End --> </font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> <a href="#2">User Goals</a></font></td>
</tr>
<tr>
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2">#1-3</font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><a href="#3">User Interface Requests</a></font></td>
</tr>
<tr>
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2">#1-4</font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><a href="#4">Lessons
learned from MrProject</a> (Gnome-based project management \
project)</font></td> </tr>
<tr>
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2">#1-5</font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><a href="#5">Request for Use Cases</a></font></td>
</tr>
<!-- End -->
</table>
<!-- END OF CONTENTS \
--------------------------------------------------------------------------- -->
<p><br>
<br>
<b><font face="Arial, Helvetica, sans-serif" size="2">I T E M S
</font></b></p>
<!-- Start of item --> <!-- Linked number --><!-- End --><a name="1"></a> \
<table width="100%" border="0" cellspacing="0" cellpadding="2">
<tr bgcolor="#000099" align="left" valign="top">
<td width="9%" bgcolor="#0033CC">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">
<!-- ID Number -->
#1-1
<!-- End -->
</font></b></font></div>
</td>
<td width="91%" bgcolor="#0033CC">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">
<!-- Name --> End User Scenarios <!-- End --> \
</font></b></font></div>
</td>
</tr>
<tr align="left" valign="top">
<td width="9%"><b><font face="Arial, Helvetica, sans-serif" \
size="2">Description</font></b></td>
<td width="91%"><font face="Arial, Helvetica, sans-serif" size="2">
<!-- Desciption info --> Take the mythical XYZZY corporation
-<br>
they make toys and sports products.<br>
It has a few different people:<br>
Abigail, who is the Managing Director;<br>
Bob, one of the five design team leaders (the others: Bill,
Brian, Bette and<br>
Bruce (his real name is Eric, but he's Australian:)<br>
Charlie, the financial controller<br>
Deb, who is in charge of marketing<br>
Edward, who is running internal production<br>
Fran, who runs the logistics team (warehousing, distribution
and materials<br>
sourcing)</font>
<p><font face="Arial, Helvetica, sans-serif" size="2">So Bob,
who has just been assigned responsibility for development
of a new<br>
scooter with a V8 motor, is probably a mechanical engineer
turned manager, and<br>
is busy trying to assign his design engineers, drafters and
test equipment to<br>
get the widget out in the time frame. He gets out kplato 1.0,
opens the<br>
document that has all his existing work, looks at the existing
tasks, figures<br>
out who can be re-assigned (full or part time), and builds
an outline of the<br>
work tasks that he needs to accomplish to get the scooter
design done as a new<br>
WBS element.</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">Bob then
calls a meeting, explains the new tasks to the relevant people,
and<br>
assigns tasks using the kplato to KDE-PIM interface. When
an individual,<br>
lowest level WBS element is completed by whoever it is assigned
to, the<br>
KDE-PIM interface updates the kplato document, \
automatically.</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">Deb knows
that a V8 scooter is going to take some serious selling in
the<br>
safety conscious marketplace, and decides that she needs to
sort out how it is<br>
going to fit in to all the other marketing she has to do.
She also uses kplato<br>
1.0, and links across to Bob's document to see when things
are going to be<br>
finished with the design, since that is the earliest a prototype
will be<br>
available.<br>
[ This means that one part of Bob's project ("running
the team") becomes a<br>
constraint on Deb's project. I'd consider that this means
that Bob's project<br>
is a sub-project to Deb's project]</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">One of
the outputs of the scooter design that will come from Bob's
team will<br>
be a Bill of Materials, that lists all the things that it
takes to make one<br>
scooter. This goes to Fran, who has to get the materials,
and to Edward, who<br>
has to assemble the scooters. Edward will also get some other
drawings, and<br>
some assembly instructions. </font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">Edward,
who is something of a geekboy, is running the new kplato 1.3
release.<br>
Edward has the ability to insert the various assembly steps
and the Bill of<br>
Materials into his kplato document, and has some extra \
interfacing code that<br>
looks at the current inventory status (maintained as a legacy
PostgresSQL<br>
database by Fran's team, althought Edward hopes for inventory
management in<br>
the upcoming kplato 1.4 release), the machine capacity and
the required<br>
production numbers (from Deb's KSpread document), and can
then schedule all<br>
those resources using kplato's constraint fitting algorithms
and a lot of CPU<br>
cycles.<br>
[This means that you need to be able to insert \
"modular" work packages into<br>
higher level documents. Those work packages are sub-tasks,
held as seperate<br>
definitions, but instantiated as part of Edward's kplato \
document.]</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">Deb can
now take the production schedule from Edward's kplato document
(even<br>
if Deb's 1.0 release can't see all the fancy work behind Edward's \
1.3 release,<br>
Deb can still get the fundamental schedule out) and schedule
the "rollout" of<br>
the sales promotions and give-aways as part of her document.
<br>
[This means that Deb's database now has multiple constraints,
one based on<br>
Bob's prototype delivery, and several based on Edward's \
production runs.]</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">Charlie
can access the kplato documents of Bob, Fran and Edward to
determine<br>
spend spread (when the dollars go out the door) for prototyping
materials and<br>
equipment, raw materials, and consumables respectively. He
can then access the<br>
kplato document of Deb, to see when the revenue is supposed
to come in from<br>
sales. If this shows a problem, then they can all get together,
replan, and<br>
resolve the problem. [ This means that Bob's, Fran's, Edward's
and Deb's<br>
projects are probably sub-projects of Charlie's KSpread document, \
since<br>
extracting constraints isn't any different to extracting \
costs]</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">Abigail,
who isn't too good on kplato scheduling, but does like the
quality of<br>
the Gantt chart layout, sends email to some of the people,
and gets some<br>
dates, extracted by hand, from each of the other kplato \
documents. These are<br>
then cut'n'pasted into kplato, and the output chart is then
linked into<br>
KPresenter, for a presentation to the Board. After she does
the kplato course,<br>
she will know that it is possible to extract the dates \
automatically and have<br>
them linked. But she won't, since email is less work than
sorting through the<br>
detail, and Managing Director's are like that :)<br>
</font></p>
<hr>
<font face="Arial, Helvetica, sans-serif" size="2"><br>
</font>
<p><font face="Arial, Helvetica, sans-serif" size="2">1. Plan
out the entire network at a high level of detail.<br>
2. Do the detailed breakdown and assignment of resources for
the next six <br>
months (as this about as far ahead as I can accurately guess
resources)<br>
3. For the rest of the high level, I would assign estimated
duration based on <br>
experience (i.e. other projects of similar size), and assign
a risk that <br>
indicates my confidence in that estimate.</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">In order
to be able to do that we need to be able to associate a <br>
risk/duration with a task alone. One way around this would
be to assign a <br>
default resource to a task if there isn't one. We could then
enforce the <br>
constraint that only task/resource pairings have durations
and risks (come to <br>
think of it this is a good idea, and could solve some other
problems I see <br>
arising).</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">I need
to do some thinking about this, because there are a few problems
to <br>
solve:</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">1) The
constraint that assigned risk (calculated is another matter)
only <br>
exists in a task/resource pairing.</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">2) An
effort is associated with a class of resources; i.e. adding
a computer <br>
doesn't affect the number of man hours available.</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">3) \
Technically
a task alone does not have an effort (effort is assigned time,
<br>
duration is calculated time). Example "Develop x \
module" requires 150 <br>
manhours -- this only makes sense if a developer is assigned.
</font> </p>
<p> </p>
</td>
<!-- End -->
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><b>References</b></font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> <!-- Reference Links --> <a \
href="http://mail.kde.org/pipermail/kplato/2001-June/000049.html">http://mail.kde.org/pipermail/kplato/2001-June/000049.html</a><br>
<a \
href="http://mail.kde.org/pipermail/kplato/2001-July/000150.html">http://mail.kde.org/pipermail/kplato/2001-July/000150.html \
<!-- End --> </a></font>
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><b>Proposed
Soloution</b></font></td>
<td width="91%" height="2">
<p><font face="Arial, Helvetica, sans-serif" size="2">The first
scenario points out some likely un-used functions of KPlato,
however, it does point out some specifics to implement. The
second seems more plausible, but is less detailed.</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">Additional
Use Cases are needed to be able to complete the Features and
Deliverables list. I'd suggest doing a paper prototype exercise
that has the project managers that are posting to the list
give feedback on how they would use the proposed system based
on a very rough set of 'screens'. Then take these results
and incorporate them into the features list, list of additional
questions and a new set of paper prototypes to iterate the
process. <!-- Proposed soloution --> </font> <!-- End -->
</p>
</td>
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2">
<a href="#contents">[contents]</a></font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2">
</font></td>
</tr>
</table>
<!-- End -->
<!-- Start of item -->
<!-- Linked number -->
<p><a name="2"></a></p>
<!-- End -->
<table width="100%" border="0" cellspacing="0" cellpadding="2">
<tr bgcolor="#000099" align="left" valign="top">
<td width="9%" bgcolor="#0033CC">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">
<!-- ID Number -->
#1-2
<!-- End -->
</font></b></font></div>
</td>
<td width="91%" bgcolor="#0033CC">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">
<!-- Name --> User Goals <!-- End --> </font></b></font></div>
</td>
</tr>
<tr align="left" valign="top">
<td width="9%"><b><font face="Arial, Helvetica, sans-serif" \
size="2">Description</font></b></td>
<td width="91%"><font face="Arial, Helvetica, sans-serif" size="2">
<!-- Desciption info -->*It would be real cool if this product
were to support Timeboxing. I think this is a real necessity
in this day and age of DSDM, RUP, and other RAD based \
methodologies.<br>
*Will there be the ability to resource share across projects
so that we don't over-schedule? <br>
*Also I prefer to be able to allocate a % of the resources work
day to 'admin' so that I know how much is truely productive
for my project(s). <br>
*One feature that I have seen nowhere is the ability to define
a task or resource as interruptable or non-interruptable. Certainly \
software folk are familiar with these concepts, but automatic
scheduling software that I am aware of is not. Interruptable
tasks and resources could (should) also have start-up and/or
shut-down penalties associated with them!!! <br>
*Allow the ability to generate a delivery date and buffer (e.g.
30 +- 5 days to complete) based on assumptions about the estimates
to complete tasks and the confidence in those \
estimations.</font></td>
<!-- End -->
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><b>References</b></font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> <!-- Reference Links --> <a \
href="http://mail.kde.org/pipermail/kplato/2001-August/000184.html">http://mail.kde.org/pipermail/kplato/2001-August/000184.html</a><br>
<a \
href="http://mail.kde.org/pipermail/kplato/2001-August/000182.html">http://mail.kde.org/pipermail/kplato/2001-August/000182.html</a> \
<br>
<a \
href="http://mail.kde.org/pipermail/kplato/2001-July/000153.html">http://mail.kde.org/pipermail/kplato/2001-July/000153.html</a> \
<br>
<a \
href="http://mail.kde.org/pipermail/kplato/2001-June/000089.html">http://mail.kde.org/pipermail/kplato/2001-June/000089.html \
</a><br>
<!-- End --> </font>
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><b>Proposed
Soloution</b></font></td>
<td width="91%" height="2">
<p><font face="Arial, Helvetica, sans-serif" size="2">I'm not
sure what Timeboxing is, additional information would be needed
to look into this further. <!-- Proposed soloution --> </font>
<!-- End --> </p>
<p><font face="Arial, Helvetica, sans-serif" size="2">Managing
and reporting on resources seems to be an important area.
Add these to the Features and Deliverables list and do some
user testing to determine what's really needed and what else
is missing.</font></p>
</td>
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2">
<a href="#contents">[contents]</a></font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2">
</font></td>
</tr>
</table>
<!-- End -->
<p><a name="3"></a></p>
<table width="100%" border="0" cellspacing="0" cellpadding="2">
<tr bgcolor="#000099" align="left" valign="top">
<td width="9%" bgcolor="#0033CC">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">
<!-- ID Number --> #1-3 <!-- End --> </font></b></font></div>
</td>
<td width="91%" bgcolor="#0033CC">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">
<!-- Name --> User Interface Requests <!-- End --> \
</font></b></font></div> </td>
</tr>
<tr align="left" valign="top">
<td width="9%"><b><font face="Arial, Helvetica, sans-serif" \
size="2">Description</font></b></td> <td width="91%">
<p><font face="Arial, Helvetica, sans-serif" size="2"> <!-- \
Desciption info -->
*Alert to the user if end dates cannot happen for a task or
project due to prior tasks falling behind or scope change.<br>
*Alert to the userover-scheduled resources for a particular
timeframe.<br>
*Specify tie-breaking rules for resources/tasks if there are
competing priorities.<br>
*Alert when tasks are past-due</font><br>
<font face="Arial, Helvetica, sans-serif" size="2">*To be
really useful, task durations and effort should be displayable
and enterable in minutes, hours, days and weeks. <br>
*I would prefer to have resources listed like CA-Superproject,
not in a column like M$ Project. <br>
*Don't change values that have been manually entered </font>
</p>
</td>
<!-- End --> </tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><b>References</b></font></td> <td width="91%" height="2">
<p><font face="Arial, Helvetica, sans-serif" size="2"> <!-- \
Reference Links --></font><font face="Arial, Helvetica, sans-serif" size="2"><a \
href="http://mail.kde.org/pipermail/kplato/2001-August/000186.html">http://mail.kde.org/pipermail/kplato/2001-August/000186.html</a> \
<br>
<a \
href="http://mail.kde.org/pipermail/kplato/2001-August/000181.html">http://mail.kde.org/pipermail/kplato/2001-August/000181.html \
</a><br>
<a \
href="http://mail.kde.org/pipermail/kplato/2001-June/000059.html">http://mail.kde.org/pipermail/kplato/2001-June/000059.html \
</a><br>
<a \
href="http://mail.kde.org/pipermail/kplato/2001-June/000089.html">http://mail.kde.org/pipermail/kplato/2001-June/000089.html \
</a><br>
<!-- End --> </font></p>
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><b>Proposed Soloution</b></font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2">These
are good candidates for user testing with paper prototypes detailed \
above.<!-- Proposed soloution --> </font> <!-- End --> </td>
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> <a href="#contents">[contents]</a></font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> </font></td>
</tr>
</table>
<!-- End -->
<p><a name="4"></a></p>
<table width="100%" border="0" cellspacing="0" cellpadding="2">
<tr bgcolor="#000099" align="left" valign="top">
<td width="9%" bgcolor="#0033CC">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">
<!-- ID Number --> #1-4 <!-- End --> </font></b></font></div>
</td>
<td width="91%" bgcolor="#0033CC">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">
<!-- Name --> Lessons learned from MrProject (Gnome-based
project management project) <!-- End --> </font></b></font></div>
</td>
</tr>
<tr align="left" valign="top">
<td width="9%"><b><font face="Arial, Helvetica, sans-serif" \
size="2">Description</font></b></td>
<td width="91%"><font face="Arial, Helvetica, sans-serif" size="2">
<!-- Desciption info --> * Dependencies... The "link"
button isn't very user friendly. As I'm building a project,
the tasks aren't<br>
necessarily listed in any meaningful order. Setting dependencies
helps me determine what order they should be in. When I set
dependencies through the interface, the direction of the dependence \
is determined by the order on the task list. I'd prefer to to
have another tab on the "Task Properties" dialog call
"dependencies" where I could manually enter the ids
of other dependent task" (This links would have to be \
preserved when I reorder also).</font> <br>
<font face="Arial, Helvetica, sans-serif" size="2">* Get that
% complete feature working!</font> <br>
<font face="Arial, Helvetica, sans-serif" size="2">* Identify
resource conflicts. Let me know if I've assigned "Bob"
to two tasks at the same time.</font> <br>
<font face="Arial, Helvetica, sans-serif" size="2">* Let us
be able to manually enter the duration right on the gantt chart
screen. We can grab the bar in the can drag it, but we can't
type in "20 hrs".<br>
* Let us drag-n-drop to reorder items in the task list. <br>
* The ability to set priorities and have a sort feature which
would order the list based on this value. The nesting would
have be taken into consideration. For instance, if a task is
nested 3 (for example) level deep but has a very high priority,
then it's top-level category should move to the top of the list
when sorted. -<br>
* The ability to "check off" completed items. Checked off items
should be flagged as such (maybe the gantt chart should turn
red). It would also be nice to hide completed items. This would
make viewing large projects much nicer. </font></td>
<!-- End --> </tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><b>References</b></font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> <!-- Reference Links --> <a \
href="http://mail.kde.org/pipermail/kplato/2001-August/000180.html">http://mail.kde.org/pipermail/kplato/2001-August/000180.html</a><br>
<a href="http://lists.codefactory.se/pipermail/mrproject/2001-July/000248.html">http://lists.codefactory.se/pipermail/mrproject/2001-July/000248.html \
</a><br>
<a \
href="http://mail.kde.org/pipermail/kplato/2001-July/000171.html">http://mail.kde.org/pipermail/kplato/2001-July/000171.html \
</a><br>
<a \
href="http://lists.codefactory.se/pipermail/mrproject/2001-July/000245.html">http://lists.codefactory.se/pipermail/mrproject/2001-July/000245.html</a> \
<br>
<a \
href="http://mrproject.codefactory.se">http://mrproject.codefactory.se </a><br>
<!-- End --> </font>
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><b>Proposed Soloution</b></font></td>
<td width="91%" height="2">
<p><font face="Arial, Helvetica, sans-serif" size="2">Generally,
keep an eye on the discussion forum for MrProject and make
a note of their lessons learned and incorporate into future
development plans.</font><font face="Arial, Helvetica, \
sans-serif" size="2"><!-- Proposed soloution --> </font> <!-- End --> </p>
</td>
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> <a href="#contents">[contents]</a></font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> </font></td>
</tr>
</table>
<!-- End -->
<p><a name="5"></a></p>
<table width="100%" border="0" cellspacing="0" cellpadding="2">
<tr bgcolor="#000099" align="left" valign="top">
<td width="9%" bgcolor="#0033CC">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">
<!-- ID Number --> #1-5 <!-- End --> </font></b></font></div>
</td>
<td width="91%" bgcolor="#0033CC">
<div align="left"><font face="Arial, Helvetica, sans-serif" \
size="2"><b><font color="#FFFFFF">
<!-- Name --> Request for Use cases<!-- End --> \
</font></b></font></div> </td>
</tr>
<tr align="left" valign="top">
<td width="9%"><b><font face="Arial, Helvetica, sans-serif" \
size="2">Description</font></b></td>
<td width="91%"><font face="Arial, Helvetica, sans-serif" size="2">
<!-- Desciption info --> Request for Use Cases</font></td>
<!-- End --> </tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><b>References</b></font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> <!-- Reference Links --> <a \
href="http://mail.kde.org/pipermail/kplato/2001-June/000106.html">http://mail.kde.org/pipermail/kplato/2001-June/000106.html</a><br>
<!-- End --> </font>
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"><b>Proposed Soloution</b></font></td>
<td width="91%" height="2">
<p><font face="Arial, Helvetica, sans-serif" size="2">Develop
Use Cases ;)</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="2">Seriously,
formalized use cases can be developed only with a clear \
understanding
of how the users will be using the system. User Scenarios
and User Testing will be the key to this \
understanding.</font><font face="Arial, Helvetica, sans-serif" size="2"><!-- Proposed \
soloution --> </font> <!-- End --> </p>
</td>
</tr>
<tr align="left" valign="top">
<td width="9%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> <a href="#contents">[contents]</a></font></td>
<td width="91%" height="2"><font face="Arial, Helvetica, sans-serif" \
size="2"> </font></td>
</tr>
</table>
<!-- End --></td>
</tr>
</table>
</td>
</tr>
<tr bgcolor="#000099">
<td width="5%" height="2"> </td>
<td width="95%" height="2">
<div align="left"><font color="#FFFFFF" face="Arial, Helvetica, sans-serif" \
size="2">
KDE Usability Study Maintainer:
<a href="mailto:jono@kde.org">Jono Bacon</a></font></div>
</td>
</tr>
</table>
</body>
</html>
_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic