Controlling the Chaos of Agile Development
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]
The diagram above and some of the ideas of this post are taken from A Very Short Course in Function Point Analysis. That post was intended to explain function point analysis. This one concentrates on the concepts and capabilities of the technique and … [Continue reading]
The above is an overview of the semi-classical estimating process. The process is fueled by the initial user stories. Conceptually, the result is a burn down chart that will show how many iterations will be required for the next release. The required … [Continue reading]