GQM+Strategies

From Wikipedia, the free encyclopedia
Jump to: navigation, search

GQM+Strategies [1][2] is a method that provides concepts and actionable steps for creating the link between goals and strategies across an organization and allows for measurement-based decision-making. It was developed by Victor Basili, Jens Heidrich, Mikael Lindvall, Jürgen Münch, Myrna Regardie, Carolyn B. Seaman, and Adam Trendowicz. The method was originally developed for organizations having a strong focus on IT and the development of software systems, but the method's popularity has grown to other domains and can be applied to any organization. The book Aligning Organizations through Measurement[3] gives a comprehensive overview of the method, provides actionable guidance, case studies, and practical applications.

Background[edit]

In today's competitive markets organizational survival and growth requires effective means of aligning the large variety of organizational goals and strategies to achieve business objectives. Effective alignment helps all parts of the organization move in the same direction. Determining the impact of business goals and strategies is crucial for effective decision making within a company. Different goals and strategies exist at different levels of an organization (e.g., on the management level, the department level, the project level). In practice, these goals and strategies are often not aligned and their success or failure is often determined as a gut feeling. For instance, in a software organization, engineers are frequently faced with apparently unrealistic goals related to software development. There is rarely a discussion of trade-offs or other options for such decisions in order to avoid deviations of budget and schedule. Goals and strategies need to be defined explicitly and derived from high-level business goals in a systematic and transparent way. Moreover, underlying assumptions and environmental factors are often not documented, which makes it hard to determine the reasons for failed strategies. Furthermore, if measurement data is collected on the project level, it is often unclear how the activities performed there and the data collected contribute to higher-level goals of the organization. Moreover, building an effective measurement program is a challenging task in itself. It involves observation, experience facilitation, collaboration, decision making, analysis, and synthesis regarding goals, context factors, and assumptions. Furthermore, it assumes an organizational structure that sustains the process and learns.

Idea[edit]

The major output of applying the GQM+Strategies approach is the so-called GQM+Strategies grid. The grid specifies goals and strategies across all levels of an organization including the measurement program needed to monitor and control them. The underlying meta-model allows multiple goal levels and permits deriving multiple strategies for each of these goal levels. A goal may be realized by a set of strategies, which may in turn lead to a sequence of goals. Selection and adaptation of predefined goals and strategies as well as definition of new goals and strategies is driven by so-called context factors and assumptions. Context factors are environmental variables that represent the organizational environment and affect the kind of models and data that can be used (e.g., the type of business, the market of an organization). Assumptions are estimated unknowns that can affect the interpretation of the data (e.g., improving customer satisfaction will increase sales). The entire GQM+Strategies model provides an organization with a mechanism not only for defining measurement consistent with larger, upper-level organizational concerns, but also for interpreting and rolling up the resulting measurement data at each level. At each goal level, measurement plans are defined in order to measure the achievement of the defined goal in combination with the chosen strategy though GQM.

The GQM+Strategies application process supports building a grid in different ways depending on whether you want to start from the top level, from the bottom level, or from somewhere in the middle of an organization. In consequence the approach addresses relevant stakeholders throughout different organizational levels.

Benefits[edit]

The GQM+Strategies method makes high-level goals, strategies, and related measurement goals explicit across all levels of an organization. The entire method provides an organization with a mechanism for defining software measurement addressing larger, upper-level organizational concerns and for interpreting and rolling up the resulting measurement data at each level. GQM+Strategies has numerous benefits such as the effective use of resources and rapid and focused improvement. It enables an organization to consistently align goals and strategies across different units, enable measurement-based decision making, transparently communicating goals and strategies within the organization, and objectively monitoring goal attainment and the success/failure of defined strategies.The approach works as an integrator for existing measurement approaches in an organization.

Experiences and Practical Applications[edit]

GQM+Strategies is typically used to link strategies with their impacts on goals and to identify existing gaps in aligning goals and strategies. Experiences from case studies in industry and evaluations of the method have been reported in literature, e.g., experiences from applying GQM+Strategies at Elektrobit[4] and an evaluation with respect to the effects of GQM+Strategies on organizational alignment.[5] Current research[6] evaluated the approach utilizing revised Bloom's taxonomy as a framework for assessing the practitioners’ cognition level of the concepts. The evaluation showed that the method has practical value and addresses current real-world problems. The approach has been applied in different industrial settings and different domains so far reaching from telecommunication, automotive, and aerospace to classical information system.[7] Most of the case studies were focusing on setting up a grid. As organizational goals and strategies change, the grid needs to be adapted accordingly and needs to be deployed to organization in a controlled manner. Therefore, future work addresses deployment and maintenance aspects of the approach.

Other Approaches[edit]

