According to many best practices frameworks for quality management and process improvement, stati... more According to many best practices frameworks for quality management and process improvement, statistical thinking is an intrinsic part of building organizational capability. In all of these frameworks there is a degree of flexibility in how the statistical thinking concepts are implemented, because these frameworks apply to many different contexts. Flexibility, however, also leads to ambiguity and inconsistency. The purpose of this article is to identify what has been observed in some organizations implementing statistical thinking. These observations can be lessons learned to help accelerate the learning curve for others implementing these frameworks.
There are a number of variants of the IFPUG Function Point method in different countries. This ch... more There are a number of variants of the IFPUG Function Point method in different countries. This chapter provides an overview of some of these variants. The IFPUG FP method is an ISO/IEC standard (the ISO standard currently at the time of printing is ISO/IEC 20926 IFPUG 4.1 unadjusted Function Point Counting Method). In addition, there are four additional functional size measurement methods (FSMMs) recognized by ISO/IEC, each of which uses its own approach to measure a piece of software's functional size. These FSMMs are identified and described in further detail in the previous Chapter Functional Size Measurement Methods. Capers Jones published a list of 35 variants of the IFPUG Function Point Method, which includes a motley crew of different sizing methods. Among those listed were: Prior versions of the IFPUG method from 1.0 (1986) through to 4.2 (2004) Well-known and publicized variants such as Feature Points Unknown or obsolete variants such as the Australian Software Metrics Association (ASMA) method (of which ASMA board members were unaware) Obsolete variants such as 3D Function Points Standalone Prior versions of the FSMMs described above Other measures of software size not necessarily based on the IFPUG method such as Object Points. The following methods are characterized as IFPUG variants and are only mentioned for historical reasons as information to the reader: SPR Function Points Feature Points 3D Function Points. These IFPUG Function Point variants consist of the following steps: Classification and counting of specific model parameters (data, objects, functions, etc.), evaluation of the application's nonfunctional requirements or
Abstract The IFPUG (International Function Point Users Group) Function Point Method (FPM) is a me... more Abstract The IFPUG (International Function Point Users Group) Function Point Method (FPM) is a method to measure the (functional) size of software from the user perspective (depicted in Fig. 12.1). As an ISO/IEC conformant Functional Size Measurement (FSM) method, the ...
According to many best practices frame-works for quality management and process improvement, stat... more According to many best practices frame-works for quality management and process improvement, statistical thinking is an intrin-sic part of building organizational capability. In all of these frameworks there is a degree of flexibility in how the statistical thinking concepts are implemented, because these frameworks apply to many different contexts. Flexibility, however, also leads to ambiguity and inconsistency. The purpose of this article is to identify what has been observed in some organizations implementing statistical think-ing. These observations can be lessons learned to help accelerate the learning curve for oth-ers implementing these frameworks.
The information and communications technology (ICT) world is “addicted ” to dysfunctional behavio... more The information and communications technology (ICT) world is “addicted ” to dysfunctional behavior and the problem is spreading globally. The sad truth is that the parties in the ICT relationship (the customer and the supplier) are largely codependent on a pattern of dysfunction characterized by ineffective communication, fixed price contracts with changing requirements, and eroding trust. This article focuses specifically on the northernSCOPE TM 12-step process for ICT program recovery. The ICT world’s dependence on dysfunctional behavior—specifically ineffective communication, fixed price contracts with changing requirements, and eroding trust—is devastating. Billions of dollars are being spent on rework and enhancements to (defective) software [1]. The latest CHAOS report says that a staggering two-thirds of ICT projects are deemed failures [2], with schedule extensions, cost overruns, and poor quality software more the norm than the exception to the rule. One can find daily news...
This Article is brought to you for free and open access by the School of Computer Science at Rese... more This Article is brought to you for free and open access by the School of Computer Science at Research Showcase. It has been accepted for inclusion in
The 30-year experience from the Software Measurement field explains that a strong resistance usua... more The 30-year experience from the Software Measurement field explains that a strong resistance usually comes from project team members, supposing the real objective is a personal evaluation on their performance and not a neutral measurement for a concrete process improvement. Concurrently, from the middle ‘80s a series of SPI models- such as the Software Capability Maturity Model (Sw-CMM) and nowadays its evolution, the CMMI – provided a guide for realising a real improvement, where measurement played an important role, before as a Common Feature, then as a separate process (MA – Measurement and Analysis) at Level 2. But a certain resistance still remain alive also after these years. Recently, in the Management field (and also in ICT) more than “serious ” books and reference guides it seems that (apparent) semi-serious publications such as the Dilbert strips by Scott Adams are referenced in technical presentations and papers as a starting point for commenting daily ICT malpractices. I...
A method without tool support has little chance for survival, and will encounter extra resistance... more A method without tool support has little chance for survival, and will encounter extra resistance for widespread use. The investment in the right tool suited for estimation for your organization can bring benefit for the organization without any doubt, even if the benefit ...
Function points (FPs) are proven to be effective and efficient units of measure for both agile/it... more Function points (FPs) are proven to be effective and efficient units of measure for both agile/iterative and waterfall software deliveries. However, inconsistencies come to light when comparing FPs counted in agile/iterative development with those counted in waterfall or combination development – and those inconsistencies can create confusion for cost, productivity, and schedule evaluations that span multiple software delivery methods. IFPUG's definitions for such terms as " project, " " elementary process, " " consistent state, " and " enhancement " do not directly translate to agile/iterative delivery methods in which the term " project " is often interchanged with such terms as " sprint, " " iteration, " " release, " or " story map. " This paper seeks to marry IFPUG definitions with equivalent concepts in agile/iterative processes so as to create a basis for consistent comparison.
According to many best practices frameworks for quality management and process improvement, stati... more According to many best practices frameworks for quality management and process improvement, statistical thinking is an intrinsic part of building organizational capability. In all of these frameworks there is a degree of flexibility in how the statistical thinking concepts are implemented, because these frameworks apply to many different contexts. Flexibility, however, also leads to ambiguity and inconsistency. The purpose of this article is to identify what has been observed in some organizations implementing statistical thinking. These observations can be lessons learned to help accelerate the learning curve for others implementing these frameworks.
There are a number of variants of the IFPUG Function Point method in different countries. This ch... more There are a number of variants of the IFPUG Function Point method in different countries. This chapter provides an overview of some of these variants. The IFPUG FP method is an ISO/IEC standard (the ISO standard currently at the time of printing is ISO/IEC 20926 IFPUG 4.1 unadjusted Function Point Counting Method). In addition, there are four additional functional size measurement methods (FSMMs) recognized by ISO/IEC, each of which uses its own approach to measure a piece of software's functional size. These FSMMs are identified and described in further detail in the previous Chapter Functional Size Measurement Methods. Capers Jones published a list of 35 variants of the IFPUG Function Point Method, which includes a motley crew of different sizing methods. Among those listed were: Prior versions of the IFPUG method from 1.0 (1986) through to 4.2 (2004) Well-known and publicized variants such as Feature Points Unknown or obsolete variants such as the Australian Software Metrics Association (ASMA) method (of which ASMA board members were unaware) Obsolete variants such as 3D Function Points Standalone Prior versions of the FSMMs described above Other measures of software size not necessarily based on the IFPUG method such as Object Points. The following methods are characterized as IFPUG variants and are only mentioned for historical reasons as information to the reader: SPR Function Points Feature Points 3D Function Points. These IFPUG Function Point variants consist of the following steps: Classification and counting of specific model parameters (data, objects, functions, etc.), evaluation of the application's nonfunctional requirements or
Abstract The IFPUG (International Function Point Users Group) Function Point Method (FPM) is a me... more Abstract The IFPUG (International Function Point Users Group) Function Point Method (FPM) is a method to measure the (functional) size of software from the user perspective (depicted in Fig. 12.1). As an ISO/IEC conformant Functional Size Measurement (FSM) method, the ...
According to many best practices frame-works for quality management and process improvement, stat... more According to many best practices frame-works for quality management and process improvement, statistical thinking is an intrin-sic part of building organizational capability. In all of these frameworks there is a degree of flexibility in how the statistical thinking concepts are implemented, because these frameworks apply to many different contexts. Flexibility, however, also leads to ambiguity and inconsistency. The purpose of this article is to identify what has been observed in some organizations implementing statistical think-ing. These observations can be lessons learned to help accelerate the learning curve for oth-ers implementing these frameworks.
The information and communications technology (ICT) world is “addicted ” to dysfunctional behavio... more The information and communications technology (ICT) world is “addicted ” to dysfunctional behavior and the problem is spreading globally. The sad truth is that the parties in the ICT relationship (the customer and the supplier) are largely codependent on a pattern of dysfunction characterized by ineffective communication, fixed price contracts with changing requirements, and eroding trust. This article focuses specifically on the northernSCOPE TM 12-step process for ICT program recovery. The ICT world’s dependence on dysfunctional behavior—specifically ineffective communication, fixed price contracts with changing requirements, and eroding trust—is devastating. Billions of dollars are being spent on rework and enhancements to (defective) software [1]. The latest CHAOS report says that a staggering two-thirds of ICT projects are deemed failures [2], with schedule extensions, cost overruns, and poor quality software more the norm than the exception to the rule. One can find daily news...
This Article is brought to you for free and open access by the School of Computer Science at Rese... more This Article is brought to you for free and open access by the School of Computer Science at Research Showcase. It has been accepted for inclusion in
The 30-year experience from the Software Measurement field explains that a strong resistance usua... more The 30-year experience from the Software Measurement field explains that a strong resistance usually comes from project team members, supposing the real objective is a personal evaluation on their performance and not a neutral measurement for a concrete process improvement. Concurrently, from the middle ‘80s a series of SPI models- such as the Software Capability Maturity Model (Sw-CMM) and nowadays its evolution, the CMMI – provided a guide for realising a real improvement, where measurement played an important role, before as a Common Feature, then as a separate process (MA – Measurement and Analysis) at Level 2. But a certain resistance still remain alive also after these years. Recently, in the Management field (and also in ICT) more than “serious ” books and reference guides it seems that (apparent) semi-serious publications such as the Dilbert strips by Scott Adams are referenced in technical presentations and papers as a starting point for commenting daily ICT malpractices. I...
A method without tool support has little chance for survival, and will encounter extra resistance... more A method without tool support has little chance for survival, and will encounter extra resistance for widespread use. The investment in the right tool suited for estimation for your organization can bring benefit for the organization without any doubt, even if the benefit ...
Function points (FPs) are proven to be effective and efficient units of measure for both agile/it... more Function points (FPs) are proven to be effective and efficient units of measure for both agile/iterative and waterfall software deliveries. However, inconsistencies come to light when comparing FPs counted in agile/iterative development with those counted in waterfall or combination development – and those inconsistencies can create confusion for cost, productivity, and schedule evaluations that span multiple software delivery methods. IFPUG's definitions for such terms as " project, " " elementary process, " " consistent state, " and " enhancement " do not directly translate to agile/iterative delivery methods in which the term " project " is often interchanged with such terms as " sprint, " " iteration, " " release, " or " story map. " This paper seeks to marry IFPUG definitions with equivalent concepts in agile/iterative processes so as to create a basis for consistent comparison.
Uploads
Papers by Carol Dekkers