Changing Software Management Culture from Academic Keiichi Katamine - PowerPoint PPT Presentation

Changing Software Management Culture from Academic Keiichi Katamine Masanobu Umeda Masaaki Hashimoto Kyushu Institute of Technology Yoshihiro Akiyama Next Process Institute Ltd.

TSP Symposium 2011 Our Deep Appreciation to ALL of YOU We all Japanese have sincerely appreciated your strong and continued support for the nuclear power plant tragedy and earthquake disaster of March 11 th , 2011. We learn from these not only technical advancement but also of our humanity on mutual supports and dependencies over the globe. 2

TSP Symposium 2011 Kyushu Institute of Technology Established 1907 (the 100 th year anniversary) Established two Engineering Schools and three Graduate Schools Major Graduate Schools related to Engineering: Engineering  Computer Science and Systems Engineering  Life Science and Systems Engineering  Campuses (Southern Japan): 500 Miles KitaKyushu City Wakamatsu Campus,  Tokyo Tobata Campus Iizuka City Iizuka Campus  3

4 TSP Symposium 2011 KIT was founded 1909

TSP Symposium 2011 Schoolhouse of Meiji College of Technology 1920 Dormitory 5

TSP Symposium 2011 1913 Mr. Shigenobu Okuma’s visit 1929 a panorama of Meiji College of Technology 6

TSP Symposium 2011 Contents Introduction Background Cultural Change Strategy Introduction of PSP at KIT Introduction of TSPi at KIT Outcomes and Discussion New Course Design Conclusion 7

TSP Symposium 2011 Introduction Dr. Watts Humphrey and the SEI investigated industry for software practice since late 1980s  High quality and effective management for software is center for modern, safe, and dependable world.  Software process is the key for the knowledge workers.  The PSP and TSP were developed and provided by the SEI since 1990s. 8

TSP Symposium 2011 Introduction -2 At academic, however,  Students code & test first, not software design  Laboratory R&D progress is very slow In industry, large effort has been spent for long time to improve process but not much change showed.  Quality is established by testing,  High quality and performance happen mostly by accident  Engineers and managers work extremely long hours. Managing software projects are deeply rooted on the current management culture. 9

TSP Symposium 2011 Background Culture creates the norms that characterize organizations, teams, and individuals, regarding the performance by its beliefs, knowledge, values, rules, behaviors, capabilities, inheritances from previous generations [The FreeDictionary] Changing culture is measurable through the attributes be changed toward a desired goal, consistently, collectively, and uniformly. 10

TSP Symposium 2011 Background -2 Changing software management culture must be accomplished through a set of attributes of software process, to be planned and measured at team and individual in a decomposed and superposed manner. The PSP and TSP bring software improvement (changing software management culture!) easily to individual, team, and managers in short time (from week to months.) 11

TSP Symposium 2011 Cultural Change Strategy Team communication  Self-directed Team Team coordination teams must be Project tracking Management TSP Risk analysis built. Goal setting  This requires a Team Role assignment team-building Building Tailored team process process. Detailed and balanced plans Team Process discipline  These individual PSP Performance measures skills are Member Estimating & planning skills necessary for the Skills Quality management skills team and a team member.. Ref. SEI course “Leading a Development Team” 12

TSP Symposium 2011 Cultural Change Strategy -2 TSP Stepwise Changes - PSP Team development (Cultural) changes by extending PSP practices PSP2.1 PSP2 from PSP0 through Design templates Code reviews Design reviews PSP2.1 PSP1.1 PSP1 Task planning Size estimating Schedule planning Test report PSP0 PSP0.1 Current process Time recording Coding standard Defect recording Size measurement Defect type standard Process improvement proposal (PIP) Ref. SEI course “PSP for Engineers - Planning” 13

TSP Symposium 2011 Cultural Change Strategy -3 Team level changes by team building for self-directed 1. Establish 4. Build overall 7. Conduct 9. Hold product and and risk management business near-term assessment review goals plan 2. Assign roles 5. Develop 8. Prepare Launch and define the quality management postmortem team goals plan briefing and launch report 6. Build 3. Produce A qualified coach guides the team individual development and through a defined process to strategy consolidated and process develop its plan and to negotiate plans that plan with management. Ref. SEI course “Leading a Development Team” 14

TSP Symposium 2011 Organization Kyushu Institute of Technology Faculty of Engineering Faculty of Computer Science and Systems Engineering Graduate School of Engineering (Master’s and Doctoral Programs) Graduate School of Computer Science and Systems Engineering (Mater’s and Doctoral Programs) Graduate School of Life Science and Systems Engineering (Master’s and Doctoral Programs) 15

TSP Symposium 2011 KIT’s three phased approach KIT introduced a program of the PSP and TSPi based software engineering education with SEI: Process Management R&D Program Phase-3 Expand the application to large Organization/Team Coverage Phase-2 Team/Individual Apply the Basic to small & real Leadership& Coaching Phase-1 Establish Basic Disciplines Basic for Individual Graduate School Program (Engineering) Capability 16

TSP Symposium 2011 Opening Talk and Seminar at KIT 17

TSP Symposium 2011 TSP Seminar at KIT - Mar. 2008 and Feb. 2010 18

TSP Symposium 2011 PSP Certificate of Completion from Dr. Nielsen and Pres. Shimomura 15 September, 2009 19

TSP Symposium 2011 Introduction of PSP at KIT  Course: PSP for Engineers (PSP-I & PSP-II)  Main Issues  Course schedule structure  SEI: 5 consecutive days (over 40hr)  KIT: 1.5hr x 15 periods (22.5hr)  Insufficient programming skills and experience  No experience in industry  Poor programming skills  Small-scale software development  No experience of software estimation 20

TSP Symposium 2011 Schedules for PSP Courses Completion Year Part Method of PSP-I(%) PSP-I 3hr lectures over 5 consecutive days 43 2007 PSP-II 3hr lectures once every two days 6hr pre-course exercise, 3hr lectures PSP-I 75 once a week 2008 PSP-II 3hr lecture once every two days 2009 80 PSP-I 3hr lecture once a week and plan 2010 100 PSP-II review several days after lecture 2011 100 21

TSP Symposium 2011 Performance of PSP Courses - Size and Time Estimating Error - n=25 (2007-2010) 22

TSP Symposium 2011 Performance of PSP Courses - Process Yield - n=25 90 1st Quartile 80 2nd Quartile 3rd Quartile 70 60 50 40 30 20 10 0 1 2 3 4 5 6 7 8 23

TSP Symposium 2011 Performance of PSP Courses - Compile and Test Time Range - Compile Time Range % n=25 16 14 1st Quartile 2nd 12 Quartile 3rd 10 Test Time Range Quartile % 35 8 1st Quartile 30 2nd 6 Quartile 3rd 25 4 Quartile 2 20 0 15 1 2 3 4 5 6 7 8 10 5 0 1 2 3 4 5 6 7 8 24

TSP Symposium 2011 Performance of PSP Courses - Defect Density - PSP1 n=25 PSP2 Defects/KLOC 180 1st Quartile 160 2nd Quartile 3rd Quartile 140 120 100 80 60 40 20 0 1 2 3 4 5 6 7 8 25

TSP Symposium 2011 Performance of PSP Courses - Defect Density (Unit Test) - n=25 Defects/KLOC 45 1st Quartile 40 2nd Quartile 35 3rd Quartile 30 25 20 15 10 5 0 1 2 3 4 5 6 7 8 26

TSP Symposium 2011 Performance of PSP Courses - Productivity - n=25 LOC/Hour 40 35 30 25 20 15 10 1st Quartile 2nd Quartile 5 3rd Quartile 0 1 2 3 4 5 6 7 8 27

TSP Symposium 2011 What PSP Course Students Understood  How to make a plan  Importance of design and review  Defect reduction by recording a defect log  Completion of software development as planned by reducing time variations in defects  Process Improvements by using process data  Students recognize performance differences between themselves and other students who have not studied PSP 28

TSP Symposium 2011 Introduction of TSPi on top of PSP  Main Issues  Course Schedule Structure  Limited class time  3 hours x 15 periods  Lack of Experience  No experience in industry  Small-scale software development  Small group activities – school festivals, part-time jobs, …  Teaching Experience  Mid-scale software development project  No TSPi teaching Experience  Faculty workshop 29

TSP Symposium 2011 Performance of TSPi Team - Overview -  Team members  3 members and each member has 2 roles  Each member completed 6A at least  Project  Change counter in TSPi text book  2 cycles plan (13weeks)  Result  1 cycle completed  0 defects in system test  42.6 defects/KLOC in the worst module 30

TSP Symposium 2011 Performance of TSPi Team - Cumulative Earned Value - 31

TSP Symposium 2011 Performance of TSPi Team - Inspection and Review Rate (System & Defective module) - Inspection & Review Rate Inspection & Review Rate - Defective module - - System - 32