Picture 1 of 2


Gallery
Picture 1 of 2


Have one to sell?
Driving Technical Change : Why People on Your Team Don't Act on G
Free US Delivery | ISBN:1934356603
US $9.63
ApproximatelyRM 40.71
Condition:
“Used book that is in excellent condition. May show signs of wear or have minor defects. 100% ”... Read moreabout condition
Very Good
A book that has been read but is in excellent condition. No obvious damage to the cover, with the dust jacket included for hard covers. No missing or damaged pages, no creases or tears, and no underlining/highlighting of text or writing in the margins. May be very minimal identifying marks on the inside cover. Very minimal wear and tear.
Oops! Looks like we're having trouble connecting to our server.
Refresh your browser window to try again.
Shipping:
Free Economy Shipping.
Located in: Reno, Nevada, United States
Delivery:
Estimated between Sat, 26 Jul and Tue, 29 Jul to 91768
Returns:
30 days return. Buyer pays for return shipping. If you use an eBay shipping label, it will be deducted from your refund amount.
Coverage:
Read item description or contact seller for details. See all detailsSee all details on coverage
(Not eligible for eBay purchase protection programmes)
Seller assumes all responsibility for this listing.
eBay item number:396580484610
Item specifics
- Condition
- Very Good
- Seller Notes
- Book Title
- Driving Technical Change : Why People on Your Team Don't Act on G
- ISBN
- 9781934356609
About this product
Product Identifiers
Publisher
Pragmatic Programmers, LLC, T.H.E.
ISBN-10
1934356603
ISBN-13
9781934356609
eBay Product ID (ePID)
117227795
Product Key Features
Number of Pages
146 Pages
Language
English
Publication Name
Driving Technical Change : Why People on Your Team Don't Act on Good Ideas, and How to Convince Them They Should
Publication Year
2010
Subject
Leadership, Social Aspects / General, Industrial Management, General, Organizational Development
Type
Textbook
Subject Area
Computers, Technology & Engineering, Business & Economics
Format
Trade Paperback
Dimensions
Item Height
0.4 in
Item Weight
9 Oz
Item Length
9.3 in
Item Width
7.5 in
Additional Product Features
Intended Audience
Scholarly & Professional
Reviews
"At its core, Driving Technical Change is a fantastic book about design patterns. In it, Terrence Ryan clearly outlines common, problematic personalities-"skeptics"-and provides proven solutions for bringing about progressive change. It is certainly an unfortunate fact of human behavior that people are oftentimes resistant to implementing best practices; however, using Terry's book as a guide, you will now be able to identify why people push back against change and what you can do to remain successful in the face of adversity. " -Ben Nadel, Chief Software Engineer, Epicenter Consulting "Politics is one of the most challenging and underestimated subjects in the field of technology. Terrence Ryan has tackled this problem courageously and with a methodical approach. His book can help you understand many types of resistance (both rational and irrational) and make a strategy for getting people on board with your technology vision." -Bill Karwin, Author of "SQL Antipatterns: Avoiding the Pitfalls of Database Programming"
Dewey Edition
22
Illustrated
Yes
Dewey Decimal
658.514
Synopsis
Your co-workers' resistance to new technologies can be baffling. Logical arguments can fail. If you don't do politics, you will fail. With _Driving Technical Change_, by Terrence Ryan, you'll learn to read users' "patterns of resistance"-and then dismantle their objections. Every developer must master the art of evangelizing. With these techniques and strategies, you'll help your organization adopt your solutions-without selling your soul to organizational politics. Finding cool languages, tools, or development techniques is easy-new ones are popping up every day. Convincing co-workers to adopt them is the hard part. The problem is political, and in political fights, logic doesn't win for logic's sake. Hard evidence of a superior solution is not enough. But that reality can be tough for programmers to overcome. In Driving Technical Change: Why People On Your Team Don't Act on Good Ideas, and How to Convince Them They Should , Adobe software evangelist Terrence Ryan breaks down the patterns and types of resistance technologists face in many organizations. You'll get a rich understanding of what blocks users from accepting your solutions. From that, you'll get techniques for dismantling their objections-without becoming some kind of technocratic Machiavelli. In Part I, Ryan clearly defines the problem. Then in Part II, he presents "resistance patterns"-there's a pattern for each type of person resisting your technology, from The Uninformed to The Herd, The Cynic, The Burned, The Time Crunched, The Boss, and The Irrational. In Part III, Ryan shares his battle-tested techniques for overcoming users' objections. These build on expertise, communication, compromise, trust, publicity, and similar factors. In Part IV, Ryan reveals strategies that put it all together-the patterns of resistance and the techniques for winning buy-in. This is the art of organizational politics. In the end, change is a two-way street: In order to get your co-workers to stretch their technical skills, you'll have to stretch your soft skills. This book will help you make that stretch without compromising your resistance to playing politics. You can overcome resistance-however illogical-in a logical way., Your co-workers' resistance to new technologies can be baffling. Logical arguments can fail. If you don't do politics, you will fail. With Driving Technical Change , by Terrence Ryan, you'll learn to read users' "patterns of resistance"-and then dismantle their objections. Every developer must master the art of evangelizing. With these techniques and strategies, you'll help your organization adopt your solutions-without selling your soul to organizational politics. Finding cool languages, tools, or development techniques is easy-new ones are popping up every day. Convincing co-workers to adopt them is the hard part. The problem is political, and in political fights, logic doesn't win for logic's sake. Hard evidence of a superior solution is not enough. But that reality can be tough for programmers to overcome. In Driving Technical Change: Why People On Your Team Don't Act on Good Ideas, and How to Convince Them They Should , Adobe software evangelist Terrence Ryan breaks down the patterns and types of resistance technologists face in many organizations. You'll get a rich understanding of what blocks users from accepting your solutions. From that, you'll get techniques for dismantling their objections-without becoming some kind of technocratic Machiavelli. In Part I, Ryan clearly defines the problem. Then in Part II, he presents "resistance patterns"-there's a pattern for each type of person resisting your technology, from The Uninformed to The Herd, The Cynic, The Burned, The Time Crunched, The Boss, and The Irrational. In Part III, Ryan shares his battle-tested techniques for overcoming users' objections. These build on expertise, communication, compromise, trust, publicity, and similar factors. In Part IV, Ryan reveals strategies that put it all together-the patterns of resistance and the techniques for winning buy-in. This is the art of organizational politics. In the end, change is a two-way street: In order to get your co-workers to stretch their technical skills, you'll have to stretch your soft skills. This book will help you make that stretch without compromising your resistance to playing politics. You can overcome resistance-however illogical-in a logical way., Finding cool languages, tools, or development techniquesis easy-new ones are popping up every day. Convincing co-workers to adopt them is the hard part. The problem ispolitical, and in political fights, logic doesn't win forlogic's sake. Hard evidence of a superior solution is notenough. But that reality can be tough for programmers ......, Finding cool languages, tools, or development techniquesis easy-new ones are popping up every day. Convincing co-workers to adopt them is the hard part. The problem ispolitical, and in political fights, logic doesn't win forlogic's sake. Hard evidence of a superior solution is notenough. But that reality can be tough for programmers toovercome. In Driving Technical Change: Why People On YourTeam Don't Act on Good Ideas, and How to Convince ThemThey Should, Adobe software evangelist Terrence Ryanbreaks down the patterns and types of resistancetechnologists face in many organizations. You'll get arich understanding of what blocks users from acceptingyour solutions. From that, you'll get techniques fordismantling their objections-without becoming some kindof technocratic Machiavelli.
LC Classification Number
HD45
Item description from the seller
Seller feedback (430,405)
- b***o (1200)- Feedback left by buyer.Past monthVerified purchaseGreat service. Thank you
- s***0 (43)- Feedback left by buyer.Past monthVerified purchaseI arrived in good condition only 10 days after I ordered. Seller was fine. Wouldn’t recommend this book though. Very detailed but written like a high schoolers journal. No pics, mps, mpg…Not what I was hoping for. Didn’t bother taking it along.
- 0***j (192)- Feedback left by buyer.Past monthVerified purchaseItem was exactly as described, shipped quickly and packaged well. Thank you!
More to explore :
- Choose Your Own Adventure,
- Yours Magazines,
- People Magazines,
- People Weekly Magazines,
- I Wonder Why Nonfiction Fiction & Books,
- Nonfiction Books Fiction & People,
- People Magazines in Spanish,
- Collector's Edition People Magazines,
- Choose Your Own Adventure Action Fiction Fiction & Nonfiction Books,
- Choose Your Own Adventure Fiction Paperbacks Books in English