IdeaWazaWiki - User contributions [en]

Wiki business plan

2007-10-22T05:42:17Z

70.110.42.219: /* Current Status */ add a qualifying statement

This is a collaborative business plan. What will this business do? What will this business sell? Who will particpate in this business? How will it make money? Will it benefit society? These are the questions to answer. Be creative, be imaginative.

There are many projects, like RepRap, OpenCores, OLPC, Cambrian House, Zopa, WikiMedia, etc, in which people collaborate to create something they deem good.

{{main|Wikipedia:Business plan}}
: This page was adapted from Wikipedia: [[Wikipedia:Content of a business plan|Content of a business plan]].

Things to keep in mind:
* There is no fixed content for a business plan.
* The content and format of the business plan is determined by the goals and audience.
* A business plan should contain whatever information is needed to decide whether or not to pursue a goal.
* Once a business plan has been developed, the key decision making points are usually summarized in an [[#Executive Summary|executive summary]].

Business plans typically cover five major content areas:
* [[#Organizational Background|Background information]]
* [[#Marketing Plan|A marketing plan]]
* [[#Operational Plan|An operational plan]]
* [[#Financial Plan|A financial plan]]
* A discussion of the [[#Decision Making Criteria|decision making criteria]] that should be used to approve the plan.

== Executive Summary ==
The executive summary summarizes the key points of the business plan. It should define the decision to be made and the reasons for approval. The specific content will be highly dependent on the core purpose and target audience. To get a sense of the difference the purpose and target audience can make, here are three different sets of key points for an executive summary - one for a loan request, one for a start-up seeking venture finance, and one for an internal plan. Items unique to a particular kind of plan are highlighted in bold:

A loan request executive summary might contain the following information:
* Company information: name of company, '''years in business''', legal structure, minority and majority owners
* Brief description of project
* '''Amount and length of loan'''
* Objective reasons why the bank should be confident that the loan will be paid back. This likely will include
** Financial track record
** The future revenue stream
** Any contracts in place that might guarantee the revenue stream is more than just a forecast.

For a new venture, the executive summary might contain:
* Company information: name of company, '''proposed legal structure''', current legal structure, minority and majority investors.
* '''Amount of investment requested'''
* '''Expected terminal value'''
* '''Description of market opportunity'''
* '''Objective reasons why the market opportunity can be exploited by this particular team'''

For an internal project plan, the executive summary might look like this:
* Company information: '''not applicable'''
* Description of project
* '''Project mandate: who requested the proposal, who is being assigned to carry it out'''
* '''Strategic''', '''tactical''' and financial justifications
* Summary of resources needed: '''staff''', funds, '''facilities'''

In some cases information will overlap. For example, some of the reasons why a loan is likely to be repaid might equally as well be used as justification for the kind of extraordinary return expected by venture capitalists.

In some cases the business plan as a whole contains similar information, but for one type of plan it is mere detail and for another it is a key decision making factor. For instance, both start-ups and internal projects need staff and facilities. However the staffing and facilities needs are considered details in a plan for start-up financing. In a plan for internal projects they are key elements and, in fact, may be the only resources needed.

Key points:
* Funding will come from a diverse size of monetary investments, from fifty cents to an unlimited amount.
* The products that will be used to create a return on investment will be created by and decided upon by the investors and community involved in the business.

== Organizational Background ==
In a written plan information may appear in a separate section, an appendix, or may be omitted all together depending on the nature of the plan. If the plan is directed at people outside of the company, a brief synopsis may appear in the executive summary. This will be supplemented with a more detailed discussion else where in the plan.

Wikiversity was established around August 2006. It is part of the Wikimedia Foundation and is a sister project to Wikipedia, a rather large project. Participants of Wikiversity can use Wikiversity as a way to explore different modes of learning. Specifically, "learning by doing" is the prefered way to learn. Businesses, can involved different people from a myriad of different disciplines. Running a business can be an invaluable learning experience for those who participate in such an endeavor. Wikiversity is an open community. Anyone can join as long as they adhere to the community standards arrived upon via the consensus of the community. In general, if participants act civil, are bold, and assume good faith in others, things function fairly smoothly, and because Wikiversity is a wiki, that anyone can edit, it tends to grow.

With all that in mind, this business plan is a seed that may or may not grow. Theoretically, because there are over a billion users on the Internet, and because everyone has access and the rights to constructively edit this plan in good faith, it could potentially become something that is useful to both individuals and society on a wider level. It seems that social entities and systems come about because of a need and a want, and perhaps this plan could fulfill an unfilled need and want.

So in summary, anyone can join this organization, and anyone can help fullfill the mission that is decided upon by the participants.

=== Mission Statement ===
A mission statement is a brief (one sentence or less) description of a company or other organization's purpose. It typically explains what the organization provides to its clients, in general terms that most of the employees can relate to. Although a company might use its mission statement as an advertising slogan, a more common use is to remind executives and employees of the overall goal they are expected to pursue.
<center><big><big><big>'''Do good.'''</big></big></big></center>

=== Current Status ===
* Number of employees
: 0
* Annual sales figures
: 0
* Key product lines
: To be determined.
* Location of facilities
: There are no facilities at this point.
* Current stage of development (start-ups)
On a scale from 1 to 10, a 0.
* Corporate structure - in the U.S. the options are:
** [[Wikipedia:Sole proprietor|Sole proprietor]]
** [[Wikipedia:Partnership|Partnership]]
** [[Wikipedia:Joint Venture|Joint Venture]]
** [[Wikipedia:Publicly traded corporation|Publicly traded corporation]]
: If micro to macro financed, could sorta be this
** [[Wikipedia:Limited liability company|Limited liability company]]
: Maybe
** [[Wikipedia:Public utility|Public utility]]
** [[Wikipedia:Non-profit organization|Non-profit organization]]
: Co-op perhaps
* Names of the majority investor, if any
: Not applicable

=== History ===
* Founding date
: 19 October 2007
* Major successes
* Strategically valuable learning experiences

=== Management Team ===
* Board members
* Owners
* Senior managers
* Managing partners
* Head scientists and researchers

== Marketing Plan ==
The marketing plan has five objectives:
If the product is a new product with no existing market, one must identify all substitute products. For each significant substitute product one must explain:
* Name, features, why substitute, why proposed product better
** Create a product with a subpage like [[/One Laptop Per Person/]], [[/wPhone/]] and so forth
* Switching costs and why new product justifies switching
* Expected adoption dynamics
* Expected role once market begins to develop (see above for existing products)

=== Pricing ===
* Chosen price points
* Proposed [[Wikipedia:Pricing|pricing strategy]]
* Research supporting chosen price points

=== Demand Management ===
In economics, demand management is the art or science of controlling economic demand to avoid a recession. The term is also used to refer to management of the distribution of, and access to goods and services on the basis of needs. An example is social security and welfare services. Rather than increasing budgets for these things, governments may develop policies that allocate existing resources according a hierarchy of need.

=== Distribution ===
* [[Wikipedia:Distribution (business)|Distribution strategy]]
* List of major distributors
* Current status of negotiations

=== Promotion and Brand Development ===
* [[Wikipedia:Promotion (marketing)|Promotion strategy]]
The promotion of this company and this companies products will be done virally.

== Operational Plan ==

=== Current Product/Project Status ===
None as of yet.

=== Research and Development Plan ===
Keep your eyes open. Think about what would be useful and socially beneficial.

=== Manufacturing/Deployment Plan ===
* [[Wikipedia:Supply chain|Supply chain]] requirements
* Production inputs
* Facility requirements - size, layout, capacity, location
* Equipment requirements
* Warehousing needs for raw materials, finished goods
** Space requirements

=== Information and Communications Technology Plan ===
* Systems needed
** Operations: Billing, HR, SCM, CRM, Knowledge bases, etc
** Websites: internal, public
* Security and privacy requirements
* Hardware requirements
* Off-the-shelf software needed
* Custom development requirements

=== Staffing Plan ===
Once capital is accrued utilize those desiring to learn, and where someone can't fullfill a role in a safe learning capacity, hire someone to do it and teach others how to do what they are doing when appropriate.

==== Staffing Needs ====
* List of roles
:Collaborators to write the business plan.
* Management structure
:Loose. Management is done by those who choose to take a leadership posistion.
* For each role
:* Number of employees
::0
:* Proposed compensation
::What is appropriate, available and fair. Perhaps for right now, the satisfaction that you are potentially contributing to something good would be enough.
:* Availability
::Quite.

==== Union issues ====
None.

==== Training Requirements ====
Utilize Wikiversity

==== Hiring Time Table ====
No hurry.

==== Staffing Budget ====
$0

=== Business Process Outsourcing Plan ===

=== Asset Development Plan ===

==== Intellectual Property Plan ====
* Intellectual property inventory
* Portfolio development plan

==== Acquisition Plan ====
Some business plans gain competitive advantage by buying companies up and down the value chain. Some gain competitive advantage by buying up companies and consolidating them. Sometimes a business plan will seek to earn a superior return by adding superior management talent to an existing weak company.

For more information see: [[Wikipedia:Mergers and Acquisitions|Mergers and Acquisitions]].

When acquisitions form a major part of the business strategy, the acquisition plan needs to be included in the business plan.
* Acquisition strategy
* Proposed acquisition targets
* Effect on market structure (if consolidation plan is being proposed)

==== Organizational Learning Plan ====
The organizational learning plan discusses what lessons will be learned from the marketing, operational, and finance plans and how those lessons will be consolidated to gain strategic advantage.
* Market sensing - organization's method for collecting information about customers (George Day)
* [[Wikipedia:Strategic Staircase|Strategic Staircase]] - the accumulation of future competencies by building on existing competencies. (Michael Hays, Costas Markides)

=== Cost Allocation Model ===
If variable costs play an important role in the business plan, it may be helpful to include a cost allocation model. This is particularly true if one has a unique business model that creates competitive advantage by transforming traditionally fixed costs into variable costs.
* Fixed cost
* Variable costs

== Financial Plan ==
For more information, see [[Wikipedia:Financial plan]].

=== Current Financing ===
* Key investors or owner:
** You.
* Angels, friends, and family:
* Existing loans and liabilities
** Terms, obligations
*** None.

=== Funding Needs ===
To be determined.

=== Funding Plan ===
* IMF - no
* World Bank - no
* Micro investments
: Everyone earns a share in the profits depending on how much they invest.
: Share of profits = (% of Business owned) * (Net earnings - a certain % reinvested in the company)
: % of business owned = (An individual's investment) / (Total all owners have ever invested)

=== Financial History ===

=== Financial Forecasts ===
* Sometimes called [[wikipedia:pro forma|pro forma]]s
** Balance sheet
** Income statement
** Cash flow statement
* 1-3-5-7 year projections (depends on length of project)
** For loans, repayment period determines length of projections, i.e. a six month loan doesn't need seven year forecasts
** For investments point at which returns stabilize ([[wikipedia:terminal value|terminal value]]) determines length of forecast
* Annual, quarterly, and monthly versions should be provided
* Graphs of key values often helpful: gross revenue, EBITDA, NPV, etc.
* Financial portions of the marketing, asset development, and operations are often placed in this section rather than in the section discussing th plan. They are viewed as elaboration on the various line items in the pro-formas.

=== Valuation ===

== Risk analysis ==
For more information, see [[Wikipedia:Risk analysis]].

=== Risk Evaluation ===
* Market risks- lack of surgeons; large geographical area so that we don't compete against our own clients;
** New entrants to market
*** Ease of entry
*** Potential threat to market share - advertising companies
** Slower than expected adoption
* Operational risks
* Staffing risks- embedding the right candidate for the right surgeon
** Availability of skilled workforce- x-pharma reps, x-equipment reps
** Union issues
* Financing risks
** Liabilities
** Poorly worded investor contracts at risk for litigation
** Investor pull-out
** Lack of follow-on funding to complete project
* Managerial risks
** Poor board or investor dynamics
** Agency risk particular to the venture

=== Risk Management Plan ===
Detailed plans are more often found as part of in internal plans.

For both companies and consumers that participate in online business, security concerns are very important. Many consumers are hesitant to buy items over the Internet because they do not trust that their personal information will remain private. Recently, some companies that do business online have been caught giving away or selling information about their customers. Several of these companies have guarantees on their websites, claiming customer information will be private. By selling customer information, these companies are breaking their own, publicized policy. Some companies that buy customer information offer the option for individuals to have their information removed from the database (known as opting out).

Plans written for funders may need to include a high level description if there are significant controllable risks.
* Methods and procedures to limit liabilities
* Reserve funds
* Continuity of operations plan

== Decision Making Criteria ==
* Wikipedia: [[Wikipedia:Break even analysis|Break even analysis]]
* Wikipedia: [[Wikipedia:NPV|NPV]]
* Wikipedia: [[Wikipedia:IRR|IRR]]
* Wikipedia: [[Wikipedia:Balanced Scorecard|Balanced Scorecard]]

== See also ==
* [[School:Business]]
* [[Wikiversity's Business Incubator]]
* [[Wikipedia:Content of a business plan]]
* [[Wikipedia:Business plan]]
* [[Novel economic mechanisms]]

==External links==
* [http://www.cambrianhouse.com/ Cambrian House]
* [http://www.cambrianhouse.com/idea/idea-promoter/ideas-id/MKHdFW4/ The idea at Cambrian House]
* [http://wikiworld.com/wiki/index.php/SolarCellFarms Solar Cell Farms]

[[Category:Business]]
[[Category:Wiki]]
[[Category:Management]]
[[Category:Entrepreneurship]]

Archive:CisLunarFreighter/Initial splashscreen, launcher, menu

2007-01-29T04:22:35Z

70.110.42.176: add a go to main components link

go to main component list[http://en.wikiversity.org/wiki/CisLunarFreighter_A_Requirements_Analysis_and_High_Level_Design_Exercise]

Component Name:Launcher

Responsibilities: This is the main java file which calls the splash animation, initializes the game, then calls the main menu for initial player interaction. When the player is done this module terminates the program.

Collaborators:

* Animation player
* Background display
* Main Menu

Archive:CisLunarFreighter/Initial splashscreen, launcher, menu

2007-01-29T04:19:27Z

70.110.42.176: Initial cut at launcher responsibilities

Component Name:Launcher

Responsibilities: This is the main java file which calls the splash animation, initializes the game, then calls the main menu for initial player interaction. When the player is done this module terminates the program.

Collaborators:

* Animation player
* Background display
* Main Menu

Archive:CisLunarFreighter/Requirement analysis and high level design

2007-01-29T04:12:29Z

70.110.42.176: break page into sections

Object Oriented Software Engineering
:Component, Responsibility, Collaborators (CRC)Cards - 4" X 6" note cards
::Design, Code, or Case Scenario Walkthroughs

==CRC Cards==

This exercise is based loosely upon the technique demonstrated in Chapter One of Classic Data Structures in C++ by Timothy A. Budd, cp1994 by Addison-Wesley Publishing Company, Inc. In a local object orieted design project using C++ CRC (Component, Responsibility, Collaborating Objects) cards are used to jot down names and bullets outlining the high level components identified in walkthrough as required for the project design.

==Local Adaptation==

The procedure we shall use here for asnychronous, distributed, walkthroughs is as follows: Individual files shall be created for proposed components. Responsibilities for that component jotted down in bullet form at the top of the screen, simulating a 4" X 6" note card. When another component is called a link will be created to that component. Actions the component must complete are list in the bottom half of the computer screen/file.

For the highest level walkthough or design Budd designates the most important characteristics of potential design components as:
1. A small set of well defined responsibilities must result. If the component has too many responsibilities then it should be busted into multiple components and the walkthrough reaccomplished.
2. Interactions with other components should be minimalized to the greatest extent possible.

Effort expended achieving the two characteristics above will provide large benefits in the coding process and final code.

==Draft Component/Card Set==

* [[cisLunarFreighter CRC Card Initial Splashscreen, Launcher, Menu]]
* [[cisLunarFreighter CRC Card Load and Mission Generator]]
* [[cisLunarFreighter CRC Card Ship]]
* [[cisLunarFreighter CRC Card Ship Designer]]
* [[cisLunarFreighter CRC Card Personal Game Data]]
* [[cisLunarFreighter CRC Card Terran Spaceport]]
* [[cisLunarFreighter CRC Card Spacecraft Freight Load Planner]]
* [[cisLunarFreighter CRC Card Planetary Takeoff or Lander Screen]]
::Terran, Lunar, Asteroid, or Saturn Pirate Base
* [[cisLunarFreighter CRC Card Pilot's Cockpit Screen]]
::Mini Map Radar Overview, Cockpit Menu, Headsup Communicator
* [[cisLunarFreighter CRC Card 2D Overview Asteroids or Meteor Shower Flythrough]]
* [[cisLunarFreighter CRC Card Solar System Game Controller]]
* [[cisLunarFreighter CRC Card User Keyboard Interface Controller]]
* [[cisLunarFreighter CRC Card User Mouse Interface Controller]]
* [[cisLunarFreighter CRC Card Background Music Selection and Player]]
* [[cisLunarFreighter CRC Card Lunar Spaceport]]

Archive:CisLunarFreighter/Requirement analysis and high level design

2007-01-29T04:10:32Z

70.110.42.176: fix formatting of card list

Object Oriented Software Engineering
:Component, Responsibility, Collaborators (CRC)Cards - 3" X 5" note cards
::Design, Code, or Case Scenario Walkthroughs

This exercise is based loosely upon the technique demonstrated in Chapter One of Classic Data Structures in C++ by Timothy A. Budd, cp1994 by Addison-Wesley Publishing Company, Inc. In a local object orieted design project using C++ CRC (Component, Responsibility, Collaborating Objects) cards are used to jot down names and bullets outlining the high level components identified in walkthrough as required for the project design.

The procedure we shall use here for asnychronous, distributed, walkthroughs is as follows: Individual files shall be created for proposed components. Responsibilities for that component jotted down in bullet form at the top of the screen, simulating a 3" X 5" note card. When another component is called a link will be created to that component. Actions the component must complete are list in the bottom half of the computer screen/file.

For the highest level walkthough or design Budd designates the most important characteristics of potential design components as:
1. A small set of well defined responsibilities must result. If the component has too many responsibilities then it should be busted into multiple components and the walkthrough reaccomplished.
2. Interactions with other components should be minimalized to the greatest extent possible.

Effort expended achieving the two characteristics above will provide large benefits in the coding process and final code.

==Draft Component/Card Set==

* [[cisLunarFreighter CRC Card Initial Splashscreen, Launcher, Menu]]
* [[cisLunarFreighter CRC Card Load and Mission Generator]]
* [[cisLunarFreighter CRC Card Ship]]
* [[cisLunarFreighter CRC Card Ship Designer]]
* [[cisLunarFreighter CRC Card Personal Game Data]]
* [[cisLunarFreighter CRC Card Terran Spaceport]]
* [[cisLunarFreighter CRC Card Spacecraft Freight Load Planner]]
* [[cisLunarFreighter CRC Card Planetary Takeoff or Lander Screen]]
::Terran, Lunar, Asteroid, or Saturn Pirate Base
* [[cisLunarFreighter CRC Card Pilot's Cockpit Screen]]
::Mini Map Radar Overview, Cockpit Menu, Headsup Communicator
* [[cisLunarFreighter CRC Card 2D Overview Asteroids or Meteor Shower Flythrough]]
* [[cisLunarFreighter CRC Card Solar System Game Controller]]
* [[cisLunarFreighter CRC Card User Keyboard Interface Controller]]
* [[cisLunarFreighter CRC Card User Mouse Interface Controller]]
* [[cisLunarFreighter CRC Card Background Music Selection and Player]]
* [[cisLunarFreighter CRC Card Lunar Spaceport]]

Archive:CisLunarFreighter/Requirement analysis and high level design

2007-01-29T04:08:44Z

70.110.42.176: Begin high level design process for cisLunarFreighter

Object Oriented Software Engineering
:Component, Responsibility, Collaborators (CRC)Cards - 3" X 5" note cards
::Design, Code, or Case Scenario Walkthroughs

This exercise is based loosely upon the technique demonstrated in Chapter One of Classic Data Structures in C++ by Timothy A. Budd, cp1994 by Addison-Wesley Publishing Company, Inc. In a local object orieted design project using C++ CRC (Component, Responsibility, Collaborating Objects) cards are used to jot down names and bullets outlining the high level components identified in walkthrough as required for the project design.

The procedure we shall use here for asnychronous, distributed, walkthroughs is as follows: Individual files shall be created for proposed components. Responsibilities for that component jotted down in bullet form at the top of the screen, simulating a 3" X 5" note card. When another component is called a link will be created to that component. Actions the component must complete are list in the bottom half of the computer screen/file.

For the highest level walkthough or design Budd designates the most important characteristics of potential design components as:
1. A small set of well defined responsibilities must result. If the component has too many responsibilities then it should be busted into multiple components and the walkthrough reaccomplished.
2. Interactions with other components should be minimalized to the greatest extent possible.

Effort expended achieving the two characteristics above will provide large benefits in the coding process and final code.

Draft Component/Card Set

[[cisLunarFreighter CRC Card Initial Splashscreen, Launcher, Menu]]
[[cisLunarFreighter CRC Card Load and Mission Generator]]
[[cisLunarFreighter CRC Card Ship]]
[[cisLunarFreighter CRC Card Ship Designer]]
[[cisLunarFreighter CRC Card Personal Game Data]]
[[cisLunarFreighter CRC Card Terran Spaceport]]
[[cisLunarFreighter CRC Card Spacecraft Freight Load Planner]]
[[cisLunarFreighter CRC Card Planetary Takeoff or Lander Screen]]
:Terran, Lunar, Asteroid, or Saturn Pirate Base
[[cisLunarFreighter CRC Card Pilot's Cockpit Screen]]
:Mini Map Radar Overview, Cockpit Menu, Headsup Communicator
[[cisLunarFreighter CRC Card 2D Overview Asteroids or Meteor Shower Flythrough]]
[[cisLunarFreighter CRC Card Solar System Game Controller]]
[[cisLunarFreighter CRC Card User Keyboard Interface Controller]]
[[cisLunarFreighter CRC Card User Mouse Interface Controller]]
[[cisLunarFreighter CRC Card Background Music Selection and Player]]
[[cisLunarFreighter CRC Card Lunar Spaceport]]

Archive:CisLunarFreighter/Detailed requirements analysis

2007-01-29T03:26:02Z

70.110.42.176: An exercise to shake out high level requirements and design

An overview of major requirements: What do we and the users want from a/the game?

1. Entertainment -- should be fun.
*Hands on ship control against fairly realistic g fields is fun
*Dodging debris and asteroids is fun
*Blasting asteroids to mine for valuable ore or artifacts is fun
*Working together as a team to accomplish some giant task is fun.
*Communicating with online buddies

2. Social -- Interaction with other people via
* chat -- most mud environments allow this
* email -- useful or not?
* game consequences -- makes the game more interesting
::Loads delivered begin to pile up or generate demand for missions. Player or others may undertake new missions.

3. Educational - Exposure to some science, engineering, and operations concepts
::Links to applicable background reading of various levels
::Internal math and reading requirements

* Math practice - Examples
:: Loading of feul and cargo mass vs. destination decisions in math assistance screen demonstrating use of spreadsheets in load balancing calculations with easy reference and reading showing sample problem solutions to control the center of mass. Java applet with sliders to allow easy selection for within specification loading.
:: MalFunction might occasionally require mission abort or manual calculations.
:: Misfortune (hijacked to Saturn by pirates) might require decisions about how much cargo to abandon or redistribute manually as feul.

* Reading around the web
* Use of open source tools for modding
* Software design and coding techniques
[[Category:Game Design]]

4. Reinforcement of Societal Norms

*Aliens and Pirates are best avoided but blasting is ok for self defense. Self defense applies only if your ship has taken demonstrable damage from the other side of the battle.
*Mistakes blasting other freighters results poor reputation, Space Patrol pursuit, and eventual game session loss or incarceration, ship lockdown.
*Responding successfuly to distress signals can improve standing with police.
*Mistakenly blasting a Space Patrol ship is not survivable since escalting levels of Space Patrol show up to capture or blast miscreants.

[[cisLunarFreighter A Requirements Analysis and High Level Design Exercise]]