Is the approach of continually developing new process models the right one? This central question arises from the experiences described in the student laboratory of the Competence Center for Agile IT Processes (KAP). Does strict adherence to a prescribed process model overly constrain the team? Isn’t it generally better to merely define the framework conditions for the process and allow the team to find the appropriate agile team process themselves? The answer to this is provided by the Meta Agile Process Model (MAP), developed by the author and first published in 2009: MAP is a systemic model that defines the framework conditions for the process but gives the team sufficient space to find the appropriate agile team process themselves. In particular, an organizational-psychological perspective of the team is taken into account. From the “map of behaviors within the team” (the “MAP types”), the prerequisites for team success are derived and their relevance demonstrated. The chapter is rounded off by the conditions for the coexistence of MAP with Scrum and the description of successful MAP projects in practice, especially in regulated environments.