headers
jukka.eklund | 12 Jan 2011 15:51
Picon

MeeGo Product management wiki created, and Change management process kicking off

Hello,

I have corrected the issue of missing wiki for PM function, by creating a page and linked it also to main page:
http://wiki.meego.com/Product_Management. The wiki is (of course) a work in progress, and missing stuff.

One of the key items on the wiki is the Change management process, which we are now kicking off. I will right
away say the process is modeled very much after Architecture team process. As said on the wiki, we shall
discuss the topics right here in this email list and document the actions on the wiki.

Looking forward to community participation also on the product management side of MeeGo!

Br,
Jukka
Permalink | Reply |
headers
Carsten Munk | 12 Jan 2011 16:29

Re: MeeGo Product management wiki created, and Change management process kicking off

2011/1/12  <jukka.eklund@...>:
> Hello,
>
> I have corrected the issue of missing wiki for PM function, by creating a page and linked it also to main
page: http://wiki.meego.com/Product_Management. The wiki is (of course) a work in progress, and
missing stuff.
>
> One of the key items on the wiki is the Change management process, which we are now kicking off. I will right
away say the process is modeled very much after Architecture team process. As said on the wiki, we shall
discuss the topics right here in this email list and document the actions on the wiki.
>
> Looking forward to community participation also on the product management side of MeeGo!

Welcome out in the open - looking forward to seeing how this will work
out in practice :)

I would suggest dropping a note to meego-dev <at>  about this wiki and
mailing list as well.

/Carsten
Permalink | Reply |
headers
jukka.eklund | 12 Jan 2011 16:30
Picon

Re: MeeGo Product management wiki created, and Change management process kicking off

Thanks, that's a good point about meego-dev.

> -----Original Message-----
> From: carsten.munk@...
[mailto:carsten.munk@...] On Behalf
> Of ext Carsten Munk
> Sent: 12. tammikuuta 2011 17:29
> To: Eklund Jukka (Nokia-MS/Tampere)
> Cc: meego-pm@...
> Subject: Re: [MeeGo-pm] MeeGo Product management wiki created, and
> Change management process kicking off
> 
> 2011/1/12  <jukka.eklund@...>:
> > Hello,
> >
> > I have corrected the issue of missing wiki for PM function, by
> creating a page and linked it also to main page:
> http://wiki.meego.com/Product_Management. The wiki is (of course) a
> work in progress, and missing stuff.
> >
> > One of the key items on the wiki is the Change management process,
> which we are now kicking off. I will right away say the process is
> modeled very much after Architecture team process. As said on the wiki,
> we shall discuss the topics right here in this email list and document
> the actions on the wiki.
> >
> > Looking forward to community participation also on the product
> management side of MeeGo!
> 
> Welcome out in the open - looking forward to seeing how this will work
(Continue reading)

Permalink | Reply |
headers
Sivan Greenberg | 12 Jan 2011 19:20

Re: MeeGo Product management wiki created, and Change management process kicking off

Hi Jukka!

On Wed, Jan 12, 2011 at 4:51 PM,  <jukka.eklund@...> wrote:
> Hello,
>
> I have corrected the issue of missing wiki for PM function, by creating a page and linked it also to main
page: http://wiki.meego.com/Product_Management. The wiki is (of course) a work in progress, and
missing stuff.
>
> One of the key items on the wiki is the Change management process, which we are now kicking off. I will right
away say the process is modeled very much after Architecture team process. As said on the wiki, we shall
discuss the topics right here in this email list and document the actions on the wiki.
>

I have a few question that could possibly define some work items:
- What does this actually mean for community members? Could this be
perhaps the channel to spec and create a usable open source "upstream"
(= originating from meego.com) touch UX for the ideapad, as an example
device, or at the very least conclude it is necessary or otherwise,
announce publicly that this is left for vendors and community forkers?
- How does this relate to the compliance spec? More interesting for
me, how does desired quality for the product is set, and which PM
activities will be carried to embody it in the spec itself?

The action items I see as of these:
- Work with community to refine product's UX for netbook.
- Discuss quality guidelines as part of the product planning, not just
as per QA. (e.g. have them higher up the plan)
- Figure ways how to Involve QA people, community and bug reporters
and/or use their input with with future product planning. Analyzing
(Continue reading)

Permalink | Reply |
headers
jukka.eklund | 14 Jan 2011 10:37
Picon

Re: MeeGo Product management wiki created, and Change management process kicking off

Hi,

I'm not fully sure I follow your thinking, but since MeeGo is all about contribution any new work items need
to come with resources eg. to create a new netbook UX. At the moment we don't have such project, but surely it
could be formed?

As for future product planning, let's see how work with the community on 1.3 and 1.4 (those releases are now
BTW visible in featurezilla).

Jukka

> -----Original Message-----
> From: sivang@...
[mailto:sivang@...] On Behalf Of ext Sivan
> Greenberg
> Sent: 12. tammikuuta 2011 20:21
> To: Eklund Jukka (Nokia-MS/Tampere)
> Cc: meego-pm@...
> Subject: Re: [MeeGo-pm] MeeGo Product management wiki created, and
> Change management process kicking off
> 
> Hi Jukka!
> 
> On Wed, Jan 12, 2011 at 4:51 PM,  <jukka.eklund@...> wrote:
> > Hello,
> >
> > I have corrected the issue of missing wiki for PM function, by
> creating a page and linked it also to main page:
> http://wiki.meego.com/Product_Management. The wiki is (of course) a
> work in progress, and missing stuff.
(Continue reading)

Permalink | Reply |
headers
Sivan Greenberg | 14 Jan 2011 12:27

Re: MeeGo Product management wiki created, and Change management process kicking off

On Fri, Jan 14, 2011 at 11:37 AM,  <jukka.eklund@...> wrote:
> Hi,
>
> I'm not fully sure I follow your thinking, but since MeeGo is all about contribution any new work items need
to come with resources eg. to create a new netbook UX. At the moment we don't have such project, but surely it
could be formed?
>
Yes, I'm sure we would be able to find people interested and able to
help us carry along this task.

> As for future product planning, let's see how work with the community on 1.3 and 1.4 (those releases are now
BTW visible in featurezilla).
>
Great, I am also looking forward for this. I think this is a great
thing to have the PM process in the open and another step towards the
great openness of this project.

Thank you!

-Sivan

> Jukka
>
>> -----Original Message-----
>> From: sivang@...
[mailto:sivang@...] On Behalf Of ext Sivan
>> Greenberg
>> Sent: 12. tammikuuta 2011 20:21
>> To: Eklund Jukka (Nokia-MS/Tampere)
>> Cc: meego-pm@...
(Continue reading)

Permalink | Reply |
headers
Quim Gil | 13 Jan 2011 00:37
Picon
Gravatar

Re: MeeGo Product management wiki created, and Change management process kicking off

On Wed, 2011-01-12 at 14:51 +0000, ext jukka.eklund@... wrote:
> Hello,
> 
> I have corrected the issue of missing wiki for PM function, by
> creating a page and linked it also to main page:
> http://wiki.meego.com/Product_Management. The wiki is (of course) a
> work in progress, and missing stuff.

Thanks!

Something missing is the scope and activities of the team.

At http://meego.com/about/governance/program-office Hillarie appears as
head of platform product management but is missing at the wiki page.
Which page is right?

Both the Governance pages and that wiki page are not giving about any
information about the Netbook UX, which happens to be the most active in
terms of releases. It would be about time to fix this gap.

> Calls happen generally every Wednesday 8AM/6PM

Wow, those are long calls! Unless you mean 8am EET / 6pm PST  ;)

Also please address http://bugs.meego.com/show_bug.cgi?id=9908 - Open
roadmapping process defined but no implemented. All that silence is
frustrating. Perhaps I could get more information asking more in
corridors and phone calls, but that would defeat the openness purpose.

