formulation of process improvement knowledge ~ 7 ... · so norimatsu, kiyoshi endo, makoto usugi,...

29
24th EuroSPI & EuroAsiaSPI Conference WS 4 Good and Bad Practices in Improvement 8. September 2017, Technical University of Ostrava, Ostrava, Czech Republic Formulation of process improvement knowledge ~ 7 components of a good PI story ~ So NORIMATSU, Kiyoshi ENDO, Makoto USUGI, Aiichiro NIWA, Eiwa KATAYAMA, Tomohiro HASHIMOTO, Koichi TANGE Japan Software Process Improvement Consortium (JASPIC) 1

Upload: others

Post on 29-Jan-2021

1 views

Category:

Documents


0 download

TRANSCRIPT

  • 24th EuroSPI & EuroAsiaSPI Conference WS 4 Good and Bad Practices in Improvement8. September 2017, Technical University of Ostrava, Ostrava, Czech Republic

    Formulation of process improvement knowledge~ 7 components of a good PI story ~

    So NORIMATSU, Kiyoshi ENDO, Makoto USUGI, Aiichiro NIWA, Eiwa KATAYAMA, Tomohiro HASHIMOTO, Koichi TANGE

    Japan Software Process Improvement Consortium (JASPIC)1

  • かけた論文は、かけてない

    Is this paper whole? or holed?

    Japan Software Process Improvement Consortium (JASPIC)

    2

  • About Japan Software Process Improvement Consortium

    ・ Objectives for Japan SPI ConsortiumJapan SPI Consortium (JASPIC), a non-profit organization established for collecting and disseminating “good practices” in Software Process Improvement efforts, have been organizing SPI conferences in Japan since 2003. Industrial experiences are presented along with keynote presentations, workshops, and tutorials. These presentations are publicly available for future usage.

    ・ Objectives for our special interest groupTo further develop systematic knowledge base of Process Improvement, the authors have formed a special interest group within JASPIC. We have analyzed the presentations of SPI conferences in Japan to extract various forms of knowledge (e.g. keywords, concepts, principles, and good practices) so that it will support producing more successful stories in the community.

    3Japan Software Process Improvement

    Consortium (JASPIC)

  • • Date: October 11-13th, 2017• Place: Tower hall Funabori (Edogawa-ward, Tokyo)• Access:

    SPI-Japan 2017 Conference

    4Japan Software Process Improvement

    Consortium (JASPIC)

  • Introduction of our research group

    Body of knowledge and Web of knowledge

    Process improvement and innovation process

    Project Management(PMBOK,…) Software Engineering(SWEBOK,…)

    Web of knowledge for SPI(SPIWOK)

    Training process

    Qualification and ability evaluation process

    Learning and research process

    Others, …..

    Personal process(PSP,…)

    5Japan Software Process Improvement

    Consortium (JASPIC)

    Body of knowledge for SPI(SPIBOK)

  • About “formulation of knowledge”

    Purpose of our research group

    tacit

    tacit

    formal

    formal

    cooperate appear

    connectdeepen

    Source: SECI-Model by NONAKA"Management of knowledge creation" Ikujirou Nonaka, Nihon Keizai Shimbun, Inc./1990)

    6

    The evolution cycle of the knowledge

    Japan Software Process Improvement Consortium (JASPIC)

  • About “formulation of knowledge”

    Purpose of our research group

    tacit

    tacit

    formal

    formal

    cooperate appear

    connectdeepen

    Source: SECI-Model by NONAKA"Management of knowledge creation" Ikujirou Nonaka, Nihon Keizai Shimbun, Inc./1990)

    7

    The evolution cycle of the knowledge

    Japan Software Process Improvement Consortium (JASPIC)

    low reusability lack of information

    low consistency

    Problems,challenges

    low quality

  • About “formulation of knowledge”

    Purpose of our research group

    tacit

    tacit

    formal

    formal

    cooperate appear

    connectdeepen

    Source: SECI-Model by NONAKA"Management of knowledge creation" Ikujirou Nonaka, Nihon Keizai Shimbun, Inc./1990)

    8

    The evolution cycle of the knowledge

    Japan Software Process Improvement Consortium (JASPIC)

    presentation at SPI Japan conference

    research groups(Body of Knowledge)

    formulation by template

    Oursolutions

  • Basic structure of the process improvement activity

    9Japan Software Process Improvement

    Consortium (JASPIC)

  • Improvement of the template(old)Template for Conference Presentation(new)

    (1) Background(2) Problems,challenges(3) Contents(Idea,etc.)(4) Effect

    10Japan Software Process Improvement

    Consortium (JASPIC)

    (1) Background(2) State before improvement(3) Causes that brought the

    state before improvement (i.e. causality)

    (4) Content of changes and/or countermeasures

    (5) Implementation of changes and/or countermeasures

    (6) State after improvement and the effect of change

    (7) Validation of improvement activity

  • 11Japan Software Process Improvement

    Consortium (JASPIC)

    Improvement of the templateRelationships among components of the new template

  • (1) Background* Motive for the activity described in this presentation, original purpose and premise, etc..

    (2) State before improvement* Selected situation, problems and symptoms considered as improvement target.

    * And, the rationale of selection.

    (3) Causes that brought the state before improvement (i.e. causality)* Phenomenon and/or cause that created a state before improvement (e.g. some processes). There can be more than one

    phenomena or cause.

    * And, the method that revealed/selected/identified these phenomena and causes.

    (4) Content of changes and/or countermeasures* Change includes situations such as "Something is changed", "Something is abolished", and "A new thing is added".

    * And, the rationale of selection.

    (5) Implementation of changes and/or countermeasures* Activities performed to achieve the change or to implement the countermeasure.

    * And, any devised efforts, or issues that were encountered.

    (6) State after improvement and the effect of change* Changes that occurred after (5) “implementation of changes and/or countermeasures”.

    * Changes of situation specified in (2) "state before improvement”, i.e. effect of change.

    * And, verification of changes being not accidental. (if possible)

    (7) Validation of improvement activity* Validity of the improvements, cost-effectiveness, remaining issues, secondary effect, after analyzing overall improvement

    activity.

    The new template

    12Japan Software Process Improvement

    Consortium (JASPIC)

  • (1) Background* Motive for the activity described in this presentation, original purpose and premise, etc..

    (2) State before improvement* Selected situation, problems and symptoms considered as improvement target.

    * And, the rationale of selection.

    (3) Causes that brought the state before improvement (i.e. causality)* Phenomenon and/or cause that created a state before improvement (e.g. some processes). There can be more than one

    phenomena or cause.

    * And, the method that revealed/selected/identified these phenomena and causes.

    (4) Content of changes and/or countermeasures* Change includes situations such as "Something is changed", "Something is abolished", and "A new thing is added".

    * And, the rationale of selection.

    (5) Implementation of changes and/or countermeasures* Activities performed to achieve the change or to implement the countermeasure.

    * And, any devised efforts, or issues that were encountered.

    (6) State after improvement and the effect of change* Changes that occurred after (5) “implementation of changes and/or countermeasures”.

    * Changes of situation specified in (2) "state before improvement”, i.e. effect of change.

    * And, verification of changes being not accidental. (if possible)

    (7) Validation of improvement activity* Validity of the improvements, cost-effectiveness, remaining issues, secondary effect, after analyzing overall improvement

    activity.13

    Japan Software Process Improvement Consortium (JASPIC)

    Degree of coverage : evaluated items (Red : 7 points are perfect.)

  • (1) Background* Motive for the activity described in this presentation, original purpose and premise, etc..

    (2) State before improvement* Selected situation, problems and symptoms considered as improvement target.

    * And, the rationale of selection.

    (3) Causes that brought the state before improvement (i.e. causality)* Phenomenon and/or cause that created a state before improvement (e.g. some processes). There can be more than one

    phenomena or cause.

    * And, the method that revealed/selected/identified these phenomena and causes.

    (4) Content of changes and/or countermeasures* Change includes situations such as "Something is changed", "Something is abolished", and "A new thing is added".

    * And, the rationale of selection.

    (5) Implementation of changes and/or countermeasures* Activities performed to achieve the change or to implement the countermeasure.

    * And, any devised efforts, or issues that were encountered.

    (6) State after improvement and the effect of change* Changes that occurred after (5) “implementation of changes and/or countermeasures”.

    * Changes of situation specified in (2) "state before improvement”, i.e. effect of change.

    * And, verification of changes being not accidental. (if possible)

    (7) Validation of improvement activity* Validity of the improvements, cost-effectiveness, remaining issues, secondary effect, after analyzing overall improvement

    activity.14

    Japan Software Process Improvement Consortium (JASPIC)

    Degree of completeness : evaluated items (Blue : 13 points are perfect.)

  • Evaluation result of the coverage

    15

    0

    2

    4

    6

    8

    10

    12

    14

    0 1 2 3 4 5 6 7

    Evaluation result of the coverage (FY2011)

    Degree of coverage

    Degree of com

    pleteness

    0

    2

    4

    6

    8

    10

    12

    14

    0 1 2 3 4 5 6 7

    Evaluation result of the coverage (FY2013)

    Degree of com

    pleteness

    Degree of coverage

    Japan Software Process Improvement Consortium (JASPIC)

    Before improvement After improvement(1st year)

  • Description statistics value of the coverageFY2011 FY2013

    Degree of coverageMean and the 95%confidence interval 3.24(46%)

    2.67-3.814.32(62%)3.55-5.09

    Standard deviation 1.39 1.86Degreeof completenessMean and the 95%confidence interval 6.50(50%)

    5.65-7.347.80(60%)6.76-8.84

    Standard deviation 2.05 2.51 16Japan Software Process Improvement

    Consortium (JASPIC)

  • Evaluation result of the coverage

    17Japan Software Process Improvement

    Consortium (JASPIC)

    After improvement(2nd year) After (3rd year) After (4th year)

  • Outcome until now

    Annual trend of scores from 2011 to 2016

    18Japan Software Process Improvement

    Consortium (JASPIC)

  • Comparison of scores for frequently missing items

    FrequentlyMissing Item

    2011Score

    2016Score

    Ratio(2016/2011)

    causal analysisof issues

    0.54 0.94 (1.7)

    verification ofresults

    0.06 0.30 (5.0)

    validation ofimprovementactivity

    0.12 0.91 (7.6)

    19Japan Software Process Improvement

    Consortium (JASPIC)

  • Comparison of scores for “successful stories”

    2011Score

    2016Score

    Ratio(2016/2011)

    Score forverification

    0.64/2.0

    1.61/2.0

    (2.5)

    Score forvalidation

    0.04/3.0

    1.00/3.0

    (25)

    Total(verification +validation)

    0.68/5.0

    2.61/5.0

    (3.8)

    20Japan Software Process Improvement

    Consortium (JASPIC)

  • • In order to collect “good process improvement stories” in the SPI conference in Japan, we formalized the structure of process improvement knowledge and standardized it as a template to be used in the conference proposal.

    • As a result, the amount of information included in these PI stories increased steadily over the last four years.

    • The quality of knowledge also improved as we saw significant growth in the scores of “successful stories”.

    Conclusion

    21Japan Software Process Improvement

    Consortium (JASPIC)

  • • Establishing – Process Improvement Body of Knowledge

    • (Draft) Ontology of Concepts used in Process Improvement

    – Process Improvement Web of Knowledge• (Prototype of) Knowledge Base

    • Using PI Story template– for PI project management

    Next target

    22Japan Software Process Improvement

    Consortium (JASPIC)

  • 欠けた論文は、書けてないHoled paper is not whole (completely written).

    書けた論文は、欠けてないWhole (completely written) paper is not holed.

    Summary

    かけた論文は、かけてない

    23

    2 sentences have the same pronunciation in Japanese.

    Japan Software Process Improvement Consortium (JASPIC)

  • Backup slides

    24

  • 0

    2

    4

    6

    8

    10

    12

    14

    0 1 2 3 4 5 6 7

    Evaluation result of the coverage (FY2011)

    Degree of coverage

    Degree of com

    pleteness

    Outcome until now

    25Japan Software Process Improvement

    Consortium (JASPIC)

  • 0

    2

    4

    6

    8

    10

    12

    14

    0 1 2 3 4 5 6 7

    Evaluation result of the coverage (FY2013)

    Degree of com

    pleteness

    Degree of coverage

    Outcome until now

    26Japan Software Process Improvement

    Consortium (JASPIC)

  • 0

    2

    4

    6

    8

    10

    12

    14

    0 1 2 3 4 5 6 7

    Evaluation result of the coverage (FY2014)

    Degree of com

    pleteness

    Degree of coverage

    Outcome until now

    27Japan Software Process Improvement

    Consortium (JASPIC)

  • 0

    2

    4

    6

    8

    10

    12

    14

    0 1 2 3 4 5 6 7

    Degree of com

    pleteness

    Degree of coverage

    Evaluation result of the coverage (FY2015)

    Outcome until now

    28Japan Software Process Improvement

    Consortium (JASPIC)

  • 0

    2

    4

    6

    8

    10

    12

    14

    0 1 2 3 4 5 6 7

    Degree of com

    pleteness

    Degree of coverage

    Evaluation result of the coverage (FY2016)

    Outcome until now

    29Japan Software Process Improvement

    Consortium (JASPIC)