Effective, experienced technical product management is crucial to make software development hum: Engineering and Product Management are symbiotic. Product managers lead and motivate by first establishing credibility with engineers, and by bringing vision, data, collaboration, prioritization, and protection. Ron Lichty has repeatedly been brought in to transform chaos to clarity in software development. Here’s what product managers can apply to lead and motivate engineers and make software development hum.
BIo:
Ron Lichty has, for 30-plus years, championed delighting customers. He believes that strong product/engineering collaboration is essential to achieving that goal. Ron co-authored the Addison-Wesley book Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams (http://www.ManagingTheUnmanageable.net) and annually coauthors the Study of Product Team Performance (http://www.ronlichty.com/study.html).
Ron spent seven years as a programmer, two years as a product manager, and 25 years managing product and development organizations at all levels - to VP of engineering, VP of product and CTO - at companies ranging in size from tiny startups to Charles Schwab,Stanford, and Apple.
He now consults across that realm, taking on fractional interim VP Engineering and acting CTO roles, training teams in agile, training managers in managing software people and teams, and coaching development teams and executives in making software development hum. (http://www.ronlichty.com)
Ron has long been a popular speaker at product, development and agile meetups and conferences. Ron@RonLichty.com
The Ultimate Test Automation Guide_ Best Practices and Tips.pdf
Leading and Motivating Engineers - what product managers need to know - product camp '17
1. Leading And Motivating Engineers:
What Product Managers Need To Know
Ron Lichty, principal, Ron Lichty Consulting
author, Managing the Unmanageable
www.RonLichty.com www.ManagingTheUnmanageable.net
28. Ordering: Value / Size: ROI
Technical PBIs*
Epics & Stories
*
PBI: Product Backlog Items; list provided by technical leadership
Sizing
ROIOrdering
Listing
Sizing
Project
29. Ordering: Not Just ROI
Technical PBIs*
Epics & Stories
*
PBI: Product Backlog Items; list provided by technical leadership
Sizing
ROI/Dependencies/RiskOrdering
Listing
Sizing
Project
31. Ordering Is More than ROI
• Good user-story ordering is a collaboration with Eng
– take dependencies into account
– support risk-first development
– reduce uncertainty
– enable design to emerge
– test architecture
– listen for opportunities
32. Ordering: Not Just ROI
Technical PBIs*
Epics & Stories
*
PBI: Product Backlog Items; list provided by technical leadership
Sizing
ROI/Dependencies/RiskOrdering
Listing
Sizing
Project
53. Prioritize
• Developers want to know they’re working on the stuff
customers will value most!
• There is no such thing as “2 top priorities”!
• Get good at the mantra, “I’ll put it in the backlog”
53
54. Prioritize
• Developers want to know they’re working on the stuff
customers will value most!
• There is no such thing as “2 top priorities”!
• Get good at the mantra, “I’ll put it in the backlog”
• “If everything is a priority, nothing is a
priority.”
— Sheila Brady, Apple project management guru
54
60. Be Available
• Be there with clarity
– with the priorities / with the backlog
– with the stories
– with the acceptance tests
– with the detail
– with the clarity / the disambiguation
60
62. Listen to Developers
• Support 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
62
67. Projects Not Suitable for Agile?
• Micromanagement disrupts Agile
• Micromanagement prevents Best Teams
• Micromanagement prevents Learning
• Micromanaged teams become order-takers
67
68. Projects Not Suitable for Agile?
• Micromanagement disrupts Agile
• Micromanagement prevents Best Teams
• Micromanagement prevents Learning
• Micromanaged teams become order-takers
• Agile calls for everyone on the team to step up
• Micromanagement causes everyone to step back
68
69. Partner
69
Photo by Esti Alvarez, Some rights reserved, http://www.Flickr.com/photos/esti/4638056301/
The 2013 Study of Product Team Performance, http://www.ronlichty.com/study.html
Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams, http://www.ManagingTheUnmanageable.net
Mike Cohn: citing Steven C.Wheelwright and Kim B.Clark (1993), Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency and Quality, 1993
Mike Cohn: citing Steven C.Wheelwright and Kim B.Clark (1993), Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency and Quality, 1993
Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams, chapter 8
3rd ‘C’ in Planning Meeting 3 C’s: Confirmation (after Cards and Conversation)
the “creamy center” of Managing the Unmanageable: Rules, Tools, and Insights for Managing Software People and Teams, http://www.ManagingTheUnmanageable.net