addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

How to change defect-driven culture?

  • Jan 8, 2013 · 5:30 PM
  • This location is shown only to members

Did you hear the one about how a defect tracking tool took over the way an organization acted/behaved? Morale went down. What do you do?

Lightning Talker - Alex Deborin

If you want to be a "lightning talker" please email me with the issue or solution that you want to discuss.

Lightning Talker - ???


We will begin the meetup at 5:30 pm with networking, food and beverages.

The lightning talks start at 6:00 and the open space goes from 6:30 to 7:30 pm.

Join or login to comment.

  • Joel

    Excellent topic. Have you thought about discussing Failure Cost as part of this as well? I may have the term off (its early, sick kids) - I first read it in a Poppendieck book. In general you have two types of costs with software dev - failure costs and value creation costs. Failure costs are associated with defects / wrongly implemented features / functionality. Value creation costs are associated with things people want / pay for.

    Looking at your IT spend based upon those two quadrants can be very enlightening.

    Tosi

    January 3, 2013

13 went

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy