<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>CBF Consulting, Inc &#187; Services</title>
	<atom:link href="http://www.cbfcinc.com/category/services/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cbfcinc.com</link>
	<description>Providing creative, innovative, &#38; effective solutions for your manufacturing challenges.</description>
	<lastBuildDate>Sat, 20 Aug 2011 18:24:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Requirements Gathering services</title>
		<link>http://www.cbfcinc.com/2006/05/requirements-gathering-services/</link>
		<comments>http://www.cbfcinc.com/2006/05/requirements-gathering-services/#comments</comments>
		<pubDate>Sat, 06 May 2006 04:27:53 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Services]]></category>

		<guid isPermaLink="false">http://www.cbfcinc.com/?p=1</guid>
		<description><![CDATA[&#8220;Analysts report that as many as 71% of software projects that fail do so because of poor requirements management, making it the single biggest reason for project failure&#8220; &#8211; CIO magazine, Nov 15 2005 Requirements are the key to project success. Gathering good quality requirements is critical to the design and development of software that [...]]]></description>
			<content:encoded><![CDATA[<blockquote><p><strong>&#8220;</strong><em><strong>Analysts report that as many as 71% of software projects that fail do so because of poor requirements management, making it the single biggest reason for project failure</strong></em><strong>&#8220;</strong> &#8211; CIO magazine, Nov 15 2005</p></blockquote>
<p>Requirements are the key to project success. Gathering good quality requirements is critical to the design and development of software that must meet strict business and quality criteria.</p>
<p>CBF Consulting Requirements Analysis is intended to:</p>
<blockquote><p>Conduct a Qualitative Analysis of client pains and needs</p>
<p>Build credibility and trust to establish a working relationship</p>
<p>Demonstrate technical competency and industry-specific manufacturing knowledge</p>
<p>Facilitate cross-departmental discussion and derive consensus on the primary inefficiencies and challenges</p>
<p>Distinguish between workflow and organizational inefficiencies</p>
<p>Deliverables as part of the Assessment Process:</p>
<blockquote><p>1. Assessment Findings Summary</p>
<p>2. Executive Summary (Top challenges identified and possible methods of improvement)</p>
<p>3. Business Case</p>
<p>4. User Requirements  (Solution requirements to meet business objectives)</p>
<p>5. Solution alternatives and lowest-risk migration path</p>
<p>6. Project Plan outlining solution path at a high level</p>
<p>7. RFQ/RFP development</p>
<p>8. Vendor proposal review with client</p></blockquote>
<p>The assessment develops the short and long term strategies that ensure a solution is a process enabler of the company&#8217;s 21<sup>st</sup> Century business practices such as Lean manufacturing or Six Sigma.</p></blockquote>
<p>Point of clarity: Engagement tailored to each client needs. A qualification call with a CBF Consulting representative is required before final contract price.</p>
<p><span id="more-1"></span>CBF recommends:</p>
<p>The Human challenges are addressed through specific Lean, Six Sigma, TQM, and other techniques applied within the organization.</p>
<p>The Technical challenges are addressed through automation and solutions that specifically enable optimized process practices.</p>
<p>A gap often exists on software projects between the software delivered and the usersâ€™ real needs. This gap is a direct result of the processes used by development organizations to capture and gather requirements. Our process is designed to be not only cost effective, but rapidly produce results that define areas of improvement, and business value around those improvements. CBF Requirement assessments will:</p>
<ul>
<li>Identify the systems currently in place at each facility.</li>
<li>Identify the basic system architecture in place and how to integrate those systems to meet business and operational needs.</li>
<li>Identify the process flow, and the interactions with between personnel and the systems.</li>
<li>Identify the overall flow of information.</li>
<li>Make recommendations around feasibility, architecture and overall system design for the operational improvements as identified during the assessment.</li>
<li>Identify systems that support corporate goals and initiatives, and, at the same time, provide the needed functionality to support customer centric operations.</li>
<li>Understand the roadmap and strategy for how to move forward with a project.</li>
<li>Determine which systems investments will have real economic and operational effectiveness and paybacks and which will not.</li>
<li>Understand how information systems can help achieve business goals and objectives, implement key strategic action points, and address head-on some identified deficiencies.</li>
</ul>
<p><em><strong>A Standish Group study revealed that over two thirds of all software projects experience major problems and over one quarter outright fail. Building great software shouldn&#8217;t be this hard. A large portion of the problems in software development are a direct result of how requirements are captured and implemented.</strong></em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.cbfcinc.com/2006/05/requirements-gathering-services/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

