There are two integral parts in product development - Discovery and Delivery.

• Discovery means to seek for ideas for exponential growth, to validate and iterate ideas, and then get these ideas spread.
• Delivery means to ensure the implementation of ideas with development team, to ship incrementally and iteratively, to identify the MVP in order to ship as early as possible. We will learn about processes, tools, practices, activities(meetings) in Discovery and Delivery and how to make use of those as a Scrum Product Owner.

You will realize the dilema and challenges for modern product development

• Why even if you know a lot about Agile, Lean Startup, Design Thinking, Business Model Canvas, Brain storming, what you have is only illusion of safety. In the end, you have nothing.
• Why it is hard to see innovation from incubators, cafe and innovation lab in the organization.
• Why prize at innovation competition will become a curse instead profitable business.
• Why it is not a wise choice to make product/service better and better
• Why most product designers focus only on linear growth and optimization but be ignorant about exponential growth.
• Why it is a dead end to compete only on price and quality
• Why it is dangerous to focus solely on predictability and perfection
• Why it is risk to invest much on Ads and SEO
• Why it is a bad idea to invest much on R&D
• Why it is a bad strategy to have a perfect release
• Why following opinions of users too early will lead to trap

You will understand necessary tools, processes, tips in modern product development.

• How to make use of uncertainty to increase the chance of Serendipity
• How to leverage the art of Boxing to control risk, prioritize and focus
• How to leverage the power of Churning to inspire emerginsight.
• Why make small mistakes continuously is most realistic and economical strategy for innovation
• How to acquire, attract, inter(hyper)link resources to enable innovation
• How to differentiate, filter, attract and fire customers and make use of characteristics to iterate product idea
• How do think from business perspective other than product perspective
• How to decide whether to quit product idea, when, and under what criteria
• How to steal like an artist
• How to use social media & social network to market product idea.
• Why it is a bad idea to validate your product idea and how to invalidate it as early as possible.
• What are possible edges of your product and how to make use of Edgecraft to find your own niche
• How to inspire soft innovation to compete with hard innovation from big organizations
• How to make sure you team release as early as possible and as frequent as possible
• How to initialize a product and iterate release plan
• How to enable collaborative discovery and delivery
• How to balance between linear optimization and uncertain serendipity
• How to apply Scrum in product discovery and delivery process

Agenda

Product development is divided into two parts that go back and forth - Discovery and Delivery. Discovery means how to find exponential growth ideas, how to make these creative ideas use social networks to speed up dissemination and amplification; Delivery means how to ensure linear growth, how to efficiently implement ideas, how to verify, how to implement, how to find MVP, How to combine with agile methods such as Scrum, how to iterate. These are two parts that complement each other and are inseparable. Therefore, the three-day course design of the CSPO course is also based on these two parts.

Day 1

• Scrum Revisit
• Deep dive into Product Owner role with simulation
• Product Discovery
  • Soft Innovation vs. Hard Innovation
  • Soft Innovation with Edge Craft
  • Effective idea brain storming with Edge Craft Thinking
  • Refine product ideas with Impact Mapping

Day 2

We will focus on soft innovation and how to make products remarkable via soft innovation. We will analyze and share how to discover ideas, incubate ideas, and link ideas through some practical cases. We will discuss:

• Product Discovery - The Right IT
  • Inspire innovative ideas via Edge Craft Technique
  • Business goals
  • Identify customer problems
  • Validate / Invalidate "customer problems" with Pretotyping
  • Prioritize from source
  • Collaborative solution design with Design Studio
  • Eliciting constructive feedback

Day 3

Based on different product forms, our marketing methods should also be different. We will explore how to stimulate product communication through practical examples, including:

• Product Discovery - Magic of Spread

  • The dilemma of mass marketing
  • New society structure
  • Types of customers and their characteristics
  • How to iterate and market product ideas based on idea diffusion curve
  • How to leverage Edgecraft to build remarkable products
  • In the end we will combine the innotavion process with Scrum and put into practice.

• Product Delivery

  • Collaborative modeling
  • Product backlog & user story
  • Story mapping
  • Learning batch and release batch
  • Requirement splitting
  • Specification by Example
  • PO in Scrum meetings

After course

We will also share a lot of real world cases and we will do it online. Typically it will take place 2 weeks after course. We will cover:

• AHA Manifesto
• AHA Process
• AHA Toolbox
• Real world stories from which I got above

Who should attend

What will you learn

• As a entrepreneur, during the three days, I will be able to understand how to do product discovery and validate product problems. How to combine modern product discovery ideas such as Lean Startup, Impact Mapping, Pretotyping, Design Thinking, Scrum into practice to increase the chance to survive.
• As a Scrum beginner，I will have good understanding of product discovery and delivery. What are the necessary tools, process, and activities to enable high performing product team.
• As a senior manager，I will master the core value, principles of modern product discovery and development. I will be prepared for the transition to agile organization.
• As a Product manager，I will realize it is a bad idea for PO to focus on product backlog and user story maintenance. PO is not a Product Owner, he should be a Problem Owner as well as a Police Office of the team. I will master necessary tools