Engineering Manifestos
We go on a journey with Engineering/Technology leaders to understand their approach to Engineering strategy, viz. how they figure out what is needed from the Engineering team to help their company win, and how they apply that to their Engineering teams.
Each company context (company, business, marketplace, competitive environment) at a given point in time is unique. In order to succeed, a set of choices within Engineering on Objectives, Culture, Organization and Process & Systems needs to be made. We seek to gain an understanding of the tools and practices/processes for building teams and products to help companies win.
Engineering Manifestos
Building Eng at Impira with Anand Mariappan
Anand Mariappan, VPE, Impira, shares his experience inheriting and running the engineering team and adapting to remote work. He also provides an overview of his 3Ps framework for enabling people to do their best work, by equipping them with the right processes and a clear sense of purpose.
- 4:00 [Objectives] Focus on time to market
- 9:30 [Company Values] Empathy (Virtual Water-cooler/Virtual Coffee and other ways to stay connected with the team)
- 14:10 [Engineering Values] Transparency (The team that sees reality the best wins - Jim Dethmer)
- 16:08 [Engineering Values] Autonomy (Enabling the team to reach their full potential)
- 21:00 [Hiring] Two-way (Company and Candidate) evaluation for fit
- 27:05 [Engineering Levels] Career Ladder (Working with the team to identify desired Engineering values & traits at each level)
- 31:25 [Team Structure] Frameworks for team structure (Product Versions, Use cases, User scenarios, Product Functionality) and resource allocation (Feature Dev/Foundation/Moonshot ideas, Core Product/New initiatives/Moonshot ideas)
- 37:35 [Architectural Decisions] (Leveraging Brain Trust from Pixar)
- 42:25 [On-boarding] 3-4 person team (Manager, Engineering mentor, Engineering buddy, Cross-functional buddy)
- 50:00 [Testing] Balancing product quality expectations, time to market and available resources
- 53:10 [Adding Capacity vs Optimizing Software] Focus on understanding the bottlenecks and starting with optimization
