Over various projects I have applied a set of Agile practices from eXtreme Programming and Scrum. Adding personal insights to specifically handle fixed price (-negotiable scope) projects resulted in my My.Fragility framework.
The framework includes a Product Backlog Estimation model, for which the main estimation process steps were highlighted as part of my Definition Of Agile Planning. Furthermore does the model at least imply an understanding of my definition of a User Story:
A User Story describes a feature from an end-user perspective. It is independent of software layers or parts of the project
A User Story can be explained as an essential Use Case
A User Story should be INVEST to be ready for development
- Independent: User Stories have as little interdependence as possible. Resolve it by putting related Stories in the same Sprint
- Negotiable: a User Story is an invitation to discuss implementation. The best design and code result from communication!
- Valuable: a User Story represents effective business value for an end-user
- Estimatable: the size and knowledge on a User Story is sufficient to reliably estimate the Story
- Small: a User Story is small enough to be estimated, developed and tested. It is comfortably realizable in one Sprint
- Testable: a User Story has a clear result that can be tested
