- Methods
- Practice
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 Estimation, Management, User Story or Verification [max. 4 tags]
Classifying product techniques by requirements type
- Methods
- Practice
Strategies for building manageable requirements hierarchies in complex problem domains
- Cross-discipline
- Practice
What does OpenAI’s ChatGPT say about RE?
- 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.
- Practice
- Cross-discipline
Concept for the successful handling of integral NFRs in Scaled Agile Environments.
- Opinions
- Cross-discipline
This system is your system. This system is my system.
- Practice
- Methods
It seems evident to test designs or prototypes of software with end-users. But what about requirements?
- Practice
- Methods
‘A large elephant is in the room but we are not able or brave or willing enough to point at it’
- Methods
- Practice
Improving requirements quality by effort estimates
- Methods
- Opinions
How to use requirements gathering techniques to determine product requirements from non-verbal subjects
- Methods
- Opinions
What are the levels of granularity of functional requirements and why this is important
- Methods
An approach for iterative and requirements-based quality assurance in DevOps
- Practice
- Opinions
Ensuring Software Quality beyond Micromanagement
- Methods
- Practice
An Example from the Automation Industry
- Methods
- Skills
How to create awareness for some of the difficulties requirements engineers face
- Practice
- Methods
When requirements and the product are elaborated concurrently
- Methods
- Practice
Effective specifications to select off-the-shelf software
- Practice
Are the practices recommended by the IREB CPRE-FL syllabus still useful in agile projects?
- Practice
- Opinions
When every new iteration can violate previously satisfied requirements
- Skills
How to build a strong foundation for business analysis and requirements engineering inside a company
- Practice
Part 2: The Art of Assigning Software Development
- Practice
Part 1: Why Fixed Price Projects Fail
- Methods
Verification and Validation of System Requirements by Animation and Automated Formal Analysis.
- Studies and Research
Welcome outsourcing!
- Practice
Effective product management is the critical success factor to make a product successful – across its life-cycle and across markets.
- Methods
A new approach for requirements validation and rigorous verification.
- Methods
- Practice
Delegation of requirement verification. A key technique for more mature requirements management.
- Practice
State of the discussion: Requirements Engineering and Product Owner in Scrum
- Practice
The Main Thing is Keeping the Main Thing
the Main Thing
- Methods
- Practice
An agile and collaborative prioritization technique
- Practice
- Methods
Why Testers should have a closer look into Requirements Engineering