Escolar Documentos
Profissional Documentos
Cultura Documentos
Project Assignment
Scope Purpose Covered in
The first steps of a start-up Gain an insight into starting Lectures 1-2, 5-7, 9.
company from an idea a company around an idea, Seminars 1-4 and 7.
towards a company: training in writing and
· a business plan reading business plans, oral
· an eco-system presentation, considering
· high-level project plan eco systems, and
· risk assessment performing project planning
including risk assessment.
This assignment shall be performed in groups of 4-6 students. The assignment is reported
through a written report and an oral presentation, which are examined and graded.
Submission deadlines are noted in the course schedule (see course web page
cs.lth.se/etsf25). Instructions for submissions and peer-reviews (SPA) can be found in
moodle.cs.lth.se.
Task Description
Your task is to develop an idea for a software-based product or service, and present (1) a
business plan, (2) an eco-system, (3) a high-level project plan and (4) a sales pitch for this
idea.
Title
1. Introduction [Business idea] 6. Project plan
2. Market 7. Risk assessment
3. Business model 8. Summary
4. Team composition 9. References
5. Eco system incl user data Appendix: Contribution statements
The complete report should consist of 5-7 A4-pages including references, using the IEEE
two-column template and be written in understandable English or Swedish (not
Swenglish) with cohesive flow using a top-down structure.
2018-11-07
ETSF25 Business of Software
Tasks
Subtask 1: Kick-off & Select idea
Create a project group and identify an idea for a new business. The idea can be for a new
product or service that uses software as a key component. For example, Skype provides a
service that relies on software to deliver music to its customers.
The initial version of the report shall cover the following parts (see Venture Cup and
Osterwalder 2010):
· Title
· Pitch of business idea and team (in Introduction section).
· Market analysis (in Market section)
· Business model: Value proposition, Customer segments, Customer relationships,
Channels and Revenue streams (in Business model section)
· Available and needed team members incl competences (in Team composition
section)
The report shall contain a list of references used (in References) and contribution
statements1 describing what each group member has contributed with.
Include a draft of all prescribed sections in the report. Sections 5, 6 and 7 may be empty
for this version.
1
The contribution statements shall be detailed enough to determine which aspects, topics, parts etc. that
each person has worked on, and to which extent. All authors are to contribute with an equal amount of time
and effort.
2018-11-07
ETSF25 Business of Software
Feedback Scheme
Area Criteria Grading 0-5 Comments
No partly Yes
The formal presentation gives a
Formality
professional impression
Subtask 4: Ecosystem
Consider your business idea in the context of an envisioned software ecosystem. Describe
your ecosystem using an overview picture and descriptive text. Consider the following
questions: Who are the participants and stakeholders, and what roles do they have (Jansen
2018-11-07
ETSF25 Business of Software
Subtask 7: Draft 2
A full draft of the report is to be submitted containing an updated business model, a
description of the sketched eco system and a project plan for developing the initial
version of the product/service. The report should consist of a minimum of four pages
using the IEEE two-column template (see course web page) and contain all sections
including (correctly formatted) reference list and contribution statements (see outline
above).
2018-11-07
ETSF25 Business of Software
Grading
The project is graded (3,4,5) based on the quality of the report and the oral presentation
(based on equal contribution from all project members), and on individual active
participation in the seminars related to the project and completion of peer reviews.
Projects not passing the first grading instance may be updated, but can then only be given
grade 3.
The project is scored on a scale 1-5 on each of the following 7 aspects, as defined in the
grading grid:
· Sales pitch (oral presentation)
· Business plan: business model, market analysis, eco system
· Project planning: plan, risk assessment
· Form: writing style
The minimum requirements for pass is at least a score of 3 for each aspect, individual
active participation in the seminars and completed peer reviews. The peer reviews must
be of substantial quality and provide constructive feedback to the authors.
The sum of scores 31-35 give grade 5, 26-30 grade 4, 21-25 grade 3.
2018-11-07
ETSF25 Project Assignment: Grading Grid
Note: Criterias 4 and 5 include all lower level criteria. Updated: 2018-10-24
Aspect 3 4 5
Sales pitch Basic structure in-line with classical rhetorical Good use of rhetorical model with logical Excellent use of rhetorical model including
model presentation of information interest grabbing opening and clear conclusion.
Business plan: Basic description of Business model with Good description of value creation, value Excellent description of value creation, value
Business model targetted customer segment(s), key resources capture, key resources required, revenue capture, key resources required, revenue
and revenue generation strategy. generation strategy. generation strategy (pricing, licensing, brand
building etc).
Business plan: Basic description of revenue streams and Good description of the market potential for Excellent description of the market potential for
Market analysis competitors relevant to your business idea. your business model using SWOT (strengths, your business model using SWOT (strengths,
weakness, opportunities, threates) analysis weakness, opportunities, threates) analysis
Business plan: Basic description of ecosystem for your business Good description and justification for an Excellent description of ecosystem including its
Ecosystem idea including an overview figure. ecosystem with its stakeholders including the stakeholders, and if it is user or data centric.
role of user data. Clearly motivated by and aligned with the
business model.
Project planning: Basic project plan with main development Good project plan with good coverage of Excellent plan covering all major activities
Plan activities at component level, reasonable effort software development activities and realistic required for implementing the product or
estimates and resources. Described by a Gantt effort estimates. service in-line with the business model.
chart and descriptive text.
Project planning: Some basic development risks identified, Good risk assessment covering the majority of Excellent risk assessment including e.g. the risk
Risk assessment prioritised and planned for. relevant aspects from Boehm's checklist. of copied innovation.
Form - writing style Readable language with some flow through use Fluent language through consistent use of top- Excellent flow and paragraph structuring
of top-down writing structure and standard down writing structure and good paragraph including topic sentences throughout.
moves for introduction. structuring including topic sentences.