Software scope is a set of activities and actions to be performed as part of the delivery of a software product. Software scope should be well defined with phase-by-phase milestones, functionalities, and deliverable components. A question like this will be asked during an interview with Google regardless of your experience level in software development. This is a fundamental question that all software developers should know and know well. Let me give you some clarifying pointers that you can use for a better explanation and response. Software scope identifies a few different but essential elements including what the product will do, what is outside the scope of the project (what is not to be done), what the timeline is for completion of the project, who is documenting the list of deliverables, goals, tasks, and what the estimated cost of the project will be. One more part should be covered because it comes up more times than not in a Google interview. Project Scope creep. This is when the project experiences changes or uncontrolled growth during the project because the project was not well defined, documented, or controlled early in the project specification phase.