Talk:WMF product development process/Proposal

Community Engagement
Thank you for creating this :) CLs have a goal to build out a toolkit that support's communities' and product teams in collaboration with one another as well; not sure how it can work within this page; if not, we'll figure something out. -Rdicerb (WMF) (talk) 22:52, 30 September 2015 (UTC)

Flow?
Can we get this talk page converted to Flow? Apparently the process to do so is to file a phab ticket in the Flow project. --KSmith (WMF) (talk) 20:13, 9 October 2015 (UTC)

"Timeboxing is a prioritization technique"
I'm not sure I would call it a prioritization technique. To me, it's more of a release management technique. The tasks have already been prioritized before they went into the timebox (or feature box). It's not a huge deal, but as I was reading I was interrupted by a statement I disagree with. Maybe the phrase could just be removed, and describe what timboxing is, rather than starting with what type of thing it is (or isn't). --KSmith (WMF) (talk) 20:21, 9 October 2015 (UTC)

Product Lifecycle
I would like this section to come across with a bit stronger agile slant, and to look less like it is promoting waterfall. Even with (or especially with) a 2-year project, I would definitely want to see multiple releases. Those releases might only go to limited (and/or internal) audiences, but avoiding a "big bang" release is a core part of agile. This section as written doesn't preclude an iterative release approach, but it should probably encourage one. I think it's important to have it in this section, rather than waiting for the "milestones" section.--KSmith (WMF) (talk) 20:33, 9 October 2015 (UTC)

Milestone Bundles
This didn't make sense to me at first, because I view a milestone as (by definition) entirely specific to a particular product at a particular time. I think this is saying that a class of milestone can be turned into a form of template, and that milestone template can be reused. I'm not sure what a "bundle" is here. --KSmith (WMF) (talk) 20:33, 9 October 2015 (UTC)

Milestones and Scrum
Milestones are not an inherent part of Scrum, and to a small degree, run counter to its main philosophy. I would be happy if "milestones are used in the product backlog" changed to "milestones can be used in the product backlog", and then adding a sentence such as "Milestones in the product backlog represent best thinking at a given time, and are likely to shift (often dramatically) over time." --KSmith (WMF) (talk) 20:33, 9 October 2015 (UTC)

Milestones and Kanban
I view milestones as being equally compatible with Kanban (for some fairly conventional definition of Kanban) and with Scrum. --KSmith (WMF) (talk) 20:34, 9 October 2015 (UTC)