Talk:Community Engagement (Product)/Collaboration process/Draft

Early stage draft
This might look better in table format. Considering visualization options; ideas welcome. --Rdicerb (WMF) (talk) 07:00, 26 January 2015 (UTC)

Exit path
Perhaps it's supposed to be implied, or an oversight, but the process does not appear to cover any exit path for cancelling a project after problems are identified. The draft indicates that projects can only be "kicked back to an earlier stage" for continued development when issues are raised. I hope you'll forgive me for noting that this is a painfully accurate reminder of the WMF's existing Community Engagement / Collaboration Process. Alsee (talk) 08:43, 7 May 2015 (UTC)
 * Thank you, Alsee, for raising this - it's something we should be asking around towards. Kicking back a project to an earlier stage generally indicates a rethinking, recalibration, redesign of the product against the problems it intends to resolve - problems which, when the product in development is cancelled, are still oftentimes a problem. I think it's more likely that a product in development would be kicked back rather than canceled, but it's appropriate that it be considered.
 * Something else that I've also been thinking: what is an initiative or product sunsetting process when WMF or communities turn off a product that has immense code rot, is otherwise unused, or some other reason to remove a particular feature (usually *not* one in development, usually a product that is no longer being supported). We do not seem to have one. I also think that how we (when I say "we", I mean the Foundation product team in collaboration with communities) make decisions initially to implement something (deciding which projects to do and when to do them) is in need of discussion. I've raised this a bit internally, and think that when the new audience-based product verticals are more settled into their individual product development processes that a there will be much more clarity around it.
 * I created this particular page in time for the MediaWiki Developer's Summit in SF in January (you can see how the first image is actually from the Product Development process draft, and then my team moved to Community Engagement Dept then Product/Engineering was reorg'ed - lots of change in a couple of months. CE(P) process supports product development process so that communities are engaged and informed in appropriate ways, so I'm asking what these new product verticals need so we can rebuild around that. Cheers, -Rdicerb (WMF) (talk) 22:30, 11 May 2015 (UTC)