In an agile process, design is an ongoing activity that occurs within each iteration or sprint, rather than a single upfront phase. During an iteration's design activities, the development team determines the specific technical approach to implement user stories. This includes identifying the necessary functions, classes, methods, and their interactions to meet the requirements of the features being built in that specific cycle. This detailed, just-in-time design is a hallmark of agile development, focusing on the immediate work at hand.

A. Writing objects is part of the implementation or development phase, which follows the design decisions made within the sprint.

B. Deciding the overall scope of the program is a high-level planning or inception activity that typically occurs before the first sprint begins.

C. Determining the high-level goals of the project is part of the initial project vision and chartering, preceding the iterative development cycles.

1. Fowler, M. (2005). The New Methodology. MartinFowler.com. Section: "Iterative Development". Fowler explains that in iterative methods like agile, design is spread throughout the project in small increments.

2. University of California, Berkeley. (2016). Agile Development. Agile 101, EECS 194. The course material describes how design in agile is emergent and happens in every sprint, focusing on the current backlog items.

3. Ambler, S. W. (2013). Agile Modeling (AM) Home Page. AgileModeling.com. Section: "Core Principles of Agile Modeling". Principle #3, "Create Several Models in Parallel," and Principle #5, "Model in Small Increments," describe how design activities (modeling) are continuous and iterative.