Changes between Version 6 and Version 7 of MolgenisTicketFaq

Timestamp:

2010-12-01T10:14:37+01:00 (14 years ago)

Author:

Morris Swertz

Comment:

--

MolgenisTicketFaq

@@ -35 +35 @@
 
 In that case it needs to be in a chain of smaller tickets, and the first ticket is than to answer all these questions.
-For example: 'Design a user interface for LIMS' is way too big. Expected evolution of your tickets:
-* Ticket 1: 'Create a mock-up for lab data-entry based on protocols'. Expected output is a wiki page with the mock-up that has been evaluated with Morris and/or team members.
-* Ticket 2: 'implement user interface for lab data-entry based on protocols'. Expected output is a working demo of (link to output of ticket 1 here) + manual that has been evaluated with Morris and/or team members.
-* Ticket 3: 'User test interface for lab-entry'. Expected output is a log on where the user had trouble. Typical result may be that Ticket 2 is reopened for improvement..
+For example: '''Design a user interface for LIMS''' is way too big. Expected evolution of your tickets in such case:
+* Ticket 1: '''Create a mock-up for lab data-entry based on protocols'''. 
+ Expected output is a wiki page with the mock-up that has been evaluated with Morris and/or team members.
+* Ticket 2: '''Implement user interface for lab data-entry based on protocols'''. 
+ Expected output is a working demo of (link to output of ticket 1 here) + manual that has been evaluated with Morris and/or team members.
+* Ticket 3: '''User test interface for lab-entry'''. 
+ Expected output is a log on where the user had trouble. Typical result may be that Ticket 2 is reopened for improvement..
 
-Implicit in above is: the code is commited to SVN and there is a manual.
+Implicit in above is: the code is commited to SVN and there is a manual on the wiki of your component.