Controlling the Chaos of Agile Development
The identification of transactions and data are part of every software sizing exercise. Processes, and sometimes data, are impacted by logical location. For example, the process “Authorize Shipment” might take place at both corporate headquarters and … [Continue reading]
Roles are logically distinct types of people who do a subset of the processes that an application supports. Examples might be clerical users, who do data entry; supervisors, who schedule and authorize actions; and executives, who review management … [Continue reading]
From the very beginning, all participants should start to form some expectation regarding the size of the application to be estimated. At the top of the post is the size distribution of new development projects. The size distribution is expressed in … [Continue reading]
It seems like batch processing should have no place in agile development. It conjures up the image of someone sitting at a IBM 026 keypunch machine typing in Job Control Language (JCL) and COBOL II. It is doubtful that any agile team has ever … [Continue reading]
This is a very short course in the International Function Point Users Group's (IFPUG's) Software Non-Functional Assessment Process (SNAP). It is offered in the same spirit as A Very Short Course in Function Point Analysis. As I begin this post, I am … [Continue reading]