Q methodology is a research method with a proven history for illuminating agreement and differences among individual and group perceptions. This technical note describes ways for applying Q methodology to assist software engineering processes. As a project management tool, it can help to articulate system requirements and project risk. It can also be used to identify many of the hidden risks and costs associated with system efforts. Q methodology complements a project manager's suite of methodologies and tools by providing a means for uncovering stakeholder perceptions of incorrectly specified requirements, looming risks, and hidden costs. In doing so, it provides stakeholders and project managers with additional insights for troubleshooting project threats.
This report is related to the following area(s) of work:
Process ImprovementTechnical Note
CMU/SEI-2004-TN-026
October 2004
SEI:
Brown, Mary; Illuminating Patterns of Perception: An Overview of Q Methodology (CMU/SEI-2004-TN-026). Software Engineering Institute, Carnegie Mellon University, 2004. http://www.sei.cmu.edu/library/abstracts/reports/04tn026.cfm
IEEE:
M. Brown, "Illuminating Patterns of Perception: An Overview of Q Methodology," Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania, Technical Note CMU/SEI-2004-TN-026, 2004. http://www.sei.cmu.edu/library/abstracts/reports/04tn026.cfm
APA:
Brown, M., (2004). Illuminating Patterns of Perception: An Overview of Q Methodology (CMU/SEI-2004-TN-026). Retrieved June 18, 2013, from the Software Engineering Institute, Carnegie Mellon University website: http://www.sei.cmu.edu/library/abstracts/reports/04tn026.cfm
CHI:
Brown, Mary, Illuminating Patterns of Perception: An Overview of Q Methodology (CMU/SEI-2004-TN-026). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2004. http://www.sei.cmu.edu/library/abstracts/reports/04tn026.cfm
MLA:
Brown, M., 2004. Illuminating Patterns of Perception: An Overview of Q Methodology (Technical Report CMU/SEI-2004-TN-026). Pittsburgh: Software Engineering Institute, Carnegie Mellon University. http://www.sei.cmu.edu/library/abstracts/reports/04tn026.cfm
For more information