This document discusses the differences between elective and requirements capture methodologies in software development. Elective methodology focuses on developing features without fully understanding user needs, which can result in building unnecessary features. Requirements capture prioritizes understanding user jobs, pains and gains to determine what problems need to be solved before identifying solutions. It aims to result in developing only the most critical and valuable features for users.