Scheduling our regular UX team iteration plan meetings

Allison Bloodworth abloodworth at berkeley.edu
Wed Jan 30 15:43:17 UTC 2008


This would be a bi-weekly meeting. +1

On Jan 30, 2008, at 6:25 AM, Mike Elledge wrote:

> Will this be weekly, or bi-weekly? +1, in either case.
>
> Mike
>
> Daphne Ogle wrote:
>> Does anyone have concerns with our iterations beginning on Tuesdays?
>>
>> If not, I  say we go with Allison's suggestions and schedule our  
>> planning meeting for Tuesday 10:00 am - noon PST / 1:00 pm - 3:00  
>> pm EST.
>> Please respond with +1 or -1 (with alternative suggestions) by end  
>> of day Thursday so we can firm this up and be ready for next week.
>>
>> Thanks,
>>
>> Daphne
>>
>> On Jan 28, 2008, at 10:45 PM, Allison Bloodworth wrote:
>>
>>> Do iterations need to start on Mondays? If not, I'm a fan of  
>>> starting the iterations and doing the planning on Tuesdays. We  
>>> could also consider doing the planning Mondays and just moving it  
>>> to Tuesdays when there is a holiday if it's important that  
>>> iterations start on Mondays.
>>> Allison
>>>
>>> On Jan 25, 2008, at 11:06 AM, Barbara Glover wrote:
>>>
>>>> Hi Daphne
>>>> While I'm open for any day, I know we did have regular meetings  
>>>> in the fall on Tuesdays.  That is earlier in the week and  
>>>> iteration as well as not being a Monday.  I'll throw that out as  
>>>> another possibility.
>>>>
>>>> Barbara
>>>>
>>>> On 25-Jan-08, at 1:58 PM, Daphne Ogle wrote:
>>>>
>>>>> One thing I'm wondering about is the timing in regards to the  
>>>>> start of an iteration.  Our iterations start on a Monday and  
>>>>> end 2 weeks later on Friday.  Does it make more sense to meet  
>>>>> closer to the end of an iteration or right at the beginning?   
>>>>> I'm thinking if we meet Wednesday we'll still have 2 to 3 days  
>>>>> of work left in an iteration.  Does that matter?
>>>>>
>>>>> We talked about moving forward that we'd like to have the  
>>>>> project leads do the work of breaking out the tasks for and  
>>>>> iteration and move any forward from the previous iteration that  
>>>>> didn't get complete prior to the planning session.  If that's  
>>>>> the case we could meet at the start of the iteration (I know  
>>>>> Monday's are hard so it's a tradeoff) and be ready to hit the  
>>>>> ground running.
>>>>>
>>>>> The other question I have is how long should the meeting be?  I  
>>>>> suggest we schedule 2 hours and just use what we need.
>>>>> Thoughts?  Toronto folks -- when do you have your internal  
>>>>> planning meetings in relation to your iteration schedule?
>>>>>
>>>>> -Daphne
>>>>>
>>>>> On Jan 24, 2008, at 1:56 PM, Colin Clark wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Fair enough. So does Wednesday at 12:30 pm PST/3:30 pm EST  
>>>>>> work for everyone? This seems like it might dig into lunch  
>>>>>> time on the west coast. Does this work, or are there other  
>>>>>> suggestions?
>>>>>>
>>>>>> Colin
>>>>>>
>>>>>> On 24-Jan-08, at 3:17 PM, Allison Bloodworth wrote:
>>>>>>
>>>>>>> I think the no Fridays request is a good idea, and we might  
>>>>>>> even want to avoid Mondays due to them often being. The one  
>>>>>>> problem I see with scheduling the meetings up right next to  
>>>>>>> each other is we've been trying to start doing a bit more  
>>>>>>> preparation for the Sakai UI meeting (which will I think  
>>>>>>> every other week will be dedicated to design patterns, and  
>>>>>>> include other members of the Open Source Design Pattern  
>>>>>>> library community), and this might make it a bit harder to do  
>>>>>>> so. My preference would be to have a little time between the  
>>>>>>> meetings, perhaps just a half hour? That timing could  
>>>>>>> actually be perfect since folks would all be reminded we have  
>>>>>>> a Sakai UI meeting coming up momentarily which could jog  
>>>>>>> their memory to do any needed prep work. Otherwise, there are  
>>>>>>> usually emails to be read. :)
>>>>>>
>>>>>> ---
>>>>>> Colin Clark
>>>>>> Technical Lead, Fluid Project
>>>>>> Adaptive Technology Resource Centre, University of Toronto
>>>>>> http://fluidproject.org
>>>>>>
>>>>>
>>>>> Daphne Ogle
>>>>> Senior Interaction Designer
>>>>> University of California, Berkeley
>>>>> Educational Technology Services
>>>>> daphne at media.berkeley.edu <mailto:daphne at media.berkeley.edu>
>>>>> cell (510)847-0308
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>> Allison Bloodworth
>>> Senior User Interaction Designer
>>> Educational Technology Services
>>> University of California, Berkeley
>>> (415) 377-8243
>>> abloodworth at berkeley.edu <mailto:abloodworth at berkeley.edu>
>>>
>>>
>>>
>>>
>>
>> Daphne Ogle
>> Senior Interaction Designer
>> University of California, Berkeley
>> Educational Technology Services
>> daphne at media.berkeley.edu <mailto:daphne at media.berkeley.edu>
>> cell (510)847-0308
>>
>>
>>
>> --------------------------------------------------------------------- 
>> ---
>>
>> _______________________________________________
>> fluid-work mailing list
>> fluid-work at fluidproject.org
>> http://fluidproject.org/mailman/listinfo/fluid-work
>>

Allison Bloodworth
Senior User Interaction Designer
Educational Technology Services
University of California, Berkeley
(415) 377-8243
abloodworth at berkeley.edu




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080130/06113385/attachment.html>


More information about the fluid-work mailing list