[Owasp-board] Communication Methods with Operations Team & Board
sarah.baso at owasp.org
Fri Nov 2 21:00:38 UTC 2012
Thanks for summarizing all of this Michael. Kate and I will work with the
other staff members to have our first "go" at this new method next week
Thursday. When we have the doc created we will send the link to the board
to kick things off. Obviously we may have to tweak the logistics and format
of this a bit to get it right, but I am optimistic that this will be a
On Thu, Nov 1, 2012 at 4:54 PM, Michael Coates <michael.coates at owasp.org>wrote:
> One thing we've struggled with over the past several months is an
> effective feedback channel for near-real time issues with the operations
> Current Process
> - Monthly board meetings
> - Impromptu emails to solicit feedback or opinions
> - Board meetings are monthly and packed already
> - Some topics just need general feedback, not formal time at a board
> - We all get lots of owasp mail and informal emails for feedback often get
> I chatted with Kate, Sarah and Seba and we have the following proposal.
> Sure, it seems a little formal, but the informal email approach is not
> * Operations team sends an email to the board each week (Thursday
> afternoon) with a link to a wiki page.
> * The wiki page contains items they'd like us to review. This could be
> asking for our feedback on ideas, exploring new issues, whatever they want
> to add
> * Each board member is required to review this page and provide one of the
> following by Monday.
> 1) Actual feedback
> 2) Acknowledgement they've read the doc by adding their name and stating
> "no feedback" (note: this implies agreement with anything stated on the doc)
> 3) Ignoring the email or not performing step 2 is not a valid option
> We're going to give this a try starting Thursday November 8th.
> Lastly, we should also use this as a bidirectional communication point.
> Sure, we love the idea of just calling up the operations staff or sending
> emails at all hours of the day. But, the reality is they don't have extra
> time. So unless our ad-hoc request can upstage our quarterly goals, we
> should think hard about interrupting their day. This proposed
> communication method allows them to capture the request and prioritize it
> appropriately (also, everyone can see it)
> Let's give this a shot and evaluate it's effectiveness. I've laid out the
> problem statement and goals above, so if this isn't the right solution then
> please consider the overall objectives as we look at other options.
> Michael Coates | OWASP | @_mwc
sarah.baso at owasp.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Owasp-board