 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: COBOL Application Project Mgt Scoping Questions</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/cobol-application-project-mgt-scoping-questions/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/cobol-application-project-mgt-scoping-questions/</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 18:27:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: johnsonfisher</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/cobol-application-project-mgt-scoping-questions/#comment-76088</link>
		<dc:creator>johnsonfisher</dc:creator>
		<pubDate>Fri, 16 Apr 2010 15:38:31 +0000</pubDate>
		<guid isPermaLink="false">#comment-76088</guid>
		<description><![CDATA[COBOL is not brain surgery, but there is well written code, operating against well designed, normalized data, that can make for a significant delta in time estimate.  That being said, as with any project, a time certain for feasibility and evaluation should yield a time certain estimate for execution of the test plan, the changes, QA with sign-off, and implementation.
  
I can understand that a few days of research could return a variable response for project completion, within reason and, for what you describe, that should be a few days or a few weeks at maximum.
  
What could throw this orderly view into the seeming conundrum you describe would be some workpalce and technology variables.  The largest variables, for a project like this, affecting project completion time estimates include the following:
	&lt;ol&gt;&lt;li&gt;IIs the software source library(s) current and complete?
	&lt;li&gt;Are the compilers dependible and licensed?
	&lt;li&gt;Does your QA process include COBOL program maintenance?
	&lt;li&gt;Does your organization respect or degrade, as being obsolete dinosaurs, developers who know COBOL?
	&lt;li&gt;As noted above, do you have developers and developer managers who know COBOL and the applications being considered for modification?&lt;/ol&gt;
If any items in the above list are unknown, uncertain or negative, then perhaps your developers are not lazy but honest.  Walk into our shop with seveal hundred servers, dozens of web servers, app servers, database servers, security, fixed maintnenace windows, change freeze periods and any estimate you would give would be meaningless or career limiting, if you don&#039;t know the application structure or have a mentor that knows this information and is willing to share.  
Consider also that perhaps the developers/programmers may be distrustful of their systems or their management.  Please don&#039;t take that personally, since the responses you are receiving may likely have been influenced by your predecessors.&lt;/li&gt;&lt;/li&gt;&lt;/li&gt;&lt;/li&gt;&lt;/li&gt;]]></description>
		<content:encoded><![CDATA[<p>COBOL is not brain surgery, but there is well written code, operating against well designed, normalized data, that can make for a significant delta in time estimate.  That being said, as with any project, a time certain for feasibility and evaluation should yield a time certain estimate for execution of the test plan, the changes, QA with sign-off, and implementation.</p>
<p>I can understand that a few days of research could return a variable response for project completion, within reason and, for what you describe, that should be a few days or a few weeks at maximum.</p>
<p>What could throw this orderly view into the seeming conundrum you describe would be some workpalce and technology variables.  The largest variables, for a project like this, affecting project completion time estimates include the following:</p>
<ol>
<li>IIs the software source library(s) current and complete?
	</li>
<li>Are the compilers dependible and licensed?
	</li>
<li>Does your QA process include COBOL program maintenance?
	</li>
<li>Does your organization respect or degrade, as being obsolete dinosaurs, developers who know COBOL?
	</li>
<li>As noted above, do you have developers and developer managers who know COBOL and the applications being considered for modification?</li>
</ol>
<p>If any items in the above list are unknown, uncertain or negative, then perhaps your developers are not lazy but honest.  Walk into our shop with seveal hundred servers, dozens of web servers, app servers, database servers, security, fixed maintnenace windows, change freeze periods and any estimate you would give would be meaningless or career limiting, if you don&#8217;t know the application structure or have a mentor that knows this information and is willing to share.<br />
Consider also that perhaps the developers/programmers may be distrustful of their systems or their management.  Please don&#8217;t take that personally, since the responses you are receiving may likely have been influenced by your predecessors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: meandyou</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/cobol-application-project-mgt-scoping-questions/#comment-75632</link>
		<dc:creator>meandyou</dc:creator>
		<pubDate>Wed, 07 Apr 2010 18:21:46 +0000</pubDate>
		<guid isPermaLink="false">#comment-75632</guid>
		<description><![CDATA[Agreed.  It sounds like they are lazy or too dumb to do their job or ....   COBOL is still COBOL ... processing is still processing ... time to kick butt? ... time to buy them presents? ... I can&#039;t help you there because i am the worst at getting people to do things (in my case it happens to be they are both lazy and less-than-bright).   
 
Good luck]]></description>
		<content:encoded><![CDATA[<p>Agreed.  It sounds like they are lazy or too dumb to do their job or &#8230;.   COBOL is still COBOL &#8230; processing is still processing &#8230; time to kick butt? &#8230; time to buy them presents? &#8230; I can&#8217;t help you there because i am the worst at getting people to do things (in my case it happens to be they are both lazy and less-than-bright).   </p>
<p>Good luck</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jzjohnson63</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/cobol-application-project-mgt-scoping-questions/#comment-75110</link>
		<dc:creator>jzjohnson63</dc:creator>
		<pubDate>Tue, 23 Mar 2010 03:12:13 +0000</pubDate>
		<guid isPermaLink="false">#comment-75110</guid>
		<description><![CDATA[I started my career in IT about 20 years ago and it started with COBOL and Pascal (and a little fortran).  But, after some initial projects move on to integration work, computer security and then financial controls and monitoring software.  My efforts began to focus more on the data and/or building web-based applications in C++, Java, etc.  When reviewing the requirements on the table, all of the requirements seem pretty simple and qualify mainly as minor mods or enhancements as the applications themselves are already mature.  For the most part, I&#039;m able to take the team through the requirement, discuss the general approach and/or verbs, etc.  Before me, they had a manager that had little or no technical background and I believe they&#039;ve used that to their advantage to increase the team size and increase the cost.  No matter how I sketch it up on the white board and no matter how many of my close friends from the COBOL consulting world I refer to I can&#039;t see how a one week task can be stretched into 5-6 months and 20+ FTEs.]]></description>
		<content:encoded><![CDATA[<p>I started my career in IT about 20 years ago and it started with COBOL and Pascal (and a little fortran).  But, after some initial projects move on to integration work, computer security and then financial controls and monitoring software.  My efforts began to focus more on the data and/or building web-based applications in C++, Java, etc.  When reviewing the requirements on the table, all of the requirements seem pretty simple and qualify mainly as minor mods or enhancements as the applications themselves are already mature.  For the most part, I&#8217;m able to take the team through the requirement, discuss the general approach and/or verbs, etc.  Before me, they had a manager that had little or no technical background and I believe they&#8217;ve used that to their advantage to increase the team size and increase the cost.  No matter how I sketch it up on the white board and no matter how many of my close friends from the COBOL consulting world I refer to I can&#8217;t see how a one week task can be stretched into 5-6 months and 20+ FTEs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/8 queries in 0.015 seconds using memcached
Object Caching 297/298 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-22 21:17:16 -->