Looking forward to seeing activity in this list!
(Continue reading)

Permalink | Reply |
headers
jukka.eklund | 14 Jan 2011 10:28
Picon

Re: MeeGo Product management wiki created, and Change management process kicking off

(Sorry for top posting, still using Outlook..)

Scope and activities of the team is product management, but yes we need to write something on the wiki to
explain a bit better. Also clarify the governance. Feel free to write a new bug and assign to me if needed.

Roadmapping is just missing better visibility, the stuff should be out in the open already. You can assign
that bug to me if you like, I will at least try to get better visibility on Core and Handset areas. Feel free to
write your comments also under "Process improvement topics" in the wiki.

On the Netbook UX we don't have product manager for that, do we, so quite hard to address. There is no persons
in Programme office for Netbook. Wwe would happy to have a Netbook PM present to tackle the issues.

Jukka

> -----Original Message-----
> From: Gil Quim (Nokia-MS/SiliconValley)
> Sent: 13. tammikuuta 2011 1:37
> To: Eklund Jukka (Nokia-MS/Tampere)
> Cc: meego-pm@...
> Subject: Re: [MeeGo-pm] MeeGo Product management wiki created, and
> Change management process kicking off
> 
> On Wed, 2011-01-12 at 14:51 +0000, ext jukka.eklund@... wrote:
> > Hello,
> >
> > I have corrected the issue of missing wiki for PM function, by
> > creating a page and linked it also to main page:
> > http://wiki.meego.com/Product_Management. The wiki is (of course) a
> > work in progress, and missing stuff.
>
(Continue reading)

Permalink | Reply |
headers
Quim Gil | 15 Jan 2011 00:35
Picon
Gravatar

Re: MeeGo Product management wiki created, and Change management process kicking off

On Fri, 2011-01-14 at 09:28 +0000, ext jukka.eklund@... wrote:
> Scope and activities of the team is product management, but yes we
> need to write something on the wiki to explain a bit better. Also
> clarify the governance. Feel free to write a new bug and assign to me
> if needed.

Not needed, I still trust you.  ;)

> Roadmapping is just missing better visibility, the stuff should be out
> in the open already. You can assign that bug to me if you like, I will
> at least try to get better visibility on Core and Handset areas. Feel
> free to write your comments also under "Process improvement topics" in
> the wiki.

Thanks, and bug assigned to you. The Core roadmap is the most critical,
since any MeeGo product needs to go through that. I have heard several
people meeting companies considering the development of MeeGo products
that even a Core OS WG would make sense.

More things:

- It's understandable that you have your regular meetings in conference
calls and it's also somewhat understandable that not everybody an join
(I wonder if a listener role would be useful though, I imagine many
companies with MeeGo related product managers interested in joining).
But in any case public minutes is a must - for any MeeGo project meting.
Please consider.

- Companies working on MeeGo products and also companies considering
adopting MeeGo miss relevant information of what is going on during the
(Continue reading)

Permalink | Reply |
headers
Jeremiah Foster | 17 Jan 2011 15:07
Favicon
Gravatar

Re: MeeGo Product management wiki created, and Change management process kicking off

On Fri, Jan 14, 2011 at 3:35 PM, Quim Gil <quim.gil@...> wrote:
> On Fri, 2011-01-14 at 09:28 +0000, ext jukka.eklund@... wrote:
>
> Thanks, and bug assigned to you. The Core roadmap is the most critical,
> since any MeeGo product needs to go through that. I have heard several
> people meeting companies considering the development of MeeGo products
> that even a Core OS WG would make sense.

In some consortia they have "observer" positions. Some companies like
this because it allows them to participate without having to commit
resources until they are ready. Perhaps MeeGo might accomodate a
certain number of these positions to allow various companies and
groups to smooth their path to contribution?

Jeremiah
Permalink | Reply |

Gmane