Editing PRINCE2 (section)

==Integration with other techniques==
The management products described by PRINCE2 are only used for the "high-level" management of the project. Within its [[Task (project management)|tasks]], task managers must still decide on their own project management framework. Some suggestions given in the PRINCE2 manual are [[product based planning]], [[change control]], quality review technique, [[Kanban board|Kanban boards]], [[Gantt chart]]s, [[PERT chart]]s and [[critical path method|critical path]] analysis.

PRINCE2 can also be used to manage projects that use [[agile software development]] methods.<ref name="PRINCE2 Agile">{{cite web |title=PRINCE2 Agile® |url=https://www.axelos.com/best-practice-solutions/prince2/prince2-agile |website=www.axelos.com |publisher=Axelos |access-date=6 March 2015 |archive-url=https://web.archive.org/web/20150315054000/https://www.axelos.com/best-practice-solutions/prince2/prince2-agile |archive-date=15 March 2015 |url-status=dead  }}</ref>

===Quality review technique===
{{See also|Quality assurance}}
The quality review technique ensures a project's products are of the required standard (i.e. meet defined quality criteria). This takes place in a quality review meeting, which identifies errors in the product. The quality review meeting will not attempt to solve the problems it identifies. The meeting brings together people who have an interest in the project's outputs (or products) and people on the project team able to address issues identified.