2011-02-01 Tuesday Meeting
Attending: Brian, Ola, Will, Jean-Marie, Chris, Colin, Andrew, Melissa, Josh, Curtis, Jason, Carlos, Scott
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)
- Everyone: review/update "4.3+ Priorities" i.e. list of "big things" for next sprint review (reminder - added to agenda for Thursday)
- Will: forward to list Jerome emails.
- Ola: Work with Scott on web unification docs.
- Donald: Talk to Jos about getting access (1/2 Doz. test accounts for Angus' lab)
- Everyone: look at download pages from chris.
-
Everyone: week from Thursday, have "Bug:" tickets below 10!
- Move them to stories with estimates
- Or do the work.
- Everyone: Sort out bugs that are too long / mislabled
- Brian: Help forum "Scripting movie error'" (see above)
- Jason: respond to forum "beginners and baby beginners"
- Andrew: Send Jason some floorplan ideas
Scott's presentation (via web) (45 mins)
Any other business (<5 mins)
In Attendance
Brian, Ola, Will, Jean-Marie, Chris, Colin, Andrew, Melissa, Josh, Curtis, Jason, Carlos, Scott
Notes
Matters Arising (<10 mins)
-
Everyone: review/update "4.3+ Priorities" i.e. list of "big things" for next sprint review (reminder - added to agenda for Thursday)
- Holding off this conversation for Thursday on the End of the Sprint
- Will: forward to list Jerome emails. - Done
- Ola: Work with Scott on web unification docs. - Done
-
Donald: Talk to Jos about getting access (1/2 Doz. test accounts for Angus' lab) - Pendng
- Jos is away
- Working on gretzky
-
Everyone: look at download pages from chris. - Pending
- Eveyrone still need to check this
-
Everyone: week from Thursday, have "Bug:" tickets below 10! - Ongoing
- Move them to stories with estimates
- Or do the work.
- Everyone: Sort out bugs that are too long / mislabled
- Brian: Help forum "Scripting movie error'" - Done
- Jason: respond to forum "beginners and baby beginners" - Jason is in conversation so Ongoing
- Andrew: Send Jason some floorplan ideas -
-
Everyone: review/update "4.3+ Priorities" i.e. list of "big things" for next sprint review (reminder - added to agenda for Thursday)
Scott's presentation (via web) (45 mins)
- Question from users: "why multiple clients" (from Paris, etc)
- Jean-Marie: re-added some code for importing from inside insight
- Trying to put a process in place for usability loopback
- Goal is to better record and respond to user feedback
- Jason: feedback (in tickets) needs to be clearly written.
- Jean-Marie: that was mostly an early-stage of feedback. Improving.
- Will: may get some good feedback from M. show video first.
-
Jean-Marie: finer granularity of tickets
- cleaner, simpler, more obvious for users
- feel more comfortable to get new versions in front of users.
- easier to manage as a pair (Jean-Marie + Scott)
-
Jason
- intense turn around on a feature in a 2 week sprint?
- developer+functionality+user with some Scott glue?
- Jean-Marie: other bits (model, etc.) can be involved
- when it's time to get feedback, then enter into intense cycle
- took 1/2 iteration too much
- but if we say, screenshot or movie at end of iteration, will help
-
Jason: quick questions
- what's the necessity or the role for the usability role?
-
Jean-Marie: few benefits
- Another view other than the developers'
- Having someone to run the sessions without dev present
- Getting a large pool of users
- Jason: key is physical/highly-interactive access to users
- Jean-Marie: will need a similar phase when we get back to scripting
- Can't demand too much time from users
-
Guidelines:
- "short meetings", "immediate feedback", "small/focus tasks",...
- don't implement everything right away
-
Chris: big issue
- we shouldn't be developing new features without strong feedback loop
- i.e. look for the best people when working on new features.
- Brian: but we got this far without the process
- Jean-Marie: probably didn't take enough screenshots as we were going.
-
Chris: would be interesting to see how this applies to prioritization of features
- Brian: same process to documentation. What do you want to read?
- Scott: also can be used among developers
- Chris: should be careful to not be influencing too heavily the workflow
Any other business (<5 mins)
-
Chris: Permissions/data visibility thread had some interesting comments
- Will, Carlos, Jason, Ola, Chris
- "I'm an admin, I want to see everyone's data"
- Jay has a similar requirement, but for collaboration
- Permissions II for 4.3?
- Jean-Marie: not many big images labs since OMERO hasn't worked for them previously
- Josh: if we go down the permissions route again, it may affect Big Images timelines
-
Ola: Google search engine does not find our website
- "omero demo server" turns up little, or the dead blog
- Chris: anyone who uses google docs gets trash results
- Ola: Finding OMERO.blog (which is horribly out of date)
- Andrew: Plone fragements urls a lot
- Brian: all for consolidation.
-
Chris: Permissions/data visibility thread had some interesting comments
Actions
- Jean-Marie & Scott: put together guidelines for the team (see above)
- Andrew: move big ticket review to the next Thursday
- Andrew: push "pending" tasks
- Everyone: Give feedback to Chris about omero/downloads page
-
Everyone: Look over bugs! Lots of old ones tha need to be fixed/remove/cleaned up
- Anything over 2 weeks should be handled.
- Everyone: opinions on blog for Thursday. Decision will be made.