The document provides an overview of product management processes at AMEE, including tracking bugs, ideas, and roadmap items. Key aspects include:
1) Bugs, ideas, and roadmap items go through review/planning processes before estimation and development.
2) Sprints include planning, daily standups, demos, and retrospectives to deliver user stories.
3) A Trello board shows the workflow from ideas to completed features through estimating, development, and deployment.
4) Metrics are needed to measure feature value through both quantitative and qualitative methods.
A presentation given for the PMI community in November 2008. The presentation shows the main difference between traditional and agile project management.
New York Bestseller Jake Knapp’s book, Sprint, explores how companies and teams can replicate Google’s sprint process to solve a problem within five days.
So how does a design sprint actually work, and how can you use a sprint to devise effective solutions in such a short period of time?
Enhance your productivity through design sprints, you’ll learn:
- What is a Design Sprint
- Design sprint case studies and success stories
- How you can run a design sprint effectively
A presentation given for the PMI community in November 2008. The presentation shows the main difference between traditional and agile project management.
New York Bestseller Jake Knapp’s book, Sprint, explores how companies and teams can replicate Google’s sprint process to solve a problem within five days.
So how does a design sprint actually work, and how can you use a sprint to devise effective solutions in such a short period of time?
Enhance your productivity through design sprints, you’ll learn:
- What is a Design Sprint
- Design sprint case studies and success stories
- How you can run a design sprint effectively
The team at GV (Google Ventures) has graciously published a fabulous book, "Sprint," in which Jake Knapp with John Zeratsky and Braden Kowitz comprehensively explain their Design Sprint Methodology. It's a five-day process that spans from Monday to Friday. Design Sprint Events or Activities are respectively Understand-Diverge-Decide-Prototype-Validate. This presentation focuses on Event 1, which is "Understand."
In this presentation, the visual tool of the Design Sprint (DS) Map is used to summarize "Understand" tasks as a visual checklist. In addition, the DS Map is used to present a worksheet that is used to visually collect, organize, select, and test (C.O.S.T.) ideas during a Design Sprint. Included in the presentation are three case studies that illustrate how the "Understand" activity is used on Day (Event) 1 of the 5-Day Sprint.
This presentation was used in "Agile workshop for FPT Aptech Hanoi students" in December 2012.
This doc covers most of core practices of an agile developer.
Distinguishing Between Healthy and Unhealthy Mistakes: How to Fail Like A ProHighland
The Failure Revolution is well underway—a celebration of missteps, failures, and errors as pivotal moments of learning and growth. But how is a blunder different from a moment of growth? What types of mistakes are worth the learning, and which costly ones would rather be avoided?
In launching over 250 digital products over the past 20 years, Highland is well-versed in the language of failure. We’re taking a moment to reflect on which failures are an intentional part of the process, which ones take us by surprise, and which ones we help organizations avoid.
Come join us for some memorable stories of hits and misses.
Attendees will learn:
• The most common failure patterns in the digital innovation process, with examples from our lived experience.
• How to recognize and avoid the most common failure points and patterns.
• How to discern learning moments from expected failures, or worse—unexpected failures.
• How to move from fearing failure to living failure, and dodging fatal failure.
Erste Bank — How to Cut off Development Times & Get Feedback From Real Users,...Agile Austria Conference
The talk will be showing through examples how to get immediate feedback from real users while skipping the development period and use Design Sprints and prototyping for it. It shows the benefits of getting user experience first and how to incorporate this in real products development life while living the Scrum cycles.
Event 5, which focuses on the activity of "Validate," is the final task of a 5-Day Lean Design Sprint. This presentation provides visual checklists and templates that can be used to facilitate the activity of "Validate."
How to efficiently build great products in a startupRoger Dudler
There are many ways to build a software product, but it’s quite hard to find the balance between a sustainable technical foundation, product innovation, implementation speed and prioritization of features. While having thousands of customers in a SaaS market, a start-up might soon have enterprise customers with special needs to take care of. This involves a lot of potential challenges – a tough journey.
In this workshop, you’ll learn about Frontify’s tactics on software product management, pitfalls and learnings as well as practical advice on tools, recruiting and more. Your business-related and technical questions will be answered by the Founder & CTO of Frontify, a fast-growing St. Gallen-based start-up.
Overview of agile values
This presentation shows some core concepts that make agile software development different.
This will help your team familiar with agile concepts and start boosting your team performance.
Adopt Your Message & Align Internal StakeholdersUXDX1
Buy-in is one of the biggest challenges in any organisation, made harder in a large and mature organisation. But how did a team from Africa's Talking get over this hurdle and rolled out 4+ products this year alone.
In this session, Anne will talk through how she created alignment between UX and engineering that allowed for more efficient processes and better product release times. She will touch on:
- How to adopt your communication style depending on your stakeholders;
- How to document new processes of communication;
- The importance of implementation to ensure overall alignment
The Business Analyst’s Critical Role in Agile ProjectsTechWell
Are you a business analyst, wondering how you fit into agile projects? Are you a ScrumMaster who wants to work with business analysts for a stronger project team? Are you a product owner who needs to supercharge your product backlog? Mark Layton introduces you to the critical role of the business analyst on agile projects. Get the essential information business analysts need to know to be successful members of an agile project team. Learn how business analysts can use their product knowledge and requirements translation skills to support product owners and stakeholders. Discover the role of product owner agent and why business analysts do well in that role. Learn how business analysts approach documentation—especially requirements—on agile projects. Dive into the details of the product backlog and user stories. Bring your questions and be ready to learn all about the who and the how of the business analyst in agile projects.
As Agile become mainstream increasingly organizations are looking to double down on the role of the Product Owner encouraging them to manage the intersection between technology and the business. But Product Ownership is a difficult role as it tries to balance the needs of the business with the reality of software delivery. Also, for many organizations there is some ‘confusion’ with existing roles of business analyst, product manager or even project manager. What does the product owner do anyway?
In this talk Dave West, Product Owner and CEO Scrum.org, the home of Scrum and Professional Scrum Trainer with Prowareness Rob van Lanen describe the genesis of the Product Owner role and how many organizations are dealing with the challenges of slotting this key role into existing product, project and release roles. They will introduce some techniques such as user centric design, and hypophysis based development and describe how approaches such as Lean Startup and pragmatic marketing are providing product owners with a tool box to do their job.
Recorded Webinar can be found at :-https://www.scrum.org/resources/who-product-owner-anyway
CLARIFICATION:
Understanding the Qur'anic methodology.
Clarifying confusion cause by attempts of those who raise the 'fitnah' regarding Islamic Theology - quoting but yet misinterpreting Qur'anic verses.
Explanation against those misinterpreting the MUTASHABIHAT 'allegorical' verses, insisting that their meaning to be in the literal sense by forbidding TA''WIL.
The team at GV (Google Ventures) has graciously published a fabulous book, "Sprint," in which Jake Knapp with John Zeratsky and Braden Kowitz comprehensively explain their Design Sprint Methodology. It's a five-day process that spans from Monday to Friday. Design Sprint Events or Activities are respectively Understand-Diverge-Decide-Prototype-Validate. This presentation focuses on Event 1, which is "Understand."
In this presentation, the visual tool of the Design Sprint (DS) Map is used to summarize "Understand" tasks as a visual checklist. In addition, the DS Map is used to present a worksheet that is used to visually collect, organize, select, and test (C.O.S.T.) ideas during a Design Sprint. Included in the presentation are three case studies that illustrate how the "Understand" activity is used on Day (Event) 1 of the 5-Day Sprint.
This presentation was used in "Agile workshop for FPT Aptech Hanoi students" in December 2012.
This doc covers most of core practices of an agile developer.
Distinguishing Between Healthy and Unhealthy Mistakes: How to Fail Like A ProHighland
The Failure Revolution is well underway—a celebration of missteps, failures, and errors as pivotal moments of learning and growth. But how is a blunder different from a moment of growth? What types of mistakes are worth the learning, and which costly ones would rather be avoided?
In launching over 250 digital products over the past 20 years, Highland is well-versed in the language of failure. We’re taking a moment to reflect on which failures are an intentional part of the process, which ones take us by surprise, and which ones we help organizations avoid.
Come join us for some memorable stories of hits and misses.
Attendees will learn:
• The most common failure patterns in the digital innovation process, with examples from our lived experience.
• How to recognize and avoid the most common failure points and patterns.
• How to discern learning moments from expected failures, or worse—unexpected failures.
• How to move from fearing failure to living failure, and dodging fatal failure.
Erste Bank — How to Cut off Development Times & Get Feedback From Real Users,...Agile Austria Conference
The talk will be showing through examples how to get immediate feedback from real users while skipping the development period and use Design Sprints and prototyping for it. It shows the benefits of getting user experience first and how to incorporate this in real products development life while living the Scrum cycles.
Event 5, which focuses on the activity of "Validate," is the final task of a 5-Day Lean Design Sprint. This presentation provides visual checklists and templates that can be used to facilitate the activity of "Validate."
How to efficiently build great products in a startupRoger Dudler
There are many ways to build a software product, but it’s quite hard to find the balance between a sustainable technical foundation, product innovation, implementation speed and prioritization of features. While having thousands of customers in a SaaS market, a start-up might soon have enterprise customers with special needs to take care of. This involves a lot of potential challenges – a tough journey.
In this workshop, you’ll learn about Frontify’s tactics on software product management, pitfalls and learnings as well as practical advice on tools, recruiting and more. Your business-related and technical questions will be answered by the Founder & CTO of Frontify, a fast-growing St. Gallen-based start-up.
Overview of agile values
This presentation shows some core concepts that make agile software development different.
This will help your team familiar with agile concepts and start boosting your team performance.
Adopt Your Message & Align Internal StakeholdersUXDX1
Buy-in is one of the biggest challenges in any organisation, made harder in a large and mature organisation. But how did a team from Africa's Talking get over this hurdle and rolled out 4+ products this year alone.
In this session, Anne will talk through how she created alignment between UX and engineering that allowed for more efficient processes and better product release times. She will touch on:
- How to adopt your communication style depending on your stakeholders;
- How to document new processes of communication;
- The importance of implementation to ensure overall alignment
The Business Analyst’s Critical Role in Agile ProjectsTechWell
Are you a business analyst, wondering how you fit into agile projects? Are you a ScrumMaster who wants to work with business analysts for a stronger project team? Are you a product owner who needs to supercharge your product backlog? Mark Layton introduces you to the critical role of the business analyst on agile projects. Get the essential information business analysts need to know to be successful members of an agile project team. Learn how business analysts can use their product knowledge and requirements translation skills to support product owners and stakeholders. Discover the role of product owner agent and why business analysts do well in that role. Learn how business analysts approach documentation—especially requirements—on agile projects. Dive into the details of the product backlog and user stories. Bring your questions and be ready to learn all about the who and the how of the business analyst in agile projects.
As Agile become mainstream increasingly organizations are looking to double down on the role of the Product Owner encouraging them to manage the intersection between technology and the business. But Product Ownership is a difficult role as it tries to balance the needs of the business with the reality of software delivery. Also, for many organizations there is some ‘confusion’ with existing roles of business analyst, product manager or even project manager. What does the product owner do anyway?
In this talk Dave West, Product Owner and CEO Scrum.org, the home of Scrum and Professional Scrum Trainer with Prowareness Rob van Lanen describe the genesis of the Product Owner role and how many organizations are dealing with the challenges of slotting this key role into existing product, project and release roles. They will introduce some techniques such as user centric design, and hypophysis based development and describe how approaches such as Lean Startup and pragmatic marketing are providing product owners with a tool box to do their job.
Recorded Webinar can be found at :-https://www.scrum.org/resources/who-product-owner-anyway
CLARIFICATION:
Understanding the Qur'anic methodology.
Clarifying confusion cause by attempts of those who raise the 'fitnah' regarding Islamic Theology - quoting but yet misinterpreting Qur'anic verses.
Explanation against those misinterpreting the MUTASHABIHAT 'allegorical' verses, insisting that their meaning to be in the literal sense by forbidding TA''WIL.
“A BEGINNERS’ COURSE ON ISLAM”
Lessons on Fardhu ‘Ain in English for Adultsconducted by Ustaz Zhulkeflee Hj Ismail
HADITH OF JIBRA-’IL
LESSON # 9
“ARKAAN AL-IIMAN”
Articles of Faith / Belief
BELIEVE IN QADHA’ AND
QADR OF ALLAH
Newcastle University & T4 Site Manager: TERMINALFOUR t44u 2013Terminalfour
'Newcastle University & T4 Site Manager':Paul Thompson and Mike Sales will discuss how Newcastle University have set up TERMINALFOUR Site Manager to support many small high turnover sites for research projects and conferences.The T4 API has been used to create a bespoke Handler to clone a template site, manage users and permissions, and send them documentation.
About Agile Programmer's skill sets
Ultimate Agilist Tokyo 2012
This presentation will be used tomorrow. after that session I have a plan to update this slide.
This slide is for Ultimate Agilist Tokyo in Japan. 2012.Nov.
I want to think about agile programmer's skill set. and I want to introduce ICAgile to Japan.
I analyzed agile value, principles, practices and ICAgile.
and participant members created some mandatory skill set in this session.
See this blog entry , that will be better.
http://simple-architect.blogspot.jp/2012/11/agile-programmers-skill-set-ultimate.html
Recording can be watched here: https://t.co/OLtqJNCMUf
Impact Mapping is a strategic planning technique that prevents Agile organizations from getting lost while building products and delivering projects by clearly communicating assumptions, helping teams align their activities with overall business objectives, and helping make better roadmap decisions. Impact mapping can help you make an impact, not just ship software. In this Scrum Alliance® Collaboration at Scale webinar, we presented an overview of Impact Mapping, outlined how it fits into Scrum-centric Agile practices, and explored some of the unique opportunities and drawbacks that occur when leveraging Impact Maps in distributed teams.
The Devbridge Way: Lean Requirements, Rapid Prototyping, Dual-track Scrum and...Devbridge Group
On September 13, 2016, Devbridge Group hosted the Chicago Agile community to discuss Lean Requirements, Rapid Prototyping, Dual-track Scrum and Scrum at Scale. Professionals from Devbridge Group's Product Management Team shared their real-life experiences with these practices. For more on these topics, visit devbridge.com.
The Scrum Master and the Product Owner are critical to success of agile development teams using Scrum with the authority to make changes to the process, suggest team members take action, and empower members to do tasks correctly, in support of increasing the probability of project success.
Dev conf 2018 DesOps - Prepare Today for Future of Design Samir Dash
The deck I am to present at
DevConf 2018, on 5th August, at Christ University, Bengaluru
More info at: http://desops.io/2018/07/04/talk-at-devconf18-designops-prepare-today-for-future-of-design/
A proposed framework for Agile Roadmap Design and MaintenanceJérôme Kehrli
Maintaining a relevant and meaningful roadmap while adopting a state of the art Agile methodology is challenging and somewhat antonymous.
This presentation proposes a framework for designing and maintaining an Agile Roadmap.
There's a lot of content available about design sprints; what they are, how to run them, why they are useful. Key to them being successful is having a diverse team, including engineers. Very little of the content available covers the important role engineers play at this stage of product creation.
Similar to Amee product workflow - 2012.08.16 (20)
2016 Nov - World Usability Day Prague - Planet Friendly Digital DesignChris Adams
This is the deck I presented at World Usability Day in Prague, Czech Republic in 2016. It's loosely based around the 4 pillars of sustainable design as described in Tim Frick's book, Design for Sustainability and was followed by a short workshop.
Getting to The Loop - London Wordpress Meetup July 28thChris Adams
This is a slightly modified version of the talk I gave at the London Wordpress meetup.
I'm putting it up here a) for people who were taking notes last night and b) to shame me into putting a polished version up here for people who couldn't make it.
thanks for @folletto for providing the graphics that split up the endless code snippets.
Postal: SiCamp Nov 2008 Submission PresentationChris Adams
My submission presentation for Social Innovation Camp in December.
Feedback welcome, but volunteers to help build this if it gets accepted are even more welcome.
2. Clear, visible process
across the company
Measurable value from
development
Lightweight, easily
adaptable to future
change.
Thursday, 16 August 12
3. Bugs
Ideas Planning Development Measure
Roadmap
Thursday, 16 August 12
4. Bugs Bugs
Defects in the product as reported by customers or staff, or issues
raised by any error logging tools.
Ideas
Ideas Planning Development
Suggestions for the product come from inside the company, or from
external sources, like customer service channels, or any external
forums for discussion of the product.
Roadmap Roadmap
Company strategy, defined in terms of high level requirements, or
high level themes for user stories.
Thursday, 16 August 12
5. Planning
Bugs
Input from each board has a qualifying
process before it makes it to planning.
Bugs are confirmed as reproducible,
Ideas are described in enough detail to be
Ideas Planning Development
understood by a product manager
Items on the roadmap are confirmed as still
relevant to the company strategy.
Requirements or draft stories are fleshed
out here, with sketches or wireframes, until
they are in a state that can be estimated
Roadmap upon by a development team, and
delivered.
Thursday, 16 August 12
6. Planning
Bugs
Developer Estimation
Review Meeting
Ideas Planning Development
Roadmap
Thursday, 16 August 12
7. Planning
Bugs
Developer Estimation
Review Meeting
Ideas Planning Development
One developer and the product
manager reviews any story or
requirement that needs an
estimate in this meeting.
Roadmap Together they weed out technical
issues, and dependencies before
a group estimation, or identify
areas that need further definition
before estimation is possible.
Thursday, 16 August 12
8. Planning
Bugs
Developer Estimation
Review Meeting
Ideas Planning Development
In an estimation meeting the
developers, and the product
manager run through the stories
and allocate a points value to
Roadmap each story based on perceived
difficulty across the whole team.
Thursday, 16 August 12
9. Sprint planning and
development
Bugs
Sprint Daily Sprint Retro-
planning Standup Demo spective
Ideas Planning Development
Roadmap
Thursday, 16 August 12
10. Sprint planning and
development
Bugs
Sprint Daily Sprint Retro-
planning Standup Demo spective
Ideas Planning Development
Stories and requirements are assigned to a sprint
in a sprint planning meeting.
A product manager reviews the stories going into
the sprint with the development team, and the
Roadmap
development team commit to delivering the work,
based on the velocity agreed in the last sprint
retrospective.
Thursday, 16 August 12
11. Sprint planning and
development
Bugs
Sprint Daily Sprint Retro-
planning Standup Demo spective
Ideas Planning Development
Every morning, the development team and the
product manager runs a 15 min stand-up meeting,
answering the following questions:
- What you did yesterday?
Roadmap doing today?
- What are
- What is blocking you?
Sprint progress is reviewed, against what was
committed to for the sprint.
Thursday, 16 August 12
12. Sprint planning and
development
Bugs
Sprint Daily Sprint Retro-
planning Standup Demo spective
Ideas Planning Development
On the last day of the sprint, the team members
run through the work they’ve completed to the
rest of the team, and the product manager.
Original ‘owners’ of an idea are optionally
Roadmap to see the requested story delivered.
present,
Thursday, 16 August 12
13. Sprint planning and
development
Bugs
Sprint Daily Sprint Retro-
planning Standup Demo spective
Ideas Planning Development
After the sprint demo, comes the retrospective.
The team discusses the good and bad aspects
of the sprint, and any changes to their process
they’d like see internally.
The team commit to a velocity for the next
Roadmap
sprint, based on the points delivered, to help
plan the next sprint.
Thursday, 16 August 12
14. Bugs
Ideas Planning Development
Roadmap
Thursday, 16 August 12
16. Bugs
Ideas Planning Development
Roadmap
Filing bugs
Thursday, 16 August 12
17. Reviewed &
Inbox Accepted
needs input
Bugs
Bug with
description
Ideas Planning Development
Roadmap
Thursday, 16 August 12
18. Reviewed &
Inbox Accepted
needs input
Bugs Bug with
description, and
steps to
reproduce, etc.
Ideas Planning Development
Roadmap
Thursday, 16 August 12
19. Reviewed &
Inbox Accepted
needs input
Bugs Bug with
description, and
steps to
reproduce, etc.
Ideas Planning Development
Roadmap
Thursday, 16 August 12
20. Bugs
Ideas Planning Development
Roadmap
Collecting Ideas
Thursday, 16 August 12
21. Awaiting Review Under review Accepted
Bugs
Idea from inside
the company
Ideas Planning
External customer Development
request
Roadmap
Ideas come from any where inside, and
outside the company
Thursday, 16 August 12
22. Awaiting Review Under review Accepted
Bugs
Idea from inside
the company
Ideas Planning
External customer Development
request
Roadmap
A product manager works with the originator,
to flesh them out.
Thursday, 16 August 12
23. Awaiting Review Under review Accepted
Bugs
Idea from inside
the company
Ideas Planning
External customer Development
request
Roadmap
When it’s understood, it can be moved to the
planning board
Thursday, 16 August 12
24. Bugs
Ideas Planning Development
Roadmap
How the roadmap
drives product
Thursday, 16 August 12
25. Now
To avoid waste,
user stories and
features only
become more
detailed and
granular as they
get closer to
development.
Future
Thursday, 16 August 12
26. Q3 Q4 2013
Bugs
Update sign-in Public sign-in for Scope 3
process companies calculation
Ideas Defined and Planning Development
documented API CRC Reporting
RAG status on
Roadmap suppliers
The Roadmap gives a high level view of areas
of focus in coming months.
Thursday, 16 August 12
27. Q3 Q4 2013
Bugs
Update sign-in Public sign-in for Scope 3
process companies calculation
Ideas Defined and Planning Development
documented API CRC Reporting
RAG status on
Roadmap suppliers
New cards are created based on these
themes in planning
Thursday, 16 August 12
28. Bugs
Ideas Planning Development
Roadmap
Defining deliverable
work
Thursday, 16 August 12
29. Ready for
To Do Spec and dev review UX and Design
Estimation
User story
Planning Development
The aim is to get cards from the left, to the right.
Thursday, 16 August 12
30. Ready for
To Do Spec and dev review UX and Design
Estimation
User story User story
Planning Development
It’s okay for cards to be sent back and forth
between stages if they need further clarification
Thursday, 16 August 12
31. Ready for
To Do Spec and dev review UX and Design
Estimation
User story User story
Planning Development
It’s okay for cards to be sent back and forth
between stages if they need further clarification
Thursday, 16 August 12
32. Ready for
To Do Spec and dev review UX and Design
Estimation
User story User story
Planning Development
It’s okay for cards to be sent back and forth
between stages if they need further clarification
Thursday, 16 August 12
33. Ready for
To Do Spec and dev review UX and Design
Estimation
User story User story
Planning Development
Cards are ready when they fit the format for a
product, are well understood and have clear
measurement criteria
Thursday, 16 August 12
34. Bugs
Ideas Planning Development
Roadmap
Delivering the work
Thursday, 16 August 12
35. Estimated Current sprint In Progress Pull Request QA Complete
A user story
A second
story
A user story
A second
story
Prioritising estimated stories
Thursday, 16 August 12
36. Estimated Current sprint In Progress Pull Request QA Complete
A user story A user story
A second A second
story story
Building a sprint, based on
Thursday, 16 August 12
velocity
37. Estimated Current sprint In Progress Pull Request QA Complete
A second A user story
A user story
story
A second
story
Picking up work from the
Thursday, 16 August 12
current sprint backlog
38. Estimated Current sprint In Progress Pull Request QA Complete
A second A user story
A user story
story
A second
story
Code review from other
Thursday, 16 August 12
developer in pull request
39. Estimated Current sprint In Progress Pull Request QA Complete
A second A user story
A user story
story
A second
story
QA performed by product
Thursday, 16 August 12
owner
40. Estimated Current sprint In Progress Pull Request QA Complete
A second A user story
A user story
story
A second
story
Feature ready for release
Thursday, 16 August 12
41. Completed features by this point
should be in a state to be
Complete 0.17.1 0.17.2
deployed to production.
A user story A user story Bug fix
Depending on the business
need, they can be pushed
directly to production (in the
A another
story User story case of severe bugs etc), or as
specific releases.
The aspiration here is to working,
QA’d, and CR’d code
automatically pushed to
production, where features can
be rolled out gradually, or
switched on or off independently
of code releases.
Deployment
Thursday, 16 August 12
42. Bugs
Ideas Planning Development Measure
Roadmap
Thursday, 16 August 12
43. Measuring the value of features
Bugs
Development doesn’t end at deployment.
Ideas every feature needs accompanying metrics, but
Not Planning Development Measure
most should have them.
Did a feature have the expected result?
Roadmap can we tell?
How
Are we measuring the right data here?
How might we improve the feature?
How are we getting feedback?
Thursday, 16 August 12
44. Measuring the value of features
Bugs
Quantitive Qualitative
Ideas Planning In-app chat
Development Measure
Kissmetrics (eg. Olark)
(individual user
interactions) Support software
(desk.com)
Google Analytics
Roadmap
(larger trends, User testing
and heatmaps) (recording how features
are used in beta / testing)
Ad-hoc API/DB
Problem &
Queries
solution interviews
( showing prototypes to
users before building)
Thursday, 16 August 12