2010-02-25 Thursday Meeting
Attending: Brian, Josh, Scott, Andrew, Chris, Will, JM, Ola, Donald, Melissa, Jason
Agenda
Remember: Agenda must be complete (with estimated times) on the day before the meeting. Any additions after that must go at the bottom (AOCB)
Accepting minutes from last meeting
Matters Arising (<10 mins)
- Chris: Send email to nitpick about patch release
- Andrew: Do the items task needed from last week's minutes
- Ola, Josh, Carlos: meeting to discuss metadata harvesting changes
- Donald: send an email to OME-DEVEL about upcoming changes to ROI storage.
- Everyone: keep up to date on the feedback to forums for ROI changes.
- Everyone: review https://trac.openmicroscopy.org.uk/omero/wiki/WorkPlan/Permissions. This is a good example of how to link tickets/revisions tp work plan pages.
- JM, Colin: Get ready to demo the new FS features for the end of this upcoming iteration.
- Chris: enable the block importing from bio-formats so Will can import his large EM images.
- Everyone: if you would like to see where BF is going (for demo) look at the test reports on Hudson.
- Brian: ready Demo of server-side history for end of iteration.
- Everyone: please check out the graffle after Jean-Marie upgrades
- Everyone: please review the new FAQ questions Andrew has added to the website.
- Everyone: schedule a meeting to gather/orgranize our code samples for the developer community.
- Everyone: please try to get your tasks for these meetings done well in advanced!
- Wlll/Andrew: set up a page where everyone can gather their examples (after reviewing existing pages).
- Scott: try to monitor everyone's usage in Agilo.
- Brian: confirm that the Agilo trac links in google still work.
- Jason: need someone to go see Tom about his Gel's!
Chris on how Agilo works (10 mins)
Generating sprint (30 mins)
- Iteration graffle
- Estimates
Email and Forum Review - checked at 1:30 (5 mins)
- Email - none
- Forums -
-
OMERO.qa reports -
There are 8 pages of new tickets (approx 200) in the system going back to October 2009. Can we close these?
Just looking at this month:- 30 new tickets
- 5 people (excluding OME team)
- 5 problems - Delete User, No Such Table, Tiff Import, File size from Huygens .ome, Heap size with .svs
AOCB (<5 mins)
- Enumerations
Notes
Review of Last Week's Meeting Minutes
-
Bioformats patch release
- Chris: Still waiting on data
- @Chris will send a direct follow
- Andrew prepared examples ticket
- @Josh, Ola, Carlos: still need to have discussion about django app
- @Donald: haven't written to ome-devel
-
FS
- Presentation Tuesday
- Intent is to get a roadmap settled
- Various issues, including permissions
- @Chris adds block import ticket
-
BF demo
- See workplan page with links to specifics
- Jean-Marie: testing beginning of March with FS?
- Should be on track, yes.
- Server-side history demo next week? Yes
-
FAQ
- Will did one
- @Andrew sends a remind to nitpick
- Scott: how often should it be done?
- Josh: we agreed to sit down together in the next weeks
-
Donald: do we have page statistics on who looks at the FAQ? Yes.
- But haven't looked at it
- @Andrew: will look at FAQ web stats to see if it's used
- Chris: at the moment, the forum is very busy.
-
Examples
- @At end of iteration, we should do the FAQ and the code samples
- Gels: @Will will go see Tom.
-
Bioformats patch release
Agilo
-
Overview
- Lots of different terms in Agilo (from what we've been using)
-
Scott's PDF
- Green are the things we already use
- Sprint backlog == what we've been trying to do with graffle
- Sprint planning == what we've been doing at the start of iteration
- Sprint == iteration
- Other terms are new, and can be ignored since there is overlap
-
Details (Screenshots)
- A lot of agilo will not work properly unless we group with tasks
- "Story" == WorkPlan page (that's the scale)
-
Agilo doesn't support cascading stories
- i.e. can't have story dependent on story
- no hierarchies
-
Important: don't associate any work with a story
- Commits not associated with a story
- Story is not necessary related to the investigation
-
Example
- Perm page -> "Build facility for Group owner to admin own group"
- @Story points: need to decide how to handle this
- Story is added on Thursday to the sprint
- time remaining is automatically calculated
- When you add a task, you include the estimated time
- all the links are handled for you.
- NB: All estimates are in days regardless of whether H or D is displayed
- Makes your life simpler if you do STORY --> TASKS!
- Jason: * backlog is our graffle? * Sprint backlog is the graffle (all tasks for given iteration)
- commit integration: makes our life simpler
-
In Progress
-
Traditional
- Nothing assigned until you're working it
- Come in in the morning, assign it to you.
- One it's in progress, it's in progress
- Our way????
-
Traditional
-
Estimations
- Agilo doesn't provide actively provide estimations and actual time worked.
- No way of displaying accurately (but we have the history)
-
In some ways we are using a "Broken" scrum
- No product owner
- No standups
- No scrum master
-
Product backlog
- All our open tickets
- Slightly better visualization via agilo
-
Summary
- Continue using trac as we were before
- On Thursday, we will start a real sprint
- @Look at commit methods and make comments
- @Chris will put the code in place.
- @Everyone will need to use the commits.
-
Ola: 2 people working on a story?
- Use 2 stories?
- NB: colors aren't working yet
-
Intertrac?
- Will have to see.
- @Chris will provide a multi-story example
-
Jason
- optimistic? suspicious?
-
Chris: very scared this morning. missing features?
- e.g. end of sprint and transitioning tickets
- but seems to work nicely.
- biggest problems: resolution of hierarchy
- commit message is very powerful
- missing: estimates are still not that great
- graphs are per sprint
-
Overview
Generating sprint / Review of workplan pages/ estimations
- NB: Jean-Marie will miss next week
- Graffle: won't spend too much time since we will be trying agilo
-
Estimates/Actual times
- Jean-Marie reviewed all the pages
- We had agreed to do it, but it wasn't done
- Still confused about what a day is? We need to clairify 'what a day' is.
- difficult to know if we were changing estimates after the fact (have to check history)
- Web: 33 days? Ola: Calendar days. Ideal day doesn't work.
-
Andrew: How to schedule things that take multiple people? (mtgs with 5 people)
- Brian: e.g. has someone else updated for you? * We should only have one person responsible for updating the page
- Chris: none of this is designed well for group work
- Andrew: how do we tell if a person is overloaded if someone else allocates?
- Jason: nothing will substitute for just talking to one another
-
Day == 6 hours. Decision. (Need a symbol :) )
- Ola: vote not for 6 hours a day
-
Jason: What do we want to measure?
- "When will Ola be done?" (in calendar days)
-
Ideal v. Absolute days
- Agree to 6 hours / day and see how the system works with that value
- We have to be fairly militant about excluding days we don't work
- 4 ideal days / week is what we agreed to in our internal survey
Forums/Emails/QA
- Forums: all done. Some self answers
- QA: 200+ feedbacks.
- @Cleaning up test system
- @Cleaning up the multiple lines from single import
- No one hits the "upload" button
-
Mostly importer related
- @Chris & Brian review
Enumerations
- Heads up: Chris & Melissa have been working with enums in BF
- Been a problem. @Need to have a meeting on coding up enums. Chris emails nitpick
- Goal: consistency across our tools/libraries
Action Items:
- Chris: send a direct follow up for BF data needed
- Josh, Ola, Carlos: discuss django app
- Donald: write to ome-devel
- Chris: add block import ticket for BF
- Andrew: send a reminder to everyone on nitpick about FAQ changes needed
- Andrew: look at the FAQ stats as well.
- Everyone: at end of iteration, FAQ/samples work
- Will: Go see Tom about his gel imports
- Everyone: look at the commit methods and make any comments
- Everyone: continue using trac, next Thursday we will be using a 'real sprint'.
- Everyone look at the examples in the commit methods.
- Chris: put up the admin stuff needed for sprint svn
- Everyone will then need to change their commit method
- Everyone: agree that 'one day = 6 working hours'
- Chris & Brain: Go through feedback QA for importer and clean up tickets.
- Everyone please remember to keep your job pages up to date!