The document discusses techniques for systematically testing startup ideas through experiments and pivots. It provides examples of startup hypotheses that were tested, such as the idea of creating lists of top professionals and whether people would pay for access to such lists. It emphasizes testing ideas quickly through real-world experiments and validating or invalidating hypotheses through metrics before committing significant resources.
The document provides an overview of software testing concepts including:
- Software testing methods like manual and automation testing.
- SDLC models like waterfall, prototype, incremental and agile models.
- Testing levels like unit, integration and system testing.
- Testing types like functionality, usability, performance and security testing.
- The software testing life cycle including test planning, design, execution and reporting.
Software testing is a vital process without which no software release can occur, it makes the software usable. Software testing offers opportunities constantly to be exposed with new development methods, new platform technologies, new product innovations.
The document provides an overview of manual testing and the software development lifecycle. It defines key terms like software testing, verification and validation. It discusses different types of testing like static testing, white-box testing and black-box testing. It also explains software quality concepts like quality assurance and quality control. The document then introduces process standards like ISO and CMMI and maturity models. It describes various software development life cycle models like waterfall, prototyping and incremental development.
01 software test engineering (manual testing)Siddireddy Balu
The document discusses various topics related to manual software testing, including:
1. The software development life cycle and where testing fits in.
2. Different testing methodologies like black box, white box, and grey box testing.
3. The different levels of testing from unit to system level.
4. Types of testing like regression, compatibility, security, and performance testing.
5. The software testing life cycle process including test planning, development, execution and reporting.
The document provides information about manual testing processes and concepts. It discusses various phases of the software development life cycle (SDLC) like requirements gathering, analysis, design, coding, testing, and deployment. It also describes different testing methodologies like black box testing, white box testing, different levels of testing from unit to user acceptance. Key terms discussed include environments, stubs, drivers, and software development process models like waterfall.
From http://wiki.directi.com/x/AgAa - This is a 24 slide internal presentation covering virtues of Automated Testing vs Manual Testing. Inkeeping with our agile adoption this presentation covers various advantages (11 to be specific) obtained in using TDD and Automated Testing as opposed to Manual Testing
UX Jackson 2013 - One-Day Lean Startup WorkshopJanice Fraser
The document outlines an agenda for a workshop on Lean Startups and user experience design fundamentals. It includes introductions and icebreakers, discussions of Lean Startup methodology and customer development, exercises in creating user personas and mapping customer interviews, and activities to identify assumptions to test. The goal is to teach techniques for building products using rapid iteration and customer feedback to reduce waste and evolve designs quickly based on evidence.
The document discusses ethnographic fieldwork and methods for uncovering insights. It provides guidance on identifying design challenges, speaking to different types of people, and using methods like interviews, observation, and self-documentation to develop themes and insights. The document emphasizes exploring commonalities, differences, and relationships between findings to group them into themes. It also provides resources for further reading on topics like ethnography, anthropology, and cultural trends research.
The document provides an overview of software testing concepts including:
- Software testing methods like manual and automation testing.
- SDLC models like waterfall, prototype, incremental and agile models.
- Testing levels like unit, integration and system testing.
- Testing types like functionality, usability, performance and security testing.
- The software testing life cycle including test planning, design, execution and reporting.
Software testing is a vital process without which no software release can occur, it makes the software usable. Software testing offers opportunities constantly to be exposed with new development methods, new platform technologies, new product innovations.
The document provides an overview of manual testing and the software development lifecycle. It defines key terms like software testing, verification and validation. It discusses different types of testing like static testing, white-box testing and black-box testing. It also explains software quality concepts like quality assurance and quality control. The document then introduces process standards like ISO and CMMI and maturity models. It describes various software development life cycle models like waterfall, prototyping and incremental development.
01 software test engineering (manual testing)Siddireddy Balu
The document discusses various topics related to manual software testing, including:
1. The software development life cycle and where testing fits in.
2. Different testing methodologies like black box, white box, and grey box testing.
3. The different levels of testing from unit to system level.
4. Types of testing like regression, compatibility, security, and performance testing.
5. The software testing life cycle process including test planning, development, execution and reporting.
The document provides information about manual testing processes and concepts. It discusses various phases of the software development life cycle (SDLC) like requirements gathering, analysis, design, coding, testing, and deployment. It also describes different testing methodologies like black box testing, white box testing, different levels of testing from unit to user acceptance. Key terms discussed include environments, stubs, drivers, and software development process models like waterfall.
From http://wiki.directi.com/x/AgAa - This is a 24 slide internal presentation covering virtues of Automated Testing vs Manual Testing. Inkeeping with our agile adoption this presentation covers various advantages (11 to be specific) obtained in using TDD and Automated Testing as opposed to Manual Testing
UX Jackson 2013 - One-Day Lean Startup WorkshopJanice Fraser
The document outlines an agenda for a workshop on Lean Startups and user experience design fundamentals. It includes introductions and icebreakers, discussions of Lean Startup methodology and customer development, exercises in creating user personas and mapping customer interviews, and activities to identify assumptions to test. The goal is to teach techniques for building products using rapid iteration and customer feedback to reduce waste and evolve designs quickly based on evidence.
The document discusses ethnographic fieldwork and methods for uncovering insights. It provides guidance on identifying design challenges, speaking to different types of people, and using methods like interviews, observation, and self-documentation to develop themes and insights. The document emphasizes exploring commonalities, differences, and relationships between findings to group them into themes. It also provides resources for further reading on topics like ethnography, anthropology, and cultural trends research.
DIYDays NY 2012 - Mark Harris & Heidi HysellMark Harris
The document discusses creative technologists, who understand technology capabilities and limits, and can help creative projects utilize software and custom tools. It says that as more content becomes software-based, from streaming to augmented reality, creative technologists are needed to ensure technology enhances creativity. It provides examples of projects combining creativity and technology and advises discussing goals openly with technologists, valuing their input, and having iterative development processes.
This document discusses the principles of building startups and products using a lean methodology. It emphasizes rapid prototyping with minimum viable products to test hypotheses, obtaining customer feedback, and continuously learning through short build-measure-learn cycles. The goal is to maximize learning while minimizing wasted time and resources on products that nobody wants.
The weSPOT project is a 36-month, EC-funded research project with 9 partners from 9 EU countries that aims to enhance students' inquiry skills. It will develop tools to support inquiry-based learning, including a model for inquiry skills and workflows, a diagnostic for measuring skills, and mobile apps. Learning analytics and an open badge system will also be used to track student activities like Twitter, blogs, and bookmarks across formal and informal learning.
Project managing your postgrad research march 2013 for slidesharecarolynejacobs
This document discusses strategies for managing postgraduate research projects. It begins by introducing project management concepts and explaining why research students need to take a project management approach. It then covers scoping a research project, developing a business case that defines goals and benefits, and identifying key requirements like understanding methodology versus methods. The document provides guidance on developing a research design that considers topics like sampling and data collection tools. It also addresses allocating resources like time and budgets, as well as techniques for effective time management and prioritization. Reflection on experiences to date is recommended to improve ongoing research management.
Talk for California Manufacturing Centers of ExcellenceNick Pinkston
I talked about some of what I've been doing with manufacturing automation, where I see our education system needing to go in order to compete in the future, and about some of the tools coming out for teaching / sharing work in the field.
The document describes CoolJunk, a company that designs and produces DIY learning kits. It aims to create the world's largest global innovation powerhouse of personal learning kits. CoolJunk develops exhaustive kits focused on fun, wow-factor, and depth of learning. The document outlines CoolJunk's history and vision, describes its first electronics kit, and provides biographies of its founding team members. It also discusses CoolJunk's culture and available marketing intern positions.
Erik Duval gave a presentation on learning analytics and dashboards for learning. He discussed how learning analytics involves collecting trace data from learners' activities to improve the learning process. Duval presented examples of learning dashboards and analytics tools that provide visualizations of student data to promote awareness, reflection, and behavior change. However, issues around data architecture, interoperability, and ensuring analytics are used to enhance rather than distort learning were also addressed.
Project managing your postgrad research feb 2013v2carolynejacobs
This document discusses project managing a postgraduate research project. It covers scoping the project, developing a business case, identifying requirements, designing the research methodology, allocating resources and managing time effectively. The presenter emphasizes developing a project plan that identifies key stages, timescales and milestones. Different project management tools are discussed, as well as using an agile or waterfall methodology. The importance of reflection and adapting the project plan as the research evolves is also highlighted.
This document appears to be notes from a presentation on content strategy. It discusses four steps to improve an organization's approach to content: 1) Admitting mistakes, 2) Self-examination, 3) Creating value and showing it, and 4) Becoming part of the business. Three concept directions are presented for a cancer society website focusing on community, knowledge, and humanization. Metrics are shown for how content strategy has improved outcomes for other organizations.
DIYDays NY 2012 - Mark Harris & Heidi HysellMark Harris
The document discusses creative technologists, who understand technology capabilities and limits, and can help creative projects utilize software and custom tools. It says that as more content becomes software-based, from streaming to augmented reality, creative technologists are needed to ensure technology enhances creativity. It provides examples of projects combining creativity and technology and advises discussing goals openly with technologists, valuing their input, and having iterative development processes.
This document discusses the principles of building startups and products using a lean methodology. It emphasizes rapid prototyping with minimum viable products to test hypotheses, obtaining customer feedback, and continuously learning through short build-measure-learn cycles. The goal is to maximize learning while minimizing wasted time and resources on products that nobody wants.
The weSPOT project is a 36-month, EC-funded research project with 9 partners from 9 EU countries that aims to enhance students' inquiry skills. It will develop tools to support inquiry-based learning, including a model for inquiry skills and workflows, a diagnostic for measuring skills, and mobile apps. Learning analytics and an open badge system will also be used to track student activities like Twitter, blogs, and bookmarks across formal and informal learning.
Project managing your postgrad research march 2013 for slidesharecarolynejacobs
This document discusses strategies for managing postgraduate research projects. It begins by introducing project management concepts and explaining why research students need to take a project management approach. It then covers scoping a research project, developing a business case that defines goals and benefits, and identifying key requirements like understanding methodology versus methods. The document provides guidance on developing a research design that considers topics like sampling and data collection tools. It also addresses allocating resources like time and budgets, as well as techniques for effective time management and prioritization. Reflection on experiences to date is recommended to improve ongoing research management.
Talk for California Manufacturing Centers of ExcellenceNick Pinkston
I talked about some of what I've been doing with manufacturing automation, where I see our education system needing to go in order to compete in the future, and about some of the tools coming out for teaching / sharing work in the field.
The document describes CoolJunk, a company that designs and produces DIY learning kits. It aims to create the world's largest global innovation powerhouse of personal learning kits. CoolJunk develops exhaustive kits focused on fun, wow-factor, and depth of learning. The document outlines CoolJunk's history and vision, describes its first electronics kit, and provides biographies of its founding team members. It also discusses CoolJunk's culture and available marketing intern positions.
Erik Duval gave a presentation on learning analytics and dashboards for learning. He discussed how learning analytics involves collecting trace data from learners' activities to improve the learning process. Duval presented examples of learning dashboards and analytics tools that provide visualizations of student data to promote awareness, reflection, and behavior change. However, issues around data architecture, interoperability, and ensuring analytics are used to enhance rather than distort learning were also addressed.
Project managing your postgrad research feb 2013v2carolynejacobs
This document discusses project managing a postgraduate research project. It covers scoping the project, developing a business case, identifying requirements, designing the research methodology, allocating resources and managing time effectively. The presenter emphasizes developing a project plan that identifies key stages, timescales and milestones. Different project management tools are discussed, as well as using an agile or waterfall methodology. The importance of reflection and adapting the project plan as the research evolves is also highlighted.
This document appears to be notes from a presentation on content strategy. It discusses four steps to improve an organization's approach to content: 1) Admitting mistakes, 2) Self-examination, 3) Creating value and showing it, and 4) Becoming part of the business. Three concept directions are presented for a cancer society website focusing on community, knowledge, and humanization. Metrics are shown for how content strategy has improved outcomes for other organizations.
3. Startup Science
Systematic Innovation
Today, in Australia and Singapore ...
Execution teams, deploying Pollenizer tools and
process create investable internet businesses in
6-9 months and we currently do this about 10
times per year.
Friday, 22 March 13
4. Startup Science
Startups = a series of
hypotheses
Friday, 22 March 13
7. Startup Science
Academy Courses
• Building Lean Startups
Take an idea from inception to pitch and everything in between.
• The Lean Product Manager
Learn how to build, measure and learn your way to success.
• Coding for Designers & Managers
You work with coders and you dream of impressing them with
your own coding chops.
• Web Development for Lean Startups
What you need to know to be a developer in a Lean Startup.
Friday, 22 March 13
8. Startup Science
About Me
Lean Product Manager
Work @ Pollenizer
Successfully failed
Ruby hacker
@micdijkstra
github.com/
micdijkstra
Friday, 22 March 13
13. Startup Science
1. Problem 4. Solution 3. UVP 9. Unfair 2. Customer
Advantage
The lean canvas shows each risk as a
8. KPI 5. Channels
hypothesis to be tested.
7. Costs 6. Revenue
Friday, 22 March 13
15. Startup Science
It’s hard to find the best person for a job
What if we could create a list of the best
people for a given profession
Friday, 22 March 13
16. Startup Science
Test #1
Recruiters will pay for (find value in) a list
of top talent in a profession.
Friday, 22 March 13
17. Startup Science
We need to find 50 top professionals for a
given role, add them to a list and
then we can start selling!
Friday, 22 March 13
30. Startup Science
Measure Viral Coefficient
• Spread of the network
New members / lists created
• Conversion
New members signed up / new members added
• Cycle
Signups who created a list
• Returning users
Existing signed in users / existing base users
Friday, 22 March 13
31. Startup Science
Within 2 weeks …
• Over 500 people listed
• 150 people signed up
• Viral coefficient of 0.31
Friday, 22 March 13
53. Startup Science
How do you know what to
manual test?
Friday, 22 March 13
54. Startup Science
Focus on the why
Figuring out the how is the easy (fun) part
Friday, 22 March 13
55. Startup Science
We want people to create lots of lists … Why?
To create a master list of talent … Why?
So we can sell it to recruiters … Why?
So they can have a shortlist of the best
candidates … Why?
So they can provide the best candidates to
employers … Why?
So an employer can find the best person for
the job.
Friday, 22 March 13
56. Startup Science
Think of the Flow
• What is the big piece of value that you are
basing everything off?
• How do you think your solution will work?
• What key stages are there?
• Can you fake one side of the market?
Friday, 22 March 13
57. Startup Science
Create lots of
lists
Generate
master list
Sell list
Friday, 22 March 13
58. Startup Science
Create lots of
lists
Fake It
Master List
Sell list
Friday, 22 March 13
59. Startup Science
What are you waiting for?
Friday, 22 March 13
60. Startup Science
If you’re so confident that your
solution will work, then you
should have no problem manual
testing to prove it.
Friday, 22 March 13
61. Questions?
Test Storyberg for me
http://storyberg.com
Friday, 22 March 13