Uutiset »
 

FiSMA SPIN 1/2012 about root cause analysis

Julkaistu 7.3.2012

Dear FISMA members,

We have our first FiSMA SPIN meeting in 2012 Thursday 29.3.2012 13 – 15.15  about Root Cause Analysis. It is most actual topic among our members! Aalto University has developed a method called ARCA in their 3-year research project ESPA. Timo Lehtinen from Aalto/ESPA project will introduce this method for us. Then we learn it better by working together  in verification and measurement topics to achieve better software quality. See more detailed agenda below. Please register in FiSMA SPIN latest Tuesday 27.3. using link http://www.webropolsurveys.com/S/A8A664973D27E46E.par

Timo Lehtinen short CV:
Timo Lehtinen, M.Sc. (Tech), is a project researcher and PhD student at Aalto University. During the past few years his interests has been in analyzing the feasibility of root cause analysis (RCA) for software project reflections. He has steered and observed various industrial problem solving sessions utilizing the methodologies of RCA and concluded RCA as a feasible and efficient method for software process improvement. RCA helps to explain why the problem occurs and how the problem can be controlled. Lehtinen is also a project manager of a small IT-team including four software developers at Golden Checkpoint Production. The team develops and maintains complex browser based services for their customers.
29.3.2012 13.00 – 15.15     FISMA SPIN workshop, Agenda:

Welcome to Nokia House and FiSMA SPIN workshop, Jukka Märijärvi, Nokia Oyj
Short introduction for root cause analysis, Timo Lehtinen, Aalto university
Practical example: “Why verification and measurement of software quality is difficult?”
•    Utilizing the ARCA method with the attendees:
-    The attendees write new causes down on paper for 5 min (the cause-effect diagram should be projected onto the wall)
-    Each attendee presents the causes he or she has written and explains where they should be placed in the cause-effect diagram
-    The attendees briefly discuss the detected causes, trying to brainstorm more causes and to recognize whether a cause has a relationship to other causes.
-    Then the above steps are repeated once more (depending on the schedule)
What is the output of RCA?
Results of the ARCA method at four software companies

Sivun alkuun Sivua muokattu 8.4.2012