Posts

Showing posts from May, 2013

Psychographics - Interesting fact of the day

Psychographics is the science of measuring and categorizing consumer lifestyles. One of the most popular classifications based on psychographic measurements is SRI International’s Values and Lifestyles (VALS) framework. The VALS 2 system classifies all U.S. adults into eight groups based on psychological attributes drawn from survey responses to demographic, attitudinal, and behavioral questions, including questions about Internet usage. The major tendencies of these groups are: ➤ Actualizers: Successful, sophisticated, active, “take-charge” people whose purchases often reflect cultivated tastes for relatively upscale, niche-oriented products. ➤ Fulfilleds: Mature, satisfied, comfortable, and reflective people who favor durability, functionality, and value in products. ➤ Achievers: Successful, career- and work-oriented consumers who favor established, prestige products that demonstrate success. ➤ Experiencers: Young, vital, enthusiastic, impulsive, and rebellious people who spend much ...

Chinese "Six Pocket Syndrome" - Interesting fact of the day

The explosive world population growth has major implications for business. A growing population does not mean growing markets unless these markets have sufficient purchasing power. Nonetheless, companies that carefully analyze their markets can find major opportunities. For example, to curb its skyrocketing population, the Chinese government has passed regulations limiting families to one child per family. Toy marketers, in particular, are paying attention to one consequence of these regulations: These children are spoiled and fussed over as never before. Known in China as “little emperors,” Chinese children are being showered with everything from candy to computers as a result of what’s known as the “ six pocket syndrome. ” As many as six adults—parents, grandparents, great-grandparents, and aunts and uncles—may be indulging the whims of each child. This trend has encouraged such companies as Japan’s Bandai Company (famous for its Mighty Morphin’ Power Rangers), Denmark’s Lego Group, ...

Waltzing with Bears : Managing Risk on Software Projects by Tom Demarco Chapter 14 to 17 Reflection

Image
Reflection on Chapters 14 to 17 of Waltzing with Bears : Managing Risk on Software Projects  by Tom Demarco Link to sample Chapter 1 from Waltzing with Bears   http://www.systemsguild.com/pdfs/bearsample.pdf Link to Waltzing with Bears Textbook Download Chapter 14 , “ A Defined process for Risk discovery ”, states that along with core risks, there may be project-specific risks that impact a project. This chapter talks about identifying project-specific risks and the factors that hinder the risk discovery process. One such factor is the “can-do” attitude of the organization, wherein a project member who articulates a risk could be termed as a negative-thinker. In order to overcome this problem, it is important that the organization encourages “what-if” thinking. This is also the basis of the defined process for risk discovery described which begins with the outcomes of the risk, unfolding the scenarios that could lead to the risk and ultimately the causes of the scenarios. Th...

Waltzing with Bears : Managing Risk on Software Projects by Tom Demarco Chapters 8 to 13 Reflection

Image
Reflection on Chapters 8 to 13 of  Waltzing with Bears : Managing Risk   on Software Projects  by Tom Demarco Link to sample Chapter 1 from Waltzing with Bears   http://www.systemsguild.com/pdfs/bearsample.pdf   Link to Waltzing with Bears Textbook Download Chapter 8 , “ Quantifying uncertainty ”, explains that one of the risks for any project is uncertainty in the schedule for completion of the project. It further illustrates how this uncertainty can be expressed in the form of a risk diagram, which helps to at least narrow down the window of uncertainty. Chapter 9 , “ Mechanics of risk management ”, talks about how risks can be identified. As the saying goes, “History repeats itself”. So the chapter states that one of the most useful methods of identifying risks is analyzing previously failed projects in the organization and listing the causes, which can serve as risks for the current project. However, I feel that this method will be highly effective only if ...

Waltzing with Bears : Managing Risk on Software Projects by Tom Demarco Chapters 5,6 and 7 Reflection

Image
Reflection on Waltzing with Bears : Managing Risk on Software Projects by Tom Demarco Chapters 5,6 and 7 Link to sample Chapter 1 from Waltzing with Bears   http://www.systemsguild.com/pdfs/bearsample.pdf Link to Waltzing with Bears Textbook Download P rimarily, the book “ Waltzing with Bears ” offers valuable insights about risk management techniques and how they can be applied. However, chapters 5, 6, and 7 deviate from the theme a little to talk about scenarios where risk management techniques cannot be employed (For example: ‘can-do’ attitude of an organization). Chapter 5 adopts a very pragmatic approach towards risk management and explains various such circumstances where risk management is avoided. For instance, stakeholder might not take up the project if he/she knew the risks involved. The author also talks about organizations that advocate the “manage for success” approach and that it is difficult for one person to swim against the tide and promote risk management i...

