Learn how leading organizations are investing more in requirements as part of their product development strategy to give everyone involved a common vision of what is being built and who the customer is. Without that common vision even the best teams risk writing the wrong test, focusing on the wrong design elements, or moving the wrong item to the top of the backlog.
Requirements are the source of more than just a set of guidelines for what sort of product to build. They also provide a wealth of information critical to making the right decisions throughout the development and delivery process.
Are you bored by hearing about Spotify’s Model, Basecamp’s Shape Up, or Netflix’s “No Rules Rules”? All of them do have something in common. They tailored something unique to match both their ambition and their strengths, while honestly acknowledging their weaknesses.
This presentation explains how Wardley Maps were used to inform the always evolving strategy for the modernization of Ticketmaster’s core ticketing platform not only in terms of technical capabilities and architecture but also process maturity, organizational design, and more.