BT
You are now in FULL VIEW
CLOSE FULL VIEW

Punishment-Driven Development
Recorded at:

| by Louise Elliott Follow 0 Followers on Mar 12, 2017 |
38:16

Summary
Louise Elliott discusses why people tend to blame and punish others, the impact of self-­blame, the unintended results from punishment, and the alternatives to punishment, which get real results.

Sponsored Content

Bio

Louise Elliott has worked in the software world for over 25 years and has seen huge changes in both technology and how software development is managed. She has successfully introduced Agile and Lean to many companies and is a great believer in the benefits of self-organizing teams. She is passionate about quality and the need to build it in from the start.

Agile Tour London is an annual conference which explores all aspects of agility and its adoption and implementation in a business environment. Packed with inspirational talks and hands-on workshops, Agile Tour London 2016 offers unmatched opportunities to learn from the best agile experts in the industry. Whether you are an agile newbie or been in the industry for years, this is the definitive agile conference you can't afford to miss.

Related Topics:

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Very nice presentation by Richard Richter

I like the stories, I like the material for thinking. It is really hard to do things "egolessly" but it can help a lot. I'm more or less successful with egoless programming, less so with people though. :-) People always heat me up. It requires some set of mind, practice and maybe some of us are simply not able to do it. ;-)
  • Like
  • Reply
  • Back to top

Re: Very nice presentation by Louise Elliott

Thanks Richard. I'm not a natural at this either - I continue to get things 'wrong' and go with my gut reaction - which rarely gives me the result I would like. The more I work on it though and recognise my mistakes the better I get. I like to think of it as using the same skills as when debugging code - something isn't happening in the way you would like and you need to use your analytical skills to work out why not, what the source of the problem is and how you might sort it out. You decide what your desired outcome is up front. You use your experience of having seen similar problems in the past to help guide you to possible answers. You experiment to find a solution which will work. You may talk to someone about the problem to see if they have had similar issues.

The skills are actually very similar - the key is in being willing to forego the immediate emotional satisfaction of reacting in order to get the longer term and larger reward. That's a matter of choice.
  • Like
  • Reply
  • Back to top

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

2 Discuss

Sponsored Content

Login to InfoQ to interact with what matters most to you.

Forgot password ? Don't have an account? Register Here

Recover your password...

Back to login Don't have an account? Register Here
Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT

We notice you're using an ad blocker

We understand why you use ad blockers. However to keep InfoQ free we need your support. InfoQ will not provide your data to third parties without individual opt-in consent. We only work with advertisers relevant to our readers. Please consider whitelisting us.