Re: [oniro-wg] Roadmap: work on the proposal for oniro-core (goofy)

[Davide Ricci <davide.ricci@xxxxxxxxxx>]

100% agreed.

We are following a very lean process re roadmapping and requirement gathering / analysis and prioritization in general.

Such process naturally leads to the yearly roadmap - but with all that happened this year we just did not follow it.

The process goes as follows:

1. identified members / people can file requirements at any time
2. requirements that are filed follow a specific template in order to capture all necessary information that allow to assess priority and form an opinion re effort vs market relevance against the project KPIs
3. requirements are filed in a "wish list" bucket (gitlab backlog)
4. bi-weekly, individuals mentioned at point number 1 meet to review requirements in wish list, ask question, clean up, etc with the goal of moving requirements from wish list to product backlog (relevant requirement, no immediate business impact) or the release backlog (relevant and immediately highly impactful)
5. changes to release backlog are to be reviewed at the SC and approved since they have impact on existing release commitments and / or might require further staffing
6. once / year as the release in development comes to fruition, requirements in the product backlog are then moved into the next release backlog and further planning / estimate takes place

We are now (Amit and I) working on 6 - w/o having followed the steps from 1 to 5 in the past 3 / 4 months - hence the restart.

We could meet to discuss 1 - 6 and how to implement given the committees available to us (i.e. SC and its role in this matter), identifying the roles / people who can file rqmnts and the right place for periodic rqmnts review.

Sounds good?

I am happy to be on point and work you on the process while I work with amit on the content - Seba is trained in the process above and can certainly be valuable as well, yet I am happy to personally follow this initial phase of defining how rqmnts are captured, managed,...and live through their lifecycle as well as I will be happy to be on point to call the periodic rqmnts review meeetings.

Do we want to get together on Wed morning to elaborate on the above re: the process?

Thanks
D

-----Original Message-----
From: Agustín Benito Bethencourt [mailto:agustin.benito@xxxxxxxxxxxxxxxxxxxxxx] 
Sent: lunedì 14 febbraio 2022 12:56
To: Sebastian Serewa <sebastian.serewa@xxxxxxxxxx>; Amit Kucheria <amit.kucheria.ext@xxxxxxxxxx>; Davide Ricci <davide.ricci@xxxxxxxxxx>
Cc: Jaroslaw Marek (Jarek) <jaroslaw.marek@xxxxxxxxxx>; oniro-wg@xxxxxxxxxxx
Subject: Re: Roadmap: work on the proposal for oniro-core (goofy)

Hello,

On Monday, February 14, 2022 11:54:47 AM CET Davide Ricci wrote:
> Hi Agustin,
> 
> If you could setup the wg dedicated subproject Amit and I can crate in 
> there the necessary boards / epic so we can then meet, show you what 
> we got and the current process, discuss / document it and in parallel 
> we would then process with goofy roadmap / epic loading as well as SC related processes.
> 
> I think we will realistically have a goofy roadmap approval somewhere 
> in march - with periodic updates and quarterly go - no go meetings for 
> the three main milestones ahead of us.
> 
> In order to get there, we want to start the decomposition / effort 
> estimate work directly in gitlab - such work will likely carry on for 
> the following
> 2-3 weeks - in time for a goofy dev kick off directly on eclipse 
> gitlab first / second week of march.
> 
> Let us tentatively meet on Wed morning assuming Amit and I had access 
> to the wg subproject and have made enough  progress to show the 
> process and the demo epics.

I suggest to split the effort into two parts:
* Roadmap content.
* Roadmapping process.

## Roadmap content

Amit and I have spoken earlier today and he is testing the procedures to create the roadmap content at the Oniro WG level and how the roadmap items can be related to the technical tasks/roadmap at project level (projects gitlab). 
A subproject was created so he can start testing.

Although I would love to participate in this process at this point, I do not have bandwidth.

## Roadmapping process.

This refers to "the how". How does the input get into the roadmap, who access and manage the information, how is the roadmap presented and approved at the Oniro WG SC, what is the scope of the Oniro WG roadmap vs the project ones, how the coordination will take place...

>From what I have seen already, from the different options we can put in place I believe we will go for something that is unique at EF so I will need, in addition, to socialise it internally at EF and make sure it meets the core principles for this topic, just like in the prospects pipeline management
(PPM) process (although there is more freedom of action in this roadmapping topic for working groups, from what I have seen).  

This is the part I would like to work with Sebastian (and who else is best) in the coming few days so we can put a proposal on the table.

You can follow the work on this second point: 

Link: https://gitlab.eclipse.org/eclipse-wg/oniro-wg/proposal-incubation-stage-oniro/proposal-incubation-oniro-management/-/issues/5 

If the Oniro WG SC is not elected by the time we have the proposal ready, as we did with the PPM process, I will suggest to seek a general consensus and start implementing it. We then can have the proposal ratified by the Oniro SC as soon as possible.

## Conclusion

I think that, this way, and as we did with the PPM process, we can unlink to some extend the content from the process so we can work in both in (semi)parallel and have them ready in a short period of time.

Any thoughts?


> 
> Cheers
> D
> 
> 
> -----Original Message-----
> From: Agustín Benito Bethencourt
> [mailto:agustin.benito@xxxxxxxxxxxxxxxxxxxxxx] Sent: lunedì 14 
> febbraio
> 2022 10:02
> To: Sebastian Serewa <sebastian.serewa@xxxxxxxxxx>; Amit Kucheria 
> <amit.kucheria.ext@xxxxxxxxxx> Cc: Jaroslaw Marek (Jarek) 
> <jaroslaw.marek@xxxxxxxxxx>; Davide Ricci <davide.ricci@xxxxxxxxxx>; 
> oniro-wg@xxxxxxxxxxx Subject: Roadmap: work on the proposal for 
> oniro-core
> (goofy)
> 
> Hello Sebastian and Amit,
> 
> as you know, one of the attributions of the Working Group is the 
> creation of the roadmap (high level). Projects also have to create 
> their own technical roadmap. Given the nature of Oniro, where we are 
> trying to create a coherent platform, we need to coordinate both.
> 
> The goal would be to create the structure that will be approved by the 
> Oniro SC in the coming weeks. Davide wrote me that you guys would like 
> to do that sooner than later so I propose the following.
> 
> We start working on the structure now, we come to agreements, we get 
> the general consensus and they are ratified by the Oniro SC in the 
> first occasion it has.
> 
> What do you think?
> 
> I believe you already have some ideas implemented for Goofy, the 
> coming release.
> 
> Can we meet so we evaluate and implement them in the Oniro WG repo? 
> This way we provide the proposal in a more visual way.
> 
> Best Regards
> --
> Agustin Benito Bethencourt
> Oniro Program Manager | Eclipse Foundation Eclipse Foundation: The 
> Community for Open Innovation and Collaboration

Best Regards
--
Agustin Benito Bethencourt
Oniro Program Manager | Eclipse Foundation Eclipse Foundation: The Community for Open Innovation and Collaboration