[IAEP] teams vs. projects

[Greg Dekoenigsberg]

On Mon, 24 Nov 2008, Walter Bender wrote:

> I think the idea of a roadmap (with project schedules) within each
> team would address much of this need.

Agreed.

Project management is a pain in the ass, and we don't always have the 
resources to have dedicated and "proper" project management -- which is 
why, at the *very least*, I advocate TODOs and weekly meetings to keep 
those TODOs moving.

cf. http://www.sugarlabs.org/go/MarketingTeam/TODO

Some teams -- perhaps the development team -- will have the need for 
stronger project management.  But at the very least, every team should be 
capturing its TODOs so that they are not lost.

I myself dislike trac for this kind of thing, but some people prefer it. 
If that's the case, I would advocate each team creating a simple trac 
query that brings up the team's TODO items, and then linking to that query 
from the TODO page.

The goal: anyone on your team should be able to answer the question "what 
are people working on?" with a single click.

--g

> On Mon, Nov 24, 2008 at 10:11 AM, Tomeu Vizoso <tomeu at tomeuvizoso.net> wrote:
>> Hi,
>>
>> was wondering if there would be some value of including the notion of
>> projects inside SugarLabs' organizational structure.
>>
>> Teams seem to me as something not bounded in time, a way to focus energy.
>>
>> Projects would be smaller in scope, involve several teams and
>> milestones would be an important part of their identity.
>>
>> Comments? Should I get some sleep instead of writing absurdities?
>>
>> Thanks,
>>
>> Tomeu
>> _______________________________________________
>> IAEP -- It's An Education Project (not a laptop project!)
>> IAEP at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/iaep
>>
>
>
>
> -- 
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>