Difference between revisions of "Work product"
(→Trivia) |
|||
| (16 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | A [[work product]] (or, simply, [[product]]) is a result of any [[process]] that has been initiated, designed, and/or performed by one or more [[human being]]s. [[Intermediate product]]s are those that one department produces for another department of the same [[legal entity]]. | |
| Line 5: | Line 5: | ||
===Definitions=== | ===Definitions=== | ||
According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | ||
| − | :[[Product]] ([[business analysis]]). A solution or component of a solution that is the result of an initiative. | + | :'''[[Product]]''' ([[business analysis]]). A solution or component of a solution that is the result of an initiative. |
:[[Work product]] ([[business analysis]]). A document or collection of notes or diagrams used by the business analyst during the requirements development process. | :[[Work product]] ([[business analysis]]). A document or collection of notes or diagrams used by the business analyst during the requirements development process. | ||
According to [[Juran's Quality Handbook by Defeo (7th edition)]], | According to [[Juran's Quality Handbook by Defeo (7th edition)]], | ||
| Line 12: | Line 12: | ||
===Product vs work product=== | ===Product vs work product=== | ||
:Literally, [[product]] is anything that is produced. This term, [[product]], has a wide range of applications: | :Literally, [[product]] is anything that is produced. This term, [[product]], has a wide range of applications: | ||
| − | :*In [[business]] and [[marketing]], [[product]] usually refers to | + | :*In [[business]] and [[marketing]], [[product]] usually refers to the [[market exchangeable]] that is produced by either an industrial process or farming to be sold and re-sold as a commodity. |
| − | :*In [[business analysis]], [[product]] may refer to | + | :*In [[business analysis]], [[product]] may refer to the ''work product'' that either [[business analyst]]s produce or the [[customer]] seeks to obtain when their [[requirement]]s are implemented. |
| − | :*In [[engineering]] and [[project management]], [[product]] usually refers to ''work product''. | + | :*In [[effort administration]], [[engineering]], and [[project management]], [[product]] usually refers to ''work product'', so does this word, [[product]], in the [[product backlog]] and [[product backlog item]] ([[product backlog item|PBI]]) terms. |
:*In [[mathematics]], [[product]] is the result from the multiplication together of numbers or expressions. | :*In [[mathematics]], [[product]] is the result from the multiplication together of numbers or expressions. | ||
:*In [[social science]], [[product]] is something or someone resulting from environment or a set of other conditions. | :*In [[social science]], [[product]] is something or someone resulting from environment or a set of other conditions. | ||
| + | |||
| + | ===Service-making product=== | ||
| + | :In [[service management]], a [[product]] is a configuration of resources, created by the organization, that will be potentially valuable for their customers. Products are typically complex and not fully visible to the consumer. The portion of a product that the consumer actually sees does not always represent all of the components that comprise the product and support its delivery. [[Service provider]]s define which product components their [[service consumer]]s see, and tailor them to suit their target consumer groups. | ||
| + | |||
| + | ===Key aspects=== | ||
| + | |||
| + | Several key aspects are important for any work product: | ||
| + | |||
| + | 1. **Functionality**: The primary purpose of any software or work product is to fulfill a specific function or set of functions effectively. It needs to perform the tasks it was designed for reliably and accurately. | ||
| + | |||
| + | 2. **Usability**: The software or work product should be user-friendly and intuitive. It should be easy for users to understand how to interact with it and accomplish their goals without unnecessary complexity or confusion. | ||
| + | |||
| + | 3. **Reliability**: Users need to be able to depend on the software or work product to perform consistently under various conditions. Reliability involves factors such as stability, robustness, and error handling. | ||
| + | |||
| + | 4. **Performance**: The software or work product should deliver acceptable performance levels, such as speed and responsiveness, to meet user expectations. Performance optimization may be necessary to achieve this goal. | ||
| + | |||
| + | 5. **Security**: Security is crucial to protect sensitive data and prevent unauthorized access or malicious activities. The software or work product should implement appropriate security measures to safeguard against potential threats. | ||
| + | |||
| + | 6. **Scalability**: As usage grows or requirements change, the software or work product should be able to scale accordingly to accommodate increased demand without significant degradation in performance or functionality. | ||
| + | |||
| + | 7. **Maintainability**: It's essential that the software or work product is maintainable over time. This includes factors such as code readability, documentation, modularity, and ease of debugging and troubleshooting. | ||
| + | |||
| + | 8. **Compatibility**: The software or work product should be compatible with relevant platforms, devices, browsers, or other systems it interacts with to ensure seamless integration and interoperability. | ||
| + | |||
| + | 9. **Compliance**: Depending on the industry or domain, adherence to regulatory standards, legal requirements, or industry best practices may be necessary. Compliance ensures that the software or work product meets necessary standards and regulations. | ||
| + | |||
| + | 10. **User Satisfaction**: Ultimately, the success of any software or work product is often measured by user satisfaction. It's important to solicit and incorporate feedback from users to continuously improve and refine the product to better meet their needs and expectations. | ||
==Development== | ==Development== | ||
| + | ===Requirements=== | ||
*[[Product backlog]]. | *[[Product backlog]]. | ||
*[[Product backlog item]]. | *[[Product backlog item]]. | ||
| − | ==Related lectures== | + | ===Modeling=== |
| − | *[[Business Modeling Quarter]]. | + | *[[Product design]]. |
| + | |||
| + | ===States=== | ||
| + | : ''Main wikipage: [[Work-product state]]'' | ||
| + | |||
| + | ==See also== | ||
| + | |||
| + | ===Related lectures=== | ||
| + | :*[[Surroundings of Projects]]. | ||
| + | :*[[Business Modeling Quarter]]. | ||
| − | [[Category: Quality Management]][[Category: Septem Artes Administrativi]][[Category: Articles]][[Category: Business Analysis]] | + | [[Category: CNM Cyber Placement]][[Category: Quality Management]][[Category: Septem Artes Administrativi]][[Category: Articles]][[Category: Business Analysis]] |
Latest revision as of 23:02, 15 April 2024
A work product (or, simply, product) is a result of any process that has been initiated, designed, and/or performed by one or more human beings. Intermediate products are those that one department produces for another department of the same legal entity.
Contents
Trivia
Definitions
According to the BABOK Guide (3rd edition),
- Product (business analysis). A solution or component of a solution that is the result of an initiative.
- Work product (business analysis). A document or collection of notes or diagrams used by the business analyst during the requirements development process.
According to Juran's Quality Handbook by Defeo (7th edition),
Product vs work product
- Literally, product is anything that is produced. This term, product, has a wide range of applications:
- In business and marketing, product usually refers to the market exchangeable that is produced by either an industrial process or farming to be sold and re-sold as a commodity.
- In business analysis, product may refer to the work product that either business analysts produce or the customer seeks to obtain when their requirements are implemented.
- In effort administration, engineering, and project management, product usually refers to work product, so does this word, product, in the product backlog and product backlog item (PBI) terms.
- In mathematics, product is the result from the multiplication together of numbers or expressions.
- In social science, product is something or someone resulting from environment or a set of other conditions.
Service-making product
- In service management, a product is a configuration of resources, created by the organization, that will be potentially valuable for their customers. Products are typically complex and not fully visible to the consumer. The portion of a product that the consumer actually sees does not always represent all of the components that comprise the product and support its delivery. Service providers define which product components their service consumers see, and tailor them to suit their target consumer groups.
Key aspects
Several key aspects are important for any work product:
1. **Functionality**: The primary purpose of any software or work product is to fulfill a specific function or set of functions effectively. It needs to perform the tasks it was designed for reliably and accurately.
2. **Usability**: The software or work product should be user-friendly and intuitive. It should be easy for users to understand how to interact with it and accomplish their goals without unnecessary complexity or confusion.
3. **Reliability**: Users need to be able to depend on the software or work product to perform consistently under various conditions. Reliability involves factors such as stability, robustness, and error handling.
4. **Performance**: The software or work product should deliver acceptable performance levels, such as speed and responsiveness, to meet user expectations. Performance optimization may be necessary to achieve this goal.
5. **Security**: Security is crucial to protect sensitive data and prevent unauthorized access or malicious activities. The software or work product should implement appropriate security measures to safeguard against potential threats.
6. **Scalability**: As usage grows or requirements change, the software or work product should be able to scale accordingly to accommodate increased demand without significant degradation in performance or functionality.
7. **Maintainability**: It's essential that the software or work product is maintainable over time. This includes factors such as code readability, documentation, modularity, and ease of debugging and troubleshooting.
8. **Compatibility**: The software or work product should be compatible with relevant platforms, devices, browsers, or other systems it interacts with to ensure seamless integration and interoperability.
9. **Compliance**: Depending on the industry or domain, adherence to regulatory standards, legal requirements, or industry best practices may be necessary. Compliance ensures that the software or work product meets necessary standards and regulations.
10. **User Satisfaction**: Ultimately, the success of any software or work product is often measured by user satisfaction. It's important to solicit and incorporate feedback from users to continuously improve and refine the product to better meet their needs and expectations.
Development
Requirements
Modeling
States
- Main wikipage: Work-product state
