Remove Engineering Management Remove Metrics Remove SCRUM Remove Weak Development Team
article thumbnail

Bridging the Gap Between Developers and Marketers with Rich Mironov

Marcus Blankenship - Podcasts

In this episode of Programming Leadership, Marcus and his guest, Rich Mironov, discuss the all too common disconnect between developers and those on the marketing side of organizations. Differences in design principles between product and engineering management (1:35). How efficient is the team? Transcript.

article thumbnail

Organise your engineering teams around the work by reteaming

Abhishek Tiwari

When it comes to organising engineering teams, a popular view has been to organise your teams based on either Spotify's agile model (i.e. squads, chapters, tribes, and guilds) or simply follow Amazon's two-pizza team model. It is one of the ways you can organise your engineering teams in a retail environment.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Bridging the PM Gap with Rich Mironov

Marcus Blankenship - Podcasts

In this episode of Programming Leadership, Marcus and his guest, Rich Mironov, discuss the all too common disconnect between developers and those on the marketing side of organizations. Differences in design principles between product and engineering management (1:35). How efficient is the team? Transcript.

article thumbnail

The One Constant with Don Gray

Marcus Blankenship - Podcasts

In this episode of Programming Leadership, Marcus and his guest Don Gray enlighten listeners regarding the world of software development, the reasons for implementing software changes and why it’s not as easy as people may think. Software development is not linear and not deterministic. Show Notes. Change is complex. Transcript.

article thumbnail

The Product Owner Problem

LeanEssays

“We’re really struggling with the Product Owner concept, and many of our Scrum teams just don’t feel very productive.” The company had several vertical markets, with a Scrum team of about ten people assigned to each market. Each market had a Product Manager, a traditional role found in most product companies.

SCRUM 58