Topic on Talk:WMF product development process

What I'm missing is: how are we measuring progress and quality, what do we do with interruptions, how do we deal with the fact that we are understaffed, etc etc. How do we deal with the fact that each product is 10000 pieces all being in another phase of this defined process ?

And how do we then COUPLE these events to the development process. Because otherwise it will be very difficult to 'recognize' these phases and then they aren't really useful.

Are we gonna label each ticket with a phase ? Will we have 'process' workboards per product with these phases ? (And then the team boards being a the agile board ?). I'm just looking for practical implementations that will help me recognize this process.

Thank you for this, @TheDJ. Very relevant points, and ones that I've been thinking about. @WMoran (WMF) and I will be in an office hours on Thursday, and I think your questions, and others, would be good things to address.

I also agree these are all valid points. This again is a high level draft that is being informed and evolved through the work with  SPDPP (Software Product Development Process Proposal). That more detailed process will have more concrete examples.

What about something like this:

• Every software project going through this process has a project page in mediawiki.org
• Every project page should have a subpage for every stage that project is going through, containing the checklist for that stage, any additional notes from the team, and a discussion page. Small projects and big feature may opt for a single subpage for all stages.
• If a project just started, only an /Understand subpage/section is expected. If a project is about to enter the Release stage, all the previous subpages/sections will be expected.
• The main project pages has an infobox with the standard project information, including the status (OK, IN PROGRESS...) for the relevant stages.

I don't think we need to bring much overhead to Phabricator (as in labelling all tickets). However, at least for big projects and complex features it might be useful to have tasks like "Product X to enter Release stage" in order to identify the main blocking tasks. To be discussed.