CHAPTER VII Problem detection & solving

1. CHAPTER VIIProblemdetection & solving

2. Identifying problems • Cycle Time : cycle time spansfromwhen the team startsworking on a piece of the project , such as a user story, untilthat item isfinished, accepted and canbedelivered. The project cycle time is the average time used on each sprint or iterationso : CT=WIP/Throughput • Knowing the cycle time allows us to makereliablecommtiments to the customer or organization about how long itwilltake to deliverwork.

3. Identifying problems • EscapedDefects : Identifyingdefectsearlywillconsiderablyreduce cycle times & costresolvingthosedefects. But what about defectswhicharen’tdetectedduring cycle times and makeit to the environment of the customer ? They are much more costly to fix . • The escapeddefects trace back to the release theywereintegrated and where the willbeaccounted for in 2 ways, ED/Release & ED/Alert time

4. Identifying problems • Project & Quality Standards: Project detection & resolutioniscloselyrelated to quality management. The testingprocess & other practices we put in place to finddefects are part of the quality assurance & quality control efforts. • Quality standardscanbegoverned by contract or internallyenforced : • automating as many test possible • Testingoccurs as part of everyiteration • Try to fix at least 90% of the defectswithin the nextiteration

5. Identifying problems • Failure modes & alternatives: relates to the human factor on performance & processes • Makingmistakes: recognize the factthatmistakeshappen, 0 defectsdoen’texist, thatiswhywe use the iterativeapproach to correct detecteddefects. • Prefer to failconservatively: whenfacedwithuncertainty people tend to refer back to whatthey know, soPM’swillfallback to welknowntraditionalprojectmethodologieswhenerror rate on the new experimentis to high • Inventingratherthanresearching : tendency to invent new ways of doingthingsratherthanresaerchavailable options to refine or to reuse the existent. • Beingcreatures of habit : we all are in a certain degreeresistant to change • Beinginconsistent : most people are veryinconsistent in following strict procedures

6. Identifying problems • Failure modes & alternatives : relates to the human factor on performance & processes • ALTERNATIVES : • Being good at lookingaround : observe, review, notice & actwhenthings are not right • Being able to learn : wegrowourskillsalong the way of looking for solutions • Beingmalleable : ability to accept change, new ideas & opproaches • Takingpride in work : take initiative, be part of the solution, not part of the problem

7. Identifying problems • Variance & trend analysis : Variance on a projectis normal but weneed to limitthose variances to an acceptable level ! • Important is to know when to intervene by avoidingmicromanagement and continue working at removingbottlenecks an impediments in facilitating teams’ operations • 2 symptomstoo variances : • Common cause to variance in the averagedifferencebetweenourday to day wok • Special cause variation, refers to the greaterdegrees of variance due to special or new factors

8. Identifying problems • Variance & trend analysis :

9. Identifying problems • Control Limits : Are the tolerancelevelsbetween up and downside of a variance or a trend thatis acceptable and performance is in good workingorder

10. Resolving problems • ContinuousIntegration: The team frequentlyintegrates new and changed code into the projects’ code repository. This practice helpsminizeintegration issues thatresultsfrom people making incompatible changes to the same code.

11. Resolving problems • ContinuousIntegration:

12. Resolving problems • Risk-based Spike:is a short proof of concept experimentwherewe test veryrisky or highlycriticalprotions of the code.

13. Resolving problems • FrequentVerification & validation :

14. Resolving problems • Test drivendevelopment: By focusing on the test first, we must think how the functionalitywillbeused by the customer (furtherextend ATDD). The approach of writingsystems in small, testedunits leads to a more modular, flexible & extendable system.

15. Resolving problems • Problemsolving : • Gather data on the issue • Organize brainstorming usingishikawafisbone • Decideon actions (SMART)