Ingegneria dei Sistemi Software e dei Servizi di Rete

Fwd: Re: [GQM] GQM+Strategies Application Scenarios


Cronologico Percorso di conversazione 
  • From: Giovanni Cantone < >
  • To:
  • Subject: Fwd: Re: [GQM] GQM+Strategies Application Scenarios
  • Date: Tue, 22 Jan 2013 15:28:01 +0100



----- Messaggio inoltrato da 

 -----
    Data: Mon, 21 Jan 2013 23:25:18 +0200
    Da: OMISSIS 
< >
 Oggetto: Re: [GQM] GQM+Strategies Application Scenarios
      A: 

      Cc: OMISSISiese.fhg.de

Hi,

One scenario I have seen is harmonization, i.e., identifying
goals on different levels of an organization and trying to match them.
I have also seen that several goals on one level were
independently defined, did not match or were not coordinated and
the resolution was done in an undefined way on lower levels (typically
by development teams). An example is that teams got content goals, quality goals, and
improvement goals from different directions in the organization (and
the line management had different goals as well). GQM+ can be used to
identify such conflicting, uncoordinated or not matching goals, to harmonize them, and to
improve prioritization of such goals.

I am not sure if this is already covered by your scenarios. Based on my
experience it seems to be especially relevant in large organizations.



                Best regards,



                                        Jürgen


--
Prof. Dr. OMISSIS
Department of Computer Science, University of Helsinki, Finland
,
 www.sserg.org
Phone: +358 50 3175318, Gustav Hällströmin katu 2b, Room C230a




Am 21.01.2013 um 17:06 schrieb OMISSIS:

Dear All,

In the context of collaboration with Japanese IPA/SEC and the work on the GQM+Strategies book we identified the need for specifying typical application scenarios for the GQM+Strategies approach. Please find attached two slides containing: (1) proposed list of scenarios and (2) an overview of recent GQM+Strategies applications with corresponding scenarios assigned. We would be grateful for your comments and remarks. Besides the completeness and conference of the list we would like to know your opinion regarding the naming of the scenarios (especially the native speakers' perspective would be needed). For example, Japanese have suggested the following changes based on their understanding of current naming:

- changing "Value Demonstration" to "Value Visualization" because in Japan, "demonstration" is perceived as "aggressive power" ("mieruka") and "Visualization" will be perceived as intended.
- changing "Internal Communication" to "Internal Sharing" because in Japan, the "communication" simply means "to convey" without any value addition. "Sharing", on the other hand, is perceived as being more proactive.

However, we think using "Visualization" and "Sharing", as suggested above, might be misleading in general (outside Japan). Our suggestion would be rather to use English naming and then adjusting it to specific geographical context by providing parallel, context-specific translation (although it might not be literal translation).

Please let us know your opinion.

Thank you!

Best regards,
Adam

--
Dr. OMISSIS, Senior Engineer
Department " Measurement, Prediction, and Empiricism"
Fraunhofer IESE | Fraunhofer-Platz 1 | 67663 Kaiserslautern | Germany
Phone: +49 631 6800-2137 | Fax: +49 631 6800-9-2137
http://www.iese.fraunhofer.de ;| 
mailto:

<GQM+Strategies Application Scenarios.pptx>_______________________________________________


----- Fine messaggio inoltrato. -----


----------------------------------------------------------------
Invito da parte dell'Ateneo:
Il tuo futuro e quello della Ricerca Scientifica hanno bisogno del
tuo aiuto. Dona il  5 x mille all'Universita' di Roma Tor Vergata
codice fiscale: 80213750583 http://5x1000.uniroma2.it





Archivio con motore MhonArc 2.6.16.

§