The step during development of a business scenario that ensures that each iteration is managed as a mini-project is the Planning Step3. The Planning Step is a preparatory step that defines how to approach each iteration of developing a business scenario3. The Planning Step involves setting up a project team with clear roles and responsibilities, defining a project plan with milestones and deliverables, identifying stakeholders and their concerns, establishing communication channels and feedback mechanisms, and securing resources and budget3. The Planning Step can help to ensure that each iteration is managed as a mini-project with clear objectives, scope, schedule, quality criteria, risks, and issues.

According to the TOGAF standard, business models are used to understand and describe the business itself, including its organization, its objectives, and how it operates. This understanding is crucial when defining an enterprise architecture as it provides a frame of reference. Business models help in identifying new capabilities that the business must develop to achieve its future state as outlined in the target business model. These capabilities may be processes, information, or technologies that the business must adopt or adapt to fulfill the strategic objectives and deliver value. TOGAF emphasizes the alignment of IT with business strategy, and the business model serves as a key link in ensuring that the capabilities delivered by the enterprise architecture will enable the desired business outcomes.

A statement of business goals and drivers can be used to help define information concepts in an information map. This statement provides the context and rationale for the information requirements of the enterprise, which can then be reflected in the information map, ensuring that the information architecture supports the business objectives.

The Architecture Development Method (ADM) is the core process of TOGAF which outlines a method for developing and managing the lifecycle of enterprise architecture. Considering the phases of the ADM, the item labeled as '2' in the provided architecture development cycle diagram likely corresponds to the 'Architecture Change Management' phase, which is responsible for providing ongoing architectural oversight and guidance to ensure that the implementation remains aligned with the architecture defined in the previous phases. This includes managing changes to the architecture in a controlled manner as the implementation progresses and ensuring that the architecture continues to meet the business needs.

The technique shown in the example is called heat mapping. It is a technique that can be used to show a range of different perspectives on a business capability map, such as maturity, effectiveness, performance, and value or cost contribution of each capability to the business2. Different attributes determine the colors of each capability on the business capability map. Heat mapping can help to identify strengths, weaknesses, opportunities, and threats in the business architecture.