| YouSigma- the web’s most extensive resource for information |
|
|
|
|
Best Practices Guideline for Managing Open Source Applications |
Streamlining Open Source Management Practices
In order to extract the maximal returns from open source applications, organizations must: (A) Create a cross-functional governing body to oversee all open source Initiatives and (B) Design and institute effective and comprehensive open source policies.
Steps to Consider
A. Create a cross-functional governing body to oversee all open source initiatives: To ensure effective management of open source applications, organizations should form a cross-functional governing body composed of individuals from the following groups: finance and budgeting, enterprise architecture, application development, legal, end-user support, human resources, procurement, operations and executive management. The primary responsibility of this Open Source Management Team (OSMT) is to ensure that proper due diligence and quality assurance is applied and all appropriate polices and procedures are followed. The OSMT will also work in tandem with the Open Source Support & Development Team (OSSDT)—group of internal developers—to certify and approve the usage of any new open source application, as well as to validate any modifications made to existing open source applications. Key Responsibilities of the Open Source Management (OSMT) and Support & Development Teams (OSSDT) includes:

Every developer (or team of developers) is assigned one open source application, and maintains contact with the external development community that specializes in work related to that application. Each developer therefore communicates with all other developers (through the Open Source Support and Development Team (OSSDT)), his individual open source application development community, and the Open Source Management Team (OSMT).
B. Design and institute effective and comprehensive open source policies 
Practice Profiles
1. Create a cross-functional governing body to oversee all open source initiatives |
Fidelity (Industry: Financial Services) created an Open Source Support Center to approve open source code before deploying it, and to validate any modifications made before sending it back to the appropriate development community. FMR Also created a central repository linked to all development communities so as to pinpoint any necessary updates or patches. |
Anthem ((Industry: Health care) created a team of enterprise architects in charge of identifying appropriate open source applications from the Web and presenting the business case to a cross-functional open source steering committee. Anthem also launched a website to store all information about open source utilities, standards, tools, and documentation. In addition, the company formed a governing body to ensure that proper due diligence is applied and to enforce appropriate policies and procedures. |
|
Texas Instruments (Industry: Electronics) formed a technology group aimed at verifying the feasibility and usability of open source applications, as well as approving and launching the application. The company also created a website to present all open source standards, and to advertise frequent user awareness meetings and training sessions. |
|
2. Design and institute effective and comprehensive open source policies |
FMR (Industry: Financial Services) heavily integrated its legal department into its open source practices to create a set of legal guidelines to govern the use of open source applications within its infrastructure. |
Texas Instruments (Industry: Electronics) formulated a set of standards to regulate the use of open source applications, and to use as a benchmark when deploying new utilities within its software environment. |
| About YouSigma | Please Donate Using PayPal, to help us Develop Content | Copyright and Disclaimer |
|
Loading
|
|
|
var pageName = "Best Practices Guideline for Managing Open Source Applications";