 |
 |
Daniel, > If we're using story points to evaluate "efficiency" then should we > make sure to have tasks that cover what we're doing? It's not required, if your ancillary tasks tend to take up about the same amount of overhead, but it doesn't hurt. > For example, I've spent half a day playing with the new xrootd > interface, but am not generating any concrete output, aside from > establishing my own reference code for using the new interface. The > xrootd interface tasks are not assigned to me, so is it important to > account for my time? If so, where? In DM-70, DM-220, DM-221, or > DM-222? Add an additional small task, whether part of another or a new one. Think of it as how you would record your activity in a status/progress report. At the end of the week, your completed tasks will be exactly that report. -- Kian-Tat Lim, LSST Data Management, [log in to unmask] ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1