Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

23
Crash Course: Managing People and Teams Ron Lichty, Ron Lichty Consulting www.ronlichty.com

description

Crash Course: Managing Software People and Teams (Engineering Leadership SIG of SVForum, 11.12), a talk by Ron Lichty, co-author of Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams. "We'd like you to manage the team now." That's about as much introduction - and training - as many of us get before our first day managing. Often preceded only by, "You're a great programmer and you've got some people skills." But while programming cred and facility with people are helpful qualifications, what do you really need to know to manage well? What makes a manager great? What are the qualities that meld teams and deliver great software? Those are among the questions that led Ron Lichty and his co-author Mickey W. Mantle to write "Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams" (Addison-Wesley, September), now available for pre-order online. In this interactive session, we'll examine the great managers each of us has experienced, and the qualities, skills, finesse and gifts of greatness that made them stand out. We'll talk about "the rest of the job": managing up, managing out, and other aspects of being a seasoned manager that reports mostly don't see. And you'll take away a few best practices that take most managers years to discover.

Transcript of Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Page 1: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Crash Course: Managing People and Teams

Ron Lichty, Ron Lichty Consultingwww.ronlichty.com

Page 2: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Ron Lichty, Managing Software People & Teams

SOFTWEST

Page 3: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Why we wrote:

* Addison Wesley published October 1, 2012

*

Page 4: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Rules of Thumb / Nuggets of Wisdom*

• Measure twice, cut once.• Life is simpler when you plow around the

stump.

• Brooks’s Law: Adding manpower to a late software project makes it later.– Frederick P. Brooks Jr.

* 300 in the book

Page 5: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Agenda

• Managing Down• Motivating• Recruiting• Handling Problem Employees• Shielding Your Team• Managing Out and Up• Establishing Culture• Communicating• So Why Manage?• Q&A

Page 6: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Managing Down

• Best manager you ever had?• Skills

• Behaviors

• Finesse

• Gifts of greatness

. . . that made them stand out?

Page 7: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Managing Down: Nugget of Wisdom• Nothing undermines your credibility as a

manager more completely than pounding on your team all year to get their work done on time and then telling them you don’t have their reviews done because you were busy. Whatever you were busy with likely wasn’t managing your people, so you’ve just proven to them that they don’t matter. Good luck motivating them next year.– Tim Swihart, engineering director, Apple Computer

Page 8: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Managing Down: Challenges

Rule of Thumb: The very thing that has made you successful will get in your way in your next role.

•Manage

•Delegate

•Be a Motivator

•Don’t Be a De-Motivator

Page 9: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Motivators vs De-Motivators

Page 10: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Motivating:Be Careful What You Reward

• “Behavior revolves around what you measure.”– Jim Highsmith

• “Firefighters who get rewarded carry matches.”– Kimberly Wiefling

• Do you define “done” as “coding complete”?– Or as features that delight customers?

Page 11: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Recruiting

• A manager’s most important job

• Give it the priority it deserves

• Always be recruiting

• There’s no perfect record

Page 12: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Handling Problem Employees

• Intervention beats performance plans & firing– Requires preparation, commitment, time– But gets the job done earlier:

• One of two results:– Turns them around– Manages them out

—Marty Brounstein: Handling the Difficult Employee

Page 13: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Shielding Your Team

• Threat to your team– Torrent of politics, “opportunities”, issues– Sap your team’s focus

• Challenge for you– Be a conduit for Mission and Passion and Strategy– While shielding your team from distraction

Be a damper to the noise. --Joe Kleinschmidt, CTO

Page 14: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Managing Out and Up

• “The single most important leader in an organization is your immediate supervisor.”– Jim Kouzes

• “You can safely assume all perceptions are real, at least to those who own them.”– Joe Folkman

Page 15: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Managing Out & Up

• Because – your peers increasingly are not technical– and your boss may not be either

• …they’ll pressure you– to micromanage your team (or let them)– to report on / prove your team’s productivity– to fill your team’s plates to capacity

Page 16: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Productivity

• The Apple Lisa team’s managers had asked engineers to report, each week, how many lines of code they’d written. The first week, Bill Atkinson turned his attention to making QuickDraw faster and more efficient, reducing the previous week’s code by 2,000 lines. He duly reported that he’d written minus-2,000 lines of code for the week.

Page 17: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Capacity• Slack is critical to throughput

– 100% capacity results in bottlenecks

--photo (c) Bud Adams, SXC, www.aimpgh.com

Page 18: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Establishing Culture

• Does your company live its values?

• Programming culture ≠ corporate culture– Wall parts off– Substitute and bolster more appropriate values

• Wherever you can, leverage culture & values

Page 19: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Establishing Culture

• “Publicly reward or acknowledge engineers who act in a way that supports the culture that you want to create.”—Juanita Mah, engineering manager

Page 20: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Communicating

• You have to communicate more• Encourage your team to communicate• Create a culture of communication

– at every level– with everyone

• up, down, within and across

• “We have two ears and one mouth. Use them in this ratio.”— Kimberly Wiefling

Page 21: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

So Why Manage?

• You get to go broad– Affect more of the product– Affect more of the customer experience

• You get to be more in the conversation

• You get to mentor and coach and motivate– A whole team– To become something more

Page 22: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

A Few Closing Rules of Thumb

• If you’re a people manager, your people are far more important than anything else you’re working on.—Tim Swihart, Engineering Director

• Projects should be run like marathons. You have to set a healthy pace that can win the race and expect to sprint for the finish line.—Ed Catmull, CTO, Pixar Animation Studios

• In applications with high technical debt, estimating is nearly impossible.—Jim Highsmith, Agile Coach and Leader

• The quality of code you demand during the first week of a project is the quality of code you’ll get every week thereafter.—Joseph Kleinschmidt, CTO, Leverage Software

Page 23: Crash course - managing software people and teams (engineering leadership sig of sv forum, 11.12)

Ron Lichty Consulting

• Mentoring and Coaching and Consulting:– http://ronlichty.com/

• The book: Managing the Unmanageable: Rules, Tools & Insights for Managing Software People & Teams– http://ManagingTheUnmanageable.net

• Training: forthcoming:– “The Agile Manager”– “Managing Software People and Teams: the class”(Email me through the site above and I’ll let you know

when.)