Product Council Review

classic Classic list List threaded Threaded
4 messages Options
Lois Brooks-2 Lois Brooks-2
Reply | Threaded
Open this post in threaded view
|

Product Council Review

Dear colleagues,

A year ago when the Product Council was formed, the Board asked that a  
review be scheduled coincident with the Sakai 2.7 release (about a  
year away).  I'm writing to start the review process.

The goal of this process is to review the premise, structure and  
actions of the Product Council as they relate to management of Sakai  
software development and the needs of the community.  This isn't a  
report card type of activity, but rather, a reflection on how best to  
serve the community needs.  The review participants will include all  
members of the Product Council as well as a few community members and  
Foundation staff.

A draft of the review process, participants and areas of assessment  
can be found at http://confluence.sakaiproject.org/display/MGT/Product+Council+Review 
   Your first task is to review the document, particularly the  
assessment questions.   We will bring the document from draft to final  
form after you've had a chance to review and comment.  Comments back  
to this list are fine, or you can bring them to the kickoff meeting  
next week.

We will have our first meeting of the review committee during next  
week's Product Council call.  Logistics follow.  External reviewers --  
it made sense to use an existing meeting time, so please do try to  
join the call if you can.  If you're not available let me know and  
I'll be sure to get your feedback incorporated into the discussion.

The next Product Council meeting is scheduled for Wednesday, May 5,  
6pm GMT/2pmEDT/11amPDT

Phone number: +1 (812) 856-7060
Internet: 156.56.240.9
Room code: 22348#
Password: 72524#


  - Lois




_______________________________________________
management mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/management

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
John Norman John Norman
Reply | Threaded
Open this post in threaded view
|

Re: Product Council Review

My observation would be that the questions point more to a review of the Product Council charter than a review of the Product Council per se.

I had anticipated something more focussed on the intended beneficiaries of the work of the Product Council with questions like:
When you heard about the product council, what did you hope the product council might achieve?
How close to your hopes did the product council charter come (have you read it)?
What do you see as the successes of the product council so far? What are the disappointments?
What would you change?
Have we got the membership right?
What are the critical functions that the community needs in the context of managing the product and what is missing from current activity/processes?

John

On 28 Apr 2010, at 21:38, Lois Brooks wrote:

> Dear colleagues,
>
> A year ago when the Product Council was formed, the Board asked that a  
> review be scheduled coincident with the Sakai 2.7 release (about a  
> year away).  I'm writing to start the review process.
>
> The goal of this process is to review the premise, structure and  
> actions of the Product Council as they relate to management of Sakai  
> software development and the needs of the community.  This isn't a  
> report card type of activity, but rather, a reflection on how best to  
> serve the community needs.  The review participants will include all  
> members of the Product Council as well as a few community members and  
> Foundation staff.
>
> A draft of the review process, participants and areas of assessment  
> can be found at http://confluence.sakaiproject.org/display/MGT/Product+Council+Review 
>   Your first task is to review the document, particularly the  
> assessment questions.   We will bring the document from draft to final  
> form after you've had a chance to review and comment.  Comments back  
> to this list are fine, or you can bring them to the kickoff meeting  
> next week.
>
> We will have our first meeting of the review committee during next  
> week's Product Council call.  Logistics follow.  External reviewers --  
> it made sense to use an existing meeting time, so please do try to  
> join the call if you can.  If you're not available let me know and  
> I'll be sure to get your feedback incorporated into the discussion.
>
> The next Product Council meeting is scheduled for Wednesday, May 5,  
> 6pm GMT/2pmEDT/11amPDT
>
> Phone number: +1 (812) 856-7060
> Internet: 156.56.240.9
> Room code: 22348#
> Password: 72524#
>
>
>  - Lois
>
>
>
>
> _______________________________________________
> management mailing list
> [hidden email]
> http://collab.sakaiproject.org/mailman/listinfo/management
>
> TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"

_______________________________________________
management mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/management

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Clay Fenlason Clay Fenlason
Reply | Threaded
Open this post in threaded view
|

Re: Product Council Review

I take part of John's point to be that a more outcomes-oriented
emphasis would be more likely to get to the real issues. It also leads
me to think that part of what we want to look at is in fact not the
Product Council per se, but the state of the community functions the
PC was trying to speak to, and we'll be better off looking at the
situation in those terms before taking up the matter of whether and
how far the product council (or a product council of a different shape
and activity) goes toward addressing these issues.

~Clay

On Thu, Apr 29, 2010 at 5:17 AM, John Norman <[hidden email]> wrote:

