BiteSizedChunks.comLearn one small thing at a time.

Course contentsShow

Software Engineering

124Functional vs Non-Functional Requirements
125Business Requirements
126User Requirements
127System Requirements
128Performance Requirements
129Security and Compliance Requirements
130Usability and Accessibility Requirements
131Reliability and Availability Requirements
132Constraints and Assumptions
133Stakeholder Identification and Analysis
134Interview Techniques for Requirements
135Workshops and Facilitated Sessions
136Observation and Ethnographic Methods
137Document Analysis and System Archaeology
138Prototyping for Requirements Discovery
139Questionnaires and Surveys
140Domain Research and Competitive Analysis
141Handling Conflicting Stakeholder Needs
142Validating Elicited Requirements
143What is a User Story?
144The User Story Format
145Writing Effective User Stories
146User Story Components: Personas and Goals
147What are Acceptance Criteria?
148Writing Clear Acceptance Criteria
149Acceptance Criteria vs Definition of Done
150Story Splitting Techniques
151Conversations and Collaboration
152The Need for Prioritization
153MoSCoW Method
154Value vs. Effort Quadrants
155Weighted Scoring Models
156Stakeholder-Driven Prioritization
157Backlog Management
158Scope Creep and Change Control
159Communicating Priorities and Trade-offs
160Why Requirements Change
161Change Impact Analysis
162Change Request Processes
163Version Control for Requirements
164Communicating Changes to Stakeholders
165Building Flexibility into Requirements

Software Engineering

124Functional vs Non-Functional Requirements
125Business Requirements
126User Requirements
127System Requirements
128Performance Requirements
129Security and Compliance Requirements
130Usability and Accessibility Requirements
131Reliability and Availability Requirements
132Constraints and Assumptions
133Stakeholder Identification and Analysis
134Interview Techniques for Requirements
135Workshops and Facilitated Sessions
136Observation and Ethnographic Methods
137Document Analysis and System Archaeology
138Prototyping for Requirements Discovery
139Questionnaires and Surveys
140Domain Research and Competitive Analysis
141Handling Conflicting Stakeholder Needs
142Validating Elicited Requirements
143What is a User Story?
144The User Story Format
145Writing Effective User Stories
146User Story Components: Personas and Goals
147What are Acceptance Criteria?
148Writing Clear Acceptance Criteria
149Acceptance Criteria vs Definition of Done
150Story Splitting Techniques
151Conversations and Collaboration
152The Need for Prioritization
153MoSCoW Method
154Value vs. Effort Quadrants
155Weighted Scoring Models
156Stakeholder-Driven Prioritization
157Backlog Management
158Scope Creep and Change Control
159Communicating Priorities and Trade-offs
160Why Requirements Change
161Change Impact Analysis
162Change Request Processes
163Version Control for Requirements
164Communicating Changes to Stakeholders
165Building Flexibility into Requirements

← Software Engineering

Lesson 153 of 1,933·4. Requirements EngineeringPro lesson

MoSCoW Method

Using Must-have, Should-have, Could-have, and Won't-have categories to classify requirements by necessity.

This lesson is for subscribers

You've completed the free preview. Subscribe to unlock every lesson in every course.

See pricing Back to course