Controlling the Chaos of Agile Development
There is a story that illustrates the relationship between product size and the time that it take to develop it. In the truly early days of computers, they were programmed using Basic Assembly Language (BAL). If you wanted to add a couple of numbers … [Continue reading]
In 2011, I wrote my thesis describing an approach to estimating agile projects early in the software development life cycle. Primarily, the thesis was concerned with sizing software. However, in one of the case studies, I described how effort and … [Continue reading]
From the beginning of the agile movement, user stories were the primary way to capture functionality. They were written on cards, called story cards. The logic here was that the story cards were meant to be informal, unlike the data flow diagrams … [Continue reading]
The diagram above looks like the bottom of the one in Overview of Semi-Classical Estimating. As a brief review, the development environment is applied to the consumer product size, made up of both estimated function points and enriched SNAP points, … [Continue reading]
Some of the ideas of this post are taken from A Very Short Course in SNAP. That post was intended to explain the basics Software Non-functional Assessment Process (SNAP). This one concentrates on the concepts and capabilities of the technique and how … [Continue reading]