Emergent Design

Correct Answer: Emergent Design

The correct answer is 'Emergent Design'. In Agile methodologies, Emergent Design allows a system's design to emerge organically over time, as the system gains more features and complexity. It uses continuous refactoring, encouraged by test-driven or behavior-driven development. The Emergent Design practice suggests that a team should only focus on implementing the simplest solution possible to meet the needs of the current iteration, with the design organically ‘emerging’ over time. 'Iterative Design' is also an Agile concept, but it is about repetitively refining the design in response to user feedback rather than the design naturally 'emerging'. 'Responsive Design' pertains more to a UI/UX concept where a design adapts to different screen sizes. 'Haphazard Design' is not a recognized Agile design approach, this term usually refers to an unplanned, chaotic design process.

Correct Answer: Emergent Design

In the context of the situation provided, the team is implementing Emergent Design. This is an Agile approach where the design of the system evolves over time, starting small and becoming more comprehensive as the system is built and refactored. In this case, due to the increasing complexity of their initial design, the team decides to adopt a more adaptable and iterative design strategy which resembles the core characteristics of Emergent DesignContrarily, the other Agile methods listed, namely Kanban, Scrum, and Lean Development follow different principles. Kanban, for instance, is focused on visualizing work, limiting work in progress, and maximizing efficiency or flow. Scrum, on the other hand, involves teams working in time-frames (sprints) to complete specific work, along with daily meetings (scrums) to review progress and plan the day's work. Meanwhile, Lean Development emphasizes on the elimination of waste to deliver the software more reliably.

Correct Answer: Emergent Design

Emergent Design is the correct answer. This approach involves evolving the design of the system as requirements and constraints are understood better over time. It is common in Agile environments, where requirements and constraints are often not well-understood upfront as the team is in the middle of the project, so the design of the software evolves during its development. The question scenario is a perfect illustration of this approach where the team adjusted and evolved the software design in response to unexpected user requirements. Fixed Design Strategy would be incorrect because in the given scenario the design was not fixed and had to be adapted to new user requirements. Iterative Design Approach, though relates to revising and improving the design with each iteration, the given scenario mainly focuses on evolving design due to unexpected requirements. Adaptive Design generally relates to the ability of the system to adapt to varying conditions or inputs but does not necessarily mean that design itself is evolved or changed as new requirements emerge.