Waltzing with Bears : Managing Risk on Software Projects by Tom Demarco Chapters 1 to 4 Reflection

Image
Reflection on Waltzing with Bears : Managing Risk on Software Projects by Tom Demarco Chapters 1 to 4 Link to sample Chapter 1 from Waltzing with Bears   http://www.systemsguild.com/pdfs/bearsample.pdf Link to Waltzing with Bears Textbook Download Chapter 1, "Running toward risk" starts off with describing what should be your attitude towards risks. There is no project without risks. And the best way to deal with risks is to accept them instead of avoiding risks. Once you accept the risk, you can work on a risk management strategy. Chapter 2, "Risk Management Is Project Management for Adults" presents examples of risk management and risk mitigation. We all do some sort of risk management or mitigation in our daily lives. Insurance, for instance, is a classic example of risk mitigation by transferring the risk of financial loss to the insurance company and obtaining coverage for a monthly premium in the event of an accident or a health problem. Tom Demarco discusses...

Similarities and Differences between Software and Systems Engineering

Image
According to CMMI, Software engineering is defined as a discipline that covers the development of software systems. It focuses on applying systematic, disciplined and quantifiable approaches to the development, operation and maintenance of software. Systems engineering is defined as a discipline that covers the development of total systems, which may or may not include software. It focuses on transforming customer needs, expectations and constraints into product solutions and supporting those product solutions throughout the product life cycle. These definitions elicit the primary difference between systems and software engineering. The differences between software and systems engineering can be further classified based on different parameters. For instance, in software engineering, the architecture can be dynamic and subject to change, based on emergent needs during the software development life cycle. Whereas in systems engineering, the architecture is established at the beginning o...

Mr. Thompkin's Journal from Death March by Tom Demarco

Image
Mr. Tompkins , a manager downsized from a giant telecommunications company, divides the huge staff of developers at his disposal into eighteen teams--three for each of the software products. The teams are different sizes and use different methods, and they compete against each other and against an impossible deadline. With these teams--and with the help of numerous "fictionalized" consultants who come to his aid--Tompkins tests the project management principles he has gathered over a lifetime. Each chapter in the book Death March by Tom Demarco closes with journal entries that form the core of the eye-opening approaches to management illustrated in this entertaining novel. This is my reflection on the journal entries of Mr. Tompkins from Death March. Mr. Tompkin's Journal packages a concise collection of insightful project management principles, approaches, skills and best practices and summary points for review. Each journal entry presents a series of conclusions for ne...

Six Sigma Methodology Critique

Six Sigma is basically a methodology, originally developed by Motorola, to improve the quality of processes by removing and preventing defects. A defect can be any feature or functionality of a product or a process that does not meet its specification. Six Sigma can be defined as a metric to measure the performance of a process. Its goal is to improve the performance and increase profitability by targeting a defect rate of less than 3.4 DPMO (defects per million opportunities). The key processes involved in applying Six Sigma are DMAIC (Define, Measure, Analyze, Improve, Control). The Define stage identifies the process to be improved. The Measure stage collects the data for the process for comparison. The Analyze stage identifies any discrepancies between the current performance and optimal performance of the process. The Improve stage fixes the inconsistencies in the target process. The Control stage targets at ensuring the non-occurrence of the discrepancies and continued optimal p...

Harvard Business Review: Case Analysis - ERP Implementation at CISCO (699022-PDF-ENG) from Strategic Role of IT perspective

Image
Presenting an analysis of the HBR case ERP Implementation at CISCO (699022-PDF-ENG)  from  Strategic Role of IT perspective. Link to the case  http://hbr.org/product/cisco-systems-inc-implementing-erp/an/699022-PDF-ENG Case Background:  Reviews Cisco System's approach to implementing Oracle's Enterprise Resource Planning (ERP) software product. This case chronologically reviews the diverse, critical success factors and obstacles facing Cisco during its implementation. Cisco faced the need for information systems replacement based on its significant growth potential and its reliance on failing legacy systems. The discussion focuses on where management was particularly savvy in contrast to where it was the beneficiary of good fortune. Introduction . 3 I.        Overview of the Business . 3 A.       Company Background . 3 B.       Market segment, Products & Channels . 3 C.  ...