Re: Beta Criteria

I don't think we need to talk Beta just yet. Instead we need to talk 
Alpha drop. We need to set absolute end-goals and work our way back, 
then decide upon milestones from there. This is actually going to be one 
part of the entire Project Management proposal that is going to hit 
early next week (assuming Tomato and I finish it Monday as planned.)

I can say that it shouldn't be either date or feature driven, it should 
be content driven. We focus on getting the content good and add features 
as-needed. Setting rough dates would be great, but we can't *really* 
depend on them too much since the work to be done is still to be 
decided. Perhaps as we sit down and map things out we can find 
reasonable dates to set to different milestones.


On 12/14/2012 12:20 PM, Doug Schepers wrote:
> Hi, folks-
> I'd like to start the discussion about this here on the public list.
> * Are we looking to be date-driven or feature-driven?
> * What criteria are we using?
> * What is our schedule?
> * Where should we track this?
> Regards-
> -Doug
> -------- Original Message --------
> Subject: RE: Agenda: Web Platform Stewards Telcon, 14 December
> Date: Thu, 13 Dec 2012 22:19:45 +0000
> From: Eliot Graff <>
> To: Doug Schepers <>
> Hi Doug.
> One thing I would like to talk about is what Beta looks like. What do 
> we set the bar at for site performance, content completeness, 
> community growth, internationalization, etc. If we have criteria for 
> these, then we can estimate time until completion and therefore set a 
> schedule. For each criteria, we can decide if we are firm or flexible 
> in getting to beta, but without some specific goals, I am afraid that 
> we're in a cycle of never ending ongoing work.
> E

Received on Friday, 14 December 2012 17:58:24 UTC