For this meet up we want to understanding the how startups go about making revenue projections.
A revenue projection is simply a guess about how much income your startup will generate once your startup starts offering its product or service to customers.
This process begins with making some assumptions about key variables that.determine the revenue of a firm.
To get started lets use this worksheet. (Click here)
Agenda
1. Purpose of competitive comparison — goal create a graphic
3. Review handout
4. Construct a Competitive Comparison for your startup
Agenda
1. Determine the colors of your company
2. Determine images for your tagline graphics
3. Save these images as png or jpg files (do not copy and paste into doc)
4. Determine tagline message
5. Post tagline messages to project blog
This work will be displayed on your business website.
A wireframe of your homepage is due on Friday.
Today, we want to determine the different costs that each of your startups will incur.
First, we will go through different kinds of cost. I suggest that you take notes while we talk about each of these costs.
Now, you want to do research to determine the dollar amount for each of the major costs.
Here is some feedback based on the conversations that I had with different teams.
For starters, consider the following template:
As a (who wants to accomplish something)
I want to (what they want to accomplish)
So that (why they want to accomplish that thing)
Here is an example:
As a bank customer
I want to withdraw money from an ATM
So that I’m not constrained by opening hours or lines at the teller’s
Applying this method to some of the projects I get the following
As a caregiver
I want to provide my patients with pictures and videos from their past
So that I can engage in meaningful conversation and social interaction
As a family member of a loved one suffering from dementia
I want to be able to offer suggestions to caregivers
So that I can participate in caregiving even thou I live miles away
As an Esports player
I want to
As an environmentally conscious student
I want a reliable and efficient way to recycle my plastic waste
So that I can participate in the solving the plastic waste problem
As a socially conscious high school student
I want to participate in a social movement that fights human trafficking
So that I can help create a more just society
As an environmentally conscious student
I want a purchase sustainable clothing that is fashionable
So that I can participate in the solving the plastic waste problem
Today, we want to understand what a user story is and how to write this kind of story.
Here is a simple formula for writing user stories:
As a [user role], I want [a feature or goal] so that [a benefit or reason].
Here are a few examples:
As a customer, I would like a one-click purchase option so that I can save time when buying online.
As an editor, I would like to review content before it is published so that I can assure it is optimized with correct grammar and tone.
As a student, I would like to be able to flag content so that I can find it more easily in the future.
As a customer, I would like to be able to flag content so that I can find it more easily in the future.
As an activist, I would like a community so that I can share ideas and collaborate with like minds.
What do you notice about these simple story starters?
One way to better understand your user story is referred to as “As a… I want to… So That…” …
Using this method, teams respond to the following prompts:
As a (who wants to accomplish something)
I want to (what they want to accomplish)
So that (why they want to accomplish that thing)
Hers is an example:
As a bank customer
I want to withdraw money from an ATM
So that I’m not constrained by opening hours or lines at the teller’s
WRITE YOUR OWN NOW…
You may have notice that your product or service has multiple users. If so, you will need to write several story starters.
Your next step is to expand your user stories.
Here are some helpful guidelines to follow when writing your user story:
1. Definition of “Done” — The story is generally “done” when the user can complete the outlined task, but make sure to define what that is.
2. Outline subtasks or tasks — Decide which specific steps need to be completed in order to solve the problem and how the user will complete these steps.
Click here for a table that will help you organize this information.
Finally, if you need a simple way to prioritize your user stories? Try the MoSCoW approach.
MoSCoW is an acronym that stands for:
Must haves – we need these stories in order to launch the project.
Should haves – these are of high importance, but are not show-stoppers for the next release.
Could haves – If we get a couple of these in it would be nice, but they can easily be moved to the next release.
Wants – These are not a priority but we want to keep track of them as possibilities for future releases.
For our projects, you should address the Must haves and then and only then the Should haves.