Program comprehension, i.e. to understand from its source code what a computer program does, is crucial for change and maintenance in software development. In this thesis, it is looked for innovative documentation techniques and tools that support program comprehension, but that are also conform to agile values and principles – commonly, documentation is considered critical due to the agile value “working software over comprehensive documentation.”1 First, a research framework is developed that embodies detailed requisites for such techniques and tools. Apart from its internal use for examining techniques and tools subsequently obtained from a literature search, this framework is intended to be likewise employed by software practitioners. Eventually, the findings of a series of survey studies conducted in an industrial software organization for the primary purpose of evaluating the obtained techniques and tools are analyzed. Three innovative techniques that meet all requisites are revealed. These are regarded by practitioners independently from the support of program comprehension as helpful for a change impact analysis conducted by non-developers. Therefore, a requisite deduced from the highest priority in agile software development – customer satisfaction – is met. It says that a technique or tool has to directly induce a benefit for non-developer stakeholders besides the benefits for them which are indirectly induced by the support of program comprehension, e.g. a potentially improved source code quality. Further, the technique most beneficial for developers as well as for non-developers among the three techniques is identified, which bases on design rationales – textual information related to the source code that states the reasons why a part of the program has been implemented in a certain way. Secondarily, the studies revealed that the research framework is difficult to understand for practitioners due to its unstructured form.