The Scrum Software Development Process for Small Teams
IEEE Software
Software Architecture in Practice
Software Architecture in Practice
New directions on agile methods: a comparative analysis
Proceedings of the 25th International Conference on Software Engineering
Generic semantics of feature diagrams
Computer Networks: The International Journal of Computer and Telecommunications Networking
A general model of software architecture design derived from five industrial approaches
Journal of Systems and Software
Kumbang: A domain ontology for modelling variability in software product families
Advanced Engineering Informatics
Using a Configurator for Predictable Component Composition
EUROMICRO '07 Proceedings of the 33rd EUROMICRO Conference on Software Engineering and Advanced Applications
Supporting Product Derivation by Adapting and Augmenting Variability Models
SPLC '07 Proceedings of the 11th International Software Product Line Conference
Empirical studies of agile software development: A systematic review
Information and Software Technology
The enterprise and scrum
Design and natural science research on information technology
Decision Support Systems
| Hi-index | 0.00 |
Agile methods have gained popularity in the software industry. A backlog, which is, roughly, a prioritized list of things to be done, is used as a means of management of development. However, one particular challenge is that a backlog does not provide information beyond isolated backlog items, e.g., especially that of composed entities, such as the product in the whole. We describe the Featback method, which provides information that the existing means do not directly provide, especially of composed entities. The information is based on analyses using the concepts from an integrated backlog and feature model, thus integrating structural and developmental information. Justification is provided by the definition specifications for analyses and by using an expository instantiation of a running example for the Featback method.