I've never felt it was "holy property". In fact, when people
reorganize the schedule wall with further time refinements, it always
seem to have been appreciated in the Open Spaces I've been too. And
further, removing the events that are over certainly makes it easier to
find sessions. I'm also finding it quite a bit nicer when I only need to
look at sessions that are up coming on the schedule wall - and not the
full history. I've never minded things the way they were before - like
you say - it works well. But this change has been quite a refreshing
change and the rest of the participants seem to be appreciating it as well.
Harold
On 10/12/10 6:24 AM, Michael M Pannwitz wrote:
I use "deadline for reports" notes in the schedule, at the newswall
and at the desk where reports are deposited... and I announce the
deadline in my intro and, in multiple day os events, in the morning
news of the second day... in the 170+ events I have been involved in,
this has always worked well.
I would never mess with the bulletin board, seems to me to be the holy
property of the participants (at the end of the event we take it down
and include it in the archives of the event alongside other
visualized material, the archives being handed over to the sponsor of
the event).
Greetings from Berlin
mmp
Shay Ben Yosef schrieb:
Thanks Harold,
Great idea. I'm preferring 'Did'nt arrived yet' instead of 'Not done'
thanks
Shay
2010/10/12 Harold Shinsato <har...@shinsato.com>
I'm writing from San Francisco after the first day of Agile Open
Northern
California.
In case you aren't familiar with Agile - it is a revolutionary and now
quite popular software development philosophy that also comes with a
number
of practices. Open Space Technology has quite a history with the Agile
movement, especially for some of the earliest Agile conferences - up
through
today.
Today I've seen one of the most effective methods ever for encouraging
prompt session reports. The approach is loaned from the Japanese
"Kanban"
which just means visual card. Kanban is now being used in software
development to help track what's planned and what's done with visual
cards
posted on a wall.
At Agile Open NorCal - once the sessions were completed, the paper
used to
announce it was are removed from the agenda wall and moved to
another wall
where there were two slots. The first is "not done", or the sessions
for
which notes were not produced. Once notes were completed, the
session page
would be moved to the "done" slot. I was impressed how it seemed to
speed up
people finishing the notes - just by having quick visibility about what
sessions had completed documentation, and which didn't.
Any thoughts about this? It seems quite easy to do.
--
Harold Shinsato
har...@shinsato.com
http://shinsato.com
twitter: @hajush <http://twitter.com/hajush>
* * ==========================================================
osl...@listserv.boisestate.edu ------------------------------ To
subscribe, unsubscribe, change your options, view the archives of
osl...@listserv.boisestate.edu:
http://listserv.boisestate.edu/archives/oslist.html To learn about
OpenSpaceEmailLists and OSLIST FAQs:
http://www.openspaceworld.org/oslist
*
*
==========================================================
osl...@listserv.boisestate.edu
------------------------------
To subscribe, unsubscribe, change your options,
view the archives of osl...@listserv.boisestate.edu:
http://listserv.boisestate.edu/archives/oslist.html
To learn about OpenSpaceEmailLists and OSLIST FAQs:
http://www.openspaceworld.org/oslist
