8 results found

1. Agile Product Ownership: Passions, Puzzles, Prouds & Sorries

   Go deep on the topic of being an Agile product owner in this engaging, informative session. In a Lean Coffee™ - a lightly structured yet agenda-less session – everyone participates. The group selects the topics, discusses their experiences, and learns from each other. Bring your brain, energy, curiosity, passions, puzzles, “prouds” and “sorries”. You don’t need to be an expert or have in-depth experience in Agile product ownership to add and obtain value.

   Ellen Gottesdiener facilitates the Lean Coffee™, as she did at the Product Management Festival in Zurich this past September. (The session was considered a highlight of the event, see http://www.productmanagementfestival.com/lean-cafe/ for more details on how it works). Join in for deep conversation, new connections, and learn a technique—Lean Coffee™—you can bring back to your community.

   Ellen Gottesdiener, Principle of EBG Consulting (www.ebgconsulting.com), an Agile coach, author, collaborative workshop facilitator, and agile requirements expert. Ellen’s most recent book, Discover to Deliver: Agile Product Planning and Analysis (www.DiscoverToDeliver.com), co-authored with Mary Gorman, describes essential practices to collaboratively deliver high value products.

   Go deep on the topic of being an Agile product owner in this engaging, informative session. In a Lean Coffee™ - a lightly structured yet agenda-less session – everyone participates. The group selects the topics, discusses their experiences, and learns from each other. Bring your brain, energy, curiosity, passions, puzzles, “prouds” and “sorries”. You don’t need to be an expert or have in-depth experience in Agile product ownership to add and obtain value.

   Ellen Gottesdiener facilitates the Lean Coffee™, as she did at the Product Management Festival in Zurich this past September. (The session was considered a highlight of the… more

   23 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Product Development  ·  Delete…  ·  Admin →

2. Dev backlog vs Product backlog vs Roadmap

   A never ending discussion on what's important and what are we developing vs what's my roadmap brings every stakeholder in organization on a discussion table. The debate can only become meaningful if a Product manager brings an effective conclusion.

   Learn what belong where and what can make way for deliverable product.

   33 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Product Development  ·  Delete…  ·  Admin →

3. The Dirty Dozen Roadmap Roadblocks

   You’re about to show the product roadmap you’ve slaved over to your executives, your key customers or your sales team. What could possibly go wrong?

   In the sequel to the most popular session at PCamp Boston 2013, Bruce McCarthy, Chief Product Person at UpUp Labs, Vice President and Chief Evangelist for the BPMA, and popular speaker, will explore the myriad mistakes product people make when developing product roadmaps.

   He’ll explore what happens when you:

   • Focus on features
   • Try too hard to please
   • Don't get buy-in
   • Prioritize on gut
   • Fail to tell a story

   And he'll tell you what you can do to avoid the dirty dozen roadmap roadblocks.

   You’re about to show the product roadmap you’ve slaved over to your executives, your key customers or your sales team. What could possibly go wrong?

   In the sequel to the most popular session at PCamp Boston 2013, Bruce McCarthy, Chief Product Person at UpUp Labs, Vice President and Chief Evangelist for the BPMA, and popular speaker, will explore the myriad mistakes product people make when developing product roadmaps.

   He’ll explore what happens when you:

   • Focus on features
   • Try too hard to please
   • Don't get buy-in
   • Prioritize on gut
   • Fail to tell a story

   And he'll tell you what you can… more

   77 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Product Development  ·  Delete…  ·  Admin →

4. Developer Evangelism: Spreading The Word, Inside & Out

   When we say that the web is becoming API-driven, we're really talking about using the offerings of specific companies like Facebook and Google. How do developers decide whose API to use and whose to abandon? Many of those companies are turning to developer evangelists and advocates to encourage developers, or even entire companies, to pursue deeper integrations.

   The job description of a developer evangelist is akin to "professional hat-wearer" and usually includes aspects of sales, marketing, community management. There's a strong case for getting them involved in product management because they collect so much feedback from real users in real situations. But how can product management best benefit from the work of someone whose paper title is in product marketing?

   When we say that the web is becoming API-driven, we're really talking about using the offerings of specific companies like Facebook and Google. How do developers decide whose API to use and whose to abandon? Many of those companies are turning to developer evangelists and advocates to encourage developers, or even entire companies, to pursue deeper integrations.

   The job description of a developer evangelist is akin to "professional hat-wearer" and usually includes aspects of sales, marketing, community management. There's a strong case for getting them involved in product management because they collect so much feedback from real users in real… more

   7 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Product Development  ·  Delete…  ·  Admin →

5. Requirements, Stories, and Agile — Oh My!

   Traditional requirements deliverables like MRDs (Market Requirements Documents) and PRDs (Product Requirements Documents) have no place in Agile… right? Or do they? Many teams throw out most “traditional” product management techniques when implementing agile, often to run into problems when it comes to planning, roadmapping, and aligning with other functions like marketing. So are MRDs and PRDs the answer? Or is there another way to have some structure while at the same time getting the benefits of agile? This session will talk about what is different about requirements within an agile environment — what product managers need to stop doing, but also what they should keep doing and why it’s important.

   Submitted by Jeff Lash. Jeff is a Research Director at SiriusDecisions, where he conducts research and advises product management teams within B2B companies on how to improve their performance and effectiveness. He has 10+ years experience in product management, user experience and product development. Jeff writes the popular How To Be a Good Product Manager blog (www.goodproductmanager.com) and is on Twitter as @jefflash.

   Traditional requirements deliverables like MRDs (Market Requirements Documents) and PRDs (Product Requirements Documents) have no place in Agile… right? Or do they? Many teams throw out most “traditional” product management techniques when implementing agile, often to run into problems when it comes to planning, roadmapping, and aligning with other functions like marketing. So are MRDs and PRDs the answer? Or is there another way to have some structure while at the same time getting the benefits of agile? This session will talk about what is different about requirements within an agile environment — what product managers need to stop doing,… more

   34 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Product Development  ·  Delete…  ·  Admin →

6. Tell Me What You Need: Customer-Oriented Product Development

   A successful new product or service strategy requires a laser focus on your customer’s wants, needs and pain points from development, to testing, to launch and support. Thus, a best-in-class NPD process takes an integrated approach that extends beyond the completion of the product to re-think and re-imagine how the launch will impact the entire value proposition -- including areas such as pricing, packaging, and sales and marketing. While many new product development processes do this to some extent, very few companies keep the customer at the center of this process every step of the way.

   While it’s true that companies should not rely on customers to directly identify their needs for new-to-the-world innovations – i.e. today’s equivalent of Ford’s Model T or Apple’s iPod -- product teams should always be thinking about what will motivate a customer to use the product and what market gap it fills. What are their goals at the end of the day, and how do their needs and pain points funnel into these goals? With practical tips and illustrative case studies, you will walk away from this session being able to:
   • Identify the difference between customer needs and goals
   • More clearly define your core customer segments for new products
   • Understand the importance of context-setting when marketing new products

   Join Mark Carr, Managing Partner, South Street Strategy who will present this valuable session

   A successful new product or service strategy requires a laser focus on your customer’s wants, needs and pain points from development, to testing, to launch and support. Thus, a best-in-class NPD process takes an integrated approach that extends beyond the completion of the product to re-think and re-imagine how the launch will impact the entire value proposition -- including areas such as pricing, packaging, and sales and marketing. While many new product development processes do this to some extent, very few companies keep the customer at the center of this process every step of the way.

   While it’s true that… more

   5 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Product Development  ·  Delete…  ·  Admin →

7. The Power Of Adjacency: Growth Strategies In Your Backyard

   Identifying and exploiting new opportunities for growth is a constant point of tension for companies. Yet in this never ending quest for growth, many business strategists fail to see the opportunities that are right in their backyards – customer or capability adjacencies that are very natural extensions of their current strategies. An adjacency-based approach to growth has the benefit of leveraging business assets that already exist, but it does come with risks. For example, strategies that are too far afield from your core offerings – and thus with weak linkages – are likely to fail.

   In this session we will discuss best practices in embedding an innovation culture into an organization through a structured approach of defining, scoping and exploiting adjacencies that can build a long-term pipeline of opportunities for growth. You will walk away from this session being able to:

   • Apply several methods for leveraging adjacencies in your own organization

   Presented by Mark Carr, Managing Partner, South Street Strategy
   • Understand how to evaluate and prioritize the best adjacencies for growth
   • Identify the key issues required to succeed with adjacencies and the risks to watch out for
   • Learn from case studies that demonstrate how a successful adjacency strategy can be developed and implemented.

   Identifying and exploiting new opportunities for growth is a constant point of tension for companies. Yet in this never ending quest for growth, many business strategists fail to see the opportunities that are right in their backyards – customer or capability adjacencies that are very natural extensions of their current strategies. An adjacency-based approach to growth has the benefit of leveraging business assets that already exist, but it does come with risks. For example, strategies that are too far afield from your core offerings – and thus with weak linkages – are likely to fail.

   In this session we will… more

   10 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Product Development  ·  Delete…  ·  Admin →

8. 'Congratulations! You have too many products' – How to make it succeed

   Here are some of the subjects we will cover:
   - How to move beyond a “one-product” company
   - Sharing infrastructure between products
   - Selling multiple products
   - Optimizing the portfolio
   - Structuring R&D
   - Licensing best practices
   - Subject Matter Experts (SME) vs. Cross functional teams

   Join Oded Valin, Director of Product Management at CyberArk to learn what worked, what didn’t work and what was learned in growing the company from a small startup with one product to 350 Employees Company with an impressive product portfolio.

   53 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Product Development  ·  Delete…  ·  Admin →