Software scope is a set of activities and actions that are 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 regardless of what experience level you are at in software development. This is a fundamental question that all software developers should know, and should 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 important elements including what the product will do, what is outside the scope of the project (what is not to be done), what is the timeline for completion of the project, who is documenting the list of deliverables, goals, tasks, and what the estimated cost of the project will be. There's one more part that should be covered because it comes up more times than not in an interview. Project Scope creep. This is when a the project experiences changes or uncontrolled growth during the project. The reason for this is because the project was not well defined, documented or controlled early in the project specification phase.