On 12/1/06, D. Hiller <[EMAIL PROTECTED]> wrote:
Am Donnerstag, den 30.11.2006, 21:27 -0600 schrieb Carlos Luis Zúñiga Sibaja: > ... > > I think before establishing a stable roadmap we should examine the wish list > and see which requirement/wish corresponds to each release. I agree to this, the wish list looks like a brainstorming of requirements. Can we finalize this brainstorming by going through the issues and adding our thoughts? And then define a concrete roadmap? In order not to loose momentum I would suggest to define a deadline for this. Would Sunday 17 Dec be too early or should we set something after Christmas? Afterwards we have to find out, how to put all the requirements in one document.
I my opinion Dec 17th is a little to agressive, taking into consideration the holidays and the fact that most people is taking time off to spend with their families and loved ones, may be we could move the date to Jan 14th?
On the other hand, I'm 100% behind you on the walk-before-run approach, ... another 100% from me. And I also agree to the remarks already made that we have to have an eye on the final structure from the beginning. I am more a user so having in mind various target groups (simple application for private activities / advanced for project managers) and roles (definition of project, status reports of team members, ...) should not become too difficult in a later stage of this activity. Dietmar --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Carlos Luis Zúñiga Sibaja __________________________ [EMAIL PROTECTED] divide et impera...
