1. FeedbackThe Lost Art Of AgileA talk by for:

2. Software developmenthas a history ofloosing feedbackA talk by for: 3. Why Lost? - Waterfall The implementation described above is risky and invites failure. Winston Royce,1970A talk by for: 4. Why Lost? - Unit Testing 1985: book on structured programming talks about unit testing 1989: we sketched out a set of test cases before putting pencil to coding pad These were punched into cards and put in the permanent test case library Gerry WeinbergA talk by for: 5. Why Lost? - Agile earl and continuous y delivery Deliver working software frequentl y Business people and developers must work together daily face-to-face conversa tionA talk by for: 6. Feedback! - Found?Validateanyassumption inmaximumtwo weeks A talk by for: 7. Why Art?Not Science.Some science might beinvolved: Statistics,Psychology, Systems Theory.A talk by for: 8. Why feedback? The Thesis.Software development is on a quest forhigh quality fast feedback, A talk by for: 9. Why feedback? A talk by for: 10. Why?To validate decisionsTo improve processesTo improve team work A talk by for: 11. Feedback is useful for...PeopleProcess A talk by for: 12. What?A process in whichinformation aboutthe past or thepresent influencesthe samephenomenon in thepresent or futureWikipedia A talk by for: 13. Feedback in EngineeringInformation by itself is notfeedback unless translatedinto action WikipediaA talk by for: 14. Feedback in Scrum A talk by for: 15. Feedback on CodeA talk by for: 16. Feedback Quiz! A talk by for: 17. A team mate introduces bugs inthe application every sprint. Quiz #1You:A)Dont careB)Tell him he should stopprogrammingC)Review his code and tell himthe problemsD)Ask him how you can help toavoid it A talk by for:E)Pair with him, identify why he 18. automated tests. Quiz #2A)You dont run them, itsintegration departmentsbusinessB)50 tests fail from time totimeC)When making a change, 20tests failD)At most two tests fail incase of a mistake A talk by for:E)All tests run nightly 19. daily Scrum for 10 and delays Quiz #3the meeting. You are the ScrumMaster. You:A)Think at something differentwhile he speaksB)Find ways to leave earlierC)Tell him to stop talkingbecause hes annoyingD)Talk to him in private and A talk by for:tell him he should stop 20. You find a piece of complicatedcode at the end of the sprint, Quiz #4while modifying in other partsof the application. You:A)Ignore it, maybe you wonthave to change itB)Write the issue down andforget about itC)Discuss it in the team and addit to the backlog A talk by for:D)Take 15 to refactor it and 21. team and have to evaluate thepeople. You: Quiz #5A)Dont evaluate them, whoeverasks for a raise might get itB)Do a yearly evaluationaccording to company policiesC)Go at the team meetings toevaluate the peopleD)Do a 360 evaluation every 2months A talk by for:E)Have weekly one-on-one 22. Feedback is HARDA talk by for: 23. ToolsIntroduce a feedbackcycle More feedback Better quality feedbackA talk by for: 24. Time to reflect...A talk by for: 25. Case Study: StartupDeploy every 2-3 daysFeedback form built in A talk by for: 26. Case Study: My Unit Testing ClassSource: feedback form,conversations, clarificationquestionsIntegrated in the courseFewer clarificationquestions, higher feedback(>9.5 / 10)A talk by for: 27. Case Study: Mozaic WorksDistributed team,different roles andbackgrounds, flatstructure6 months teamretreats2 weeks companysprintsFull visibilityA talk by for: 28. Case Study: Presentation CreationSlides, practiceSlides, record, listenBrainstorm, structure,record, listen, slidesFrom 3 days to 4 hrsNeed more practice andfeedback :)A talk by for: 29. Main IdeasSoftware development ison a quest for more, higherquality feedbackIt is feedback only if youdo something about itTools: Introduce cycle,Get more, Get betterFeedback is hardA talk by for: 30. Conclusions We are rediscoveringthat feedback is at thecore of software development. A talk by for: 31. Your turn to give feedback! A talk by for: 32. Questions?A talk by for: