200 lines
3.7 KiB
HTML
200 lines
3.7 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Institutionalize CVS in the Organization</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
|
REL="HOME"
|
|
TITLE="CVS Best Practices"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Software Builds"
|
|
HREF="section1-softwarebuild.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Best Practices in Action"
|
|
HREF="section1-inaction.html"></HEAD
|
|
><BODY
|
|
CLASS="sect1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>CVS Best Practices</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="section1-softwarebuild.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="section1-inaction.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="sect1"
|
|
><H1
|
|
CLASS="sect1"
|
|
><A
|
|
NAME="section1-instprocess"
|
|
></A
|
|
>9. Institutionalize CVS in the Organization</H1
|
|
><P
|
|
>Here we will look at the best practices for institutionalizing CVS
|
|
usage in the organization.
|
|
</P
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="section2-chngmgmt"
|
|
></A
|
|
>9.1. Implement Change Management Process</H2
|
|
><P
|
|
>All organizations must implement a good Change management process
|
|
(<SPAN
|
|
CLASS="acronym"
|
|
>CMP</SPAN
|
|
>). A good CMP will define how changes are received,
|
|
recorded, tracked, executed and delivered. CVS provides version
|
|
control for your project. Change management addresses the <SPAN
|
|
CLASS="QUOTE"
|
|
>"bigger
|
|
picture"</SPAN
|
|
> of how enhancements and bugs are received, tracked and
|
|
closed. CVS will play a smaller but a very important part in this
|
|
entire picture. With a formal change management process in place in the
|
|
organization, tools such as CVS will be looked at as aiding this process
|
|
instead of acting as a general development overhead. </P
|
|
><P
|
|
>Change management is quite a vast topic that cannot be done justice
|
|
here. Please look up other sources of information on change management. </P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="section2-objectives"
|
|
></A
|
|
>9.2. Make CVS Usage part of Objectives</H2
|
|
><P
|
|
>To institutionalize CVS, it can be made as part of the performance
|
|
objectives for the developer to use CVS in the project. In addition, it
|
|
can also be made as part of the objective for the project manager to deploy
|
|
CVS in his or her project. </P
|
|
><P
|
|
>Compliance of this can then be reviewed as part of the appraisal cycle
|
|
for the employee. </P
|
|
></DIV
|
|
><DIV
|
|
CLASS="sect2"
|
|
><H2
|
|
CLASS="sect2"
|
|
><A
|
|
NAME="section2-metrics"
|
|
></A
|
|
>9.3. Collect metrics on CVS usage</H2
|
|
><P
|
|
>CVS usage metrics can be collected in terms of percentage of
|
|
deployment in the organization, project size handled etc., This information
|
|
will spur other line managers and program managers to look at CVS as a
|
|
tool that will aid them in their daily operations. </P
|
|
></DIV
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="section1-softwarebuild.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="section1-inaction.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Software Builds</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Best Practices in Action</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |