Hi Claus,
I'm a newbie to the OOPM project, but I do have a few thoughts. Perhaps I
should start by introducing myself.
I work for a major telco supplier as an R&D Manager. I've been the Manager
of a core development team in Network Management as well as the Manager
responsible for builds, tools (including test tracking and requirements
management), configuration management tools and automated testing. I've also
worked as an IT Manager and helped develop a problem tracking system that
had several hundred concurrent users. I am currently the "Chief System
Integrator" for a product with 5+ million lines of code and about a hundred
developers. I do not work as a Project Manager, but I have worked with
Project Managers for years and have used Microsoft Project for about 6
years. I'm also somewhat of a heretic. I like lots of Microsoft's products
and have no personal bias against Bill Gates. On the other hand I find
Microsoft's products too expensive, their licensing terms too restrictive
and I work in a multi-platform world. Hence a strong desire to contribute to
an open source development project. Realistically, I haven't done serious
programming in years. But I can write requirements, help with architecture,
develop and execute formal test cases and work on documentation.
Now for the important part - some thoughts to share. We've got a great wish
list, but the wish list itself doesn't suggest a direction for us to proceed
in. Trying to fulfil the wish list means we'll never get off the ground. So
I'd like to suggest the following multi-phased development plan:
Define an architecture. For example, if we eventually want to have a product
that can act as a server for multiple simultaneous updates, we might want to
store each item in the WBS as a separate row in a database with row level
locking. We don't need to build a heavy-weight architecture to start, but we
need to design and evolve the architecture with a knowledge of where we want
to go.
Develop version 0.1. This will have WBS, the ability to link tasks and
display them as a GANTT chart. Mostly a look and feel demonstrator.
Develop version 0.2. This will be targeted at simple software development
projects. Add vacation time and simple resource leveling. This will be the
first usable version. At this point we can start using our own tool to track
the progress of our development.
Develop version 0.3. Add reporting, printing, help screens, etc.
Multiple iterations will follow, adding Pert charts, critical path, resource
cost, support for project management of non-software projects, client-server
capabilities, email updates, and all the good things on the wish list, etc.
In other words, design an architecture, start simple, create a first release
with a specific target user community, and then broaden the scope of what we
want to accomplish.
Thoughts, as always, are welcome.
Regards,
Shawn
----- Original Message -----
From: "Claus Agerskov" <[EMAIL PROTECTED]>
To: <dev@oopm.openoffice.org>
Sent: Wednesday, October 26, 2005 6:05 PM
Subject: [oopm-dev] Putting the wishes from the survey on the OOPM website
Hi OOPM'ers
I have updated the OOPM wish page:
http://oopm.openoffice.org/initial_analyze/wishes.html
I will update more of the OOPM homepage the next days.
If you have some ideas for the page I am all ears. But please post them on
list.
The most enjoyable greetings
--
Claus Agerskov #=== Analyze OpenOffice.org
Content Developer ==== Requirements Project Management Tool
[EMAIL PROTECTED] ==== Design/model Subproject
http://ooo.chbs.dk/ ==== Implement
http://oopm.openoffice.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
