Extreme programming explained: embrace change
Extreme programming explained: embrace change
Agile Software Development with Scrum
Agile Software Development with Scrum
Participatory Design: Principles and Practices
Participatory Design: Principles and Practices
A Practical Guide to Feature-Driven Development
A Practical Guide to Feature-Driven Development
A Cost-Value Approach for Prioritizing Requirements
IEEE Software
An Agile Request For Proposal (RFP) Process
ADC '03 Proceedings of the Conference on Agile Development
User Stories Applied: For Agile Software Development
User Stories Applied: For Agile Software Development
A conceptual model of client-driven agile requirements prioritization: results of a case study
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
Agile requirements prioritization: what happens in practice and what is described in literature
REFSQ'11 Proceedings of the 17th international working conference on Requirements engineering: foundation for software quality
| Hi-index | 0.00 |
Very little has been written to date on how to prioritize and sequence the development of new features and capabilities on an agile software development project. Agile product managers have been advised to prioritize based on “business value.” While this seems an appropriate goal, it is vague and provides little specific guidance. Our approach to optimizing “business value” uses tactics to minimize costs and maximize benefits through strategic learning. In order to provide specific and actionable advice to agile product managers, we present two guidelines. These guidelines are meant to provide a set of considerations and a process by which an agile product manager can achieve the goal of optimizing “business value” while recognizing that different product managers will vary in their notions of what “business value” is.