- Testing (8)
- Agile (24)
- Approaches (38)
- Attributes (4)
- Business Analysis (16)
- Elicitation (23)
- Estimation (5)
- Prioritization (5)
- Team (16)
- User Story (7)
- Template (2)
- Framework (7)
- Goals (8)
- Reuse (2)
- Software Engineering (7)
- Traceability (9)
- Perception (9)
- Management (11)
- Verification (5)
- Study (15)
- Development (9)
- CPRE (4)
- Automation (5)
- Documentation (15)
- Software Quality (9)
- ReqIF (1)
- Standards (3)
- Analysis (15)
- Business Value (7)
- Metrics (5)
- Validation (9)
- Modeling (11)
- Security (2)
- SysML (3)
- Stakeholder (8)
- Big Data (3)
- Opinion (13)
- Literature (3)
How you can use the natural partitioning of business events to flexibly synchronise your agile development.
How applying Lean Startup, Design Thinking, and others, impact the task of modeling requirements
Who works in RE and what competences do they need, particularly soft skills?
Views of a real RE pioneer
The Future How Viewpoint.
Preliminary Results from an Ongoing Study
‘A large elephant is in the room but we are not able or brave or willing enough to point at it’
An Approach for the Inspection of the Completeness of individual Software Requirements Specifications by Semantic Analysis of the Argument Structures
Evaluating Business Analysts‘ role in the Data Driven Economy
Using verbs’ valency to improve requirements’ quality
Improving requirements quality by effort estimates
How to use requirements gathering techniques to determine product requirements from non-verbal subjects
Requirements Engineering at Dutch Railways
A short and fun elicitation workshop for Agile teams and architects
Some thoughts on problems and goals in the context of requirements engineering
Requirements and where to put them
From Requirements to Code
What is Agile Business Analysis, and 10 reasons why it’s worth developing the competency within your agile organization
Goals are intended, Requirements are imposed
Agile in the Large Enterprise
What are the levels of granularity of functional requirements and why this is important
How bias will affect even the simplest of specifications
When shall does not need to be must
An approach for iterative and requirements-based quality assurance in DevOps
Do you know what acceptance criteria are?
Ensuring Software Quality beyond Micromanagement
Driving innovation with crowd-based techniques
How to create awareness for some of the difficulties requirements engineers face
Results of research project announced in a previous issue.
New opportunities for requirements engineers & challenges within the organization
Effective specifications to select off-the-shelf software
When requirements and the product are elaborated concurrently
How to build a strong foundation for business analysis and requirements engineering inside a company
When every new iteration can violate previously satisfied requirements
Are the practices recommended by the IREB CPRE-FL syllabus still useful in agile projects?
How can the standard UML FSM be improved to better serve the requirements engineer?
Has RE adapted itself to the challenges of Agile methods?
Part 2: The Art of Assigning Software Development
Paying attention to requirements in an agile work environment
How to capture the functional size of an application in early project phases and how to create a reliable cost estimate
Part 1: Why Fixed Price Projects Fail
9 Essentials for Product Success
Agile Requirements Engineering Procedure Model using the RE Tool Jama.
My experiences from the Telecoms industry.
Effective product management is the critical success factor to make a product successful – across its life-cycle and across markets.
The Main Thing is Keeping the Main Thing the Main Thing
State of the discussion: Requirements Engineering and Product Owner in Scrum
Delegation of requirement verification. A key technique for more mature requirements management.
Why Testers should have a closer look into Requirements Engineering
An agile and collaborative prioritization technique