Several approaches to (software) measurement have been developed using different mechanisms for guiding the choice of data to be collected and analyzed:

  • The GQM[8] approach provides a method for defining goals, refining them into questions and finally data to be collected, and then analyzing and interpreting them. Several instruments and tools are available for visualizing the GQM model (e.g., as an abstraction sheet or a GQM tree).
  • Balanced Scorecard (BSC)[9] links strategic objectives and measures. The typical visualization consists of four perspectives: financial, customer, internal business processes, and learning and growth. Strategy maps are used to link strategies associated with those perspectives.
  • Practical Software Measurement (PSM)[10] offers detailed guidance on software measurement. Tree-like structures are used to link issues, measurement categories, and measures.
  • Becker and Bostelman[11] address the misalignment between strategy at the organizational level and the project level of software organizations. They focus on two causes of misalignment: (1) project data that does not address organizational goals and (2) organizational goals that are not operationalized through processes and metrics at the project level. The authors propose a common measurement framework to support the alignment of organizational and project-level goals. Their approach is to embed a GQM structure within each of the four BSC perspectives.
  • The M3P – Model, Measure, Manage Paradigm[12] – is an extension of the QIP and GQM presented by Offen and Jeffery. Similar to Becker and Bostelman's approach, M3P embeds GQM as a measurement definition technique within a larger framework that encompasses higher-level organizational concerns.
  • COBIT[13] and ITIL[14] are approaches from the IT governance/service domain and offer connections between sets of goals and attributes of the IT infrastructure. COBIT uses a fixed linkage structure between outcome measures and performance indicators on the business, IT, process, and activity levels. Although these approaches recognize the need to link organizational goals and measures, they do not support building up a comprehensive grid of goals and strategies at different levels of the organization that are linked explicitly.

References[edit]

  1. ^ Basili, V.R.; J. Heidrich, M. Lindvall, J. Münch, C.B. Seaman, M. Regardie, A. Trendowicz (2009). "Determining the impact of business strategies using principles from goal-oriented measurement". Business Services: Konzepte, Technologien, Anwendungen. 9. Internationale Tagung Wirtschaftsinformatik. Books OCG. Vienna, Austria: Österreichische Computer Gesellschaft. ISBN 978-3-85403-246-5. 
  2. ^ Basili, Victor R; Mikael Lindvall; Myrna Regardie; Carolyn Seaman; Jens Heidrich; Jurgen Munch; Dieter Rombach; Adam Trendowicz (2010). "Linking Software Development and Business Strategy Through Measurement". Computer 43 (4): 57–65. doi:10.1109/MC.2010.108. ISSN 0018-9162. Retrieved 2010-05-26. 
  3. ^ Basili, Victor; Adam Trendowicz; Martin Kowalczyk; Jens Heidrich; Carolyn Seaman; Jürgen Münch; Dieter Rombach (2014). Aligning Organizations through Measurement - The GQM+Strategies Approach. Springer-Verlag. 
  4. ^ Münch, Jürgen; Fabian Fagerholm; Petri Kettunen; Max Pagels; Jari Partanen (2013). "The Effects of GQM+Strategies on Organizational Alignment". Proceedings of the DASMA Software Metric Congress (MetriKon 2013). Magdeburger Schriften zum Empirischen Software Engineering. Kaiserslautern, Germany: University of Magdeburg. 
  5. ^ Münch, Jürgen; Fabian Fagerholm; Petri Kettunen; Max Pagels; Jari Partanen (2013). "Experiences and Insights from Applying GQM+Strategies in a Systems Product Development Organisation". Proceedings of the 39th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA 2013). Santander, Spain. 
  6. ^ Mandic, V.; L. Harjumaa; J. Markkula; M. Oivo (2010). "Early Empirical Assessment of the Practical Value of GQM+Strategies". International Conference on Software Process, ICSP 2010 Proceedings. LNCS. Paderborn, Germany: Springer-Verlag. 
  7. ^ "GQM+Strategies application domains". March 2010. Retrieved 2010-04-07. 
  8. ^ Basili, V.R.; G. Caldiera; D. Rombach (1994). "The Goal Question Metrics Approach". Encyclopedia of Software Engineering (Wiley). 
  9. ^ Kaplan, R.; D. Norton (1992). "The Balanced Scorecard-Measures That Drive Performance". Harvard Business Review. 
  10. ^ "Practical Software Measurement, A Foundation for Objective Project Management, v. 4.0b". October 2000. Retrieved 2007-04-12. 
  11. ^ Becker, S.A.; M.L. Bostelman (1999). "Aligning Strategic and Project Measurement Systems". IEEE Software 16 (3): 46–51. doi:10.1109/52.765786. 
  12. ^ Offen, R.J.; R. Jeffery (1997). "Establishing Software Measurement Programs". IEEE Software 14 (2): 45–53. doi:10.1109/52.582974. 
  13. ^ "Control Objectives for Information and related Technology (COBIT)". Retrieved 2007-04-12. 
  14. ^ Office of Government Commerce (OGC) (2002). The IT Infrastructure Library (ITIL) Service Delivery. The Stationery Office London.