The document provides guidance for lean product development. It recommends:
1. Validating business ideas through customer development and getting feedback to turn ideas into a series of testable hypotheses rather than guesses.
2. Building software faster using techniques like acceptance test-driven development (ATDD) and just-in-time architecture to minimize waste and inventory in the development process.
3. Measuring key metrics to understand customer needs and prioritize features, determine when requirements are met, and track progress over time.
Maneuver Warfare and Other Badass Habits of a Lean Product Developer Marko Taipale
This document discusses how to become a lean product developer by adopting habits that focus on efficiency and continuous learning. It recommends "leaning" business ideas through customer validation, building solutions faster or not at all using just-in-time implementation, and continuously measuring what matters to optimize the system and throw away waste. The document emphasizes learning by getting customer feedback, formulating hypotheses to test, using A3 problem solving templates, and shipping solutions frequently to learn from real-world use. The overall message is that respecting people, understanding purpose, improving continuously, and engaging customers are key habits of lean product development.
This document describes several case studies involving companies transitioning to more agile ways of working.
The first case study involves an international gaming company that was trying to speed up product development. Mapping their entire value stream and showing areas of waste and delay helped them transition to Scrum and reduce their time-to-market from 24 months to 3 months.
The second case study involves a software product company that was just starting to adopt Scrum. Mapping out their current roles and processes revealed a lack of clear responsibilities that was causing confusion and delays. Introducing a Chief Product Owner role helped clarify responsibilities and align the various teams.
The third case study involves a company that was developing a new way of working to
How to use agile for roadmapping and be successful at itAnupam Kundu
The document discusses how agile practices can help product owners successfully manage product roadmaps. It defines the role of a product owner and explains how agile planning, such as identifying and prioritizing features, allows product owners to better align products with business goals and stakeholder needs. The document also shares examples of how agile roadmapping helped one company increase productivity and delivery of new products.
The document provides an overview of agile software development practices compared to traditional waterfall approaches. It summarizes the author's experience transitioning from waterfall to agile development and embracing eXtreme Programming (XP) practices like test-driven development, pair programming, and continuous integration. The author then integrated XP with Scrum, the most popular agile framework. The document compares different agile methodologies and emphasizes that agile is about values and principles over prescriptive rules.
This document provides advice for new product owners on their role and responsibilities in Scrum. It discusses establishing a clear product vision through collaboration. An effective vision should describe the target customer and value proposition in a concise, memorable way. It also covers principles for effective story writing like defining requirements of ready and focusing on user experience. Release planning techniques like story mapping and calculating team velocity are presented. The document emphasizes that an empowered, dedicated product owner with a strong vision is key to achieving great results with Scrum.
Customer Development - What Strategic Planning can learn from StartupsLHBS
This is an interactive presentation that Stefan Erschwendner, Managing Director of LHBS gave for the Account Planning Group Germany at the Google Office in Berlin on the 29th of February 2013. Certain parts of the presentation are blank since they got build up during the presentation.
The document presents a 10 step model for agile requirements that includes defining the objective, stakeholders, vision, roles, personas, user stories, acceptance tests, development, delivery, and checking the delivered value. It argues that there is more to requirements than just user stories and that projects should either take a "salami slice" or goal-directed agile approach. The model is intended to provide insights and ideas for linking together all aspects of agile requirements.
How to be a successful agile product managerAnupam Kundu
This document discusses the role and responsibilities of a product manager in an agile environment. It outlines that a product manager must constantly gather feedback from customers, prioritize requirements, and work closely with development teams to deliver value through iterative releases. The document also highlights common challenges product managers face, such as unclear influence, unempowered teams, lack of business model validation, and organizational culture clashes. Overall, the document provides an overview of an agile product manager's duties and some issues they may encounter.
Maneuver Warfare and Other Badass Habits of a Lean Product Developer Marko Taipale
This document discusses how to become a lean product developer by adopting habits that focus on efficiency and continuous learning. It recommends "leaning" business ideas through customer validation, building solutions faster or not at all using just-in-time implementation, and continuously measuring what matters to optimize the system and throw away waste. The document emphasizes learning by getting customer feedback, formulating hypotheses to test, using A3 problem solving templates, and shipping solutions frequently to learn from real-world use. The overall message is that respecting people, understanding purpose, improving continuously, and engaging customers are key habits of lean product development.
This document describes several case studies involving companies transitioning to more agile ways of working.
The first case study involves an international gaming company that was trying to speed up product development. Mapping their entire value stream and showing areas of waste and delay helped them transition to Scrum and reduce their time-to-market from 24 months to 3 months.
The second case study involves a software product company that was just starting to adopt Scrum. Mapping out their current roles and processes revealed a lack of clear responsibilities that was causing confusion and delays. Introducing a Chief Product Owner role helped clarify responsibilities and align the various teams.
The third case study involves a company that was developing a new way of working to
How to use agile for roadmapping and be successful at itAnupam Kundu
The document discusses how agile practices can help product owners successfully manage product roadmaps. It defines the role of a product owner and explains how agile planning, such as identifying and prioritizing features, allows product owners to better align products with business goals and stakeholder needs. The document also shares examples of how agile roadmapping helped one company increase productivity and delivery of new products.
The document provides an overview of agile software development practices compared to traditional waterfall approaches. It summarizes the author's experience transitioning from waterfall to agile development and embracing eXtreme Programming (XP) practices like test-driven development, pair programming, and continuous integration. The author then integrated XP with Scrum, the most popular agile framework. The document compares different agile methodologies and emphasizes that agile is about values and principles over prescriptive rules.
This document provides advice for new product owners on their role and responsibilities in Scrum. It discusses establishing a clear product vision through collaboration. An effective vision should describe the target customer and value proposition in a concise, memorable way. It also covers principles for effective story writing like defining requirements of ready and focusing on user experience. Release planning techniques like story mapping and calculating team velocity are presented. The document emphasizes that an empowered, dedicated product owner with a strong vision is key to achieving great results with Scrum.
Customer Development - What Strategic Planning can learn from StartupsLHBS
This is an interactive presentation that Stefan Erschwendner, Managing Director of LHBS gave for the Account Planning Group Germany at the Google Office in Berlin on the 29th of February 2013. Certain parts of the presentation are blank since they got build up during the presentation.
The document presents a 10 step model for agile requirements that includes defining the objective, stakeholders, vision, roles, personas, user stories, acceptance tests, development, delivery, and checking the delivered value. It argues that there is more to requirements than just user stories and that projects should either take a "salami slice" or goal-directed agile approach. The model is intended to provide insights and ideas for linking together all aspects of agile requirements.
How to be a successful agile product managerAnupam Kundu
This document discusses the role and responsibilities of a product manager in an agile environment. It outlines that a product manager must constantly gather feedback from customers, prioritize requirements, and work closely with development teams to deliver value through iterative releases. The document also highlights common challenges product managers face, such as unclear influence, unempowered teams, lack of business model validation, and organizational culture clashes. Overall, the document provides an overview of an agile product manager's duties and some issues they may encounter.
The Essential Product Owner - Partnering with the teamCprime
Bob Galen shares real-world stories where he’s seen “effectively partnered” teams and Product Owners truly deliver balanced value for their business stakeholders. In this session he’ll show you how story mapping and release planning can truly set the stage for effective team workflow—establishing a “Big Picture” for everyone to shoot for. How establishing shared goals, both at the iteration and release levels, truly cements the partnership between team and Product Owner. And finally, how setting a tempo of regular, focused backlog grooming sessions establishes a mechanism for the team and Product Owner to explore well-nuanced and high value backlogs.
Product Management 101: Techniques for SuccessMatterport
This is a snapshot from a living document. To see the current document, please go to https://goo.gl/yFFrml.
Topics covered include:
- Resources
- General Overview
- The Role of Product Management
- Characteristics of Great Project and Product Managers
- Problem Space and Solution Space
- Customer Personas
- User Stories
- Product Documentation
- Agile Product Development
- Succeeding with Agile from The Lean Playbook
- Analytics, Customer Engagement, & Monetization
- Pricing Strategies
- Overall Leadership and Organizational Development
- Final Guidelines and Recommendations
The document provides information on the role of a product owner, including organizing work into user stories and prioritizing stories. It discusses that a product owner understands customers, is empowered to make decisions, and acts as the final voice. They define the product vision and backlog, prioritize features, and ensure delivery of business value. Effective product owners attend ceremonies like planning and retrospectives. The document also covers how to write user stories and acceptance criteria, and methods for prioritizing stories like value vs complexity.
This document discusses what being the first QA engineer at a company means. It explains that being the first means there was no dedicated QA engineer previously. The author recommends becoming the first QA engineer for reasons like having autonomy, social impact, and potential stock options. Key responsibilities for a first QA engineer are outlined, such as auditing test cases and defects, understanding release cycles, and determining when a second QA engineer is needed. Common misconceptions addressed are that being the first does not mean the very first to do QA, and that other engineers likely have QA experience too.
This document discusses strategies for using technology to drive growth and profitability for professional contractors. It begins with an introduction to Sage, a business management software company, and the key industries they serve. It then discusses how economic downturns can impact contractors' revenue, costs, competition and customers. The document proposes that technology can improve business performance in areas like operations, people, money, marketing, sales, customers, leadership and management. It provides examples of how technologies like mobility, paperless processes and business development tools can help contractors adapt to challenges. It concludes by emphasizing the need to actually implement and use technologies in order to realize their full potential return on investment.
Clorox decided to pursue open innovation in 2000 to lead in innovation as competitors grew larger. This required changing its culture from internally-focused to open to external ideas. Key changes included overhauling innovation processes and systems to source ideas externally and form strategic supplier partnerships. As a case study, Clorox's disinfecting wipes were developed through open innovation by partnering with a supplier to obtain nonwoven technology enabling a package that encouraged consumer reuse. Open innovation impacted Clorox's product development across technical, consumer and business considerations and required new collaboration skills and ways of working.
Agile product owners-what ails them (philly_dayofagile)Anupam Kundu
Presentation I used at Philadelphia Day of Agile (#dayofagile) http://dayofagile.org/agenda.
It was received well within the audience. Any comments are welcome...
Power Up - Your Influence on Non-Design DeliverablesPeter Boersma
Presentation at IxDA Hamburg networking event on Monday, September 26, 2011.
The presentation aims to make UX people aware that they can and should influence non-design deliverables.
This document discusses customer development and its importance for startups. It argues that product development alone is not enough and that startups need a parallel process focused on customer development from the beginning. This includes discovering customers, validating problems and solutions, creating customers, and building a company around them. Customer development should be iterative and focus on learning rather than linear execution. It is as important as product development for startup success.
With an increasing number of organizations adopting Agile practices and the majority of them following SCRUM, Agile has gained mainstream recognition in the past couple of years. Today organizations are seeing the value in Agile ceremonies and have brought in the roles and practices that are instrumental in the success of SCRUM.
The Agile workshop has several benefits such as helping you understand the SCRUM process, providing the ability to prune product backlog, conduct release planning ceremony and much more.
This document provides an overview and agenda for a Lean Startup workshop. It discusses key concepts like customer development, agile development, validated learning, and build-measure-learn cycles. The Lean Startup methodology aims to shorten the feedback loop between new products or features and customer feedback through iterative development and experimentation.
This document discusses factors important for competitiveness, including reducing lead times. It defines various lead times and emphasizes reducing non-value added time to improve responsiveness to customers. The document also covers 5S standards, waste elimination, and continuous improvement principles like standardizing work and ongoing inspection.
The document discusses the process of transforming a business idea into a company through a "learning startup". It describes a learning startup as an organization that runs explicit learning processes to test hypotheses and refine its business model by solving technology and customer risks. The key steps involve building an initial business model, testing it through product development and customer validation, then building systems to implement the validated business model and transition to an ongoing company.
Product Management 2.0 focuses on continuous learning and innovation to deliver maximum customer value. It involves:
1) Understanding customer needs through observation and empathy, not just requirements gathering.
2) Developing products iteratively based on customer insights rather than laundry lists of features.
3) Ensuring the development team stays focused on the essential by saying "no" to unnecessary features and technical debt.
The document discusses conducting customer interviews as part of new product roadmapping. It provides details on the customer interview process, including who should conduct the interviews, interview skills, who to interview, and the structure of the interviews. The interviews involve surveying customers on the importance and satisfaction of various product attributes. This information is then used to identify opportunities for new product development and guide the roadmapping process. Examples are provided of how customer insights have been used at other companies to successfully develop new products that meet customer needs.
The Essential Product Owner - Partnering with the teamCprime
Bob Galen shares real-world stories where he’s seen “effectively partnered” teams and Product Owners truly deliver balanced value for their business stakeholders. In this session he’ll show you how story mapping and release planning can truly set the stage for effective team workflow—establishing a “Big Picture” for everyone to shoot for. How establishing shared goals, both at the iteration and release levels, truly cements the partnership between team and Product Owner. And finally, how setting a tempo of regular, focused backlog grooming sessions establishes a mechanism for the team and Product Owner to explore well-nuanced and high value backlogs.
Product Management 101: Techniques for SuccessMatterport
This is a snapshot from a living document. To see the current document, please go to https://goo.gl/yFFrml.
Topics covered include:
- Resources
- General Overview
- The Role of Product Management
- Characteristics of Great Project and Product Managers
- Problem Space and Solution Space
- Customer Personas
- User Stories
- Product Documentation
- Agile Product Development
- Succeeding with Agile from The Lean Playbook
- Analytics, Customer Engagement, & Monetization
- Pricing Strategies
- Overall Leadership and Organizational Development
- Final Guidelines and Recommendations
The document provides information on the role of a product owner, including organizing work into user stories and prioritizing stories. It discusses that a product owner understands customers, is empowered to make decisions, and acts as the final voice. They define the product vision and backlog, prioritize features, and ensure delivery of business value. Effective product owners attend ceremonies like planning and retrospectives. The document also covers how to write user stories and acceptance criteria, and methods for prioritizing stories like value vs complexity.
This document discusses what being the first QA engineer at a company means. It explains that being the first means there was no dedicated QA engineer previously. The author recommends becoming the first QA engineer for reasons like having autonomy, social impact, and potential stock options. Key responsibilities for a first QA engineer are outlined, such as auditing test cases and defects, understanding release cycles, and determining when a second QA engineer is needed. Common misconceptions addressed are that being the first does not mean the very first to do QA, and that other engineers likely have QA experience too.
This document discusses strategies for using technology to drive growth and profitability for professional contractors. It begins with an introduction to Sage, a business management software company, and the key industries they serve. It then discusses how economic downturns can impact contractors' revenue, costs, competition and customers. The document proposes that technology can improve business performance in areas like operations, people, money, marketing, sales, customers, leadership and management. It provides examples of how technologies like mobility, paperless processes and business development tools can help contractors adapt to challenges. It concludes by emphasizing the need to actually implement and use technologies in order to realize their full potential return on investment.
Clorox decided to pursue open innovation in 2000 to lead in innovation as competitors grew larger. This required changing its culture from internally-focused to open to external ideas. Key changes included overhauling innovation processes and systems to source ideas externally and form strategic supplier partnerships. As a case study, Clorox's disinfecting wipes were developed through open innovation by partnering with a supplier to obtain nonwoven technology enabling a package that encouraged consumer reuse. Open innovation impacted Clorox's product development across technical, consumer and business considerations and required new collaboration skills and ways of working.
Agile product owners-what ails them (philly_dayofagile)Anupam Kundu
Presentation I used at Philadelphia Day of Agile (#dayofagile) http://dayofagile.org/agenda.
It was received well within the audience. Any comments are welcome...
Power Up - Your Influence on Non-Design DeliverablesPeter Boersma
Presentation at IxDA Hamburg networking event on Monday, September 26, 2011.
The presentation aims to make UX people aware that they can and should influence non-design deliverables.
This document discusses customer development and its importance for startups. It argues that product development alone is not enough and that startups need a parallel process focused on customer development from the beginning. This includes discovering customers, validating problems and solutions, creating customers, and building a company around them. Customer development should be iterative and focus on learning rather than linear execution. It is as important as product development for startup success.
With an increasing number of organizations adopting Agile practices and the majority of them following SCRUM, Agile has gained mainstream recognition in the past couple of years. Today organizations are seeing the value in Agile ceremonies and have brought in the roles and practices that are instrumental in the success of SCRUM.
The Agile workshop has several benefits such as helping you understand the SCRUM process, providing the ability to prune product backlog, conduct release planning ceremony and much more.
This document provides an overview and agenda for a Lean Startup workshop. It discusses key concepts like customer development, agile development, validated learning, and build-measure-learn cycles. The Lean Startup methodology aims to shorten the feedback loop between new products or features and customer feedback through iterative development and experimentation.
This document discusses factors important for competitiveness, including reducing lead times. It defines various lead times and emphasizes reducing non-value added time to improve responsiveness to customers. The document also covers 5S standards, waste elimination, and continuous improvement principles like standardizing work and ongoing inspection.
The document discusses the process of transforming a business idea into a company through a "learning startup". It describes a learning startup as an organization that runs explicit learning processes to test hypotheses and refine its business model by solving technology and customer risks. The key steps involve building an initial business model, testing it through product development and customer validation, then building systems to implement the validated business model and transition to an ongoing company.
Product Management 2.0 focuses on continuous learning and innovation to deliver maximum customer value. It involves:
1) Understanding customer needs through observation and empathy, not just requirements gathering.
2) Developing products iteratively based on customer insights rather than laundry lists of features.
3) Ensuring the development team stays focused on the essential by saying "no" to unnecessary features and technical debt.
The document discusses conducting customer interviews as part of new product roadmapping. It provides details on the customer interview process, including who should conduct the interviews, interview skills, who to interview, and the structure of the interviews. The interviews involve surveying customers on the importance and satisfaction of various product attributes. This information is then used to identify opportunities for new product development and guide the roadmapping process. Examples are provided of how customer insights have been used at other companies to successfully develop new products that meet customer needs.
The document discusses type-driven development in Scala. It covers various techniques for preventing bugs using static types, including value classes, Option types, dependent types, the IO monad, and validation. Advanced concepts from libraries like Scalaz and Shapeless are also mentioned, such as path dependent types, sized types, and using numbers as types. While static types add complexity, the document argues they can help catch bugs earlier by allowing compilers to validate code correctness.
The document discusses several technology trends for 2015, including reactive web development using Meteor, adopting an API-first approach and microservices architecture, implementing continuous delivery practices like releasing software updates almost everyday, using Docker to standardize infrastructure management, and applying lean startup principles like building, measuring, learning, and pivoting products.
The document discusses different approaches to agile software development including Scrum, Kanban, Extreme Programming (XP), Lean Startups, and Design Driven Development (D3). It explains that agile is a philosophy focused on individuals, collaboration, adaptability to change, and delivering working software frequently. Specific agile methods then apply this philosophy through practices like test-driven development, daily standups, limiting work in progress, and continuous delivery.
Creative Branching Models for Multiple Release StreamsAtlassian
Nuance Communications is making the move from SVN to Git! Why? To take advantage of its strong branching and merging capabilities... and to keep their developers happy. With wild variations between each product's release model, they have multiple releases of one or more components in play at a given time. So they had to get creative with a branching model. This talk will discuss choosing the right Git branching model for each of your release streams, and managing multiple releases using Bitbucket (including Stash), JIRA, Bamboo, and Maven.
This document summarizes a novel LC-MS/MS method developed at Cleveland Clinic to simultaneously quantify 20 drugs and metabolites in urine, monitoring use of 16 prescription and illicit drugs. Sample preparation involves enzymatic hydrolysis followed by online turbulent flow extraction. The method has been validated and successfully used to analyze over 85,000 samples from pain management clinics over six years. It provides benefits over previous methods by simultaneously measuring a large panel of drugs in one run with improved sensitivity, accuracy and reproducibility.
El documento habla sobre las sociedades colectivas. Explica que son sociedades conformadas por personas y que la razón social puede incluir uno o varios de los socios. También describe los casos en los que un socio puede ser excluido de la sociedad, como si no paga su aporte o compite con la sociedad. Además, señala que la administración de la sociedad requiere el concurso de todos los socios gestores y no puede ser transmitida a los herederos de un gestor fallecido.
Transavia.com is a Dutch low-cost airline and subsidiary of Air France-KLM. It operates out of bases at Amsterdam Airport Schiphol, Rotterdam The Hague Airport, and Eindhoven Airport. Transavia.com flies scheduled and charter routes to holiday destinations using a fleet of Boeing 737 aircraft. The airline's headquarters are located at Schiphol Airport in the Netherlands.
Supporting SMEs and the inclusive agribusiness innovation system in Southeast...Food_Systems_Innovation
This document discusses failures in Southeast Asian agribusiness systems and opportunities to catalyze sustainable change. It notes key findings from research on inclusive agribusiness and impact investing in the region. The document examines innovation in small and medium enterprises (SMEs), the role of impact investment, and potential solutions to system failures. It explores what solutions could look like, such as an innovation facility that provides investment, analysis, communication/networking, learning, and other support functions. Any facility would need to address both individual market failures and larger system failures through short and long-term strategies.
Roberta Carson, creator of ZaggoCare Systems, and Christy S Harris, PharmD, BCPS, BCOP of Dana-Farber Cancer Institute discuss tips for cancer patients to manage the multiple medications they may be taking.
Whitlow Elementary School is a school in Cumming, Georgia that is nearing capacity. The document evaluates the school's reference collection, which includes print and online resources, and finds that while substantial for a new school, the print collection could use updating as many items are outdated or missing pieces. A plan is proposed to purchase new reference materials using funds from the school budget and a book fair to improve the reference skills of the students.
Market Research & The Psychotherapeutic ApproachIpsos
This document discusses how psychotherapeutic approaches can help marketers better understand consumer motivations and relationships with brands. It presents a model mapping a consumer's relationship with a brand and product category from the perspectives of being a child, adult, and parent. Understanding these relationships through transactional analysis and other psychotherapeutic lenses can provide insights for brand strategy, such as new product launches. The document argues that psychotherapy reveals the depth of consumer-brand connections and what drives consumers to embrace or reject brand messages.
Huancayo no se considera actualmente una ciudad sostenible debido a que no mantiene un equilibrio entre los factores económico, social y medioambiental. Si bien cuenta con algunas edificaciones que cumplen con principios de arquitectura sustentable, como el uso de materiales locales y energías renovables, muchas otras presentan problemas como un alto consumo energético y filtraciones en el sistema de agua que generan altos costos. Para lograr la sostenibilidad, Huancayo debe optimizar el uso de recursos y espacios en las edificaciones
My books- Learning to Go https://gum.co/learn2go & The 30 Goals Challenge for Teachers http://amazon.com/The-Goals-Challenge-Teachers-Transform/dp/0415735343
Resources at http://shellyterrell.com/playgrounds
Presentation for Sydney Project Managers' Meetup. Compare and contrast between Lean Startup and tradiitonal project management in a product development context.
Project Management vs Account ManagementRich Whalen
Difference between Project Management and Account Management in professional services organization. Geared more towards marketing and advertising, this model will show the differences in roles and when it makes sense to separate.
This document provides an overview of how to build a successful startup using business model innovation. It discusses identifying customer problems, developing solutions, and validating ideas through customer interviews and testing. Key steps include identifying the problem or need, taking a first stab at the solution, building a minimum viable product to test, and iterating based on customer feedback to find product-market fit. The document emphasizes that successful entrepreneurs discover problems through observation and experimentation rather than beginning with fully formed ideas.
The document outlines an agenda for a SWOT analysis meeting estimated to take 3 hours. The agenda includes an overview of SWOT, findings from the analysis, potential solutions, developing a roadmap, scoring solutions, revisiting the roadmap, and discussing next steps. Major topics to be analyzed include sales, corporate culture, products/services, communications, and project management. Potential solutions are grouped into categories like development, sales, corporate improvements, products, services, and support.
Building Winning Business, the Human-Centered wayLamin Mansaray
Business problems come in all shapes and sizes, the complexity of those issues are only growing. Human Centered Design (Design Thinking) is the best-kept problem-solving approach to adaptive challenges.
This document outlines an 11-step process for developing an app using design thinking principles. It discusses defining the problem, envisioning potential solutions, refining options through prototyping and user testing, and ultimately selecting a final solution. The key steps involve understanding the current reality, brainstorming what could be through concepts and business models, testing ideas through pretypes and experiments, and iterating based on feedback to identify the best option to implement. Design thinking is presented as a human-centered approach to problem-solving that generates innovative solutions through empirical means.
The document introduces building a data science platform in the cloud using Amazon Web Services and open source technologies. It discusses motivations for using a cloud-based approach for flexibility and cost effectiveness. The key building blocks are described as Amazon EC2 for infrastructure, Vertica for fast data storage and querying, and RStudio Server for analytical capabilities. Step-by-step instructions are provided to set up these components, including launching an EC2 instance, attaching an EBS volume for storage, installing Vertica and RStudio Server, and configuring connectivity between components. The platform allows for experimenting and iterating quickly on data analysis projects in the cloud.
This session provides glimpse and overview into the tools and techniques of strategic consulting. This presentation covers the latest strategic consulting methods and tools adopted successfully by the global consulting giants like: McKinsey, PWC, BCG and others. This presentation will also map those successful strategic consulting methods and tools enterprise level software development.
The document provides information about StartupWeekend events taking place in Slovakia, including dates and locations. It outlines the schedule for the first day (Friday) which includes an intro, idea pitching and voting, and team forming. Other sections provide overviews of what a startup is, the weekend roadmap, judging criteria, and introductions of mentors, speakers and the jury. The document encourages participation and sharing of ideas, and concludes by thanking local sponsors.
Presentation slides and background material for customer development kick-off session at Aalto Summer of Startups 2012 program on June 11th, 2012. Presentors and coaches: Juha Mattsson of Symbioosi and Heikki Leskelä of Bluebiiit
5 Things Product Managers Should Stop DoingJeremy Horn
Slides Jordan Bergtraum recently used in his discussion w/ mentees of The Product Mentor.
Synopsis: A successful Product Manager needs to be good at knowing which activities NOT to take on just as much as which activities they should. The PM role is broad enough to drown a whale, don't add more dead weight to your already difficult job and sink. You will learn 5 activities that you are likely doing on a weekly basis that you should STOP doing immediately.
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
This presentation from the Smart Insights Webcast series explains how to structure a marketing plan using the SOSTAC(R) planning framework created by PR Smith (see www.prsmith.org for more).
Growth Marketing Conference '17 Atlanta - Creating a Company Wide Growth CultureThibault Imbert
This document provides 11 tips for creating a company-wide growth culture from Adobe Spark's Head of Growth. The tips are: 1) start with organic retention and product-market fit; 2) start small with early wins; 3) get executive sponsorship for a long-term growth strategy; 4) hire people with the right mindset over skills; 5) test value through third parties before building features; 6) differentiate your efforts from competitors; 7) form a growth squad of cross-functional engineers and PMs; 8) look for activation opportunities from data; 9) combine quantitative and qualitative research; 10) establish an experiment pipeline process; and 11) evangelize your growth team and process.
Quant + Qual + Iteration for Great ProductsBen Carey
This document discusses the importance of combining quantitative, qualitative, and iterative methods for product development. It argues that quantitative data tells you what problems exist, qualitative research reveals why those problems exist, and iteration allows you to fix them. The document provides examples of quantitative metrics like retention, activation, and sentiment analysis that can be tracked. It also emphasizes the importance of qualitative methods like design thinking, observation, and human-centered design to understand user needs at a deeper level. The overall message is that using both quantitative and qualitative approaches together in an iterative process leads to better product outcomes.
Content marketing For Marketing Automation DemandGen
Trying to connect the dots between Content Marketing and Marketing Automation? Join DemandGen for another exploration of B2B Marketing Automation best practice. This webcast will be looking at the relationship between Content Marketing and Marketing Automation. We’ve put together another panel of smart b2b practitioners. This month’s insights are provided by Doug Kessler of Velocity Partners, author of The B2B Content Marketing Workbook and Bob Apollo, founder of Inflexion-Point, B2B Sales and Marketing Performance Improvement specialists.
We’ll be taking a closer look at the relationship between Marketing Automation and Content Marketing:
- Rules of thought leadership
- Aligning content to the buying cycle
- Best practices: Building an integrated content marketing strategy with Marketing Automation tools
- B2B content marketing examples and successes
- Measuring the results
This document discusses enterprise business analysis. It provides an input-task-output diagram for enterprise analysis. It explores defining business needs, capability gaps, solution approaches, and business cases. It compares enterprise business analysis to business design, architecture, and transformation. It notes the challenges of working at an enterprise scale with unknown problems and solutions. Finally, it provides tips for growing as an enterprise business analyst, including strategic thinking, understanding different perspectives, building skills, and having the courage to try new approaches.
The document discusses 5 common issues with sales training and recommended solutions:
1) Sales training apathy - lack of buy-in from salespeople and executives. Solutions include leadership support and change management.
2) Wrong sales training mix - not aligning training to sales process and buyer needs. Solutions include focusing on skills and coaching.
3) Lack of sales development system - reactive approach not addressing skills gaps. Solutions include competency-based learning programs.
4) Poor measurement techniques - not tracking outcomes of training and coaching. Solutions include measuring outputs and behavior change.
5) The wrong content - one-size-fits-all approach. Solutions include customizing based on needs and understanding organizational maturity.
Similar to How to be a Lean Product Developer? @Agile Riga Day 2012 (20)
Mashing up customers, users, product and businessMarko Taipale
The document discusses customer and product development using an agile approach. It emphasizes starting with the customer to identify problems, then developing minimum viable products to validate solutions fit the problems. Each step involves validation, whether validating the customer has a problem, the solution fits the problem, or there is a market for the product. Tools like lean canvases and validation boards help share understanding and co-create. The process is iterative, refining the product based on frequent customer feedback to maximize learning.
How do we use lean startup in service developmentMarko Taipale
The document discusses using Lean Startup methodology in service development. It explains that there are three levels of knowing: build-measure-learn. Lean Startup involves developing both the business model and customers through experiments and validation. All projects start with concepts which are developed into business models and hypotheses to be tested. Customer development focuses on problem-solution fit through experiments conducted outside the office with customers. The key is to iterate based on lessons learned from validating assumptions and hypotheses.
Osaaminen uuden yrityksen johtajan näkökulmastaMarko Taipale
Esitys johtamisen osaamisesta. Esitetty 28.5.2013 Johtamisen kehittämisverkoston johtoryhmän työseminaarissa (Johtamisverkosto ja Sosiaali- ja Terveysministeriö)
Marko Taipale shares stories from coaching companies through agile adoption challenges. The first story describes helping a subcontractor deliver a project on time by analyzing 600 use cases and improving delivery from 100 to 25 months. The second story addresses misaligned goals between development and sales causing performance issues. The third story shows improving a gaming company's time to market from 24 to 3 months by optimizing the whole product development system rather than just individual teams. Lessons focus on analyzing systems holistically and aligning incentives rather than blaming individuals.
Product Owners, Santa and other GoblinsMarko Taipale
The document discusses the role of a product owner (PO) and proposes an alternative approach. It suggests that rather than having a single PO, an organization should take a system-centric view and:
1) Create a customer development team to understand customer value and validate what to build.
2) Connect this team to the development team to understand costs.
3) Ensure the customer development team consists of and meets with stakeholders to understand risks by studying the market and getting feedback from the development team.
4) This approach avoids bottlenecks and allows for more communication and innovation compared to relying only on a single PO role.
From a concept to viable business — How do we know if we are building the rig...Marko Taipale
This document discusses building the right product by focusing on problem/solution fit, business model/market fit, hypothesis/experiment fit, and user needs/service fit. It emphasizes the importance of validating your concepts by talking to customers and measuring results rather than assuming you know requirements. The key steps outlined are drawing a business model canvas, stating hypotheses to test, and getting customer feedback through discovery and validation. Pivoting based on learnings is important rather than prematurely scaling execution without verifying the business model. Overall the message is to interface business, design and engineering to create successful businesses by making the business the driver.
Provocation to the Product Owner challenge - Agile Coaching CircleMarko Taipale
The document discusses challenges with the Product Owner (PO) role in Scrum and Agile processes. It questions whether the single PO model is effective given the amount of information and responsibilities. It also questions what happens between understanding customer needs and generating the product vision and backlog. Additionally, it argues that Agile methods sometimes marginalize understanding the business and customer needs upstream of product development. The document advocates for more learning and direct customer interaction rather than relying solely on the PO as a single point of contact. It poses several questions about how organizations implement the PO role and manage product strategy.
The document describes an Agile consulting and coaching circle that meets monthly for 2.5 hours. Each gathering includes a 20 minute peer coaching session where one person receives feedback, a topic introduction and discussion, and a retrospective and backlog grooming. The circle is meant for sharing and learning in an open group format. Facilitator contact information is provided for questions, ideas or contributions.
This is the presentation I gave at LESS2010 on 18th of Oct in 2010. The deck describes how we do lean product development and customer development and what are the current results.
Lean Startup for AaltoES Summer of StartupsMarko Taipale
The document discusses lean startup principles and how they were applied at Nextdoor.fi. It describes how Nextdoor used short development cycles, frequent releases, customer feedback, and minimum viable products to build their service iteratively while minimizing unused features. They were able to develop and maintain the site with no testers or full-time developers through techniques like continuous delivery, daily backups and reporting, and keeping the product queue small.
1.Why do you want to be agile?
L1: Set a goal for being agile or you achieve nothing
L2: Commit to agile values and principles; your practices will follow
L3: Piloting is learning. Learning is progress.
2.How to reach business agility?
L4: Business agility is about having adaptability and predictability
L5: Create product vision and validate it with customer development
L6: Find your Minimum Viable Product
3.Organization as a people system
L7:Optimize the whole
L8: Build great teams
In this presentation I tell why selling agile without a goal is nonsense and why agile pilots fail so often from biz point of view. I presented these slides in Turku Agile Day 2010.
The APCO Geopolitical Radar - Q3 2024 The Global Operating Environment for Bu...APCO
The Radar reflects input from APCO’s teams located around the world. It distils a host of interconnected events and trends into insights to inform operational and strategic decisions. Issues covered in this edition include:
[To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations]
This PowerPoint compilation offers a comprehensive overview of 20 leading innovation management frameworks and methodologies, selected for their broad applicability across various industries and organizational contexts. These frameworks are valuable resources for a wide range of users, including business professionals, educators, and consultants.
Each framework is presented with visually engaging diagrams and templates, ensuring the content is both informative and appealing. While this compilation is thorough, please note that the slides are intended as supplementary resources and may not be sufficient for standalone instructional purposes.
This compilation is ideal for anyone looking to enhance their understanding of innovation management and drive meaningful change within their organization. Whether you aim to improve product development processes, enhance customer experiences, or drive digital transformation, these frameworks offer valuable insights and tools to help you achieve your goals.
INCLUDED FRAMEWORKS/MODELS:
1. Stanford’s Design Thinking
2. IDEO’s Human-Centered Design
3. Strategyzer’s Business Model Innovation
4. Lean Startup Methodology
5. Agile Innovation Framework
6. Doblin’s Ten Types of Innovation
7. McKinsey’s Three Horizons of Growth
8. Customer Journey Map
9. Christensen’s Disruptive Innovation Theory
10. Blue Ocean Strategy
11. Strategyn’s Jobs-To-Be-Done (JTBD) Framework with Job Map
12. Design Sprint Framework
13. The Double Diamond
14. Lean Six Sigma DMAIC
15. TRIZ Problem-Solving Framework
16. Edward de Bono’s Six Thinking Hats
17. Stage-Gate Model
18. Toyota’s Six Steps of Kaizen
19. Microsoft’s Digital Transformation Framework
20. Design for Six Sigma (DFSS)
To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations
Discover timeless style with the 2022 Vintage Roman Numerals Men's Ring. Crafted from premium stainless steel, this 6mm wide ring embodies elegance and durability. Perfect as a gift, it seamlessly blends classic Roman numeral detailing with modern sophistication, making it an ideal accessory for any occasion.
https://rb.gy/usj1a2
Starting a business is like embarking on an unpredictable adventure. It’s a journey filled with highs and lows, victories and defeats. But what if I told you that those setbacks and failures could be the very stepping stones that lead you to fortune? Let’s explore how resilience, adaptability, and strategic thinking can transform adversity into opportunity.
Anny Serafina Love - Letter of Recommendation by Kellen Harkins, MS.AnnySerafinaLove
This letter, written by Kellen Harkins, Course Director at Full Sail University, commends Anny Love's exemplary performance in the Video Sharing Platforms class. It highlights her dedication, willingness to challenge herself, and exceptional skills in production, editing, and marketing across various video platforms like YouTube, TikTok, and Instagram.
Best Competitive Marble Pricing in Dubai - ☎ 9928909666Stone Art Hub
Stone Art Hub offers the best competitive Marble Pricing in Dubai, ensuring affordability without compromising quality. With a wide range of exquisite marble options to choose from, you can enhance your spaces with elegance and sophistication. For inquiries or orders, contact us at ☎ 9928909666. Experience luxury at unbeatable prices.
Taurus Zodiac Sign: Unveiling the Traits, Dates, and Horoscope Insights of th...my Pandit
Dive into the steadfast world of the Taurus Zodiac Sign. Discover the grounded, stable, and logical nature of Taurus individuals, and explore their key personality traits, important dates, and horoscope insights. Learn how the determination and patience of the Taurus sign make them the rock-steady achievers and anchors of the zodiac.
Digital Marketing with a Focus on Sustainabilitysssourabhsharma
Digital Marketing best practices including influencer marketing, content creators, and omnichannel marketing for Sustainable Brands at the Sustainable Cosmetics Summit 2024 in New York
Call8328958814 satta matka Kalyan result satta guessing➑➌➋➑➒➎➑➑➊➍
Satta Matka Kalyan Main Mumbai Fastest Results
Satta Matka ❋ Sattamatka ❋ New Mumbai Ratan Satta Matka ❋ Fast Matka ❋ Milan Market ❋ Kalyan Matka Results ❋ Satta Game ❋ Matka Game ❋ Satta Matka ❋ Kalyan Satta Matka ❋ Mumbai Main ❋ Online Matka Results ❋ Satta Matka Tips ❋ Milan Chart ❋ Satta Matka Boss❋ New Star Day ❋ Satta King ❋ Live Satta Matka Results ❋ Satta Matka Company ❋ Indian Matka ❋ Satta Matka 143❋ Kalyan Night Matka..
Storytelling is an incredibly valuable tool to share data and information. To get the most impact from stories there are a number of key ingredients. These are based on science and human nature. Using these elements in a story you can deliver information impactfully, ensure action and drive change.
3 Simple Steps To Buy Verified Payoneer Account In 2024SEOSMMEARTH
Buy Verified Payoneer Account: Quick and Secure Way to Receive Payments
Buy Verified Payoneer Account With 100% secure documents, [ USA, UK, CA ]. Are you looking for a reliable and safe way to receive payments online? Then you need buy verified Payoneer account ! Payoneer is a global payment platform that allows businesses and individuals to send and receive money in over 200 countries.
If You Want To More Information just Contact Now:
Skype: SEOSMMEARTH
Telegram: @seosmmearth
Gmail: seosmmearth@gmail.com
SATTA MATKA SATTA FAST RESULT KALYAN TOP MATKA RESULT KALYAN SATTA MATKA FAST RESULT MILAN RATAN RAJDHANI MAIN BAZAR MATKA FAST TIPS RESULT MATKA CHART JODI CHART PANEL CHART FREE FIX GAME SATTAMATKA ! MATKA MOBI SATTA 143 spboss.in TOP NO1 RESULT FULL RATE MATKA ONLINE GAME PLAY BY APP SPBOSS
5. 1
We are wasting time and effort
on doing the wrong thing
Saturday, March 17, 12
6. Features used
16%
13% 20% valuable
19% Sometimes
Often
7% Always
Never
Rarely
45%
XP2002 CHAOS report
Saturday, March 17, 12
7. 2
53% of us don’t know what the
company is trying to achieve
TBWA North - Study on 2010
We do not see the purpose in our work
or
We do not know if the work we do has a purpose
Saturday, March 17, 12
10. Guide for a lean
product developer
1. "Lean" your business ideas IDEAS
2. Build faster (or not at all!)
LEARN BUILD
3. Measure it!
MEASURE
4. Learn Faster
Saturday, March 17, 12
11. 1. "Lean" your business ideas
2. Build faster (or not at all!)
3. Measure it!
4. Learn Faster
Saturday, March 17, 12
12. What is a ”business idea”?
Saturday, March 17, 12
13. What is a ”business idea”?
This guy is guessing...
It is just a “series of guesses”
Saturday, March 17, 12
19. Customer Development
Customer Customer Customer Company
Discovery Validation Creation Building
Problem / Product /
Solution Fit Market Fit Scale
Organization
Proposed Business Scale
MVP Model Execution
Scale
Operations
Sales &
Proposed Marketing
Funnels Roadmap
Saturday, March 17, 12
20. Customer Development
Customer Customer Customer Company
Discovery Validation Creation Building
Problem / Product /
Solution Fit Market Fit Scale
Get out of the building! Organization
Proposed Business Scale
MVP Model Execution
Scale
Operations
Sales &
Proposed Marketing
Funnels Roadmap
Saturday, March 17, 12
21. Customer Customer Customer Company
Discovery Validation Creation Building
hypotheses,
experiments,
insights
data, feedback,
insights
Product
Development
Saturday, March 17, 12
22. Customer Customer Customer Company
Discovery
Problem Team
Validation Creation Building
hypotheses,
experiments,
insights
data, feedback,
insights Solution Team
Product
Development
Saturday, March 17, 12
23. Lean Business Idea -
Summary
• Business idea is just a series of guesses
• You can validate the guesses with the help
of Customer Development
• Business Model Canvas is effective
tool to communicate your business ideas
Saturday, March 17, 12
24. 1. "Lean" your business ideas
2. Build faster (or not at all!)
3. Measure it!
4. Learn Faster
Saturday, March 17, 12
25. The Concept of an
inventory
Business Design Development
case
Testing Deployment
Saturday, March 17, 12
26. The Concept of an
inventory
2 8 10
Business Design Development
case
Testing Deployment
5
25
Saturday, March 17, 12
27. Don’t write the code!
Business Design Development
case
Testing Deployment
Saturday, March 17, 12
28. Don’t write the code!
Business Design Development
case
Testing Deployment
If you write the code..
Saturday, March 17, 12
29. Inventory with ATDD
2 8 5
Business Development
Design
case & Test
Deployment
15
Saturday, March 17, 12
30. Architecture
Realisation Vision
Saturday, March 17, 12
31. Inventory with ATDD +
JIT Architecture
2 5
Business Design, Development Deployment
case & Test
7
Saturday, March 17, 12
32. Continuous Integration
Get the stuff
Build & deploy Test & Report
from VCS
+
Continuous Deployment
Deploy to Monitor &
Backup
production Alert
Saturday, March 17, 12
34. Inventory with ATDD +
JIT Architecture + CD
2
Business Design, Development
case & ATDD & Continuous
Deployment
2
Saturday, March 17, 12
35. What about design of
the product?
• UX
• Business model pivots etc.
• Some inventories are needed - they are
actually buffers
Saturday, March 17, 12
37. Summary- Build faster
• Think timing (Just-In-Time)
• Think big, implement small (and fast)
• be aware of the inventory (queues) in your
product development process (system)
Saturday, March 17, 12
38. 1. "Lean" your business ideas
2. Build faster (or not at all!)
3. Measure it!
4. Learn Faster
Saturday, March 17, 12
39. What are things we
NEED to measure?
• How do you know you’re done?
• How do you know something is more
important/valuable than something else?
• How do you know how are you doing?
• How do you choose between two or more
solutions?
Saturday, March 17, 12
40. Number One Waste?
Features used
16%
13%
19% Sometimes
Often
7% Always
Never
Rarely
45%
XP2002 CHAOS report
Saturday, March 17, 12
41. Measuring if it is used
Owner: Marko
Size: S
Comments for service offers and requests
5 days
QUEUE: 1.6.2010 DONE: 6.6.2010
READY: 3.6.2010
3 days
Saturday, March 17, 12
42. Levels Monitoring
of monitoring
Biz reports Business
Hearbeat.rb
& navigator Application
Hearbeat.rb
& Monit Containers & DB
Monit &
Nagios OS & Services
Monit &
Nagios Hardware
Saturday, March 17, 12
44. Testing hypotheses with
Split Testing
A B
Acquisition Acquisition
Activation Activation
Retention Retention
Referral Referral
Revenue Revenue
20% 40%
Saturday, March 17, 12
45. Summary - Measure it
• Measure what matters to you
• Measure to throw away the waste
(optimize the whole system)
• Think measuring when implementing the
solution
• Measure the business (not only tech)
Saturday, March 17, 12
46. 1. "Lean" your business ideas
2. Build faster (or not at all!)
3. Measure it!
4. Learn Faster
Saturday, March 17, 12
48. Ship it! - learning
inventory
2
Business Design, Development
case & ATDD & Continuous
Deployment
Amazon: new deployment every 11.6 seconds
Facebook: continuous deployment
Flickr: same thing
IMVU, KaChing, KISSMetrics...
Elisa, Huitale...
Saturday, March 17, 12
49. Get out of the building
Saturday, March 17, 12
50. Testing hypotheses with
Split Testing
A B
Acquisition Acquisition
Activation Activation
Retention Retention
Referral Referral
Revenue Revenue
20% 40%
Saturday, March 17, 12
51. Everything is a guess
So how to formulate that as
hypotheses?
Saturday, March 17, 12
52. A way of learning
5 whys
Saturday, March 17, 12
53. A3 template for problem
solving
http://www.crisp.se/lean/a3-template
Saturday, March 17, 12
54. Customer Customer Customer Company
Discovery
Problem Team
Validation Creation Building
hypotheses,
experiments,
insights
data, feedback,
insights Solution Team
Product
Development
Saturday, March 17, 12
55. Summary - Learn faster
• Truth is out there: Ship It & Get out from
the building
• Identify root causes and use A3 for
problem solving
Saturday, March 17, 12
56. Executive summary
• Stop wasting people’s time
• Communicate the purpose to engage
people around you
Saturday, March 17, 12
57. Marko Taipale
@markotaipale
huitale.blogspot.com
marko.taipale@huitale.com
I help companies to improve by showing
what I have done, how I have done it
and what I have learned about it
I am also a CTO of
Saturday, March 17, 12