Hello Jürgen
On 08/01/2005, you wrote:
Hello,
I propose we go the commité route for the project management, with 2 senior devs & 2 managers.
One senior dev for linux One for AOS
A rescource manager
And finally one manager who makes the final calls based on feedback of the other 3.
Hi! Well, I am far to busy to follow your discussion as the whole, but I'd like to add my two cents here. And before I go on, can anyone please let me know, why there is a need to support Linux here ?
We don't need linux support, but we do need someone fairly well aquinted with linux to help guide the porting, that can explain to the others what this & that bit do on linux, and offer help in working arround things not possible in AOS
Let me introduce myself, before I go on. I had an Amiga sales company back in Austria until the last 6 month ago, I have some experience in SW so far, and I moved to the US in July to built up the SW R&D department for our (Austrian) company building Casino games. I lead a small SW department here (incl. SW Test) , so I have some experience on what I'd like to add here.
Anyway, before we talk about managment (which is a word I do not really like), we should talk about functional entitys, define the responsibilities and try to find people taking over those responsibilities. Afterwards, we make some sort of internal applications for these jobs and pick (vote) for the best candidate.
You just described management ;)
OK, that's how it goes:
Tools development, build process engineering: Responsible for getting the built process running incl. SVN (is this decision made yet ?), Phyton, compiler and configurations. (maintenaince of make files, not in detail, but as a whole) Also responsible for SVN synchronisation and built managmanet (daily builts, etc)
- One Lead Programmer ( = Built engineer)
- additional programmers/maintainers (matter of discussion)
Application programming:
- Lead programmer Application Responsible for the application in total. Give technical directions and has a overview over the whole code. Is also responsible on module integration. Is also responsible to work out detailed timetables for component development and integration
- Senior programmers / SW modules lead position on compontents yet to identify in the package
- Component programmers programmers assigned to a component to implement with a senior programmer
SW Test:
- Lead SW Tester Works out test plans and component test. Sets up SW Test tools (e.g. Bugzilla, etc). Defines timetables for component testing
- SW Tester Works with test plans and implements component testing. Assigns bug reports too SW engineers. Also implements test frameworks (what ever this is, e.g. cppunit). Should have programming skills.
PjM (Projectmanagment) - Keeps track of seperate modules and synchronises them. Works close with SW Lead / SW Test Lead. PjM can have multiple "liason engineers" to communication with SW development
Also, various support positions: Web Site maintenance, graphics (logo), public communication, etc.
Good list, let's see how the others reply :)
So, before we go on, we should work out this areas in detail, a smaller group should identify the amount of people required for each area. We should put this organisation chart on a (private) website, so everybody can apply to one of the positions of interesst and it is visible to everybody who is doing what. It's important to have a good, focused communication and avoid overhead. Therefore, a clear responsibility who is doing what and how this person can be reached is important.
I agree, that's actually what i'm trying to get us to achieve, organisation, your proposition is more then welcome :)
Sorry, was a bit long, but I hope you might find the one or other thought usefull to set up an effective team. I am pretty sure I missed some things here, so if you have things to add, please go ahead.
Feedback is always good :)
Regards