Not surprisingly, the gives and gets also revolve around the scope of deliverables. In these situations, it becomes a fine balancing act between moving forward with new functionality, which is what Product wants, and tackling scalability and performance issues, which is what Engineering may need. These reality-moments sometimes revolve around the need to address an engineering challenge before a new feature that Product wants can be built - especially if limitations with the underlying architecture and technical debt will impede development. Product will have these big ideas, and while Engineering’s role is not to shatter their dreams, it is to bring them back to reality.” As one participant explained, “You have Product trying to define the broad vision and engineering trying to fulfill the goals of the product.
Recognize the size and shape of the friction monsterīy nature, the roles and responsibilities of product managers and engineers can create an adversarial relationship. The conversation also illuminated some creative ideas to help smooth out bumps in the road.
#Roadmap planner ios apps code
Know what really animates development leaders? Talking about release cycles! The ACC meetup in March was a lively discussion about release trends and strategies for getting new code out the door with speed - without sacrificing quality and the customer experience.ĭoes anything cause more tension between Product and Engineering teams than roadmap planning? The ACC meetup in September tackled this complex topic, as participants discussed the gives and gets that often get hashed out between these two teams. This blog is part of a series that delivers insights from the monthly meetups of Bugsnag’s Apps + Coffee Connection (ACC) community.
0 kommentar(er)
