<?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>Cellphone Gadget and Technology News &#187; Robotics</title>
	<atom:link href="http://www.alfarnaterural.com/category/robotics/feed" rel="self" type="application/rss+xml" />
	<link>http://www.alfarnaterural.com</link>
	<description></description>
	<lastBuildDate>Thu, 29 Jul 2010 23:06:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Craftsmanship: Its Cultural and Managerial Implications</title>
		<link>http://www.alfarnaterural.com/craftsmanship-its-cultural-and-managerial-implications.cfm</link>
		<comments>http://www.alfarnaterural.com/craftsmanship-its-cultural-and-managerial-implications.cfm#comments</comments>
		<pubDate>Wed, 28 Jul 2010 19:10:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Robotics]]></category>
		<category><![CDATA[Craftsmanship]]></category>
		<category><![CDATA[Managerial Implications]]></category>

		<guid isPermaLink="false">http://www.crawbot.co.cc/?p=2404</guid>
		<description><![CDATA[&#8220;Craftsmanship = (Knowledge + Experience + Attitude) X Success&#8221;- Bryce&#8217;s LawINTRODUCTIONThe purpose of this essay is to review the state of craftsmanship in the 21st century, determine if it still has merit in today&#8217;s corporate culture, and if so, devise recommendations for perpetuating it.BackgroundAlthough there are no definitive numbers to prove so, there is a [...]]]></description>
			<content:encoded><![CDATA[<div><br/><br/>&#8220;Craftsmanship = (Knowledge + Experience + Attitude) X Success&#8221;<br/><br/>- Bryce&#8217;s Law<br/><br/>INTRODUCTION<br/><br/>The purpose of this essay is to review the state of craftsmanship in the 21st century, determine if it still has merit in today&#8217;s corporate culture, and if so, devise recommendations for perpetuating it.<br/><br/>Background<br/><br/>Although there are no definitive numbers to prove so, there is a general consensus that craftsmanship has been in decline in North America since the 1980&#8217;s. This era marked the beginning of stiff worldwide competition in just about every industrial sector, led predominantly by Japan and Germany. Since then, the European community has been unified and become a formidable foe, as has the rest of Asia. In response, American corporations began a policy of belt-tightening, downsizing, outsourcing, and use of new technology (e.g., robotics) all of which played an important part in the decline of labor unions during this period. This also led to the implementation of several corporate cost-cutting measures, including the reduction of employee education/training. In-house training and schools to develop employee skills were sharply curtailed, if not eliminated completely. Consequently, this led to a noticeable decline in human skills and a change in attitude by employees towards their work, thereby becoming more apathetic. It could be argued this also led to an increase in defects in workmanship which triggered the interest in Quality Assurance concepts and techniques beginning in the 1980&#8217;s.<br/><br/>Today, the prevailing attitude in the workplace appears to be less focused on what is to be produced, and more on the time needed to produce it. In other words, employees are more focused on their paycheck as opposed to their work product. Undoubtedly this has contributed to the current trend of micromanagement (a Theory X dictatorial style of management).<br/><br/>As such, an interesting dichotomy has emerged between management and workers:<br/><br/><br/><br/>Management &#8211; believes there is no employee loyalty, dedication or professionalism.<br/><br/>Employees &#8211; lack faith in management&#8217;s judgment and are suspicious of business ethics. Believes management is more concerned with the bottom-line as opposed to people.<br/><br/><br/><br/>Whereas micromanagement is the dominant style of management in today&#8217;s workplace, workers generally want more freedom and participation in the decision making process. But instead of worker empowerment, there is more of an inclination by management to dominate and more closely supervise workers. This growing rift between management and workers, along with changes in corporate socioeconomic conditions, has led to the decline in craftsmanship.<br/><br/>In the decades prior to the 1980&#8217;s, craftsmanship flourished primarily because workmen were well trained, they were empowered to perform their work accordingly, and the work produced was considered a reflection of the worker&#8217;s personal character. But if continuous employee improvement is discouraged (such as the reduction or elimination of employee training), self-initiative is prohibited (through micromanagement), and there is a general lack of trust between management and workers, then the decline of craftsmanship was inevitable.<br/><br/>The term &#8220;craftsmanship&#8221; is still bandied about, but more for marketing purposes than anything else. Most of the true craftsmen of this country have long since retired, but there are still a few practicing their craft either at home or in small-to-medium sized businesses where it is appreciated.<br/><br/>Why the interest in craftsmanship now? Due to heightened awareness by the media in such things as fashion, food, and architecture, there appears to be a growing trend in prestige consumer products. The fact that companies advertise their products are produced with &#8220;high craftsmanship&#8221; is indicative the consumer appreciates superior work products. There is also a growing realization that superior goods will last longer.<br/><br/>CRAFTSMANSHIP DEFINED<br/><br/>Before we go further, let&#8217;s examine what exactly we mean by the term &#8220;craftsmanship&#8221;:<br/><br/>&#8220;The practice and pursuit of excellence in building/delivering superior work products by workers.&#8221;<br/><br/>This implies craftsmanship is a universally applicable concept for any field of endeavor, be it producing a product or delivering a service. Basically, it is a commitment to excellence which is most definitely not the same as quality. Quality simply relates to the absence of errors or defects in the finished product or service. In other words, finished goods operate according to their specifications (customers get precisely what they ordered). Although quality is certainly an element of craftsmanship, the emphasis on &#8220;superior work products&#8221; means the worker wants to go beyond the status quo and is constantly looking for new and imaginative ways to produce superior results. This suggests the craftsman is personally involved with the work products and treats them as an extension of his/her life.<br/><br/>Craftsmanship can be found in either the overall work process or a section of it. For example, there are craftsmen who are intimate with all facets of building furniture, such as a table, a chair or desk, and can develop the product from start to finish. However, as products grow in complexity, it becomes difficult to find people suitably qualified to build them from the womb to the tomb. Consider military weapons alone, such as the complicated ships, tanks, and airplanes we now use, with thousands or millions of parts to assemble. Such complexity makes it virtually impossible for a single person to have the expertise to build the whole product. The same is true in the service sector where different types of expertise and capabilities may be required. In other words, craftsmen have a specific scope of work. The scope of work may relate to other types of craftsmen through a chain of work dependencies, e.g., Craftsmen A, B and C concentrate on separate subassemblies which are eventually joined into a single product.<br/><br/>Craftsmanship is also a human trait. Some might argue a computer or industrial robot can produce quality products and are, therefore, craftsmen. However, we must remember these devices are programmed by human beings in accordance with the rules of the craftsman. As such, they are nothing more than a tool of the craftsman.<br/><br/>ATTRIBUTES<br/><br/>Craftsmen can be characterized by a variety of adjectives, such as: patient, determined, curious, thorough, expert, methodical, focused, self-starter, and pays attention to detail. More specifically though, craftsmanship requires the use of:<br/><br/><br/><br/>TOOLS &#8211; In addition to the hand, the foot, and the eye, craftsmen must be knowledgeable in the use of other mechanical devices for his/her area of specialty.<br/><br/>THE MIND &#8211; Requiring specific knowledge, experience and judgment to implement the work product. This brings up an important point: education alone is not sufficient to be recognized as a craftsman; it also includes a record of proven success to demonstrate the worker knows how to apply the education.<br/><br/>In terms of education, there are two parts to consider: initial education, either learned through formal training (e.g., college and vocational school diplomas) or through on-the-job experience (&#8221;School of Hard Knocks&#8221;), and; continuous improvement, representing ongoing training/education through such things as certification, supplemental training, studying industry periodicals and books, or participation in industry trade groups. Although initial education is certainly important, continuous improvement is the earmark of a craftsman.<br/><br/>The craftsman is knowledgeable in all facets of the methodology for his/her line of work. For our purposes here, a methodology refers to &#8220;Who&#8221; is to perform &#8220;What,&#8221; &#8220;When,&#8221; &#8220;Where,&#8221; &#8220;Why,&#8221; and &#8220;How&#8221; (aka &#8220;5W+H&#8221;). As such, the craftsman must be fully cognizant of the work breakdown structure, the dependencies between steps, deliverables, along with the various techniques<br />
and tools used throughout the methodology. From this, he/she can devise a reliable estimate of the costs needed to produce the work product, as well as schedule the time to deliver it.<br/><br/>A true craftsman is so knowledgeable about the work product and the methodology to produce it he/she can even advise other professionals in how to modify/improve them, such as architects and engineers (including industrial engineers).<br/><br/>THE SPIRIT &#8211; This represents the personal desire to not only see the job performed correctly, but better than others. This means the craftsman is personally committed to producing superior work products simply because he/she views his/her professional life as an extension of his/her personal life. As such, the craftsman must be empowered to make certain decisions on how to build/deliver the work product in order to achieve a sense of ownership. From this perspective, techniques such as micromanagement is not conducive for encouraging a program of craftsmanship.<br/><br/>A craftsman sweats over the smallest details in producing the work product and is well aware of the risks involved with skipping steps or doing something out of sequence. Such commitment to producing superior results suggests the craftsman possesses a higher work ethic than others, and in all likelihood possesses higher moral values due to his/her fastidious attention to &#8220;Right and Wrong.&#8221;<br/><br/><br/><br/>To summarize, the elements of craftsmanship can perhaps be best expressed using the following formula:<br/><br/>Craftsmanship = (Knowledge + Experience + Attitude) X Success<br/><br/>Knowledge &#8211; refers to both the person&#8217;s initial and ongoing education.<br/><br/>Experience &#8211; refers to the person&#8217;s application of his/her knowledge.<br/><br/>Attitude &#8211; refers to the person&#8217;s sense of professionalism and dedication to his/her craft.<br/><br/>Success &#8211; refers to both customer and company satisfaction of the person&#8217;s work.<br/><br/>WHO IS AFFECTED BY CRAFTSMANSHIP?<br/><br/>There are three interrelated parties involved with craftsmanship:<br/><br/>1. The Worker &#8211; charged with producing the work product.<br/><br/>2. The Company &#8211; which provides for a program of craftsmanship.<br/><br/>3. The Consumer &#8211; to purchase and express satisfaction with the work product.<br/><br/>Without any one of these elements, craftsmanship breaks down. For example:<br/><br/><br/><br/>It is not sufficient for a worker to simply want to be a craftsman; if the company implements an unsuitable corporate culture, craftsmanship will not be allowed.<br/><br/>It is not sufficient for the company to simply want to promote craftsmanship; if workers do not exhibit self-initiative to produce superior results, craftsmanship will not flourish. After all, &#8220;You cannot make a silk purse out of a sow&#8217;s ear.&#8221;<br/><br/>It is not sufficient for the consumer to simply say they want products built by craftsman; they must create the demand for such products and offer feedback in terms of their satisfaction with them.<br/><br/><br/><br/>IMPLEMENTING CRAFTSMANSHIP<br/><br/>To embrace craftsmanship, a company must devise a suitable corporate culture. This includes the following elements:<br/><br/><br/><br/>EMPOWERMENT OF THE WORKER to make certain decisions regarding development of the work product. This is often described as managing from the &#8220;bottom-up&#8221; as opposed to just &#8220;top-down&#8221; which is conducive to a Theory Y form of management philosophy. Under this scenario, the worker is given assignments by management and is held accountable for delivery. In turn, decisions regarding the development of the work product are delegated to the worker who is responsible for the preparation of an estimate and schedule to deliver the work product for approval by management. In other words, the worker is allowed more freedom to manage his/her own affairs and is not under the constant scrutiny of management. Further, the worker is allowed to offer feedback to management for improving products and work conditions. Last but not least, workers are recognized for outstanding achievement.<br/><br/>CREATION OF A MORE DISCIPLINED AND ORGANIZED WORK ENVIRONMENT promoting a more professional attitude amongst the workers. Ideally, the creation of an environment where workers can focus on their work with minimal distractions and take pleasure in coming to work (a sort of &#8220;home away from home&#8221;). Inevitably, this will include a redefinition of acceptable forms of dress and behavior, grooming, form of address, and office appearance.<br/><br/>This also includes a corporate position of zero tolerance in defects and inferior workmanship and the adoption of standard methodologies thereby defining best practices for building/delivering work products. Such standardization provides consistency in deliverables and allows for the inter-changeability of workers on different assignments. For example, suppose a worker becomes ill in the middle of an assignment and is unable to work on it further. Standard methodologies provides the means to allow another worker to complete the assignment in the same manner as the first worker. Also, standard methodologies provides an excellent training vehicle for young workers to learn and grow to become craftsmen.<br/><br/>PROMOTE A PROGRAM OF CONTINUOUS IMPROVEMENT to sharpen worker skills, stay abreast of industrial developments, and seek new ways of improving work products and the methodologies used to produce them. This will undoubtedly result in the reintroduction of in-house training and schools, as well as participation in certification programs and trade groups.<br/><br/>ESTABLISHMENT OF THREE CLASSES OF WORKERS to denote the level of expertise. Historically, this has been referred to as &#8220;Apprentices&#8221; (novices requiring training), &#8220;Intermediate&#8221; (educated and experienced, but not yet expert), and &#8220;Master&#8221; (expert craftsman). Such a designation of craftsmen is needed not to create barriers but to help establish a career path and mentoring program whereby the more experienced workers provide guidance to those less experienced or knowledgeable.<br/><br/>ESTABLISH LINK BETWEEN WORKERS-PRODUCTS-CUSTOMERS to establish a feedback loop to judge satisfaction with a specific product and to the exact worker(s) who produced it. It is impossible to recognize or reprimand workers without such a loop. For example, without it, customers may complain or compliment the company on the work product, yet management is at a loss as to who produced it. Ideally, a system should be set in place to provide for such analysis thereby providing a convenient means to monitor worker performance.<br/><br/><br/><br/>The premise behind affecting the corporate culture in this regards is to treat workers like professionals who should act as such in return.<br/><br/>BENEFITS &#038; BYPRODUCTS<br/><br/>From a corporate viewpoint, is true craftsmanship the right path to follow? Does it really add value to the corporate bottom-line or not? First, it is a myth that work products produced by craftsmen costs more than those produced by less skilled workers. For products of the same class, it actually costs more to produce products using less skilled workers; after all, they do not have the same level of knowledge and experience that veteran craftsman have to produce it and, as such, craftsman can produce it faster with fewer mistakes. The cost for an experienced craftsman will undoubtedly be higher than novice workers, but savings will be realized simply by expedited development time and fewer mistakes (thereby causing the elimination of corrections or replacements). Further, superior work products have the added nuance of developing satisfied customers representing repetitive business as well as referrals.<br/><br/>Comparing the development cost of different classes of products is like comparing apples and oranges, it is simply not an accurate comparison. For example, the cost to build a luxury automobile will be substantially different than the cost to develop an economical subcompact. But if the product is of the same fundamental class, the craftsman will produce it faster and better than the novice (and at less cost).<br/><br/>So<br />
me of the byproducts realized from embracing a corporate program of craftsmanship includes:<br/><br/><br/><br/>A work environment more conducive for building superior work products.<br/><br/>Employees develop a better sense of self-worth which promotes loyalty, dedication, and professionalism.<br/><br/>Standard methodologies promote consistent and measurable work products, the inter-changeability of workers on assignments (as opposed to developing dependencies on individual worker expertise), provides a career path for younger workers, and brings order out of chaos. Also, standard practices improves communications, thereby promoting cooperation and teamwork.<br/><br/><br/><br/>CONCLUSION<br/><br/>A program of true craftsmanship adds value primarily to three parties:<br/><br/><br/><br/>The customer &#8211; Satisfaction with the product means the consumer believes his money was well spent and takes pride in it, thereby encouraging others to purchase the same, thereby benefiting the company.<br/><br/>The worker &#8211; believes he/she is leading a worthy and meaningful life, thus promoting self-esteem and employee development.<br/><br/>The company &#8211; receives fewer customer complaints and returned products that are defective requiring replacement or rework. Workers who take pleasure in their work are less likely to switch jobs thereby causing production interruptions. Harmony in the workplace also promotes improved communications, teamwork and corporate loyalty. In other words, craftsmanship adds to the bottom-line of a business.<br/><br/><br/><br/>But make no mistake, the consumer is the impetus for craftsmanship. As long as customers accept inferior workmanship without complaint, companies will continue to produce shoddy work products in the least expensive means possible and workers will not be allowed to produce superior products.<br/><br/>The outcry for craftsmanship must begin with the customer.<br/><br/>If you would like to discuss this with me in more depth, please do not hesitate to send me an e-mail at timb001@phmainstreet.com<br/><br/>NOTES<br/><br/>1 &#8211; The author wants to acknowledge and thank Mario Guertin of Painting in Partnership for his generous input.<br/><br/>2 &#8211; In an Internet survey conducted in December 2007, random people were asked,<br/><br/>&#8220;In your opinion, do you believe Craftsmanship in general is in decline in North America?&#8221;<br/><br/>- YES &#8211; Craftsmanship is in decline., 25 votes, 81.00%<br/><br/>- NO &#8211; Craftsmanship is not in decline., 6 votes, 19.00%<br/><br/>REFERENCE<br/><br/>1 &#8211; Craftsmanship: the Meaning of Life by Tim Bryce<br/><br/>&#8220;PRIDE&#8221; Special Subjects Bulletin #6, January 10, 2005<br/><br/></div>
]]></content:encoded>
			<wfw:commentRss>http://www.alfarnaterural.com/craftsmanship-its-cultural-and-managerial-implications.cfm/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Methodologies versus Techniques and Tools</title>
		<link>http://www.alfarnaterural.com/methodologies-versus-techniques-and-tools.cfm</link>
		<comments>http://www.alfarnaterural.com/methodologies-versus-techniques-and-tools.cfm#comments</comments>
		<pubDate>Wed, 30 Jun 2010 17:39:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Robotics]]></category>

		<guid isPermaLink="false">http://www.crawbot.co.cc/?p=2402</guid>
		<description><![CDATA[&#8220;Having a Project Management system without a methodology is likeattaching a speedometer to an orange crate; it measures nothing.&#8221;- Bryce&#8217;s LawINTRODUCTIONThe term &#8220;methodology&#8221; is being bandied about by just about everysoftware development vendor and consultant imaginable. You would behard pressed to find a vendor who, in addition to their usual tooloffering, doesn&#8217;t promise a methodology [...]]]></description>
			<content:encoded><![CDATA[<div><br/><br/>&#8220;Having a Project Management system without a methodology is like<br/><br/>attaching a speedometer to an orange crate; it measures nothing.&#8221;<br/><br/>- Bryce&#8217;s Law<br/><br/>INTRODUCTION<br/><br/>The term &#8220;methodology&#8221; is being bandied about by just about every<br/><br/>software development vendor and consultant imaginable. You would be<br/><br/>hard pressed to find a vendor who, in addition to their usual tool<br/><br/>offering, doesn&#8217;t promise a methodology to solve all of your development<br/><br/>problems. But like many things in this industry, the terminology is<br/><br/>getting sloppy and it is becoming apparent the true definition of<br/><br/>&#8220;methodology&#8221; is being bastardized.<br/><br/>IN THE BEGINNING<br/><br/>The term &#8220;methodology&#8221; became popular in information systems in the<br/><br/>early 1970&#8217;s, initially as a response to the question, &#8220;What is it?&#8221; Milt<br/><br/>Bryce first applied the term to systems development in 1971, to describe his<br/><br/>Information Systems Engineering process. Bryce referred to &#8220;methodology&#8221; as<br/><br/>a process which ends with the delivery of a product or a completely defined<br/><br/>result.<br/><br/>Later on, during the structured programming movement, a different<br/><br/>interpretation of the word emerged from software gurus such as Yourdon,<br/><br/>Gane/Sarson, Orr, Finklestein, Martin, Warnier/Orr, etc. Instead of<br/><br/>describing the overall process by which development occurs, the structured<br/><br/>programming people began to use the term &#8220;methodology&#8221; to describe their<br/><br/>techniques for designing software (e., functional decomposition, data<br/><br/>driven design, object oriented design, etc.). Consequently, software<br/><br/>development tools, which represent automated extensions of these techniques,<br/><br/>began to tout their products as &#8220;methodology&#8221; enablers.<br/><br/>This division in the use of the term &#8220;methodology&#8221; is a major source<br/><br/>of confusion to the industry. Not all &#8220;methodologies&#8221; are created equally.<br/><br/>There are fundamentally two interpretations: as a term referring to the<br/><br/>&#8220;process&#8221; by which work is performed, and; as a term referring to a<br/><br/>particular design technique. To truly understand &#8220;methodologies&#8221; you<br/><br/>must know the difference.<br/><br/>METHODOLOGIES AS &#8220;PROCESS MANAGEMENT&#8221;<br/><br/>We at MBA define a methodology as, &#8220;a process which ends with the delivery<br/><br/>of a product or a completely defined result.&#8221; Under this perspective,<br/><br/>a methodology defines the &#8220;5-W&#8217;s&#8221;; it defines WHO, is to perform WHAT work,<br/><br/>WHEN, WHERE, and WHY. If this sounds like an engineering/manufacturing<br/><br/>process, it is. MBA contends information resources can be designed and<br/><br/>developed in the same manner as any other product. Here, a methodology<br/><br/>defines the division of labor and synchronization of work effort. With<br/><br/>this approach, the development effort is divided into smaller more<br/><br/>manageable pieces just as in an assembly line process. Construction<br/><br/>projects represent another example (e,g., shipbuilding, office/home<br/><br/>construction, etc.), where the work is carefully divided into stages with<br/><br/>precedent relationships.<br/><br/>METHODOLOGY AS A DESIGN TECHNIQUE<br/><br/>As opposed to the &#8220;5-W&#8217;s&#8221; interpretation by MBA, a methodology<br/><br/>supported by the software design people defines HOW a particular task<br/><br/>is to be performed. For example, the forte of design techniques such<br/><br/>as &#8220;object oriented programming,&#8221; &#8220;structured programming,&#8221; or &#8220;information<br/><br/>engineering&#8221; is on HOW to accomplish specific activities of work. From<br/><br/>this context, the term &#8220;methodology&#8221; is a misnomer which should be<br/><br/>replaced by the term &#8220;technique,&#8221; a more apt description.<br/><br/>Techniques may differ from company to company, and there is not always<br/><br/>a single way to perform a task. For example, in the automotive industry,<br/><br/>fenders have always been a part of the car, but they have not always been<br/><br/>attached the same way. Originally, fenders were bolted to the body of the<br/><br/>car. Years later, an automotive worker welded the fender to the car. Today,<br/><br/>welding robotics perform the task. The task, attaching the fender to the car,<br/><br/>hasn&#8217;t changed, but the techniques to do it have. Improved techniques can<br/><br/>mean realizing the same result with savings in time and money.<br/><br/>The same is true in the information systems world. Whereas there are<br/><br/>generic stages of work for designing and developing a system, there are a<br/><br/>multitude of techniques for performing the work. For example, there are<br/><br/>significant differences between &#8220;structured programming&#8221; and &#8220;object<br/><br/>oriented programming,&#8221; yet the result is fundamentally the same, the<br/><br/>development of an executable program. The difference is the chosen approach<br/><br/>of implementation (there are pros and cons for both techniques). Whereas<br/><br/>&#8220;Software Engineering&#8221; represents a phase of work in a development project,<br/><br/>&#8220;structured programming&#8221; and &#8220;object oriented programming&#8221; represent<br/><br/>techniques that can be used to perform the phase.<br/><br/>Does this mean there are overlaps or conflicts in the use of the<br/><br/>different types of &#8220;methodologies&#8221;? Not quite. But to appreciate the<br/><br/>difference, one must understand the concept of &#8220;Productivity&#8221; (as<br/><br/>we have discussed in other &#8220;PRIDE&#8221; Special Subject Bulletins).<br/><br/>PRODUCTIVITY = EFFECTIVENESS X EFFICIENCY<br/><br/>Productivity is not simply a matter of how fast a task can be performed,<br/><br/>it&#8217;s a matter of performing the right task at the right time. This is what<br/><br/>underlies the concept of productivity. Whereas &#8220;efficiency&#8221; concentrates<br/><br/>on speed of delivery, &#8220;effectiveness&#8221; is concerned with doing the right<br/><br/>thing at the right time; the two are not synonymous. For example, performing<br/><br/>a weld using robotics may be a far more efficient means than performing the<br/><br/>task manually, but it is useless if you are welding the wrong thing. There<br/><br/>is nothing more unproductive than to build something efficiently that should<br/><br/>never have been built in the first place. Zero percent effectiveness<br/><br/>times 1000% efficiency equals zero productivity.<br/><br/>A true methodology addresses the effectiveness side of the equation<br/><br/>(Who, What, When, Where, Why), and a technique addresses the efficiency<br/><br/>side (How to). Whereas a methodology defines the work environment, the<br/><br/>technique defines how the work is to be performed. The two are obviously<br/><br/>complementary and one does not eliminate the need for the other. But<br/><br/>comparing one with another is like comparing apples with oranges, they are<br/><br/>simply not the same.<br/><br/>FACTORY CONCEPT<br/><br/>Within an engineering/manufacturing facility you will typically find:<br/><br/> <br/><br/>An Assembly Line where products are developed in stages.<br/><br/> <br/><br/>Production Control monitoring the assembly line for delays or<br/><br/>accelerations in production.<br/><br/> <br/><br/>Techniques for performing work.<br/><br/> <br/><br/>Tools providing mechanical leverage.<br/><br/> <br/><br/>These elements can be found in any development environment, including<br/><br/>the IT world. What is interesting is the relationship between the elements:<br/><br/>ASSEMBLY LINE &#8211; at the heart of the factory is the Assembly Line process<br/><br/>where products are developed in stages by workers with different skills<br/><br/>for the different stages of work. In IT terminology, this is the<br/><br/>&#8220;methodology.&#8221;<br/><br/>PRODUCTION CONTROL monitors the assembly line using dials and gauges.<br/><br/>Production Control is not an entity by itself; it is totally dependent on<br/><br/>the existence of the Assembly Line in order to measure performance.<br/><br/>In IT terminology, this is Project Management. However, this brings up<br/><br/>an important point; without a de<br />
fined methodology, Project Management is<br/><br/>an exercise in futility. It measures nothing. Only if a defined mode<br/><br/>of operation exists can dials and gauges be effectively applied.<br/><br/>TECHNIQUES, as mentioned, represent ways for performing specific tasks<br/><br/>(&#8221;how to&#8221;). A variety of techniques may be used on the Assembly Line.<br/><br/>Obviously, it would be counter-productive to use a technique at the wrong<br/><br/>time on the Assembly Line. This means the effective use of techniques<br/><br/>is dependent upon a defined Assembly Line.<br/><br/>TOOLS implement techniques. Tools provide mechanical leverage for performing<br/><br/>a specific task. In this sense, it is an extension of a technique, and like<br/><br/>the technique, tools must be deployed at the proper locations along the<br/><br/>Assembly Line. This is the reason why many software engineering tools are failing;<br/><br/>not because they are bad tools, but simply because companies have not defined<br/><br/>their Assembly Lines (methodologies) and haven&#8217;t specified when the techniques<br/><br/>and tools are to be used.<br/><br/>What this highlights is that a methodology is the focal point within a<br/><br/>development environment. Without a defined methodology, Project Management<br/><br/>will be ineffective, and design techniques and software development tools<br/><br/>will be misapplied. Productivity will be low.<br/><br/>METHODOLOGY CRITERIA<br/><br/>Since a methodology is critical to the success or failure of a<br/><br/>development environment, it is important to be able to differentiate<br/><br/>between a methodology, technique and tool. The generic properties of<br/><br/>a methodology include:<br/><br/>1. DEFINES THE STAGES OF WORK (a work breakdown structure normally<br/><br/>consisting of phases, activities and tasks). The stages of work<br/><br/>defines the &#8220;5-W&#8217;s&#8221; (Who, What, When, Where, Why). The synchronization<br/><br/>of work is needed to define direction and is provided by the precedent<br/><br/>relationships between the various steps in the methodology. Defined<br/><br/>duties and responsibilities provides insight for performing the work<br/><br/>and methodology standardization improves communications between workers.<br/><br/>2. MEASURABLE &#8211; The stages of work can be evaluated in terms of how long<br/><br/>it takes to perform them and how much they cost to perform. Further,<br/><br/>criteria is provided to substantiate completion of deliverables<br/><br/>thereby assuring the development of a quality product.<br/><br/>3. TECHNIQUE AND TOOL INDEPENDENT &#8211; various techniques and tools can be<br/><br/>deployed as required.<br/><br/>4. PROJECT MANAGEMENT INDEPENDENT &#8211; can work with or without a Project<br/><br/>Management system. For example, an Assembly Line can still function<br/><br/>without Production Control, but not vice versa.<br/><br/>If the methodology you are evaluating does not match this simple<br/><br/>criteria, it is not a methodology and probably some form of technique.<br/><br/>TYPES OF METHODOLOGIES<br/><br/>Of the &#8220;process management&#8221; methodologies, there are fundamentally<br/><br/>three types:<br/><br/>LINEAR &#8220;WATERFALL&#8221; METHODOLOGY (sometimes referred to as &#8220;Life Cycle&#8221;) -<br/><br/>this is perhaps the best known of the methodologies. Various interpretations<br/><br/>of this approach have been published for several years, both commercially and<br/><br/>public domain. Fundamentally, it a sequential process where the design of an<br/><br/>application moves from the general to the specific; for example:<br/><br/> FEASIBILITY STUDY DESIGN  PROGRAMMING TESTING REVIEW <br/><br/>The problem with this approach has been its orientation towards computer<br/><br/>software and not on total systems. But the biggest pitfall has been its<br/><br/>sequential orientation which tends to prohibit parallel development.<br/><br/>SPIRAL DEVELOPMENT &#8211; this approach is based on the premise the development<br/><br/>process is evolutionary in nature (which, in fact, it is). The concept is<br/><br/>to initially design a program, then add additional phases of work to<br/><br/>constantly revise the program to enhance its features. From a Project<br/><br/>Management perspective, the problem with this approach is that the project<br/><br/>never ends.<br/><br/>PRODUCT DEVELOPMENT &#8211; as proposed by MBA, this approach uses elements of<br/><br/>the other two methodologies, with the added nuance of using a product<br/><br/>orientation as the basis for the development process. Under this approach,<br/><br/>a system is viewed as a product. Consequently, it can be designed in the same<br/><br/>manner as any other product. For example, when a product is being designed<br/><br/>(such as an automobile), the overall assemblies are first designed (such as<br/><br/>the body, chassis, engine, etc.). After this phase, each assembly is designed<br/><br/>by teams of engineers who refine the design of each assembly into sub-assemblies<br/><br/>and parts. All of this occurs as parallel phases. MBA advocates the same<br/><br/>approach for systems development. An initial phase is used to design<br/><br/>the architecture of the system, followed by succeeding parallel phases to<br/><br/>refine the design. This is the best approach for parallel development.<br/><br/>INDUSTRIAL ENGINEERING<br/><br/>In an engineering/manufacturing environment, the responsibility for<br/><br/>defining the work environment is normally delegated to an &#8220;Industrial<br/><br/>Engineer.&#8221; It is the Industrial Engineer&#8217;s responsibility to define the<br/><br/>Assembly Line, the types of people and skill sets required to perform the<br/><br/>work, and the deployment of techniques and tools to be used on the<br/><br/>Assembly Lines. Industrial Engineering is a recognized profession in<br/><br/>the engineering/manufacturing world. A comparable position is required<br/><br/>in the information systems world.<br/><br/>Unfortunately, most development methodologies purchased today are<br/><br/>evaluated by the wrong people. Quite often, the evaluation of a methodology<br/><br/>is delegated to programmers or technicians who are more enamored with the<br/><br/>latest software design technique or tool than in defining a managed development<br/><br/>environment. This is like Henry Ford allowing the UAW to invent the concept<br/><br/>of the Assembly Line. They simply have the wrong perspective. Someone who<br/><br/>specializes in installing headlights doesn&#8217;t necessarily have the expertise to<br/><br/>develop Assembly Lines. True, their input can be helpful when evaluating a<br/><br/>technique or a tool, but not for an overall development environment. This is<br/><br/>one area where American businesses have abdicated complete control.<br/><br/>CONCLUSION<br/><br/>There are essentially two interpretations for the term &#8220;methodology&#8221; in<br/><br/>the IT industry. One interpretation is as a disciplined process for developing<br/><br/>information resources, from inception to conclusion. Another is as a technique<br/><br/>for performing a specific task of work. These are subtle but significant<br/><br/>differences, particularly if a company is analyzing their development<br/><br/>environment. As companies have learned, it is not simply a matter of<br/><br/>purchasing the latest software engineering tool to overcome their productivity<br/><br/>problems. Studies show such tools are failing to have an effect in this area,<br/><br/>primarily because they are being misapplied by the users. People looking for<br/><br/>programming tools to bring order out of chaos are going to be sorely<br/><br/>disappointed. This is not their forte. Rather, they represent an efficient<br/><br/>approach for implementing design techniques. The intent of a true methodology<br/><br/>is to define the work environment, thereby providing the ability to effectively<br/><br/>deploy tools and techniques. To implement a methodology, a development<br/><br/>organization needs to reorient themselves into an &#8220;Information Factory&#8221;<br/><br/>environment, where systems and software (products) are developed in the<br/><br/>same manner as any other engineering/manufactu<br />
ring facility.<br/><br/></div>
]]></content:encoded>
			<wfw:commentRss>http://www.alfarnaterural.com/methodologies-versus-techniques-and-tools.cfm/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Bad Apple Logic Board Can be Very Inexpensive to Repair</title>
		<link>http://www.alfarnaterural.com/a-bad-apple-logic-board-can-be-very-inexpensive-to-repair.cfm</link>
		<comments>http://www.alfarnaterural.com/a-bad-apple-logic-board-can-be-very-inexpensive-to-repair.cfm#comments</comments>
		<pubDate>Wed, 17 Mar 2010 04:01:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Robotics]]></category>

		<guid isPermaLink="false">http://www.crawbot.co.cc/?p=2406</guid>
		<description><![CDATA[ The cost savings of having your apple logic board repaired instead of swapped out completely add up to over $800 dollars on some apple computer models. Quotes in excess of $1000 dollars have been issued for the replacement logic board and labor! Finding the right facility to repair an apple logic board instead of replacement [...]]]></description>
			<content:encoded><![CDATA[<div><br/><br/> The cost savings of having your apple logic board repaired instead of swapped out completely add up to over $800 dollars on some apple computer models. Quotes in excess of $1000 dollars have been issued for the replacement logic board and labor! Finding the right facility to repair an apple logic board instead of replacement can make a big difference.<br/><br/> That is the tricky part. Finding an apple repair center that can repair the board itself can take months to find then MONTHS to get the repair finished. Proper logic board repaira do take a longer time to complete properly due to Q/A testing of the actual apple computer repair. A week or 7 business days is a reasonable expectation for a normal turn around time on a mail in apple laptop repair.<br/><br/> I don&#8217;t think even apple them self could beat 7 days on a logic board swap anyway. So that is reasonable for a smaller company to meet or even sometimes beat. I believe it is worth a week of down time to save $800 dollars and I bet you do also!<br/><br/> The apple logic board repair company should have at least a 90 day warranty. Sadly, a lot of companies that install refurbished boards can&#8217;t even offer a warranty on the board itself.That is another reason to have your current logic board repaired properly instead of replaced. You know the history behind your computer. You could end up with some 17 year old kids logic board who spilled coke on it and played video games 24-7! We all understand how much stress and heat video games cause to logic boards!<br/><br/>  The price for a correct apple logic board repair should vary based on model and speed of the apple laptop or desk top to be repaired. At most it should not exceed $250 dollars and include return insured shipping and a 90 day warranty. At that price it is much less expensive than buying a whole new laptop or apple desktop. You have the security of knowing the past history of your complete computer.<br/><br/> Make sure the apple repair center has the ability to replace actual components on the board itself. The machinery to do this cost hundreds of thousands because it must be done with inhuman precision. Some apple logic board components require proper alignment of over 160 TINY pins. Impossible for a human to remove or install these types of components without error or mechanical assistance!<br/><br/> The reward of saving $600 or $800 dollars on a repair is sweet. Getting your computer fixed for $250 after you spilled coke in it is even better! Yes, any honest board level repair facility should be able to fix most liquid spills. There are very few liquid spills that cannot be fixed by a proper application of logic board repair techniques!<br/><br/> Hopefully you are now inspired to save that rotten apple computer, you know the one you love so much until it had come down with a bad logic board? With the cost of living going up consider repairing an older computer you may have lying around and give it to one of your children to save money instead of buying new. Knowing the computers history is a huge plus. <br/><br/> When running a business from your computer, you really need a back up. That is another great reason to get that broken mac repaired instead of tossing it and buying a new one. Most likely if you have it repaired you can Easily resell it for a lot more working than you paid to repair the logic board. All of there things should be considered when you are saving so much money on the apple computer repair itself!<br/><br/> <br/><br/> <br/><br/></div>
]]></content:encoded>
			<wfw:commentRss>http://www.alfarnaterural.com/a-bad-apple-logic-board-can-be-very-inexpensive-to-repair.cfm/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
