The document discusses how games can be used to support business analysis activities. It provides examples of different types of games that can be used for requirements gathering, prioritization, discovery, and innovation. Some key games discussed include Speed Boat to identify customer pain points, Spider Web to understand relationships between products, and Buy a Feature to prioritize features based on customer willingness to pay. The document advocates that games create structured activities that allow free and playful thinking to generate insights. It also provides tips for facilitating different games.
3 karabak kuyavets transformation of business analyst to product ownerIevgenii Katsan
The document discusses the transformation of a business analyst to a product owner role. It notes that hierarchical management modes are no longer suited for modern business challenges. Product modes were developed to allow teams to build, run, and iterate solutions continuously rather than separating these stages. A business analyst focuses on requirements gathering, while a product owner sets vision and priorities and makes decisions to support the team. The document advises business analysts to adopt a product owner mindset by focusing more on business objectives and outcomes rather than just requirements. It provides five recommendations for when and how to shift one's mindset to that of a product owner.
22 May 2018 talk on differences between consumer tech (B2C) and enterprise tech (B2B) companies for Lean Product/UX Silicon Valley meetup. Emphasis on:
- dozens of in-depth interviews vs. thousands of market funnel A/B tests
- understand both buyers and users
- predicable pressure for “specials” on major deals
- need for product to deliver against customer's quantitative metrics
This document discusses different organizational patterns for product management departments. It identifies four common patterns: specialization, external-internal, product area, and emerging. The specialization pattern structures the department into functional roles with rigid responsibilities. The best structure depends on business context, but rigid roles should be avoided. Agile product management aims to be adaptive to changing markets and customer needs.
The Scrum Product Owner needs to bring creative thinking to the team and to the product development. This was presented at the Atlanta Scrum Gathering 2012.
This document discusses the differences between product managers and product owners in agile development. It notes that product managers have a broader scope and are responsible for the overall product strategy, roadmap, and market success, while product owners focus intensely on individual agile teams. The document outlines common failure modes when these roles are not properly defined or staffed. It provides examples of small and large organizational structures and emphasizes that product owner roles must be fully staffed and selected thoughtfully based on each team's focus area.
AgileCamp Dallas: Unpacking Business Value (Mironov)Rich Mironov
From the development side, we often think of Business Value as accurate, one-dimensional, and easy to auto-sort. We unpack this a bit, and try to get back to real customer value. Core analogy: is freeze-dried astronaut ice cream really ice cream? Do our paying customers care about business value points, or only real improvements they can directly experience?
A keynote at AgileCamp Dallas, 19 Oct 2015
What Is A Product Manager? | The Quick Guide To Product ManagementProdPad
This document provides an overview of the product manager role. It discusses how product managers are multidisciplinary, strategic, persistent, and collaborative. Their key responsibilities include setting a product vision, managing ideas and feedback, planning and prioritizing, building a product roadmap, leading product execution, shipping the product, getting feedback and shipping more. Product managers often have experience in product marketing, UX design, software development or other disciplines. They are naturally curious, good at managing people, creative, humble, inquisitive, big picture thinkers, practical, and very organized. The role attracts people from diverse backgrounds.
3 karabak kuyavets transformation of business analyst to product ownerIevgenii Katsan
The document discusses the transformation of a business analyst to a product owner role. It notes that hierarchical management modes are no longer suited for modern business challenges. Product modes were developed to allow teams to build, run, and iterate solutions continuously rather than separating these stages. A business analyst focuses on requirements gathering, while a product owner sets vision and priorities and makes decisions to support the team. The document advises business analysts to adopt a product owner mindset by focusing more on business objectives and outcomes rather than just requirements. It provides five recommendations for when and how to shift one's mindset to that of a product owner.
22 May 2018 talk on differences between consumer tech (B2C) and enterprise tech (B2B) companies for Lean Product/UX Silicon Valley meetup. Emphasis on:
- dozens of in-depth interviews vs. thousands of market funnel A/B tests
- understand both buyers and users
- predicable pressure for “specials” on major deals
- need for product to deliver against customer's quantitative metrics
This document discusses different organizational patterns for product management departments. It identifies four common patterns: specialization, external-internal, product area, and emerging. The specialization pattern structures the department into functional roles with rigid responsibilities. The best structure depends on business context, but rigid roles should be avoided. Agile product management aims to be adaptive to changing markets and customer needs.
The Scrum Product Owner needs to bring creative thinking to the team and to the product development. This was presented at the Atlanta Scrum Gathering 2012.
This document discusses the differences between product managers and product owners in agile development. It notes that product managers have a broader scope and are responsible for the overall product strategy, roadmap, and market success, while product owners focus intensely on individual agile teams. The document outlines common failure modes when these roles are not properly defined or staffed. It provides examples of small and large organizational structures and emphasizes that product owner roles must be fully staffed and selected thoughtfully based on each team's focus area.
AgileCamp Dallas: Unpacking Business Value (Mironov)Rich Mironov
From the development side, we often think of Business Value as accurate, one-dimensional, and easy to auto-sort. We unpack this a bit, and try to get back to real customer value. Core analogy: is freeze-dried astronaut ice cream really ice cream? Do our paying customers care about business value points, or only real improvements they can directly experience?
A keynote at AgileCamp Dallas, 19 Oct 2015
What Is A Product Manager? | The Quick Guide To Product ManagementProdPad
This document provides an overview of the product manager role. It discusses how product managers are multidisciplinary, strategic, persistent, and collaborative. Their key responsibilities include setting a product vision, managing ideas and feedback, planning and prioritizing, building a product roadmap, leading product execution, shipping the product, getting feedback and shipping more. Product managers often have experience in product marketing, UX design, software development or other disciplines. They are naturally curious, good at managing people, creative, humble, inquisitive, big picture thinkers, practical, and very organized. The role attracts people from diverse backgrounds.
The document provides an overview of release planning, including:
1. It outlines the basic components of a release plan - creating a backlog, sizing and ordering items, determining velocity range, and finalizing the plan.
2. It discusses different types of release planning approaches - fixed date with variable scope being most common.
3. It emphasizes the importance of continual delivery of value to customers through thin vertical slices and fast feedback.
Technical Debt is a gap between Computer Science and Software Engineering. Common understanding of causes for the Technical Debt is centered on the careless software development choices for the sake of speed and expediency. However Technical Debt usually goes beyond just Technology. This presentation covers the origins of Technical and Product Debt, how to manage it and mitigate it
This document discusses lean product development processes. It begins by comparing waterfall, agile, and lean methodologies. Waterfall involves completing each stage sequentially before beginning the next, while agile is iterative with cross-functional collaboration and frequent demos. Lean combines agile development with customer validation to build only necessary features. The document then outlines a lean process with four stages: thinking through the product idea, building a minimum viable product, shipping to users while measuring, and continuously tweaking the product. It emphasizes outcomes over deliverables and iterating often through building, testing, and learning from customers.
Rich Mironov discusses the differences between product managers and product owners in agile development. He outlines common failure modes when these roles are not properly defined or staffed. For larger organizations, Mironov proposes organizational maps that divide responsibilities between product managers and multiple product owners across several agile teams, to ensure products have both technical and market focus. The presentation emphasizes the need to thoughtfully assign these critical roles rather than using a one-size-fits-all approach.
Product Management or the Intricate Art of Getting (the Right) Things DoneCprime
The document provides an overview of product management at different organizational scales, from a single product to multiple products and teams. It discusses the roles and responsibilities of product managers and how they influence, decide, and advocate for their products. It outlines common struggles and traps faced by product managers as an organization grows from one product with one team, to one product across several teams, and finally to multiple products across many teams. The key responsibilities for product managers are defined for each structure.
When Agile teams begin to deliver products incrementally, new opportunities open up at the portfolio level to deliver strategic business value. However, the traditional approach to portfolio management — which depends on long-range forecasting and fixed financial controls — breaks down as business environments grow more complex, leaving portfolio managers ill-equipped to reap the potential benefits of their Agile programs.
SolutionsIQ Managing Director John Rudd and Dave West, Chief Product Officer at Tasktop, discuss active portfolio management from a product management point of view and how it can help guide decision making in an Agile enterprise.
This document discusses factors to consider when choosing between Agile and traditional methodologies for software development projects. It summarizes that Agile is not always the best approach, providing examples where traditional methods may be preferable such as when requirements are clear or frequent approvals are needed. It also discusses how Agile allows for earlier product launches through prioritizing minimum viable features. Budgeting is covered, noting that Agile works best with a set budget rather than estimates that can change. Unnoticed benefits of Agile include improved team culture and readiness for future projects.
How IT services companies who want to build non linear growth models need to make the necessary shifts internally to be able to innovate in product creation
Analysis is so important to agile teams they do it every day. Every. Single. Day. In some respects agile teams perform analysis in a very different manner than traditional teams, and in some respects in a very similar manner. Agile analysis is collaborative and evolutionary in nature. Disciplined agile analysis takes it up a notch to address the complexity factors agile teams face at scale.
In this presentation we discuss how disciplined agile teams address analysis activities throughout the lifecycle. The transition to agile requires a mindset, skill set, and very often role change for people who are currently business analysts. On the majority of agile teams the role of business analyst has disappeared, but in some situations at scale the role is of vital importance – this isn’t your father’s software team any more. Lessons learned from several organizations making the transition to agile will be shared.
Key learning points:
• Discover how disciplined agile teams approach analysis, and modeling in general
• Learn agile analysis and modeling strategies
• Discover how business analysts can transition to an agile environment
Video can be found here: https://www.youtube.com/watch?v=-8tR-UbUpvI
This document outlines a Quantum R&D (QRaD) process for conducting low-cost, rapid exploratory research and development. The goals are to perform small experiments, develop hardware demonstrators for new ideas, and explore potential "thought leadership" technologies. Individual projects would each be staffed by 1-2 people plus a summer intern with a budget of $30k. Ideas are solicited internally and from customers. A selection panel of innovators chooses the most promising ideas based on factors like understanding future trends, demonstrating a "wow factor", and enabling potential future customer benefits. Selected projects run over the summer and present final demonstrations in August.
"How to Build an Innovation pipeline in Large Organizations" Atzmon Tal, Inno...it-people
This document outlines how to build an innovation funnel in large organizations. It discusses challenges like stifling innovation and looking for shortcuts. It then presents HPE Software's innovation funnel model as a case study. The model includes four stages - ideation, incubation, seed, and growth. Ideas are submitted and refined through each stage, which involves validating problems/solutions, building MVPs, and handing projects off to businesses. Metrics are used to manage the funnel. The results for HPE show over 600 ideas submitted, 110 incubated, 18 seeded, and 11 grown into projects over two years. It concludes that organizations should start by validating a use case to reduce innovation risks.
Aagile business analytics - how a new generation bi is reducing risk and incr...Andrew Marks
1) The document discusses how agile business analytics, or "Generation BI", can help reduce risk and increase adoption of business intelligence solutions. It emphasizes taking an iterative and flexible approach to deployment.
2) Key aspects of an agile approach include involving stakeholders throughout, prioritizing requirements, embracing change, and delivering working software in short iterations. This allows for demonstrating progress regularly and adjusting based on feedback.
3) Other important considerations include understanding how users will leverage the solution, thorough testing and validation, and training end users to drive adoption and mitigate risks. Taking an agile approach helps ensure the BI solution can adapt to changing business needs.
The Product Management X-Factor: How to be a Rock Star Product ManagerPaul Young
Product Management is a tough job: we need to be business oriented, tactical, strategic, and technical all at the same time. But some people have cracked the code about how to be more effective product managers than others. What is it about these rock star product managers that separates them from the rest of us?
Over the past 10 years in product management, Paul Young has observed what makes some people successful where others fail, and boiled it down to seven product management "x-factors," that turn good people into great.
Winner of "Best Session" at Rocky Mountain ProductCamp 2010.
NOTE: Because of the limitations of SlideShare, the formatting of this presentation does not match the original. Come to ProductCamp Austin in Jan 2011 to see this presentation live. productcampaustin.org
Lean Portfolio Strategy Part 3: Epic Management - Take the ExitsCprime
Organizations might have set up all the process steps for portfolio flow: the monthly strategic portfolio review, the portfolio kanban, even the lean business case. But, they are still not getting the idea that small, testable, constantly evaluated initiatives are what really increase your output of value to the customer and put you way ahead of the competition.
In part 1 of this webinar we explored how signs of imitation LPM show up in an organization’s approach to strategy. In part 2, we covered how to organize around value streams with examples of successful LPM.
Now, in this third webinar in our Lean Portfolio Management series we’ll join Cprime's Michiko Quinones (Jira Align Consultant), Jean Dahl (General Manager, Scaled Agility), & Neha Tiwari (Business Agility Portfolio Consultant) to learn techniques to:
Question performing work that doesn't clearly align to your organization's strategy
Develop a process that makes things smaller and testable when it comes to initiative creation and management
Build a culture that allows work to stop if it's not going to meet its intended purpose
Make sure that you are "thinking lean," rather than just "doing lean"
Stakeholder Management for Product Managers - ProductTank ParisJean-Yves SIMON
How to manage your Stakeholders, mainly internally when you're a Product Manager working in a medium to large organization. Tips on how to be efficient and recognized within your organization.
The document discusses Innovation Games, which are serious games used to solve product strategy and management problems. Innovation Games are played with customers, stakeholders, online or in-person. They work to manage roadmaps, identify new products, train sales teams, and more. Some example games described are Product Box, Speed Boat, Prune the Product Tree, and Spider Web. Case studies show how companies like Wyse Technologies, Qualcomm, and Aladdin Knowledge Systems have used Innovation Games to get customer feedback and insights to improve their products.
Innovation Games - Making fun work for you!Tathagat Varma
The document discusses using games and play to foster innovation. It introduces Innovation Games as a method to collaboratively engage customers through activities like Product Box, where customers design packaging, and Show and Tell, where they share important artifacts. Games create purpose, rules, feedback and voluntary participation to solve problems in a fun, visual way. Several companies are cited as using Innovation Games successfully to prioritize features and better understand customer needs.
The document provides an overview of release planning, including:
1. It outlines the basic components of a release plan - creating a backlog, sizing and ordering items, determining velocity range, and finalizing the plan.
2. It discusses different types of release planning approaches - fixed date with variable scope being most common.
3. It emphasizes the importance of continual delivery of value to customers through thin vertical slices and fast feedback.
Technical Debt is a gap between Computer Science and Software Engineering. Common understanding of causes for the Technical Debt is centered on the careless software development choices for the sake of speed and expediency. However Technical Debt usually goes beyond just Technology. This presentation covers the origins of Technical and Product Debt, how to manage it and mitigate it
This document discusses lean product development processes. It begins by comparing waterfall, agile, and lean methodologies. Waterfall involves completing each stage sequentially before beginning the next, while agile is iterative with cross-functional collaboration and frequent demos. Lean combines agile development with customer validation to build only necessary features. The document then outlines a lean process with four stages: thinking through the product idea, building a minimum viable product, shipping to users while measuring, and continuously tweaking the product. It emphasizes outcomes over deliverables and iterating often through building, testing, and learning from customers.
Rich Mironov discusses the differences between product managers and product owners in agile development. He outlines common failure modes when these roles are not properly defined or staffed. For larger organizations, Mironov proposes organizational maps that divide responsibilities between product managers and multiple product owners across several agile teams, to ensure products have both technical and market focus. The presentation emphasizes the need to thoughtfully assign these critical roles rather than using a one-size-fits-all approach.
Product Management or the Intricate Art of Getting (the Right) Things DoneCprime
The document provides an overview of product management at different organizational scales, from a single product to multiple products and teams. It discusses the roles and responsibilities of product managers and how they influence, decide, and advocate for their products. It outlines common struggles and traps faced by product managers as an organization grows from one product with one team, to one product across several teams, and finally to multiple products across many teams. The key responsibilities for product managers are defined for each structure.
When Agile teams begin to deliver products incrementally, new opportunities open up at the portfolio level to deliver strategic business value. However, the traditional approach to portfolio management — which depends on long-range forecasting and fixed financial controls — breaks down as business environments grow more complex, leaving portfolio managers ill-equipped to reap the potential benefits of their Agile programs.
SolutionsIQ Managing Director John Rudd and Dave West, Chief Product Officer at Tasktop, discuss active portfolio management from a product management point of view and how it can help guide decision making in an Agile enterprise.
This document discusses factors to consider when choosing between Agile and traditional methodologies for software development projects. It summarizes that Agile is not always the best approach, providing examples where traditional methods may be preferable such as when requirements are clear or frequent approvals are needed. It also discusses how Agile allows for earlier product launches through prioritizing minimum viable features. Budgeting is covered, noting that Agile works best with a set budget rather than estimates that can change. Unnoticed benefits of Agile include improved team culture and readiness for future projects.
How IT services companies who want to build non linear growth models need to make the necessary shifts internally to be able to innovate in product creation
Analysis is so important to agile teams they do it every day. Every. Single. Day. In some respects agile teams perform analysis in a very different manner than traditional teams, and in some respects in a very similar manner. Agile analysis is collaborative and evolutionary in nature. Disciplined agile analysis takes it up a notch to address the complexity factors agile teams face at scale.
In this presentation we discuss how disciplined agile teams address analysis activities throughout the lifecycle. The transition to agile requires a mindset, skill set, and very often role change for people who are currently business analysts. On the majority of agile teams the role of business analyst has disappeared, but in some situations at scale the role is of vital importance – this isn’t your father’s software team any more. Lessons learned from several organizations making the transition to agile will be shared.
Key learning points:
• Discover how disciplined agile teams approach analysis, and modeling in general
• Learn agile analysis and modeling strategies
• Discover how business analysts can transition to an agile environment
Video can be found here: https://www.youtube.com/watch?v=-8tR-UbUpvI
This document outlines a Quantum R&D (QRaD) process for conducting low-cost, rapid exploratory research and development. The goals are to perform small experiments, develop hardware demonstrators for new ideas, and explore potential "thought leadership" technologies. Individual projects would each be staffed by 1-2 people plus a summer intern with a budget of $30k. Ideas are solicited internally and from customers. A selection panel of innovators chooses the most promising ideas based on factors like understanding future trends, demonstrating a "wow factor", and enabling potential future customer benefits. Selected projects run over the summer and present final demonstrations in August.
"How to Build an Innovation pipeline in Large Organizations" Atzmon Tal, Inno...it-people
This document outlines how to build an innovation funnel in large organizations. It discusses challenges like stifling innovation and looking for shortcuts. It then presents HPE Software's innovation funnel model as a case study. The model includes four stages - ideation, incubation, seed, and growth. Ideas are submitted and refined through each stage, which involves validating problems/solutions, building MVPs, and handing projects off to businesses. Metrics are used to manage the funnel. The results for HPE show over 600 ideas submitted, 110 incubated, 18 seeded, and 11 grown into projects over two years. It concludes that organizations should start by validating a use case to reduce innovation risks.
Aagile business analytics - how a new generation bi is reducing risk and incr...Andrew Marks
1) The document discusses how agile business analytics, or "Generation BI", can help reduce risk and increase adoption of business intelligence solutions. It emphasizes taking an iterative and flexible approach to deployment.
2) Key aspects of an agile approach include involving stakeholders throughout, prioritizing requirements, embracing change, and delivering working software in short iterations. This allows for demonstrating progress regularly and adjusting based on feedback.
3) Other important considerations include understanding how users will leverage the solution, thorough testing and validation, and training end users to drive adoption and mitigate risks. Taking an agile approach helps ensure the BI solution can adapt to changing business needs.
The Product Management X-Factor: How to be a Rock Star Product ManagerPaul Young
Product Management is a tough job: we need to be business oriented, tactical, strategic, and technical all at the same time. But some people have cracked the code about how to be more effective product managers than others. What is it about these rock star product managers that separates them from the rest of us?
Over the past 10 years in product management, Paul Young has observed what makes some people successful where others fail, and boiled it down to seven product management "x-factors," that turn good people into great.
Winner of "Best Session" at Rocky Mountain ProductCamp 2010.
NOTE: Because of the limitations of SlideShare, the formatting of this presentation does not match the original. Come to ProductCamp Austin in Jan 2011 to see this presentation live. productcampaustin.org
Lean Portfolio Strategy Part 3: Epic Management - Take the ExitsCprime
Organizations might have set up all the process steps for portfolio flow: the monthly strategic portfolio review, the portfolio kanban, even the lean business case. But, they are still not getting the idea that small, testable, constantly evaluated initiatives are what really increase your output of value to the customer and put you way ahead of the competition.
In part 1 of this webinar we explored how signs of imitation LPM show up in an organization’s approach to strategy. In part 2, we covered how to organize around value streams with examples of successful LPM.
Now, in this third webinar in our Lean Portfolio Management series we’ll join Cprime's Michiko Quinones (Jira Align Consultant), Jean Dahl (General Manager, Scaled Agility), & Neha Tiwari (Business Agility Portfolio Consultant) to learn techniques to:
Question performing work that doesn't clearly align to your organization's strategy
Develop a process that makes things smaller and testable when it comes to initiative creation and management
Build a culture that allows work to stop if it's not going to meet its intended purpose
Make sure that you are "thinking lean," rather than just "doing lean"
Stakeholder Management for Product Managers - ProductTank ParisJean-Yves SIMON
How to manage your Stakeholders, mainly internally when you're a Product Manager working in a medium to large organization. Tips on how to be efficient and recognized within your organization.
The document discusses Innovation Games, which are serious games used to solve product strategy and management problems. Innovation Games are played with customers, stakeholders, online or in-person. They work to manage roadmaps, identify new products, train sales teams, and more. Some example games described are Product Box, Speed Boat, Prune the Product Tree, and Spider Web. Case studies show how companies like Wyse Technologies, Qualcomm, and Aladdin Knowledge Systems have used Innovation Games to get customer feedback and insights to improve their products.
Innovation Games - Making fun work for you!Tathagat Varma
The document discusses using games and play to foster innovation. It introduces Innovation Games as a method to collaboratively engage customers through activities like Product Box, where customers design packaging, and Show and Tell, where they share important artifacts. Games create purpose, rules, feedback and voluntary participation to solve problems in a fun, visual way. Several companies are cited as using Innovation Games successfully to prioritize features and better understand customer needs.
This document discusses Innovation Games, which are informal games used to elicit customer needs and desires to aid in qualitative market research. It was created by Luke Hohmann and similar Community Games were initiated by Sunny Brown and David Gray. The document lists and describes various Innovation Games, including their objectives. It notes how Innovation Games can be used for discovery, shaping, prioritizing and acting. It also discusses how Agile practices and Innovation Games fit together and provides further links for additional information.
12 Rules for Building Your Product Management PlaybookJeremy Horn
Slides Ian Moulton recently used in his discussion w/ mentees of The Product Mentor.
The Product Mentor is a program designed to pair Product Mentors and Mentees from around the World, across all industries, from start-up to enterprise, guided by the fundamental goals…Better Decisions. Better Products. Better Product People.
Throughout the program, each mentor leads a conversation in an area of their expertise that is live streamed and available to both mentee and the broader product community.
http://TheProductMentor.com
The document provides an overview of a hypothetical product development process led by a product manager named Mr. DB at a company called ACowStick Pvt Ltd. Mr. DB identifies an opportunity in the growing tablet accessories market and conceptualizes a new product called FunTabStick, which is a tablet cover that doubles as speakers. He develops a product line and obtains initial cost quotes from suppliers. Mr. DB then presents his concept and return on investment analysis to the company's executive committee for approval to further evaluate the product's requirements and feasibility.
The document provides an overview of design thinking methodology and how it can be combined with LEAN principles for product development. It discusses the key stages of design thinking - empathizing to understand user needs, defining insights, ideating potential solutions, prototyping ideas, and testing prototypes with users. It also explains how minimum viable products and build-measure-learn cycles from LEAN can help accelerate the design process. The presentation aims to illustrate how design thinking and LEAN can be applied together to more efficiently develop products that meet user needs.
Innovation games are a set of facilitated games used to engage participants in creative problem solving and strategic thinking. Some key types are idea engine games that use visual collaboration, and decision engine games that use virtual currency. Innovation games provide goals, rules, feedback and voluntary participation to generate ideas. They have been used by many organizations for purposes like product development, retrospectives, and budget planning.
Prioritizing for Profit from AgilePaloozaEnthiosys Inc
The document discusses prioritizing a product backlog for profit. It recommends considering three core groups when prioritizing: stakeholder alignment, strategic alignment, and driving profit. For stakeholder alignment, the backlog should include at least one item for each stakeholder group. For strategic alignment, it should include at least one item that aligns with the company's strategy. And to drive profit, it should include at least one item that generates revenue or reduces costs. The document provides various techniques for involving stakeholders, determining strategic priorities, and identifying profit drivers to create a holistically prioritized backlog.
Design 101 : Beyond ideation - Transforming Ideas to Software RequirementsHawkman Academy
1. The document provides guidance on transforming ideas into software requirements through establishing a product vision, identifying users, writing user stories, and building a prototype.
2. It emphasizes balancing business and user needs, iterating to improve the product, and focusing on user experience (UX).
3. The agenda includes creating a product vision, identifying personas, writing user stories organized on a user story map, and building a paper prototype using the Pop app to demo functionality.
This document outlines a 12-step user experience (UX) planning process for developing content management system (CMS) sites from a business perspective. The key steps include understanding business objectives, users and user stories through research and personas; designing information architecture through card sorting and site maps; wireframing; applying design patterns; and testing concepts with users. The goal is to apply user-centric planning concepts typically used in UX design to CMS projects to ensure a strong focus on problem-solving, content, and user experience.
Xing User Group Agile Rhein-Main: Innovation Games™Michael Tarnowski
Michael Tarnowski from Plays-In-Business.com gave a presentation of a Teaser Event on Innovation Games™ for the Xing User Group Agile Rhein-Main (https://www.xing.com/net/pria952a0x/agilerheinmain/).
What are Innovation Games and for what you can use them... Questions over questions... Here you get the answers!
The document discusses agile requirements discovery. It covers cross-functional teams, product vision, personas, user stories, epics, and user story mapping. Teams participate in exercises to practice forming cross-functional teams, creating a product vision statement, and mapping out a user story for a product idea. The presentation provides examples and templates for each agile requirement technique. It also outlines some pros and cons of the agile approach to requirements.
Presentation on Innovation Games ™ - What are Innovation Games and for what you can use them... Questions over questions... ;-)
Here you get the answers!
The document discusses lean startup approaches such as prototyping and minimum viable products (MVPs) to validate ideas with customers quickly and efficiently. It outlines different types of prototypes including low and high fidelity prototypes and how personas can help focus products. The document also provides guidance on different MVP approaches and market types including existing, new, cloned, and niche markets.
This document discusses embracing imperfection and how the concept of "good enough" can be a perfect solution. It promotes agile thinking and emphasizes understanding the problem, defining a minimum viable product (MVP), and building credibility incrementally. The document provides examples from ThinkGeek of addressing issues like address normalization and pre-orders with iterative, pragmatic solutions. It also discusses techniques like design sprints and feature planning that help determine MVPs and prioritize work. The overall message is that by focusing on solving core customer problems with iterative solutions, organizations can achieve success without needing a perfect plan or solution.
There’s a lot of speculation about open source product development. How can a product with “no IP” be competitive? What are the viable business models, when the code is freely available? And how am I supposed to build and take a viable product to market if my open source company is focused on services, not products?
The truth is, you can build — and successfully take to market — an open source product. But the rules are different, and must not be ignored. Product development is guided by different goals. Business models are based on different value propositions. And open source communities must be considered partners in the effort, not detractors or nay-sayers.
This talk will focus on three areas of open source products: product development, go-to-market strategy, and balancing product and services work. We’ll look at examples of open source products who have threaded the needle and “made it,” as well as a few that have crashed and burned. Most importantly, we’ll offer clear tips and guidance for those considering building or marketing an open source product.
This document discusses various strategies for monetizing a technology product or service. It begins by evaluating economies of scale and common pitfalls startups face. It then discusses how to guarantee customer adoption, such as Apple's strategy of making the Apple II accessible to non-hobbyists. Next, it addresses frameworks for determining appropriate product tiers and pricing, such as using a Kickstarter campaign to test pricing. Finally, it presents different options for monetization, including memberships, selling content, sponsorships, and leveraging user data. The overall document provides an overview of important considerations for startups seeking to effectively monetize their offerings.
Similar to 5 victoria cupet - learn to play business analysis (20)
5 hans van loenhoud - master-class the 7 skills of highly successful teamsIevgenii Katsan
The document describes the 7 skills that are important for effective teamwork: communicate, empathize, explore, collaborate, ideate, tell, and sell. It provides examples and exercises for each skill, such as creating personas to understand customers, exploring problems and goals, identifying team roles using Belbin's model, brainstorming ideas through divergent and convergent thinking, and using storytelling to present solutions. The overall message is that soft skills are critical for team and project success in addition to technical skills.
7 hans van loenhoud - the problem-goal-solution trinityIevgenii Katsan
The document discusses the problem-goal-solution trinity, which refers to the relationship between problems, goals, and solutions from the perspective of stakeholders. It defines a problem as an undesirable current state that inhibits desired behavior, a goal as a desirable future state that requires action to achieve, and a solution as a roadmap or plan to remove the problem and enable reaching the goal. It notes that problems and goals can only be identified through stakeholder elicitation, and that one stakeholder's problem may be another's goal. The document also discusses how problems, goals, and their relationships are not static and can change over time and context.
Digital disruption is defined as an effect that changes fundamental expectations and behaviors in a culture, market, industry or process through digital capabilities. It is an innovation that uses digital technologies to create change in our society and can threaten existing market players. Successful digital disruption satisfies a higher goal in a completely new way that is better, easier and cheaper, often through digital means. Design thinking is a light-weight approach using methods like prototyping to develop practical solutions to ill-defined problems, focusing on building quick prototypes to fail fast and succeed sooner through techniques like empathy mapping and the double diamond model. The lean startup approach emphasizes building minimal viable products to collect maximum learning from customers with minimum effort through pivoting based on testing and metrics.
3 zornitsa nikolova - the product manager between decision making and facil...Ievgenii Katsan
The document discusses the role of the product manager and describes them as being like a "mini-CEO" who must lead by example. It defines the ideal product manager as being DRIVEN, which stands for decisive, ruthless, informed, versatile, empowering, and negotiable. Each of these traits is then further explained, with examples of how a product manager can demonstrate being decisive by prioritizing important decisions, informed by verifying assumptions, and negotiable by seeking consensus or consent from stakeholders. The document concludes by having product managers assess themselves on how well they embody these DRIVEN traits in their daily work.
9 natali renska - product and outsource development, how to cook 2 meals in...Ievgenii Katsan
Natali Renska discusses cooking two meals in one pan by presenting steps such as cooking proteins or vegetables for one meal first before adding ingredients for a second meal to the same pan. The document provides tips on saving time and money by using one pan to cook multiple ingredients sequentially for two separate meals. Various techniques are proposed, such as cooking pasta or rice as a base before adding protein and sauce components for another meal.
7 denis parkhomenko - from idea to execution how to make a product that cus...Ievgenii Katsan
The document provides tips on how to make a product that customers will love. It discusses focusing on the problem and solution, targeting a specific market, and building a strong brand. It also outlines the typical stages a startup goes through, from creating an idea to releasing a minimum viable product to scaling up and harvesting returns. The overall message is that developing a deep understanding of customers, focusing efforts, iterating based on feedback, and having a clear business model are keys to success.
Anton Vitiaz has over 10 years of experience in business analysis, custom software development, and Microsoft CRM/SharePoint implementation. He discusses creating a minimum viable product (MVP) in 3 days by focusing on key features, keeping things very simple, and ensuring it works. The process involves planning simple implementations, cutting unnecessary elements, conducting micro 2-3 hour iterations with quick demos, adding demo data, presenting key concepts, and running simple tests. Motivating participants, having expertise, providing the right support tools, and limiting the timeframe to 3 days or less are important to success, while distractions, overcomplicating the task, and unrealistic deadlines can lead to failure.
5 mariya popova - ideal product management. unicorns in our realityIevgenii Katsan
The document discusses product management and how to transform unrealistic expectations ("unicorns") into practical realities. It defines product management and what product managers do, including developing strategy, managing releases, conducting research, and more. However, unrealistic expectations can cause problems if customer and product requirements do not align, or if "nice-to-have" features are prioritized over product improvements. The presentation provides tips on how to take a more realistic approach by understanding customer needs, conducting market research, determining requirements, and developing a product roadmap to guide the process. Templates are also shared for SWOT analysis, development charters, requirements documents, timelines, and roadmaps.
The document outlines a process for homework fieldwork that involves brainstorming ideas, exploring customer needs through interviews, prototyping potential solutions through storyboards and mockups, testing prototypes with customers to co-create, implementing a solution by 25% each assignment period and rolling a dice, and delivering the final solution to validate it and get feedback.
4 anton parkhomenko - how to make effective user research with no budget at...Ievgenii Katsan
The document discusses how to conduct effective user research with no budget and limited time. It provides recommendations for free or low-cost tools to conduct remote interviews and usability testing, including Zoom, OBS, Screencastify, Loom, and Lookback. It also recommends using YouTube to store recordings, Google Docs for transcripts, and Airtable to organize findings into an atomic database structure of people, sessions, jobs, pains, gains, and features linked to evidence from interviews. The methodology outlined atomizes research into small units that can be easily shared and built upon over time.
This document provides an overview of wound healing, its functions, stages, mechanisms, factors affecting it, and complications.
A wound is a break in the integrity of the skin or tissues, which may be associated with disruption of the structure and function.
Healing is the body’s response to injury in an attempt to restore normal structure and functions.
Healing can occur in two ways: Regeneration and Repair
There are 4 phases of wound healing: hemostasis, inflammation, proliferation, and remodeling. This document also describes the mechanism of wound healing. Factors that affect healing include infection, uncontrolled diabetes, poor nutrition, age, anemia, the presence of foreign bodies, etc.
Complications of wound healing like infection, hyperpigmentation of scar, contractures, and keloid formation.
Walmart Business+ and Spark Good for Nonprofits.pdfTechSoup
"Learn about all the ways Walmart supports nonprofit organizations.
You will hear from Liz Willett, the Head of Nonprofits, and hear about what Walmart is doing to help nonprofits, including Walmart Business and Spark Good. Walmart Business+ is a new offer for nonprofits that offers discounts and also streamlines nonprofits order and expense tracking, saving time and money.
The webinar may also give some examples on how nonprofits can best leverage Walmart Business+.
The event will cover the following::
Walmart Business + (https://business.walmart.com/plus) is a new shopping experience for nonprofits, schools, and local business customers that connects an exclusive online shopping experience to stores. Benefits include free delivery and shipping, a 'Spend Analytics” feature, special discounts, deals and tax-exempt shopping.
Special TechSoup offer for a free 180 days membership, and up to $150 in discounts on eligible orders.
Spark Good (walmart.com/sparkgood) is a charitable platform that enables nonprofits to receive donations directly from customers and associates.
Answers about how you can do more with Walmart!"
This presentation was provided by Rebecca Benner, Ph.D., of the American Society of Anesthesiologists, for the second session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session Two: 'Expanding Pathways to Publishing Careers,' was held June 13, 2024.
Gender and Mental Health - Counselling and Family Therapy Applications and In...PsychoTech Services
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
Level 3 NCEA - NZ: A Nation In the Making 1872 - 1900 SML.pptHenry Hollis
The History of NZ 1870-1900.
Making of a Nation.
From the NZ Wars to Liberals,
Richard Seddon, George Grey,
Social Laboratory, New Zealand,
Confiscations, Kotahitanga, Kingitanga, Parliament, Suffrage, Repudiation, Economic Change, Agriculture, Gold Mining, Timber, Flax, Sheep, Dairying,
2. Regional Director Europe & Africa @ IIBA
LEGO® SERIOUS PLAY® Facilitator
Business Trainer & Coach
Keynote Speaker
Bestselling Author
Victoria Cupet CBAP, PMP, PMI-PBA
7. Games
• Involves people
• Have structure and goals
• Operates more like a real-world system
• Results are unpredictable
• Small changes in variables generate dramatic differences in the result
8. Four Defining Traits of a Game
Goal
• “Sense of Purpose”
Rules
• “Unleash creativity and
foster strategic thinking”
Feedback
• “Provides motivation to
keep playing”
Voluntary Participation
• “Establishes common
ground”
GAME
9. Games in Business Analysis
• Are alternatives to standard business meetings
• Are structured activities
– a facilitator leads a group towards some goal by way of a game
– provides scope for thinking freely, even playfully
• Require a few props such as
– sticky notes, poster paper, markers, random pictures from magazines, or other
thought provoking objects
10. Games and The Voice of the Customer (VOC)
• Games support VOC to provide
– Detailed understanding of the customer’s requirements
– Common language for the team going forward
– Key input for the setting of appropriate design specifications for the new
product or service
– Highly useful foundation for product innovation
32. What Are Innovation Games®?
• Are serious games that solve a wide range of
product strategy and management problems
across the market lifecycle
• Are played:
– with customers & internal stakeholders
– online or in-person
– within or across organizational units
– in single or multi-game formats
33. What Makes Innovation Games Special?
• Games of collaborative play
• Leverage deep principles of cognitive
psychology and organizational
behavior
• Uncover data that is difficult to uncover
using traditional research techniques
• Customers are fully engaged in the task
• Produces the most honest and useful
feedback
https://www.innovationgames.com/agile-teams/
34. Collaboration DOES Need Tools
https://www.slideshare.net/jeffbrantley/brantley-innovation-gamespcamp2010done
35. Fields of Application
• Not only applicable for market research and
product design, but also for
– Portfolio management,
– Requirements management,
– Project management
– .....
• ...any number of tasks of
– Innovative Thinking
– Brainstorming
– Workshops
https://www.innovationgames.com/the-innovation-games/
36. Speed Boat
Identify What Customers Don’t Like About Your Product or Service
• Draw a boat on a whiteboard or sheet of butcher paper
• You’d like the boat to really move fast
• Unfortunately, the boat has a few anchors holding it back
• The boat is your system, and the features that your
customers don’t like are its anchors
• Customers write what they don’t like on an anchor
• They can also estimate how much faster the boat would
go when that anchor was cut
• Estimates of speed are really estimates of pain
https://www.innovationgames.com/the-innovation-games/
38. Spider Web
Understand Product Relationships
• Put the name of your product or service in the center of
a circle
• Ask your customers to draw other products and services,
ask them to tell you when, how, and why these are used
• Ask them to draw lines between the different products
and services
• As your customers reviews when and where they user
your offering, you can capture the various
interrelationships that exist between the different
products and service that they use throughout the day
https://www.innovationgames.com/the-innovation-games/
40. Me and My Shadow
Identify Your Customers’ Hidden Needs
• Shadow your customer while they use your product
or service. Literally.
• Sit next to them and watch what they do
• Periodically ask them
– “Why are you doing that?”
– “What are you thinking?”
• Take along a camera or camcorder and record key
activities
• Ask for copies of important artifacts created or used
by your customer while they are doing the work
https://www.innovationgames.com/the-innovation-games/
41. Show and Tell
Identify the Most Important Artifacts Created by Your Product
• Ask your customers to bring examples of artifacts
created or modified by your product or service
• Ask them to tell you why these artifacts are
important, and when and how they’re used
• Pay careful attention to anything that surprises
you – artifacts you expected them to create or
modify that they have ignored, artifacts that
aren’t used, or artifacts used in unexpected ways.
https://www.innovationgames.com/the-innovation-games/
42. The Apprentice
Create Empathy for the Customer Experience
• Ask your engineers and product developers to perform
the “work” of the system that they are building
• If they’re building a new data entry system, have them
do the work of the current data entry operators
• If they’re building workflow management software for
furniture delivery people, have them deliver furniture
• If they’re building a system to analyze vehicle
performance data, ask them to change the oil in the car
• They gain knowledge of the customer experience and
some degree of empathy for the real problem that your
customer is trying to solve
https://www.innovationgames.com/the-innovation-games/
43. Remember the Future
Understand Your Customers’ Definition of Success
• Hand each of your customers a few pieces of paper
• Ask them to imagine that it is sometime in the
future and that they’ve been using your product
almost continuously between now and that future
date (month, year, whatever)
• Then ask them to write down exactly what your
product will have done to make them happy or
successful or rich or safe or secure or art – choose
what works best for your product
• Key point – ask
– “What will the system have done?”
– not “What should the system do?”
https://www.innovationgames.com/the-innovation-games/
45. Give Them a Hot Tub
Use Outrageous Features to Discover Hidden Breakthroughs
• Write several features on note cards, one feature per
card
• Include several completely outrageous features
• If you’re making a portable MP3 player, try adding
features like “heats coffee”, “cracks concrete” or
“conditions dog hair”
• If you’re making a system that manages payroll, try
adding features like “plans family reunions” or
“refinishes wooden floors”
• Observe what happens with a customer uncovers one
of these outrageous features
https://www.innovationgames.com/the-innovation-games/
46. Product Box
Identify the Most Exciting Product Features
• Ask your customers to imagine that they’re
selling your product at a tradeshow, retail
outlet, or public market
• Give them a few cardboard boxes and ask them
to literally design a product box that they
would buy
• The box should have the key marketing slogans
that they find interesting
• When finished, pretend that you’re a skeptical
prospect and ask your customer to use their
box to sell your product to you
https://www.innovationgames.com/the-innovation-games/
48. Prune the Product Tree
Shape Your Product to Market Needs
• Start by drawing a very large tree on a whiteboard
• Thick limbs represent major areas of functionality within your
system
• The edge of the tree – its outermost branches – represent the
features available in the current release
• Write potential new features on several index cards, ideally
shaped as leaves
• Ask your customers to place desired features around the tree
• Observe how the tree gets structured
– Does one branch get the bulk of the growth?
– Does an underutilized aspect become stronger?
https://www.innovationgames.com/the-innovation-games/
49. Prune the Product Tree
In Action
https://www.innovationgames.com/the-innovation-games/
51. 20/20 Vision
Understand Customer Priorities
• When you’re getting fitted for glasses, your
optometrist will often ask you to compare between
two potential lenses by alternately showing each of
them
• Start by writing one feature each on large index
cards
• Shuffle the pile and put them face down
• Take the first one form the top and put it on the wall
• Take the next one and ask your customers if it is
more or less important than the one on the wall
• Place it above or below, depending on its relative
importance
• Repeat this with all of your feature cards
https://www.innovationgames.com/the-innovation-games/
52. Buy a Feature
Prioritize Features
• Create a list of features with an estimated cost
• The cost can be development effort or actual
cost you intend to charge for the feature
• Customers buy features that they want
• Features are priced high enough that no singe
customer can buy the features
• This helps motivate customers to negotiate
between themselves as to which features are
most important
• Observation of this negotiation provides great
insight into what customers are willing to pay
for
https://www.innovationgames.com/the-innovation-games/
53. Buy a Feature
In Action
https://www.slideshare.net/21apps/innovation-games-knowing-whats-important
54. Buy a Feature
In Action
https://www.innovationgames.com/buy-a-feature/
55. Start Your Day
Understand When and How Your Customer Uses Your Product
• Ask your customer to describe the daily, weekly,
monthly, and yearly events that are related to their
use of your product on pre-printed, poster sized
calendars or a simple timeline on poster paper
• Ask them to describe events in time frames
appropriate for your project
• Special event that are unique to an industry or
sector (like a conference), or days in which
everything goes horribly wrong and they’re looking
for help
• While they’re doing this, be alert for how your
product helps – or hinders – their day
56. Start Your Day
In Action
https://www.pinterest.com/pin/269301252692070089/ https://www.slideshare.net/jeffbrantley/brantley-innovation-gamespcamp2010done