SLR 6 - Software Development 2

What is the main focus of Rapid Application Development (RAD)?

• Long development cycles

• Formal design specifications

• Prototyping

• Rigid planning

Which of the following is NOT a benefit of RAD?

• Good for smaller projects

• Suitable for unclear requirements

• High code quality

• Emphasis on continuous feedback

What is a key criticism of RAD?

• Encourages sloppiness

• Requires high degree of communication

• Focuses on code quality

• Uses a kanban board

What is the core principle of Extreme Programming (XP)?

• Lack of user involvement

• Frequent releases in short development cycles

• Emphasis on rigid planning

• Focus on prototyping

In XP, what is the role of the user or their representative?

• To remove impediments

• To provide feedback at every stage

• To maintain the kanban board

• To manage the stakeholders

What is a key difference between XP and RAD?

• XP focuses on code quality

• RAD uses kanban boards

• XP has no user involvement

• RAD has frequent releases

What is the role of the Scrum Master in a Scrum project?

• To lead the team

• To provide user stories

• To manage the Product Backlog

• To safeguard the team's performance

What is the purpose of the Daily Scrum meeting?

• To evaluate the working environment

• To demonstrate new features

• To review progress and plan for the next 24 hours

• To discuss new requirements

What is a key concept of the Kanban approach?

• Limiting 'work in progress'

• Pair programming

• Frequent releases

• Daily stand-up meetings

What does a Kanban board typically include?

• User stories and epics

• Product Backlog

• Columns like 'To do', 'In progress', 'Blocked', and 'Done'

• Sprint Retrospective notes