During a sprint, if a developer needs to exclude a specific feature while keeping others, what method do they use?

The correct approach in this scenario is to recommit files with the deselection of the feature. This method allows the developer to include only the desired changes while explicitly excluding the specific feature that is not ready or needed for the current sprint. By doing this, the developer can maintain the integrity of the ongoing work and focus on delivering the remaining features without the potential impact of the excluded one.

This process usually involves selecting the specific modifications or files that are relevant to the sprint's objectives and committing only those changes to the version control system. This keeps the codebase clean and helps ensure that only the intended features are included in the development build, enabling a smoother integration and testing process.

The other options do not align well with standard practices in agile development. Rolling back to a previous version would negate any progress on other changes and is generally not advisable unless there is a critical issue. Making changes in a separate sprint is impractical for a feature that needs immediate exclusion, as it delays the delivery and can disrupt the workflow. Committing changes without exclusions would lead to including unwanted features, undermining the sprint's goals and potentially introducing instability to the project.