<?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>Numetrics &#187; Schedule</title>
	<atom:link href="http://www.numetrics.com/tag/schedule/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.numetrics.com</link>
	<description>Numetrics makes semiconductor product-development teams more productive</description>
	<lastBuildDate>Thu, 02 Feb 2012 07:25:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Re-Planning semiconductor design projects effectively</title>
		<link>http://www.numetrics.com/2009/08/03/re-planning/</link>
		<comments>http://www.numetrics.com/2009/08/03/re-planning/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 17:29:10 +0000</pubDate>
		<dc:creator>Numetrics</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Products]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Analysis]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Schedule]]></category>
		<category><![CDATA[Schedule Predictability]]></category>
		<category><![CDATA[semiconductor]]></category>
		<category><![CDATA[semiconductor design]]></category>

		<guid isPermaLink="false">http://202.142.150.34/numetricsblog/?p=23</guid>
		<description><![CDATA[
Summary: Re-planning a semiconductor design project is often inevitable as the program is underway. The key to effective, productive re-planning lies in understanding complexity, schedule and resources.

Change is inevitable. Economic factors, mergers and acquisitions, customer specification changes, management and strategy changes all affect project planning and execution. These factors create a need for re-planning IC [...]


Related posts:<ol><li><a href='http://www.numetrics.com/2011/03/03/optimal-team-sizes-for-chip-projects/' rel='bookmark' title='Permanent Link: Optimal Team Sizes for Chip Projects'>Optimal Team Sizes for Chip Projects</a> <small> What&#8217;s the optimal team size for a given IC...</small></li></ol>

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p><!--StartFragment--></p>
<blockquote>
<p class="MsoBodyText"><em><strong>Summary</strong>: Re-planning a semiconductor design project is often inevitable as the program is underway. The key to effective, productive re-planning lies in understanding complexity, schedule and resources.</em></p>
</blockquote>
<p class="MsoBodyText">Change is inevitable. Economic factors, mergers and acquisitions, customer specification changes, management and strategy changes all affect project planning and execution. These factors create a need for re-planning IC projects while they are ongoing.</p>
<p class="MsoBodyText">The key to re-planning is the same as for the original planning process: an understanding of <a href="http://202.142.150.34/numetricsblog/?p=12">complexity</a>, schedule and resources. Numetrics’ NMX-ERP can capture not only the starting characteristics of your design, but also updates as work is completed. This means that at any point during the design, you can calculate the work remaining and the resource and/or schedule implications of that.</p>
<p class="MsoBodyText">Re-planning is simply a process of updating the assumptions based on new information. From there it is a simple process to re-run the analysis, and to generate a new plan. This is easy not only because there is explicit support in the tools for re-planning and the management of multiple scenarios for a single design, but also because there is no need for data re-entry. Everything is built from the original plan, saving a great deal of time for your planners.</p>
<div class="wp-caption alignright" style="width: 353px"><a href="http://www.numetrics.com/images/product_schedulerisk.jpg"><img style="border: 1px solid black;" title="Risk Analyzer" src="http://www.numetrics.com/images/product_schedulerisk.jpg" alt="Schedule Risk Analyzer generates a comprehensive set of reports that quantitatively assess the underlying schedule risk, given the design’s complexity, staffing assigned to the project and target cycle-time." width="343" height="224" /></a><p class="wp-caption-text">Schedule Risk Analyzer generates a comprehensive set of reports that quantitatively assess the underlying schedule risk, given the design’s complexity, staffing assigned to the project and target cycle-time.</p></div>
<p class="MsoBodyText">The real implication of the re-planning capability is that when a change is proposed, you can <strong>quickly determine feasibility</strong>. For example, if marketing comes to you and says, “We need samples six weeks early for a key customer,” you can rapidly tell them what that means for resources. If additional resources are not available, you might consider scaling back product features to meet the new schedule. Alternatively, you may be forced to complete the design with fewer engineers than you had originally planned for. In such a case, you can quickly determine the best way to meet your business objectives with the new constraint—either reducing the feature set, or planning for a managed schedule slip.</p>
<p class="MsoBodyText">The net benefit of Numetrics’ re-planning tools is fact-based decision-making in a time of stress. Fact-based planning improves the quality of internal decisions, leading to a healthier business and happier employees. And that can’t be bad.</p>
<p><!--EndFragment--></p>


<p>Related posts:<ol><li><a href='http://www.numetrics.com/2011/03/03/optimal-team-sizes-for-chip-projects/' rel='bookmark' title='Permanent Link: Optimal Team Sizes for Chip Projects'>Optimal Team Sizes for Chip Projects</a> <small> What&#8217;s the optimal team size for a given IC...</small></li></ol></p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.numetrics.com/2009/08/03/re-planning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to minimize IC development schedule risk</title>
		<link>http://www.numetrics.com/2009/05/05/schedule-risk/</link>
		<comments>http://www.numetrics.com/2009/05/05/schedule-risk/#comments</comments>
		<pubDate>Tue, 05 May 2009 17:26:54 +0000</pubDate>
		<dc:creator>Numetrics</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Analysis]]></category>
		<category><![CDATA[Schedule Predictability]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Risk]]></category>
		<category><![CDATA[Schedule]]></category>
		<category><![CDATA[semiconductor]]></category>

		<guid isPermaLink="false">http://202.142.150.34/numetricsblog/?p=21</guid>
		<description><![CDATA[
 





Summary: Risk to IC development schedules can be minimized by comparing design plan assumptions with a database of historical industry designs and your company&#8217;s own history of completed projects to help you determine tradeoffs.

Simply put, schedule risk is the difference between the planned schedule, and the lessons of history. If you plan to finish [...]


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p><!--StartFragment--></p>
<blockquote>
<p class="MsoBodyText"><a href="http://www.freewebs.com/nakednews21110am/_42216354_5.jpg"><img class="alignleft" title="Base jumping " src="http://www.freewebs.com/nakednews21110am/_42216354_5.jpg" alt="" width="196" height="141" /></a><strong> </strong></p>
<p class="MsoBodyText">
<p class="MsoBodyText">
<p class="MsoBodyText">
<p class="MsoBodyText">
<p class="MsoBodyText">
<p class="MsoBodyText"><strong>Summary</strong>: Risk to IC development schedules can be minimized by comparing design plan assumptions with a database of historical industry designs and your company&#8217;s own history of completed projects to help you determine tradeoffs.</p>
</blockquote>
<p class="MsoBodyText">Simply put, <em>schedule risk</em><span> <strong>is the difference between the planned schedule, and the lessons of history</strong>. If you plan to finish a design with 20 engineers in 25 weeks, yet industry and corporate comparisons indicate that you need either 27 engineers or to lengthen the schedule to 34 weeks, you have identified schedule risk. </span></p>
<p class="MsoBodyText">The Numetrics tools can compare your design plan assumptions with all designs in the industry database, or with a subset based on powerful filters, or most powerfully with your own company’s history of completed design projects. If your plan is more aggressive than the results achieved historically, then you risk missing your schedule. <strong>High le</strong><strong>vels of schedule risk disempower your engineers</strong>, because the plan feels unrealistic to them. It also creates business risk, especially if schedule is critical. It doesn’t make sense to agree to a plan that requires productivity much greater than you have historically been able to deliver.</p>
<p class="MsoBodyText">On the other hand, it is reasonable to set a stretch goal that is a little better than your historical performance or the industry averages. That’s a stretch goal, and if the team believes it’s feasible, they will work hard to achieve it. This is a point <a href="http://www.numetrics.com/products/scheduleriskanalyzer.jsp">where risk is managed</a>, and the goals are achievable. Everyone likes to outperform their peers, but no one wants to be set up for failure.</p>
<p class="MsoBodyText">By using <a href="http://www.numetrics.com/products/overview.jsp">Numetrics’ tools</a> to analyze schedule risk, you can create a plan that is aggressive, but not so aggressive that it is doomed to fail. Such a plan is good for your team, and good for your business.</p>
<p><!--EndFragment--></p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.numetrics.com/2009/05/05/schedule-risk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ensuring schedule predictability for IC designs</title>
		<link>http://www.numetrics.com/2009/04/03/schedule-predictability/</link>
		<comments>http://www.numetrics.com/2009/04/03/schedule-predictability/#comments</comments>
		<pubDate>Fri, 03 Apr 2009 17:24:09 +0000</pubDate>
		<dc:creator>Numetrics</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Analysis]]></category>
		<category><![CDATA[Schedule Predictability]]></category>
		<category><![CDATA[ERP software]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[planning software]]></category>
		<category><![CDATA[Predictability]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[project management software]]></category>
		<category><![CDATA[risk assessment]]></category>
		<category><![CDATA[risk management]]></category>
		<category><![CDATA[Schedule]]></category>
		<category><![CDATA[semiconductor]]></category>
		<category><![CDATA[semiconductor design]]></category>
		<category><![CDATA[semiconductors]]></category>

		<guid isPermaLink="false">http://202.142.150.34/numetricsblog/?p=19</guid>
		<description><![CDATA[

Summary: Schedule predictability is the art and science of determining the completion date for your semiconductor IC project, based on a statistical model, validated across multiple designs.

When you plan a project, you are working with incomplete information. Organizational changes, specification changes, technical challenges and more conspire to make it difficult to accurately predict when your [...]


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p><!--StartFragment--><br />
<a href="http://www.nist.gov/public_affairs/licweb/images/wafer_closeup.jpg"><img class="alignright" title="Semiconductor wafer" src="http://www.nist.gov/public_affairs/licweb/images/wafer_closeup.jpg" alt="" width="241" height="203" /></a></p>
<blockquote>
<p class="MsoBodyText"><strong>Summary</strong>: Schedule predictability is the art and science of determining the completion date for your semiconductor IC project, based on a statistical model, validated across multiple designs.</p>
</blockquote>
<p class="MsoBodyText">When you plan a project, you are working with incomplete information. Organizational changes, specification changes, technical challenges and more conspire to make it difficult to accurately predict when your new product will be ready.</p>
<p class="MsoBodyText">Schedule predictability is the art and science of determining the completion date for your project, based on a statistical model, validated across multiple designs. The key ingredients are your design’s complexity, coupled with your resource plan. With these two inputs, Numetrics can <strong>significantly improve the accuracy </strong>of your schedule predictions. <a href="http://www.numetrics.com/about/customervideos.jsp">One customer</a> went from consistent overruns to accuracy within a few percent on the first designs they modeled in the Numetrics toolset.</p>
<p class="MsoBodyText">How is this possible? The core is the Numetrics ability:</p>
<ul>
<li>To understand which factors drive <a href="http://202.142.150.34/numetricsblog/?p=12">complexity</a></li>
<li>To create a normalized characterization of your design that allows comparison with others.</li>
</ul>
<p class="MsoBodyText">When we compare your proposed design with historical productivity and schedule information, we can statistically determine the expected schedule for your new project. The accuracy of the model is enhanced by our industry database of over 1200 designs, coupled with specific information from your company’s historical project record.</p>
<p class="MsoBodyText">The result is a <strong>robust, realistic prediction of the schedule</strong>, based on</p>
<ul>
<li>Complexity</li>
<li>Resource availability and</li>
<li>Historical data.</li>
</ul>
<p class="MsoBodyText">The value is a greatly enhanced ability to meet your market windows, time and time again.</p>
<p><!--EndFragment--></p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.numetrics.com/2009/04/03/schedule-predictability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Excellence in Semiconductor Design Productivity</title>
		<link>http://www.numetrics.com/2009/02/23/productivity-excellence/</link>
		<comments>http://www.numetrics.com/2009/02/23/productivity-excellence/#comments</comments>
		<pubDate>Mon, 23 Feb 2009 17:30:24 +0000</pubDate>
		<dc:creator>Numetrics</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Case Studies]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Productivity]]></category>
		<category><![CDATA[Resource Planning]]></category>
		<category><![CDATA[Schedule]]></category>
		<category><![CDATA[Schedule Predictability]]></category>
		<category><![CDATA[semiconductor]]></category>
		<category><![CDATA[semiconductor design]]></category>

		<guid isPermaLink="false">http://202.142.150.34/numetricsblog/?p=25</guid>
		<description><![CDATA[
Summary: Everybody wants to increase productivity. But there’s no free lunch: assigning too few resources to a project increases stress and creates schedule risk.

Productivity excellence is the process of maximizing productivity by setting the most aggressive targets that are still achievable. Achievable targets mean that you will meet your schedule goals. Aggressive means that everyone [...]


No related posts.

Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p><!--StartFragment--></p>
<blockquote>
<p class="MsoBodyText"><em><strong>Summary</strong>: Everybody wants to increase productivity. But there’s no free lunch: assigning too few resources to a project increases stress and creates schedule risk.</em></p>
</blockquote>
<p class="MsoBodyText"><em>Productivity excellence </em><span>is the process of maximizing productivity by setting the most aggressive targets that are still achievable. </span><em>Achievable targets</em><span> mean that you will meet your schedule goals. </span><em>Aggressive</em><span> means that everyone will be working really hard to get there. The combination ensures that your products will come to market at the earliest possible time, given hard, focused work from a team no larger than you need. </span></p>
<p class="MsoBodyText">The value of productivity excellence is felt in three main areas.</p>
<ul>
<li>First, in these tough economic times, you can be sure you haven’t spent money on resources that are not essential to your project.</li>
<li>Second, you have set the bar appropriately for an ambitious, capable engineering team.</li>
<li>Third, you have controlled schedule risk, and minimized the likelihood of a schedule slip, with potentially disastrous implications for revenues and market share.</li>
</ul>
<p class="MsoBodyText">At the end of the day, productivity excellence means<strong> meeting your business goals efficiently</strong>, with a motivated workforce doing their best to meet an aggressive, but still feasible plan. Take a look at our customer <a href="http://www.numetrics.com/downloads/testimonials/innovasic_case_study.pdf" target="_blank">case study involving Innovasic</a>, which maximized its design throughput by benchmarking<br />
microcontroller development team productivity.</p>
<p><!--EndFragment--></p>


<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://mitcho.com/code/yarpp/'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.numetrics.com/2009/02/23/productivity-excellence/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

