Controlling the Chaos of Agile Development
Many applications display information on screens. The example above is the WordPress screen that shows the posts that make up the blog. If we were developing the WordPress application, then adding this screen would probably be in the first release. … [Continue reading]
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]