The sooner the organization's maturity reuse is leveraged, the sooner the organization will be able to be both global and locally flexible.
Reusability is both art and science. It’s important to diagnose current problems, build a good reusability strategy, generate the value based on shared components or any fair reasons with scientific practices that make economic sense.
Figure out the very reasons to reuse: Knows when to reuse and when not to reuse: where it may be bad, where there may be risks, but also where, if appropriately mitigated, the reuse could be good. Know how to handle reuse at both strategic and tactical level. The goal of reusability is to manage cost scientifically and shorten the development cycle significantly. The management should enforce the governance/oversight to guarantee that reusability development maintains conformance to that business need, and the combination of quality and price for any given service feature is competitive for delighting customers and comparable to the marketplace from a cost/performance perspective.
Changes to reusable components have to be acceptable to a wider body of customers, you need some way to get consensus for any change. You need to test the change against all parties requirements to ensure you don't break anything, but that extends the time required. Help stakeholders balance quality and functionality and help them decide when to invest in testing, in reviews, and in defect prevention.
Leverages common maintenance and standard features: Re-usability is about creating simple building blocks that can be applied over and over to minimize design cost and maximize value over the products/services delivery cycle. When implemented seamlessly, it will bring in required simplicity at an enterprise level and speed up product delivery cycle. Resource, talent, etc, are all critical factors in product research and development. Throwing up services because "everyone's doing it" is only going to waste time and money. Reuse is science in this regard.
Reuse happens at many levels, although in most cases the upside of reuse out-weights the penalties. Just keep remembering that everything has downsides and they should be considered along with the benefits. But give a thought to the negatives as well as the positives, in order to measure application reusability via the lenses of efficiency, effectiveness, and agility.
Raise associated ROI: The business value of application reuse is easiest to communicate after educating the business on the different stages of technical maturity, the advantages and costs of each stage. Technically, the management needs to clarify the engineering disciples behind reusability. Where is it deployed (multiple sites, outsourced cloud infrastructure, etc.)? Which modules are used by which people in which processes? )What are the integration points (people, process, technology) for these modules? Are there technical standards issues with the product? Are there SLA issues?
Known bugs can be fixed, ignored or tolerated; and understanding a reasonable set of choices is based on the circumstances and impact of the defect. You can only manage what you measure. Do know why you are collecting the metrics. Establish a good root question. Identify the purpose of the information and the stakeholders who will use it. Ask whether the metrics can reveal anything meaningful for the identified purpose of reusability, and how to raise associated ROI.
Reusability is both art and science. There are different dynamics at work in each area, and therefore different paths to reusability success. The sooner the organization's maturity reuse is leveraged, the sooner the organization will be able to be both global and locally flexible.
Figure out the very reasons to reuse: Knows when to reuse and when not to reuse: where it may be bad, where there may be risks, but also where, if appropriately mitigated, the reuse could be good. Know how to handle reuse at both strategic and tactical level. The goal of reusability is to manage cost scientifically and shorten the development cycle significantly. The management should enforce the governance/oversight to guarantee that reusability development maintains conformance to that business need, and the combination of quality and price for any given service feature is competitive for delighting customers and comparable to the marketplace from a cost/performance perspective.
Changes to reusable components have to be acceptable to a wider body of customers, you need some way to get consensus for any change. You need to test the change against all parties requirements to ensure you don't break anything, but that extends the time required. Help stakeholders balance quality and functionality and help them decide when to invest in testing, in reviews, and in defect prevention.
Leverages common maintenance and standard features: Re-usability is about creating simple building blocks that can be applied over and over to minimize design cost and maximize value over the products/services delivery cycle. When implemented seamlessly, it will bring in required simplicity at an enterprise level and speed up product delivery cycle. Resource, talent, etc, are all critical factors in product research and development. Throwing up services because "everyone's doing it" is only going to waste time and money. Reuse is science in this regard.
Reuse happens at many levels, although in most cases the upside of reuse out-weights the penalties. Just keep remembering that everything has downsides and they should be considered along with the benefits. But give a thought to the negatives as well as the positives, in order to measure application reusability via the lenses of efficiency, effectiveness, and agility.
Raise associated ROI: The business value of application reuse is easiest to communicate after educating the business on the different stages of technical maturity, the advantages and costs of each stage. Technically, the management needs to clarify the engineering disciples behind reusability. Where is it deployed (multiple sites, outsourced cloud infrastructure, etc.)? Which modules are used by which people in which processes? )What are the integration points (people, process, technology) for these modules? Are there technical standards issues with the product? Are there SLA issues?
Known bugs can be fixed, ignored or tolerated; and understanding a reasonable set of choices is based on the circumstances and impact of the defect. You can only manage what you measure. Do know why you are collecting the metrics. Establish a good root question. Identify the purpose of the information and the stakeholders who will use it. Ask whether the metrics can reveal anything meaningful for the identified purpose of reusability, and how to raise associated ROI.
Reusability is both art and science. There are different dynamics at work in each area, and therefore different paths to reusability success. The sooner the organization's maturity reuse is leveraged, the sooner the organization will be able to be both global and locally flexible.
0 comments:
Post a Comment