All related (5)
Vasanth Arunachalam
Director, Technical Program Management, Meta | Formerly MicrosoftMay 2

I’ll try to answer this question to the best extent possible because I havent worked at a company that had formal SCRUM master roles. My understanding is that the SCRUM master focuses on ensuring the team and the individual team members are set up for success (via daily stand ups, educating on best practices, conflict resolution, project tracking etc). In today’s world, I believe these are skills that everyone should possess (PM, Technical PM, Engineering Lead et al). That’s how Meta operates and any of the aforementioned functional leaders could play that role. This could be a controversial thing to say, IMHO the SCRUM master role could be antiquated soon if not already, especially in fast paced tech companies and start ups.

Vasanth Arunachalam
Director, Technical Program Management, Meta | Formerly Microsoft
“Change is the only constant” is a cliched phrase in the industry but the reality is not far off in many lines of businesses. At Meta we often get to work with the best available information in hand and not afraid of pivoting when that information changes. That comes with a degree of ambiguity, churn and sometimes loss of motivation for the teams involved. As a leader, my role is to ensure the teams have a strong understanding of the ‘why’ and when priorities change, again communicating the ‘why’ with full transparency. I then empower the teams to drive towards subsequent outcomes which cou...
Rupali Jain
Chief Product Officer, WorkBoard
I'm going to suggest a few processes, but please do scale each process to the size of the organization. Treat your processes like you treat your product - establish 2-3 internal customer problems that are actually worth solving, and solve them with an MVP of a process and iterate as you learn - don't try to introduce everything at once. * Quarterly priorities: Getting into the habit early of writing down the plan for the quarter is a good muscle to build early in establishing the PM discipline even with only a handful of PMs.  Focus on articulating the big bets for that quarter a...
Zeeshan Qamruddin
Director of Product Management, Fintech, Hubspot | Formerly Segment, WeWork, Airbnb
At the company level, there are a few different methods of communications to keep everyone abreast of updates: 1. Product Notification emails (Ad Hoc) - These emails have a set template and allow product teams from around the company to share updates to their areas in a digestable format as major features go out of the door.  2. Product Newsletter emails (Weekly) - The weekly newsletter summarized major product updates and initiatives to all product team members.  3. Quartery Business Review meetings (Quarterly) - These larger meetings gather key parts of the business to...
David Cutler
VP Product, CookUnity
I've noticed a trend in the tech industry for product organizations to follow a structure that Spotify helped craft over the years, in which a company is organized into business sub-orgs that roll up into their own respective product and engineering leads. And those leads oversee various squads that make up the product areas within that sub-org. At CookUnity we call the product areas "zones", in which a product lead exists to drive the product strategy and manage the PM team. In smaller companies (<500), those product leads are likely the direct leadership team for the Head of Product.  ...