http://mfeldstein.com/understanding-the-sakai-product-council/ What We Are Learning About Online Learning...Online Sun, 05 Feb 2012 04:42:18 +0000 hourly 1 http://mfeldstein.com/understanding-the-sakai-product-council/#comment-1715 First Product Post | Cappuccino Espresso Maker Sun, 21 Mar 2010 19:16:07 +0000 http://mfeldstein.com/?p=1321#comment-1715 [...] Understanding the Sakai Product Council [...] [...] Understanding the Sakai Product Council [...]

]]> http://mfeldstein.com/understanding-the-sakai-product-council/#comment-1714 Michael Feldstein Mon, 15 Mar 2010 12:19:01 +0000 http://mfeldstein.com/?p=1321#comment-1714 I'm not sure if I agree that dialogue with the release management and maintenance teams is <strong>more</strong> important than with the project owners, but I agree that it's pretty important. And since I don't recall the topic of how all these groups need to work together coming up except in the most brief and superficial ways, we definitely need to talk about this. I’m not sure if I agree that dialogue with the release management and maintenance teams is more important than with the project owners, but I agree that it’s pretty important. And since I don’t recall the topic of how all these groups need to work together coming up except in the most brief and superficial ways, we definitely need to talk about this.

]]> http://mfeldstein.com/understanding-the-sakai-product-council/#comment-1713 DavidH Mon, 15 Mar 2010 08:03:38 +0000 http://mfeldstein.com/?p=1321#comment-1713 Michael, thanks for the reflections from the PC point of view. What I find missing from both this and Nate's report is evaluating the PC relation to other groups (RM, MT etc). I think reflection and dialogue here is frankly more important that with project owners. This should focus both on what the PC has done (tool promotions) but also areas where the PC can halp and support these initiatives - for instance by advising on areas of the prduct like browser version and database support Michael, thanks for the reflections from the PC point of view. What I find missing from both this and Nate’s report is evaluating the PC relation to other groups (RM, MT etc). I think reflection and dialogue here is frankly more important that with project owners. This should focus both on what the PC has done (tool promotions) but also areas where the PC can halp and support these initiatives – for instance by advising on areas of the prduct like browser version and database support

]]>