- Practice
- Methods
By search term
By topic
By tag
- Testing (9)
- Agile (29)
- Approaches (42)
- Attributes (4)
- Business Analysis (21)
- Elicitation (27)
- Estimation (5)
- Prioritization (7)
- Team (17)
- User Story (11)
- Template (3)
- Framework (10)
- Goals (8)
- Reuse (2)
- Software Engineering (9)
- Traceability (9)
- Perception (10)
- Management (14)
- Verification (6)
- Study (15)
- Development (12)
- CPRE (5)
- Automation (6)
- Documentation (20)
- Software Quality (10)
- ReqIF (1)
- Standards (6)
- Analysis (19)
- Business Value (10)
- Metrics (5)
- Validation (10)
- Modeling (14)
- Security (3)
- SysML (3)
- Stakeholder (12)
- Big Data (4)
- Opinion (15)
- Literature (4)
By author
- Howard Podeswa (3)
- Rainer Grau (2)
- Erik van Veenendaal (1)
- Cristina Palomares (1)
- Carme Quer (1)
- Xavier Franch (2)
- Mats Wessberg (1)
- Kim Lauenroth (2)
- Joseph Aracic (1)
- IREB (1)
- Jens Schirpenbach (1)
- Alexander Rachmann (1)
- Jesko Schneider (1)
- Frank Engel (1)
- Dr. Ralph R. Young (2)
- Maria-Therese Teichmann (1)
- Eva Gebetsroither (1)
- Corinna Unterfurtner (1)
- Alexandra Kreuzeder (1)
- Harry Sneed (2)
Articles
Showing 31 articles tagged with Prioritization, Study, Template or User Story [max. 4 tags]
When requirements and the product are elaborated concurrently
- Studies and Research
Building the bridge between experience and research: The future Research Section of the RE Magazine
- Methods
- Opinions
How to use requirements gathering techniques to determine product requirements from non-verbal subjects
- Cross-discipline
- Practice
What does OpenAI’s ChatGPT say about RE?
- Methods
- Skills
Evaluating Business Analysts‘ role in the Data Driven Economy
- Studies and Research
- Skills
What do we learn from Gender Studies for Requirements Engineering
- Methods
- Studies and Research
Driving innovation with crowd-based techniques
- Studies and Research
Analysis, results, and recommendations
- Methods
- Practice
An agile and collaborative prioritization technique
- Cross-discipline
- Methods
How you can use the natural partitioning of business events to flexibly synchronise your agile development.
- Practice
- Opinions
When every new iteration can violate previously satisfied requirements
- Methods
An approach for iterative and requirements-based quality assurance in DevOps
- Practice
- Methods
‘A large elephant is in the room but we are not able or brave or willing enough to point at it’
- Studies and Research
An Intelligent Assistant for Improving Requirement Authoring
- Practice
- Cross-discipline
Concept for the successful handling of integral NFRs in Scaled Agile Environments.
- Practice
- Studies and Research
The True Measure of Requirements Quality.
- Practice
- Methods
Why Testers should have a closer look into Requirements Engineering
- Studies and Research
Has RE adapted itself to the challenges of Agile methods?
- Studies and Research
Results of research project announced in a previous issue.
- Practice
- Methods
Readable requirements are not a matter of course – or are they?
- Studies and Research
Preliminary Results of a Questionnaire
- Methods
- Practice
Classifying product techniques by requirements type
- Skills
- Studies and Research
A study concerning the question of whether domain knowledge is rather conducive, or rather hindering, for a requirements engineer
- Studies and Research
A statistical analysis and trends from 2009 to 2015
- Cross-discipline
Who works in RE and what competences do they need, particularly soft skills?
- Studies and Research
Lessons learned from a European Framework Project
- Opinions
When shall does not need to be must
- Methods
- Practice
Strategies for building manageable requirements hierarchies in complex problem domains
- Methods
- Skills
How to create awareness for some of the difficulties requirements engineers face
- Studies and Research
- Practice
Preliminary Results from an Ongoing Study
- Practice
- Studies and Research
How Product Owners (POs), Business Analysts and Requirements Engineers Use Agile Requirements Engineering (RE) to optimize the work of the team and maximize the value delivered to stakeholders.