> My observation would be that the questions point more to a review of the Product Council charter than a review of the Product Council per se.
>
> I had anticipated something more focussed on the intended beneficiaries of the work of the Product Council with questions like:
> When you heard about the product council, what did you hope the product council might achieve?
> How close to your hopes did the product council charter come (have you read it)?
> What do you see as the successes of the product council so far? What are the disappointments?
> What would you change?
> Have we got the membership right?
> What are the critical functions that the community needs in the context of managing the product and what is missing from current activity/processes?
>
> John
>
> On 28 Apr 2010, at 21:38, Lois Brooks wrote:
>
>> Dear colleagues,
>>
>> A year ago when the Product Council was formed, the Board asked that a
>> review be scheduled coincident with the Sakai 2.7 release (about a
>> year away).  I'm writing to start the review process.
>>
>> The goal of this process is to review the premise, structure and
>> actions of the Product Council as they relate to management of Sakai
>> software development and the needs of the community.  This isn't a
>> report card type of activity, but rather, a reflection on how best to
>> serve the community needs.  The review participants will include all
>> members of the Product Council as well as a few community members and
>> Foundation staff.
>>
>> A draft of the review process, participants and areas of assessment
>> can be found at http://confluence.sakaiproject.org/display/MGT/Product+Council+Review
>>   Your first task is to review the document, particularly the
>> assessment questions.   We will bring the document from draft to final
>> form after you've had a chance to review and comment.  Comments back
>> to this list are fine, or you can bring them to the kickoff meeting
>> next week.
>>
>> We will have our first meeting of the review committee during next
>> week's Product Council call.  Logistics follow.  External reviewers --
>> it made sense to use an existing meeting time, so please do try to
>> join the call if you can.  If you're not available let me know and
>> I'll be sure to get your feedback incorporated into the discussion.
>>
>> The next Product Council meeting is scheduled for Wednesday, May 5,
>> 6pm GMT/2pmEDT/11amPDT
>>
>> Phone number: +1 (812) 856-7060
>> Internet: 156.56.240.9
>> Room code: 22348#
>> Password: 72524#
>>
>>
>>  - Lois
>>
>>
>>
>>
>> _______________________________________________
>> management mailing list
>> [hidden email]
>> http://collab.sakaiproject.org/mailman/listinfo/management
>>
>> TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
>
> _______________________________________________
> management mailing list
> [hidden email]
> http://collab.sakaiproject.org/mailman/listinfo/management
>
> TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
>
_______________________________________________
management mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/management

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"
Lois Brooks-2 Lois Brooks-2
Reply | Threaded
Open this post in threaded view
|

Re: Product Council Review

Clay,

This is just the perspective that the community members participating  
in the review will bring, so I believe we can concurrently evaluate  
community needs and the structure and deliverables of the Product  
Council.  John's suggestions point to a gap analysis approach, which  
was inherent in the outcome, a set of recommendations, but not  
explicitly stated.  I'll update the phrasing to see if I can capture  
both your suggestions.

One note to all participants -- please don't read either endorsement  
or indictment of the Product Council into my questions and comments.  
I'm really quite neutral and uninformed about the Council's activities  
over the past year, though will undoubtedly be well informed by the  
time the review is complete.   For now, we're sharpening the framework  
that will let us get a useful assessment done in an objective, and (I  
hope) efficient way.

   - Lois




On Apr 29, 2010, at 6:36 AM, Clay Fenlason wrote:

I take part of John's point to be that a more outcomes-oriented
emphasis would be more likely to get to the real issues. It also leads
me to think that part of what we want to look at is in fact not the
Product Council per se, but the state of the community functions the
PC was trying to speak to, and we'll be better off looking at the
situation in those terms before taking up the matter of whether and
how far the product council (or a product council of a different shape
and activity) goes toward addressing these issues.

~Clay

On Thu, Apr 29, 2010 at 5:17 AM, John Norman <[hidden email]>  
wrote:

> My observation would be that the questions point more to a review of  
> the Product Council charter than a review of the Product Council per  
> se.
>
> I had anticipated something more focussed on the intended  
> beneficiaries of the work of the Product Council with questions like:
> When you heard about the product council, what did you hope the  
> product council might achieve?
> How close to your hopes did the product council charter come (have  
> you read it)?
> What do you see as the successes of the product council so far? What  
> are the disappointments?
> What would you change?
> Have we got the membership right?
> What are the critical functions that the community needs in the  
> context of managing the product and what is missing from current  
> activity/processes?
>
> John
>
> On 28 Apr 2010, at 21:38, Lois Brooks wrote:
>
>> Dear colleagues,
>>
>> A year ago when the Product Council was formed, the Board asked  
>> that a
>> review be scheduled coincident with the Sakai 2.7 release (about a
>> year away).  I'm writing to start the review process.
>>
>> The goal of this process is to review the premise, structure and
>> actions of the Product Council as they relate to management of Sakai
>> software development and the needs of the community.  This isn't a
>> report card type of activity, but rather, a reflection on how best to
>> serve the community needs.  The review participants will include all
>> members of the Product Council as well as a few community members and
>> Foundation staff.
>>
>> A draft of the review process, participants and areas of assessment
>> can be found at http://confluence.sakaiproject.org/display/MGT/Product+Council+Review
>>   Your first task is to review the document, particularly the
>> assessment questions.   We will bring the document from draft to  
>> final
>> form after you've had a chance to review and comment.  Comments back
>> to this list are fine, or you can bring them to the kickoff meeting
>> next week.
>>
>> We will have our first meeting of the review committee during next
>> week's Product Council call.  Logistics follow.  External reviewers  
>> --
>> it made sense to use an existing meeting time, so please do try to
>> join the call if you can.  If you're not available let me know and
>> I'll be sure to get your feedback incorporated into the discussion.
>>
>> The next Product Council meeting is scheduled for Wednesday, May 5,
>> 6pm GMT/2pmEDT/11amPDT
>>
>> Phone number: +1 (812) 856-7060
>> Internet: 156.56.240.9
>> Room code: 22348#
>> Password: 72524#
>>
>>
>>  - Lois
>>
>>
>>
>>
>> _______________________________________________
>> management mailing list
>> [hidden email]
>> http://collab.sakaiproject.org/mailman/listinfo/management
>>
>> TO UNSUBSCRIBE: send email to [hidden email]
>>  with a subject of "unsubscribe"
>
> _______________________________________________
> management mailing list
> [hidden email]
> http://collab.sakaiproject.org/mailman/listinfo/management
>
> TO UNSUBSCRIBE: send email to [hidden email]
>  with a subject of "unsubscribe"
>
_______________________________________________
management mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/management

TO UNSUBSCRIBE: send email to [hidden email]
  with a subject of "unsubscribe"

_______________________________________________
management mailing list
[hidden email]
http://collab.sakaiproject.org/mailman/listinfo/management

TO UNSUBSCRIBE: send email to [hidden email] with a subject of "unsubscribe"