This document discusses impact mapping as a technique for delivering projects with impact. It provides an example of impact mapping for an MDM (mobile device management) product. The key steps of impact mapping include: defining goals and who they impact; identifying desired behaviors and how to enable them; establishing metrics to measure impact; and planning milestones to test assumptions. Impact mapping focuses on creating actual behavioral change rather than just shipping software.
174 starting a new product management role at ludicrous speed (chugh and ei...ProductCamp Boston
This document provides advice for taking on a new product management role. It discusses common situations a new PM may face like turnaround, sustaining success, or high growth. It recommends being ready before starting by understanding the product and situation, setting goals in the first two months like building relationships and quick wins, and then going forward by achieving a big first win and making major changes. The document also covers resolving complications like unclear expectations, unraveling complex problems, or spreading resources too thin. The overall message is to come prepared, establish credibility early on, and guide the product and team to success over time.
SF 10/12/17 - Scaling Product with Data by Jonathan Zazove, AtlassianAmplitude
Jonathan Zazove discusses how to scale product development with data. He emphasizes using both qualitative and quantitative customer feedback. Qualitatively, teams should speak to customers weekly to understand problems directly. Quantitatively, teams should constantly analyze usage data to see what customers actually do. Bringing the entire team to listen to customers and explore data helps everyone focus on the mission and build the right solutions. When used together, qualitative and quantitative feedback allows teams to deeply understand customer needs and make informed decisions about product development.
Questions product managers should ask customersProductPlan
This document provides 12 questions that product managers should ask customers to gain valuable insights. Open-ended questions that uncover customer values, pains, and motivations are most effective. Questions should challenge assumptions and lead to further insights. Customer answers will guide the features included on a product roadmap. The document advises getting customer interviews by explaining their benefit and being gracious. It also recommends documenting interviews quickly and discussing them to eliminate false positives and summarize insights.
How to Break Down PM in Startups vs. Big Companies by WeWork PMProduct School
Main takeaways:
- Know the difference in roles and responsibilities of a product manager at a large company vs a startup
- Learn the skills necessary to succeed in a large company vs a startup, and where the similarities are
- Leave with a better understanding of both, and an idea of which environment might be better for you
201 good product launch, bad product launch (john zilch)ProductCamp Boston
The document discusses factors that contribute to good and bad product launches. A good product launch focuses on having a marketable product that meets customer demand and solves their problems. It launches at the right time and uses "pull" marketing to highlight the product's value and benefits. In contrast, a bad product launch releases a minimum viable product prematurely without fully understanding the market or customer needs. It relies on "push" marketing that emphasizes product features rather than why customers should buy. A good launch also ensures operational readiness to scale while a bad one lacks adequate planning and preparation.
Understanding Engineering Challenges without a Tech BackgroundProduct School
While it can be intimidating for people without technical backgrounds to jump into a technical environment, there is amazing potential to affect change and act as a multiplier. In this session, Andrew walked through lessons he has learned in how to better understand, prioritize, and tackle technical issues facing engineers in the workplace.
This document discusses impact mapping as a technique for delivering projects with impact. It provides an example of impact mapping for an MDM (mobile device management) product. The key steps of impact mapping include: defining goals and who they impact; identifying desired behaviors and how to enable them; establishing metrics to measure impact; and planning milestones to test assumptions. Impact mapping focuses on creating actual behavioral change rather than just shipping software.
174 starting a new product management role at ludicrous speed (chugh and ei...ProductCamp Boston
This document provides advice for taking on a new product management role. It discusses common situations a new PM may face like turnaround, sustaining success, or high growth. It recommends being ready before starting by understanding the product and situation, setting goals in the first two months like building relationships and quick wins, and then going forward by achieving a big first win and making major changes. The document also covers resolving complications like unclear expectations, unraveling complex problems, or spreading resources too thin. The overall message is to come prepared, establish credibility early on, and guide the product and team to success over time.
SF 10/12/17 - Scaling Product with Data by Jonathan Zazove, AtlassianAmplitude
Jonathan Zazove discusses how to scale product development with data. He emphasizes using both qualitative and quantitative customer feedback. Qualitatively, teams should speak to customers weekly to understand problems directly. Quantitatively, teams should constantly analyze usage data to see what customers actually do. Bringing the entire team to listen to customers and explore data helps everyone focus on the mission and build the right solutions. When used together, qualitative and quantitative feedback allows teams to deeply understand customer needs and make informed decisions about product development.
Questions product managers should ask customersProductPlan
This document provides 12 questions that product managers should ask customers to gain valuable insights. Open-ended questions that uncover customer values, pains, and motivations are most effective. Questions should challenge assumptions and lead to further insights. Customer answers will guide the features included on a product roadmap. The document advises getting customer interviews by explaining their benefit and being gracious. It also recommends documenting interviews quickly and discussing them to eliminate false positives and summarize insights.
How to Break Down PM in Startups vs. Big Companies by WeWork PMProduct School
Main takeaways:
- Know the difference in roles and responsibilities of a product manager at a large company vs a startup
- Learn the skills necessary to succeed in a large company vs a startup, and where the similarities are
- Leave with a better understanding of both, and an idea of which environment might be better for you
201 good product launch, bad product launch (john zilch)ProductCamp Boston
The document discusses factors that contribute to good and bad product launches. A good product launch focuses on having a marketable product that meets customer demand and solves their problems. It launches at the right time and uses "pull" marketing to highlight the product's value and benefits. In contrast, a bad product launch releases a minimum viable product prematurely without fully understanding the market or customer needs. It relies on "push" marketing that emphasizes product features rather than why customers should buy. A good launch also ensures operational readiness to scale while a bad one lacks adequate planning and preparation.
Understanding Engineering Challenges without a Tech BackgroundProduct School
While it can be intimidating for people without technical backgrounds to jump into a technical environment, there is amazing potential to affect change and act as a multiplier. In this session, Andrew walked through lessons he has learned in how to better understand, prioritize, and tackle technical issues facing engineers in the workplace.
This document introduces devToM, an AI-powered product intelligence platform that helps users answer questions and solve problems at different stages of product development. It does this by providing organized insights from vast datasets using tools like NLP, machine learning, and computer vision. The platform guides users through developing products from idea to reality or maintaining existing products. It has modules for product research and design/risk assessment. DevToM is meant for individuals and companies involved in innovation, R&D, product management, and more by enabling faster decision making.
Ben Ryan, Head of Product at FatSecret shares his & his company's journey on using continuous discovery to understand their customers. Here are his 3 takeaways from this journey.
Working together: Agile teams, developers, and product managersDanielle Martin
I spoke to students at Ada Developer Academy in Seattle, WA about how product managers and software engineers work together. In the presentation I cover: what's an agile team and how do they work; case studies of real work by my agile product development team; advice about behaviors that create successful product manager and developer working relationships; and other career/life advice for students starting their careers as software engineers.
How to hire the best people for your startup-Gitta Blat-Head of PeopleWooga
Gitta Blatt, Head of People at Wooga, provides lessons learned and recommendations for hiring the best people for startups. She discusses the importance of getting recruitment basics right by defining what roles and skills are needed. Referrals are the top talent channel at Wooga, making up 40% of hires, so networking and managing university relations are key. While volume is important, focus is crucial - don't pursue ideas just because they are popular. Consider fit over just skills, look at individuality and personality, and engage candidates throughout the screening and interviewing process. Make hiring decisions based on what you really want to know about candidates, not just opinions of the highest paid employees.
In a lot of companies, people like to scream “MVP” without knowing what it is and why you want to have it. In this talk we will walk through a couple of weeks where 5 developers and 1 UX Guy were put together to accomplish the near Impossible. Deliver a project in 3 weeks that was supposed to take 6 weeks. All of this without a Scrum master and a Product Owner.
Emotional Product Management by LinkedIn Sr PMProduct School
Main takeaways:
- How emotions play into building experiences
- Why emotions matter in teamwork
- Emotions and their importance to your well being as a PM
How Product Managers & Developers Deliver Value at AvvoDanielle Martin
I gave a talk at Code Fellows' Partner Power Hour series about how product managers and developers work together at Avvo -- including lessons we've learned and tips for dev students starting their careers.
This document promotes a website that provides psychology capstone project writing services. It emphasizes that the capstone project is the most important work in one's training and must meet high standards. It states that conducting the necessary research can be difficult and time-consuming for students. The website offers to simplify the writing task by having experts with psychology backgrounds and publishing experience complete projects. It highlights the benefits of using their service, such as meeting deadlines and ensuring work is plagiarism-free. Samples of past projects are available for review on quality.
How to Think Big as a Product Manager by Amazon Sr PMProduct School
This document discusses how to think big as a product manager according to an Amazon senior product manager. It provides three key takeaways: 1) Start with understanding the real problem customers face rather than assuming the stated problem is correct, 2) Be open to learning by listening to others and subscribing to relevant resources, and 3) Be comfortable with ambiguity when refining big ideas and use testing and learning to improve ideas. The document encourages product managers to ask deeper "why" questions to uncover real problems, set up mechanisms to gain new insights regularly, and view ambiguity positively when refining ideas through an optimism curve.
EiR & Engineering Continuing Ed: Understanding the Web Site Feedback LoopLaunch Angels
This document discusses the importance of the feedback loop when building an MVP. It outlines the 5 Ws (What, Why, Who, Where, When) that founders should consider when analyzing feedback. The 5 Ws help determine goals, reasons for projects, appropriate users to collect feedback from, where users spend their time, and how much data is needed before making decisions. The document also recommends tools for the feedback loop like Google Analytics, Crazy Egg, Survey Monkey and human-to-human contact, and emphasizes continuously collecting data, validating the business model, and never stopping analysis.
208 radical product - translating vision and strategy to execution product ...ProductCamp Boston
This document provides guidance on translating a product strategy into an execution plan. It discusses measuring the right metrics aligned to the product vision, prioritizing work, and influencing other teams. Key points covered include common issues like being obsessed with metrics without a clear strategy, and how Lean/Agile are not sufficient for creating customer-centric products alone. The document introduces the Radical Product framework for defining a vision, developing an RDCL strategy, crafting a strategic roadmap, and building an execution plan with hypotheses and activities to test progress.
Risk Management: Evaluate Risks in your ProjectGagan Gupta
I am sharing this presentation, which I prepared during my PG. Hope this will help you people a bit. Check and please feedback me if needed any changes. write me: ggngupta@hotmail.com with subject title: Feedback-Slideshare <filename>. Thanks
The document discusses various challenges that can cause project failure if not properly managed. It notes that project management is a dynamic process that utilizes organizational resources in a controlled manner to achieve strategic objectives. Some challenges discussed include scope creep, poor communication, inadequate resources, unrealistic customer expectations, lack of change management, unrealistic timelines, and failure to properly plan for risks. The document emphasizes the importance of thorough planning, clear requirements, change management processes, effective communication, and risk planning to avoid these challenges and ensure project success.
The document discusses various challenges that can cause project failure if not properly managed. It notes that project management is a dynamic process that utilizes organizational resources in a controlled manner to achieve strategic objectives. Some key issues discussed include scope creep, poor communication, inadequate resources, unrealistic customer expectations, lack of change management, unrealistic timelines, and failure to properly plan for risks. The document emphasizes the importance of thorough planning, clear requirements, change management processes, effective communication, and risk planning to avoid these pitfalls and ensure project success.
The document discusses common problems that can cause project failure and provides recommendations to address them. It notes that project failure occurs when a project does not meet stakeholder expectations and can result in cost and time overruns, quality issues, and stress. Specific issues covered include scope creep, poor communication, inadequate resources, unclear requirements, unrealistic timelines, unmanaged risks, undefined deliverables, lack of planning, and insufficient project management skills. The document recommends properly documenting requirements, following a change management process, communicating effectively, allocating sufficient resources, conducting risk analysis, clearly defining deliverables, taking time for planning, and obtaining project management education.
This document discusses common problems that can cause project failure and provides recommendations to address them. It notes that projects can fail when they do not meet stakeholder expectations, experience cost and time overruns, or have quality issues. Specific problems covered include scope creep, poor communication, inadequate resources, unclear requirements, unrealistic timelines, unmanaged risks, undefined deliverables, and lack of planning. The document recommends establishing clear requirements, comprehensive plans, change management processes, risk management strategies, and using project management tools and techniques to initiate, plan, execute and control projects.
LeanUX: Getting out of the Deliverables BusinessMatthew Mamet
This document discusses Lean UX, which focuses on getting user experience (UX) design work out quickly with less emphasis on deliverables and more focus on the actual experience being designed. Lean UX is inspired by Lean Startup and Agile development theories. It advocates validating designs with customers early and iterating quickly based on user feedback, rather than spending a long time perfecting designs that may not meet user needs. The document provides examples of how to implement Lean UX and overcome challenges agencies may face in moving from traditional deliverable-focused processes to Lean UX.
The document discusses getting lean at startups. It recommends having a small "Goldilocks" team that works well together. The team should be fast, focused, and make small bets to test ideas quickly through a build-measure-learn process. To get lean, the author recommends reorganizing teams around product, reducing meetings in favor of continuous communication, and investing resources in what works based on measuring results. The overall message is that being lean is about moving quickly through testing ideas rather than being cheap.
This document introduces devToM, an AI-powered product intelligence platform that helps users answer questions and solve problems at different stages of product development. It does this by providing organized insights from vast datasets using tools like NLP, machine learning, and computer vision. The platform guides users through developing products from idea to reality or maintaining existing products. It has modules for product research and design/risk assessment. DevToM is meant for individuals and companies involved in innovation, R&D, product management, and more by enabling faster decision making.
Ben Ryan, Head of Product at FatSecret shares his & his company's journey on using continuous discovery to understand their customers. Here are his 3 takeaways from this journey.
Working together: Agile teams, developers, and product managersDanielle Martin
I spoke to students at Ada Developer Academy in Seattle, WA about how product managers and software engineers work together. In the presentation I cover: what's an agile team and how do they work; case studies of real work by my agile product development team; advice about behaviors that create successful product manager and developer working relationships; and other career/life advice for students starting their careers as software engineers.
How to hire the best people for your startup-Gitta Blat-Head of PeopleWooga
Gitta Blatt, Head of People at Wooga, provides lessons learned and recommendations for hiring the best people for startups. She discusses the importance of getting recruitment basics right by defining what roles and skills are needed. Referrals are the top talent channel at Wooga, making up 40% of hires, so networking and managing university relations are key. While volume is important, focus is crucial - don't pursue ideas just because they are popular. Consider fit over just skills, look at individuality and personality, and engage candidates throughout the screening and interviewing process. Make hiring decisions based on what you really want to know about candidates, not just opinions of the highest paid employees.
In a lot of companies, people like to scream “MVP” without knowing what it is and why you want to have it. In this talk we will walk through a couple of weeks where 5 developers and 1 UX Guy were put together to accomplish the near Impossible. Deliver a project in 3 weeks that was supposed to take 6 weeks. All of this without a Scrum master and a Product Owner.
Emotional Product Management by LinkedIn Sr PMProduct School
Main takeaways:
- How emotions play into building experiences
- Why emotions matter in teamwork
- Emotions and their importance to your well being as a PM
How Product Managers & Developers Deliver Value at AvvoDanielle Martin
I gave a talk at Code Fellows' Partner Power Hour series about how product managers and developers work together at Avvo -- including lessons we've learned and tips for dev students starting their careers.
This document promotes a website that provides psychology capstone project writing services. It emphasizes that the capstone project is the most important work in one's training and must meet high standards. It states that conducting the necessary research can be difficult and time-consuming for students. The website offers to simplify the writing task by having experts with psychology backgrounds and publishing experience complete projects. It highlights the benefits of using their service, such as meeting deadlines and ensuring work is plagiarism-free. Samples of past projects are available for review on quality.
How to Think Big as a Product Manager by Amazon Sr PMProduct School
This document discusses how to think big as a product manager according to an Amazon senior product manager. It provides three key takeaways: 1) Start with understanding the real problem customers face rather than assuming the stated problem is correct, 2) Be open to learning by listening to others and subscribing to relevant resources, and 3) Be comfortable with ambiguity when refining big ideas and use testing and learning to improve ideas. The document encourages product managers to ask deeper "why" questions to uncover real problems, set up mechanisms to gain new insights regularly, and view ambiguity positively when refining ideas through an optimism curve.
EiR & Engineering Continuing Ed: Understanding the Web Site Feedback LoopLaunch Angels
This document discusses the importance of the feedback loop when building an MVP. It outlines the 5 Ws (What, Why, Who, Where, When) that founders should consider when analyzing feedback. The 5 Ws help determine goals, reasons for projects, appropriate users to collect feedback from, where users spend their time, and how much data is needed before making decisions. The document also recommends tools for the feedback loop like Google Analytics, Crazy Egg, Survey Monkey and human-to-human contact, and emphasizes continuously collecting data, validating the business model, and never stopping analysis.
208 radical product - translating vision and strategy to execution product ...ProductCamp Boston
This document provides guidance on translating a product strategy into an execution plan. It discusses measuring the right metrics aligned to the product vision, prioritizing work, and influencing other teams. Key points covered include common issues like being obsessed with metrics without a clear strategy, and how Lean/Agile are not sufficient for creating customer-centric products alone. The document introduces the Radical Product framework for defining a vision, developing an RDCL strategy, crafting a strategic roadmap, and building an execution plan with hypotheses and activities to test progress.
Risk Management: Evaluate Risks in your ProjectGagan Gupta
I am sharing this presentation, which I prepared during my PG. Hope this will help you people a bit. Check and please feedback me if needed any changes. write me: ggngupta@hotmail.com with subject title: Feedback-Slideshare <filename>. Thanks
The document discusses various challenges that can cause project failure if not properly managed. It notes that project management is a dynamic process that utilizes organizational resources in a controlled manner to achieve strategic objectives. Some challenges discussed include scope creep, poor communication, inadequate resources, unrealistic customer expectations, lack of change management, unrealistic timelines, and failure to properly plan for risks. The document emphasizes the importance of thorough planning, clear requirements, change management processes, effective communication, and risk planning to avoid these challenges and ensure project success.
The document discusses various challenges that can cause project failure if not properly managed. It notes that project management is a dynamic process that utilizes organizational resources in a controlled manner to achieve strategic objectives. Some key issues discussed include scope creep, poor communication, inadequate resources, unrealistic customer expectations, lack of change management, unrealistic timelines, and failure to properly plan for risks. The document emphasizes the importance of thorough planning, clear requirements, change management processes, effective communication, and risk planning to avoid these pitfalls and ensure project success.
The document discusses common problems that can cause project failure and provides recommendations to address them. It notes that project failure occurs when a project does not meet stakeholder expectations and can result in cost and time overruns, quality issues, and stress. Specific issues covered include scope creep, poor communication, inadequate resources, unclear requirements, unrealistic timelines, unmanaged risks, undefined deliverables, lack of planning, and insufficient project management skills. The document recommends properly documenting requirements, following a change management process, communicating effectively, allocating sufficient resources, conducting risk analysis, clearly defining deliverables, taking time for planning, and obtaining project management education.
This document discusses common problems that can cause project failure and provides recommendations to address them. It notes that projects can fail when they do not meet stakeholder expectations, experience cost and time overruns, or have quality issues. Specific problems covered include scope creep, poor communication, inadequate resources, unclear requirements, unrealistic timelines, unmanaged risks, undefined deliverables, and lack of planning. The document recommends establishing clear requirements, comprehensive plans, change management processes, risk management strategies, and using project management tools and techniques to initiate, plan, execute and control projects.
LeanUX: Getting out of the Deliverables BusinessMatthew Mamet
This document discusses Lean UX, which focuses on getting user experience (UX) design work out quickly with less emphasis on deliverables and more focus on the actual experience being designed. Lean UX is inspired by Lean Startup and Agile development theories. It advocates validating designs with customers early and iterating quickly based on user feedback, rather than spending a long time perfecting designs that may not meet user needs. The document provides examples of how to implement Lean UX and overcome challenges agencies may face in moving from traditional deliverable-focused processes to Lean UX.
The document discusses getting lean at startups. It recommends having a small "Goldilocks" team that works well together. The team should be fast, focused, and make small bets to test ideas quickly through a build-measure-learn process. To get lean, the author recommends reorganizing teams around product, reducing meetings in favor of continuous communication, and investing resources in what works based on measuring results. The overall message is that being lean is about moving quickly through testing ideas rather than being cheap.
The document discusses a software project that failed due to scope creep. It began as a project to automate workflows for a proprietary language site, but numerous new requirements were discovered during stakeholder interviews. This led to a massive increase in the scope of the project. Documentation grew out of control, a prototype was never finished, and the functional specification was never signed off. The project cost doubled and the agency lost money while the client lost confidence and brought the project in-house. The key lessons were that application sites require different development methods than static sites, documentation needs management, and scope creep must be controlled.
Bob Cavezza is founder at EasyUnsubscriber.com,a Builder at Ibuildmvps.com, Blogger at Foundersblock.com, and lives in Boston.
EasyUnsubscriber is a tool that allows people to unsubscribe from all emails they don't want in 5 minutes.
Bob shared his lessons learned on building EasyUnsubscriber from the ground up as an MVP, and how he arrived at the decision to discard this MVP at the June 2011 meetup of the Lean Startup Circle Boston.
1) Agile managers guide and collaborate with project teams, program teams, and management teams to work together effectively. They manage the entire organizational system for success.
2) Agile managers strategically manage the project portfolio, remove organizational obstacles, build trusting relationships, lead hiring decisions, and build organizational capacity. They collaborate to maximize value for the organization.
3) Agile managers become champions for their teams by not micromanaging, building trusting relationships through regular one-on-one meetings, and helping to provide feedback to encourage collaboration over perfection.
Learning from Failures: a Lightweight Approach to Run-Time Behavioural Adapta...José Antonio Martín Baena
These are the slides I presented in FACS'11 regarding this accepted paper (http://goo.gl/SKPga).
Normally, when designing a distributed system, you have to develop a choreograpy or orchestration able to coordinate the different services. This process is called synthesis and it is usually done at design time and it entails an exponential complexity. In this work, we developed dynamic learning adaptors that don't require the synthesis, it is a lightweight algorithm and is able to adapt to sporadic errors and changes in the system
Presented at Ford's 2017 Global IT Learning Summit (GLITS)Ron Lazaro
Presentation Details: The best way to think about product discovery is to think about it in relation to product delivery. It's not possible to build a product without doing both discovery and delivery. Discovery encompasses all the activities that we do to decide what to build. It includes all the decisions we make to decide what to build next, whereas delivery is all the activities we do to write code, package releases, ship products. It's how we deliver value to our customers.
Key takeaway for the participants will be to help them understand the difference between Product Discovery and Product Delivery and how to apply techniques in doing both.
Customer Feedback: the missing piece of the Agile puzzleskierkowski
The document provides 8 rules and 10 mechanisms for building products customers want. The 8 rules are: 1) Your opinion is wrong, 2) Don't ask what people want, 3) Fake it till you make it, 4) Make it cheap and throw it out, 5) Scalability is not a problem, 6) Overcommit and deliver, 7) Don't bother with feature lists, 8) Not all users are customers. The 10 mechanisms are ways to understand customer needs and include outstanding support, surveys, interviews, and analytics tools.
This one weird trick will fix all your Agile problemsAnthony Marter
In this presentation I cover the importance of a well functioning Product Management practice to following the 12 Agile principles. Often we focus just on the process parts of Scrum, and here I cover why this misses half of the principles.
This webinar discusses best practices for bringing an idea to implementation, including defining project cycles and audience, assembling a team, setting goals and metrics, developing product requirements, establishing milestones and schedules, engaging communities, and planning for sustainability and revenue generation. Key recommendations include persona building for audiences, using project management tools, conducting user testing, regularly reviewing metrics, and developing multiple revenue strategies. Resources like circuit riders and publications are also suggested for additional guidance.
This webinar discusses best practices for bringing an idea to implementation, including defining project cycles and audience, assembling a team, setting goals and metrics, developing product requirements, establishing milestones and schedules, engaging communities, and planning for sustainability and revenue generation. Key recommendations include persona building for audiences, using project management tools, conducting user testing, regularly reviewing metrics and making adjustments, and developing multiple revenue strategies. Resources like circuit riders and publications are also suggested for additional guidance.
MVP: Minimum Viable Product vs. Maximum Value ProductLiquid Reality
Start-ups and product reboots are all thinking the same thing - how quickly can we get to market? The app market is break-kneck, and being first-to-market, or soon-to-market can be important, but, not at the expense of quality. In this talk we'll explore the motivations for being first, and argue the values of being "better"
From experience, we'll focus on how to convince clients and stakeholders to buy-in to quality over "fast" - as a philosophy, as a differentiator, and as a process to making it happen.
Anyone can make an app - just look at any of the app stores, but only the ones that focus on the customer, on quality, and on the entire experience as a whole will succeed.
This talk will give you a roadmap to create better products, get and keep clients on-board with your direction, and deliver outstanding products to the market.
From Software Developer to Proud Product Owner (Agile Connect Aveiro Meetup #20)Sergio Freire
As you evolve in your career, at every single moment you will face challenges; nothing is linear. From software developer to team leader to product owner and product manager, every step represents a challenge. This challenge is also affected depending on whether you are working on Waterfall or Agile contexts. Let's make this road trip together and talk a bit about these roles, the challenges I had and still have and try to discuss some possible ways of overcoming them.
Presentation for Agile Australia Conference 2013. Introducing Lean Startup concepts in a way accessible to people used to usual project management methods. With lean startup you don't assume you know the end state required, (as you do with a project), you assume you need to focus on learning to discover the end state to solve the problem you area you looking at.
How to Build Customer Centric Products by Microsoft Senior PMProduct School
This document summarizes best practices for building customer-centric products based on a talk by Ritika Kapadia. It outlines a 5 step process: 1) setting up customer interviews; 2) understanding customers through open-ended questions; 3) validating solution ideas with customers; 4) validating solution details with usability studies and experiments; 5) evolving the product based on customer metrics and feedback from programs. The key takeaway is that product managers must directly interface with customers to make decisions rooted in customer needs rather than their own assumptions.
Most businesses fail within the first year or two. How do you improve your odds of success? We’ll review the magic in learning loops, how to understand your users and customer development, and what you need in team dynamics to drive your startup forward and point you in a more successful direction.
By Nick Barendt & Nicole Capuana
Spitfire Group 2014 Mile High Agile Tips for Timeboxed Kanban ProgramMike Byrne
The document provides 13 tips for instituting Kanban on a time boxed program based on the experiences of a software development team. The tips include taking advantage of all Kanban aspects, making processes and metrics visible, maintaining quality as throughput increases, gaining business trust, and recognizing that productivity does not scale linearly with team growth. Visualizing work, establishing definitions of done, limiting work in progress, and using story maps are emphasized.
How Yammer Stayed Lean Post-Acquisition: Customer Development as Survival Str...Cindy Alvarez
1) After being acquired by Microsoft, Yammer stayed lean by continuing to focus on customer development and maintaining their startup culture and processes.
2) Key aspects of Yammer's product development process included building products based on identified customer problems, autonomous cross-functional teams, and testing all features through A/B testing.
3) Yammer also focused on data-driven decision making, maintaining a supportive and empowering culture, and finding early adopters within Microsoft to socialize their approach.
12/2/2014 Milwaukee Agile Presentation: Persuading Your Oganization to be AgileNVISIA
12/2/2014 Milwaukee Agile Presentation: Persuading Your Organization to be Agile was delivered to 54 practitioners. NVISIA's Tracey Barrett shared tips on how to persuade an organization to become Agile. Interestingly enough, Tracey suggests being Agile in your adoption of Agile.
How to leverage your work with a Product Mindset - Mark Opanasiuk.pdfMark Opanasiuk
How to leverage your work with a Product Mindset - Mark Opanasiuk
1. What is a Product Mindset?
2. Product Thinking Mindset on Personal level.
3. Product Mindset on Organization level.
This document provides an overview of how to do great marketing without spending a lot. It discusses laying the foundation through developing buyer personas, keyword definitions, and lead definitions. It recommends attracting prospects through thought leadership, humor and personality. The document also discusses nurturing leads over time through content like blogs, newsletters, webinars and white papers. It emphasizes the importance of measuring marketing performance through metrics. The overall summary is how to develop buyer personas, attract prospects through thought leadership, nurture leads over time with content, and measure marketing performance with metrics.
5 Lessons Learned in Product Management by Twitch Senior PMProduct School
Main takeaways:
- How to take a non traditional path to product management
- How to leverage your unique background to differentiate yourself as a Product Manager
- Steps you can take to build your product management skills/portfolio while in other fields
Tapping into your market: how to develop a framework to make sense of user fe...Emma Hill
As a Product Manager turned Customer Success Manager, I share my tips on creating a manageable framework for making it easier for your organisation to get value out of your feedback from internal and external stakeholders.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Best 20 SEO Techniques To Improve Website Visibility In SERPPixlogix Infotech
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...alexjohnson7307
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
9. Ways we are lean
• Assumptions and plan to validate
• Product before marketing – the product must
do its job
• Relentless focus on metrics
• Test and track – Google Analytics & CrazyEgg
10. Ways we’re not lean
• No revenue goals for first 12 months
• Decision about “launch”
– Me: When the product looks pretty good
– Everyone Else: Now!
11. How we use customer development
Daily calls from customers asking
to pay us…
… require tremendous discipline
NOT to build tools for them.
(our focus right
now is on users)
12. Biggest lessons learned so far…
• Things we thought were important turned
out not to be: Privacy
• Things we didn’t think
were important turned
out to be: Orphan tests