Information Systems Acquisition, Development, and Implementation - Acquisition and Development

Correct Answer: To explore multiple design solutions in parallel before converging on the final approach

In Lean Software Development methodology, Set-Based Design refers to exploring multiple design solutions in parallel rather than iterating on a single solution. The correct answer describes this approach accurately. Set-Based Design involves considering multiple design options simultaneously and gradually eliminating inferior alternatives as more knowledge is gained, until converging on an optimal solution. The second option is incorrect because it describes a waterfall-like approach with detailed specifications before implementation, which contradicts Lean's iterative nature. The third option describes iterative refinement of a single solution, which is more aligned with traditional iterative development rather than Set-Based Design's parallel exploration approach. The fourth option incorrectly emphasizes comprehensive documentation, which runs counter to Lean's focus on eliminating waste and unnecessary documentation.

Correct Answer: Providing strategic direction and resolving escalated issues

The project steering committee is responsible for providing strategic direction, oversight, and executive-level decision making for projects. They typically handle high-level guidance, approve major deliverables, resolve escalated issues that cannot be resolved at the project management level, and ensure the project aligns with organizational goals. Option A is correct because providing strategic direction and resolving escalated issues are indeed primary responsibilities of a steering committee. Option B is incorrect because handling daily operational tasks and resource allocation are responsibilities of project managers and team leads, not the steering committee which operates at a higher strategic level. Option C is incorrect because creating detailed project schedules and assigning technical tasks are responsibilities of project managers and technical leads, which are tactical rather than strategic activities. Option D is incorrect because developing technical documentation and maintaining project artifacts are responsibilities of project team members, technical writers, or configuration management personnel, not the steering committee.

Correct Answer: To synchronize activities and identify impediments

The primary purpose of a Daily Standup meeting in Scrum is to synchronize activities and identify impediments. This brief (typically 15-minute) meeting allows team members to share what they've accomplished since the last meeting, what they plan to work on next, and any blockers or challenges they're facing. The other answers are incorrect: - Performing detailed technical design reviews and assigning tasks is not the purpose of the Daily Standup. In Scrum, teams are self-organizing, and the Daily Standup is for coordination, not for managers to assign work. - Evaluating and grading individual performance is contrary to Scrum principles, which emphasize team accountability rather than individual evaluation during these meetings. - Having extended discussions about implementation details contradicts the time-boxed nature of the Daily Standup. Such discussions should be taken offline with only relevant team members after the standup concludes.