Scientist recently discovered a planet where there is trace of water which is the basic requirement for life (at least we believe so). The planet is about 20.5 light years away from the Libra constellation. The planet circles the red dwarf star Gliese 581 in a Goldilocks orbit that sets it temperature between 32 and 104 degrees Fahrenheit.
Scientists have long followed the principle of “follow the water’ for detecting life existence. I define life as a body which is capable to generate energy from any form of matter, sustain itself and of course reproduce. This discovery will certainly be a significant landmark in the quest to find extra terrestrial life, if any.
Successful Meetings
Consider a meeting scenario where attendees are roughly about the same age, there is no hierarchy and it is a unofficial meeting. My experience is that when there is no hierarchy (boss –worker/employee) and every one has a right to argue his/her point until the end; the place normally turns to be a fish market. Here are some rules and ethics that should be followed for successful meetings:
1 There should be a definite agenda with allotted time for each topic
2 The meeting place should be in some suitable facility where there are no external disturbances. Arranging meetings over dinner or lunch is more of a socialization meeting than actual discussion and conclusions (if its just 2-3 people it may acceptable)
3 Every person should have a note pad (laptop - any digital gadget) to note his her action points and important issues discussed
4 I always believe there should be a chairperson who can intervene if the discussion is going out of bounds and becoming more of a personal view than helping the cause discussed.
5 One person should be responsible noting meetings minutes and making them available for all members after meeting.
6 Internet access availability solves some simple problems which may take up valuable meeting time
7 Personal communication between the members should be strictly avoided and some sort of discipline should be maintained
8 If the members are from wide variety of backgrounds and countries, communication in respective local languages should be strictly avoided. The standard language (which is normally English) should be followed.
9 Try to keep it short and frequent than one long meeting where one tends to lose his focus.
10 Meeting place should be preferably centrally located thus minimizing the member complains and initial bias.
11 Schedule a suitable time. Keeping the meeting early morning or late night will certainly be counter productive.
12 If the member do not know each other make sure you arrange for name tags for each participating entity
13 Personally I feel snacks should be avoided ( non alcoholic beverages are fine)
14 Last and the most important point, start and end on time
1 There should be a definite agenda with allotted time for each topic
2 The meeting place should be in some suitable facility where there are no external disturbances. Arranging meetings over dinner or lunch is more of a socialization meeting than actual discussion and conclusions (if its just 2-3 people it may acceptable)
3 Every person should have a note pad (laptop - any digital gadget) to note his her action points and important issues discussed
4 I always believe there should be a chairperson who can intervene if the discussion is going out of bounds and becoming more of a personal view than helping the cause discussed.
5 One person should be responsible noting meetings minutes and making them available for all members after meeting.
6 Internet access availability solves some simple problems which may take up valuable meeting time
7 Personal communication between the members should be strictly avoided and some sort of discipline should be maintained
8 If the members are from wide variety of backgrounds and countries, communication in respective local languages should be strictly avoided. The standard language (which is normally English) should be followed.
9 Try to keep it short and frequent than one long meeting where one tends to lose his focus.
10 Meeting place should be preferably centrally located thus minimizing the member complains and initial bias.
11 Schedule a suitable time. Keeping the meeting early morning or late night will certainly be counter productive.
12 If the member do not know each other make sure you arrange for name tags for each participating entity
13 Personally I feel snacks should be avoided ( non alcoholic beverages are fine)
14 Last and the most important point, start and end on time
Open Source Estimation
Open Source software development is an interesting phenomenon where the software development is collaborative and source code is open and available to public. The renowned literature of the ‘Cathedral and Bazaar’ by Eric S. Raymond was published more than 10 years back and still considered a pioneer work in the field of Open Source. Unfortunately, there are no well-defined processes and estimation techniques (models) in the Open Source world like the COCOMO, function points or SLIM models for the classical software development. Its very interesting that even with presence and support from the large organizations like Google, IBM, Oracle and tons of others Open Source world has not come up with any standardization. I agree that there may be well-defined processes and best practices in commercial open source software companies like Red Hat, MySQL and SugarCRM but certainly not a universally accepted standard. One reason may be that Open Source development is very unpredictable and largely depends upon the motivation of a handful of developers who are committed to develop such collaborative software. There are thousands of projects registered on SourceForge and FreshMeat (largest repository of the open source software projects) by a single developer, which never proceed further to development. There are also projects that are currently in the inactive stage.
I guess with boom and wide spread of Open Source today we certainly need some estimation techniques for the required number of developers (effort) and expected size of the community and thus an overview of the complete ecosystem around the software. Such models or processes will certainly help the community for better planning and effective execution of an Open Source project.
OSS Processes
Open Source software development is an interesting phenomenon where the software development is collaborative and source code is open and available to public. The renowned ‘Cathedral and Bazaar’ book by Eric S. Raymond was published more than 10 years back and is still considered a pioneer work in the field of Open Source. Unfortunately, there are no well-defined processes and estimation techniques (models) in the Open Source world like the COCOMO, function points or SLIM models for the classical software development. Its very interesting that even with presence and support from the large organizations like Google, IBM, Oracle and tons of others Open Source world has not come up with any standardization. I agree that there may be well-defined processes and best practices in commercial open source software companies like Red Hat, MySQL and SugarCRM but certainly not a universally accepted standard. One reason may be that Open Source development is very unpredictable and largely depends upon the motivation of a handful of developers who are committed to develop such collaborative software. There are thousands of projects registered on SourceForge and FreshMeat (largest repository of the open source software projects) by a single developer, which never proceed further to development. There are also projects that are currently in the inactive stage. I guess with boom and wide spread of Open Source, we certainly need some estimation techniques for the required number of developers (effort) and expected size of the community and an overview of the complete ecosystem around the software. Such models and processes will certainly help the community for better planning and effective execution of an Open Source projects.
Subscribe to:
Posts (Atom)