 |
 |
Daniel I heard epics are things that take longer than 2-3 weeks, and stories should be some smaller things: days to ~2-3 weeks long. We are all still learning, and I am sure we will have more discussions about it. But I was assured by both Mario and KT that we should have both stories and epics in qserv. Please go ahead and add descriptions as you find things missing or incomplete. *We all* are custodians of this thing, don't think it is just me :), I'd really like to see the whole team actively changing things, improving, commenting on and massaging as needed. Otherwise, it won't work. Thanks Jacek On 03/17/2014 03:19 PM, Wang, Daniel Liwei wrote: > I think the epics need some description. > e.g., Qserv refactoring: Modules should have clear responsibilities, and > each module's interface to other modules should be as narrow and limited > as is practical. > > "Qserv Design week II" sounds like it should be a label or a "story". > Probably a label. The things we want to treat and cover over the week > have their own lifetimes, with a specific thing we hope to accomplish > during qdw2. i.e., For DM-56, the task for qdw2 might be "evaluate > current css implementation and integration". > > I think "epics" are supposed to be something you can describe as well as > a "story", except that you can't (more or less) guarantee the scope and > completion time. Hence they often get stories added to them as you learn > more about them. > > http://www.agilemodeling.com/artifacts/userStory.htm > http://advancedtopicsinscrum.com/glossary-agile-scrum-terms/epic/ > http://scrummethodology.com/scrum-epics/ > > Thinly veiled behind the jira switch is really a wholesale switch to > agile in terms of planning, organizing, and executing work. If we're not > switching, we should ignore epics and stories, no? > > -Daniel > > On 03/14/2014 09:29 PM, Jacek Becla wrote: >> Hi >> >> I entered all S14 tasks we earlier discussed through the >> spreadsheet into jira. (for your reference the spreadsheet >> is attached with the corresponding jira numbers). >> >> It'd be really good if all of you could try to look, just >> to get familiar with jira. I am happy to carve 15-20 min at >> the meeting next week to walk you through various things >> in jira (I am still learning, but I spent many hours in jira >> by now, so I guess I learned a few things). We will be >> tracking all S14 things through jira, so there is virtually >> no way you could avoid using jira in the near future... >> >> We still don't have Fabrice's account there, so "his" tasks >> are temporarily assigned to me, I'll fix that once his >> account gets created. >> >> I took liberty to come up with a few "epics", and now it is >> time to get your opinion (including K-T's!) if that makes >> sense... it is basically: >> - hackathon >> - major refactoring of all qserv code (it is a big one!) >> - fully automated testbed >> - logging >> - configuration >> >> some tasks are not assigned to any epic. You can see all >> that by sorting by issue type, and tweaking which columns >> are displayed. >> >> Many "stories" are still at a high level, we will be adding >> subtasks covering actual work soon (and assigning many of >> them to you, as opposed to me :) >> >> Feel free to improve, tweak, add missing dependencies etc. >> >> Heads up: I am considering using jira in place of our weekly >> round table report (once you all get used to jira...), and >> use the time at meetings to focus on design topics/blockers >> and other things that actually need discussion for real. >> >> Jacek >> >> ######################################################################## >> 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 > ######################################################################## 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