Re: Priority list for WPD work going forward

I think if we go with a scrum project management solution then we should
not have a real priority list. Also, we should drop timing on issues and
instead assign point values. Then say our goal of points to get done in X
time is Y, then get to work.

Also, for now I think a priority list is fine. At least until we get TBG
online and in-use. Then it would get moved in there as milestones with
certain issues attached for specifics.


On Mon, Jan 14, 2013 at 7:02 AM, Chris Mills <cmills@opera.com> wrote:

> Thanks Scott, Julee,
>
> I knew some of the timings would not be right - I just put something there
> for now. Feel free to update them with more accurate info when you have
> done your scoping work.
>
> The Scrum process sounds interesting, and I would like to see more detail
> on how it would work.
>
> So does this priority list work for now? Or do we need something entirely
> different?
>
> Chris Mills
> Opera Software, dev.opera.com
> W3C Fellow, web education and webplatform.org
> Author of "Practical CSS3: Develop and Design" (http://goo.gl/AKf9M)
>
> On 11 Jan 2013, at 21:21, Julee Burdekin <jburdeki@adobe.com> wrote:
>
> > Yes, thanks Chris! Yes, API will take more than a month. I'm wondering
> if we couldn't creating a little scrum process for content to identify
> what's priority, get it done & reviewed, and "release" it via social media
> channels. That way, whenever the site is functionally at beta, we could go
> out with whatever content is there and highlight the great stuff.
> >
> > What do you think?
> >
> > J
> > ----------------------------
> > julee@adobe.com
> > @adobejulee
> >
> > From: Scott Rowe <scottrowe@google.com>
> > Date: Friday, January 11, 2013 1:09 PM
> > To: Chris Mills <cmills@opera.com>
> > Cc: "public-webplatform@w3.org" <public-webplatform@w3.org>
> > Subject: Re: Priority list for WPD work going forward
> > Resent-From: <public-webplatform@w3.org>
> > Resent-Date: Friday, January 11, 2013 1:10 PM
> >
> > Wow, Chris! Thanks for this exhaustive (and exhausting) list.
> >
> > One thing, the API Docs project is definitely going to take longer than
> a month. With the Resources arm of the rubber triangle not known, it is
> difficult to gage how long, but Dave and I are in the midst of scoping the
> work and planning for recruitment (yes, posters, too).
> >
> > We'll want to marshall forces for the CSS Properties project first,
> however. A lot of work could get done during the doc sprint.
> >
> > +Scott
> >
> >
> >
> > On Fri, Jan 11, 2013 at 10:02 AM, Chris Mills <cmills@opera.com> wrote:
> >> As actioned in Monday's meeting, I have started to draw up a list of
> different tasks that we want to do to sort content out going forward,
> arranged in a priority list. I haven't finished it yet; I wanted to get
> some feedback from everyone before going any further
> >>
> >> http://docs.webplatform.org/wiki/WPD:Beta_Requirements
> >>
> >> Is this a useful way to represent the data? When TBG is set up, we can
> probably move it there, which will allow a much more intelligent
> structuring of the work.
> >>
> >> Best,
> >>
> >> Chris Mills
> >> Opera Software, dev.opera.com
> >> W3C Fellow, web education and webplatform.org
> >> Author of "Practical CSS3: Develop and Design" (http://goo.gl/AKf9M)
> >>
> >>
> >
>
>
>