Feedback -  The Lost Art of Agile
Upcoming SlideShare
Loading in...5

Feedback - The Lost Art of Agile







Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Feedback -  The Lost Art of Agile Feedback - The Lost Art of Agile Presentation Transcript

  • FeedbackThe Lost Art Of Agile A talk by for:
  • Software development has a history of loosing feedback A talk by for:
  • Why Lost? - Waterfall “The implementa tion described above is risky and invites failure.” Winston Royce, 1970 A talk by for:
  • 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 Weinberg A talk by for:
  • Why Lost? - Agile “earl and continuous y delivery” “Deliver working software frequentl y” “Business people and developers must work together dail y” “face-to-face conversa tion” A talk by for:
  • Feedback! - Found? Validate any assumptio n in maximum two weeks A talk by for:
  • Why Art? Not Science.Some science might beinvolved: Statistics,Psychology, Systems Theory. A talk by for:
  • Why feedback? The Thesis.Software development is on a quest forhigh quality fast feedback , A talk by for:
  • Why feedback? A talk by for:
  • Why?● To validate decisions● To improve processes● To improve team work A talk by for:
  • Feedback is useful for...People Process A talk by for:
  • What?“A process in whichinformation aboutthe past or thepresent influencesthe samephenomenon in thepresent or future” Wikipedia A talk by for:
  • Feedback in Engineering“Information by itself is notfeedback unless translated into action” Wikipedia A talk by for:
  • Feedback in Scrum A talk by for:
  • Feedback on Code A talk by for:
  • Feedback Quiz! A talk by for:
  • 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
  • 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
  • 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
  • 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
  • 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
  • Feedback is HARD A talk by for:
  • ToolsIntroduce a feedback cycle More feedback Better quality feedback A talk by for:
  • Time to reflect... A talk by for:
  • Case Study: Startup● Deploy every 2-3 days● Feedback form built in A talk by for:
  • Case Study: My Unit Testing Class● Source: feedback form, conversations, clarification questions● Integrated in the course● Fewer clarification questions, higher feedback (>9.5 / 10) A talk by for:
  • Case Study: Mozaic Works● Distributed team, different roles and backgrounds, flat structure● 6 months team retreats● 2 weeks company sprints● Full visibility A talk by for:
  • Case Study: Presentation Creation● Slides, practice● Slides, record, listen● Brainstorm, structure, record, listen, slides● From 3 days to 4 hrs● Need more practice and feedback :) A talk by for:
  • Main Ideas● Software development is on a quest for more, higher quality feedback● It is feedback only if you do something about it● Tools: Introduce cycle, Get more, Get better● Feedback is hard A talk by for:
  • Conclusions We are rediscoveringthat feedback is at the core of software development. A talk by for:
  • Your turn to give feedback! A talk by for:
  • Questions?A talk by for: