Changes between Version 3 and Version 4 of MolgenisTicketFaq

Timestamp:

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

Author:

Morris Swertz

Comment:

--

MolgenisTicketFaq

@@ -15 +15 @@
 * if you have many small todos, please put them in ONE extra ticket so we can still discuss them during work meeting
 
-== What makes a good ticket ==
+== What makes a good ticket? ==
 
-'''Tickets always have a description''' that explains for all team members to understand:
+For a good ticket you can easily answer the following questions: 
 
-* Motivation: why or for whom do we do this? For example?
-* Expected output: what will we have in hand when the tickets is closed?
-* (Optional) what is the plan of '''actions''' to achieve it.
-* (Optional) how do we measure this output. For example a 'test case'.
+When the ticket is new:
+* Motivation: '''Why or for whom''' do we have this ticket? For example: for LifeLines.
+* Scope: What is the '''expected output''' to close this ticket? For example: wiki page, Excel file, Working demo, Unit test, etc.
 
-Please use the discussion mechanism to log your progress on the ticket.
+When the ticket is worked upon:
+* Actions: What are we '''planning to do to''' produce the expected output? For example: interview, program, design, statistical test, etc.
+* Evaluation: What are the '''criteria of succes''' on which we (or the customer) decides the outcome is good enough? For example: evaluated by person X, test-case passed, presented at meeting X.
 
-For example: 
-For medgen and bbmri (=for whom): we compare imputation methods Beagle, Impute and MACH to the percentage correctly estimated SNPs (=output). We take existing genotype data from 1M arrays and split the data randomly in two. The first half we input into the impute methods. Then we calculate percentage correctly estimated SNPs on the other half for each method (=actions).
+Please use the discussion mechanism to have discussions on the actions. It is like a forum :-)
+
+== Size of tickets? ==
+
+If you can't easily answer the questions above for your ticket is probably too big and needs to be in a chain of smaller tickets.
+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..
+
+Implicit in above is: the code is commited to SVN and there is a manual.