In this introductory segment of a YouTube interview, Glenn Barnett, a founding engineer and product leader at Jellyfish, outlines his long‑standing frustration with communicating engineering constraints, opportunities, and priorities to executives and board members. He frames this communication gap as the core problem Jellyfish aims to solve. He is joined by Matthew Raimondo, a senior program manager at Genesis with extensive experience as a release manager working closely with Jira and engineering teams. Both speakers set the stage for a discussion on why effective use of Jira is critical for aligning engineering operations with business leadership, establishing the relevance of the upcoming best‑practice recommendations.
Chapters
My name is Glenn Barnett. I joined Jellyfish just over 4 years ago as the first hire, and over that time I've been involved with engineering and product and design, and most recently with helping to scale our success team. Prior to Jellyfish, I had led engineering and product teams and was often frustrated by the, I guess, the perpetual search for the ideal way to communicate with the rest of the business, with the CEO, with the board about, you know, what are the constraints and the opportunities we face and how can we make the best decisions? And that's one of the main problems that we're trying to solve with Jellyfish. I'm joined today by Matt Raimondo from Genesis. Matt, thank you so much for joining us today. Why don't you introduce yourself?
Yeah, Glenn, thanks for having me. I'm Matthew Raimondo. I work for Genesis. Over the last few years, I've Worked through a number of roles, release manager, right now senior program manager in the R&D space over the entire time working with, with Jira and engineering teams, which is why I believe you're having me on today.
Absolutely. And, you know, tell me a little bit about why this topic is important to you.
This topic strikes a chord for me because Jira and really the entire Atlassian software suite has been a toolset that I've used over a number of positions of mine, going from startups all the way to Genesis, which is an enterprise R&D company. And really, regardless of the needs, we've been able to use the tool to accomplish whatever we needed, regardless of, you know, size of the team, size of the company. And so there's— it's just, it's something I have experiences with. And when you see it being used effectively, you could really see gains in your ability to deliver features and really accomplish anything else you want to accomplish within the tool.