Is your product marketing plan just a list of tactical activities? Are constant requests from Sales dominating your time and resources? The Effective Product Marketing seminar explores the outbound marketing roles, priorities and processes that characterize market-driven technology companies. Learn how to quickly develop a convincing plan for anything from a single campaign to a strategic go-to-market initiative.
LocationSan Francisco Airport Marriott
Are you new to Product Management and don't know where to start? Does your Product Management function need more structure and process?
Emphasizing market-driven techniques, this two-day Practical Product Management or three-day (with Requirements That Work) seminar analyzes critical product management and marketing activities in detail using the Pragmatic Marketing Framework.
Offering tips for how to be effective at the strategic elements and how to manage multiple tactical tasks, every concept is designed to be actionable as soon as you return to the office.
Who should attend?Regardless of title, you should attend if you make decisions about what to build and who to build it for, product direction or strategy, functionality, or taking the product to market.
Titles routinely seen in the seminar include product manager, technical product manager, product marketing manager and market/industry manager. Directors and executive leadership of product management and product marketing teams will find the seminar especially useful for determining roles & responsibilities.
Seminar fees$1,595 US per person for the 2-day Practical Product Management seminar.
$2,195 US per person for the 2-day Practical Product Management with the 1-day Requirements That Work seminars.
LocationHilton San Diego Del Mar
How can you ensure an Agile development team remains aligned to company strategy and market needs? No matter how agile Development is, you'll never build a successful product if the work being done isn’t focused on building products people want to buy.
Living in an Agile World teaches that product managers are responsible for defining requirements and maintaining the product backlog, but how should they be expressed in Agile? What artifacts are necessary? Which meetings are mandatory? What’s a burn-down chart and who creates it? And where do these requirements originate anyway?
©2010 Pragmatic Marketing. All rights reserved