SixSigmaObjectives - henk52/knowledgesharing GitHub Wiki
-
Objectives, Cardinal SixSigma: These are the Base objectives use/acted on when Defining the Business ObjectivesEdit: %TOPIC%
-
There are two types og objectives: Business and strategic.
-
Busines objectives: Goals the must routinely be pursued within an organization it is to function.
-
Strategic objectives: Goals that must be accomplished to pursue the presidential strategy of an organization.
-
There are four basic categories of key objectives Ref6,p69/Git06, ch3:
-
Financial:
- More - Profit, Market share, Dominance.
- Less waste: %X% Waste of what? Money, resources. Time is money, but doesn't this tie into efficiency?
- Probably wast of physical material.
- Less Turnover:
- Emplyoee: Is this because it is expensive to train new people?
- Assets: In accounting, the number of times an asset is replaced during a financial period. You would have to sit down and analyse the the data in order to decide on how to invest in an asset, go cheap with possible high turnover or expensive with hopefully long turnover?
- Inventory: Here you actually want high turnover to keep as little money as possible tied up in inventory and storage for the inventory.
- Portfolio: The number of shares traded for a period as a percentage of the total shares in a portfolio or of an exchange.
- Less financial loss: %X% hmm.
- Less Customer defection: Possibly because it is expensive to cultivate new customers.
-
Process:
- Consistent, uniform output: %X% is this like the control thing of SixSigma?
- High productivity: %X% what does that mean?
- Products, services and processes exceeds the needs and want of current and future stakeholders
- Product, services and processes that are easy to create and low cost to provide
- Products and services that meet technical specifications
- Products and services that do not incur warranty costs
- Products that are easy to distribute throughout the channels of distribution
-
Inovation:
- %X% Is this because it introduces disrubtive technology/solutions that will leave the competition in the dust?
-
Customer satisfaction: (TODO V Fit these with the QualityAttributes.)
- Customer's desired outcomes:
- Joy
- Security
- Personal time
- Belonging - Isn't this what apple does?
- Health
- Customer's undesired outcomes
- avoidance or elimination of death
- taxes
- discomfort
- wasted time
- Frustration
- customer's desired product and service attributes
- ease-of-use
- accessibility
- low cost of ownership
- durability
- appeal
- Customer's desired process characteristics.
- Timely arrival
- No waiting time
- ease of acquisition
- TODO C What about affecting the customers ability to earn money.
- Customer's desired outcomes:
-
Employee growth and development:
- Improving leadership skills
- Provide training opportunities
- Stimulating special assignments%STOPINCLUDE%
-
Where does CoPQ CTQ fit in here?
-
- Availability: (Wie03,144)Availability is a measure of the planned uptime during which the system is actually available for use and fully operational. More formally, availability equals the mean time to failure (MTTF) for the system divided by the sum of the MTTF and the mean time to repair the system after a failure is encountered. Scheduled maintenance periods also affect availability. Some authors view availability as encompassing reliability, maintainability, and integrity (Gilb 1988).
- Related -
- Efficiency: (Wie03,145) is a measure of how well the system utilizes processor capacity, disk space, memory, or communication bandwidth (Davis 1993).
- Related - Performance.
- Flexibility: Also known as extensibility , augmentability, extendability , and expandability , flexibility measures how easy it is to add new capabilities to the product(Wie03,146).
- Related -
- Integrity: which encompasses security, deals with blocking unauthorized access to system functions, preventing information loss, ensuring that the software is protected from virus infection, and protecting the privacy and safety of data entered into the system(Wie03,146).
- Related -
- Interoperability: indicates how easily the system can exchange data or services with other systems. To assess interoperability, you need to know which other applications the users will employ in conjunction with your product and what data they expect to exchange(Wie03,146).
- Related -
- Maintainability: indicates how easy it is to correct a defect or modify the software(Wie03,148).
- Related - flexibility and testability.
- Portability: The effort required to migrate a piece of software from one operating environment to
another is a measure of portability(Wie03,149).
- Related - Reusabel.
- Reliability: The probability of the software executing without failure for a specific period of time is known as reliability (Musa, Iannino, and Okumoto 1 987). Robustness is sometimes considered an aspect of reliability. Ways to measure software reliability include the percentage of operations that are completed correctly and the average length of time the system runs before failing(Wie03,147).
- Establish quantitative reliability requirements based on how severe the impact would be if a failure occurred and whether the cost of maximizing reliability is justifiable.
- Aka - Robustness. TODO V On page (Wie03,151) robustness is listes, as well as reliability, and the two entries does not have the same effects on the other attributes...
- Reusability: indicates the relative effort involved to convert a software component for use in other applications(Wie03,149).
- Reusable software must be modular, well documented, independent of a specific application and operating environment, and somewhat generic in capability(Wie03,149).
- Testability: refers to the ease with which software components or the integrated product can be tested to look for defects(Wie03,149).
- aka - verifiability.
- Usability: addresses the myriad factors that constitute what users often describe as user-friendliness(Wie03,148).
- Usability measures the effort required to prepare input for, operate, and interpret the output of the product(Wie03,148). *Inquire whether the new system must conform to any user interface standards or conventions, or whether its user interface needs to be consistent with those of other frequently used systems(Wie03,148).