This document outlines the schedule and deliverables for a software engineering project. It includes timelines for completing tasks like selecting a topic, conducting a state of the art review, and developing architectural views. The document also discusses key aspects of developing a project vision, including defining customer needs and benefits, perceived value, and key technologies. Additional resources on writing a quality vision statement are provided.

1. Software Engineering
Prof.Dr.ir. F. Gielen
Project Vision Statement
Vakgroep Informatietechnologie – IBCN

2. Project Time Schedule & Delivery
Week 1 Make teams, topic preview
Week 2 Select & Present Topic
Week 3/4 State-of-the-art study – Review
Week 5 DELIVERY: State-of-art report
Week 5/6 Vision document - Review
Week 7 DELIVERY: Vision document
Week 7/8 Scenario document - Review
Week 9 DELIVERY: Scenario document
Week 9/10 Architectural views
Week 11 DELIVERY: Architecture document
Week 12 FINAL : Presentation & MVP Demo
p. 2
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN

3. The Value Hypothesis
Product
Business
Partners
Model
Product Strategy
Competition
Roadmap
Vision
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN p. 3

4. Incremental & Iterative
Idea NABC Project Business
Vision Model
External: Internal: Run the
Elevator Drive the
Pitch Team
Business
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN p. 4

5. Project Visions
 From an idea to a product definition that
you can implement.
 Scrum (Agile development):
“Every Scrum project needs a product vision that
acts as the project’s true north, sets the direction
and guides the Scrum team. It is the overarching
goal everyone must share – Product Owner,
ScrumMaster, team, management, customers and
other stakeholders. “
“The minimum plan necessary to start a Scrum
project consists of a vision and a Product Backlog.
The vision describes why the project is being
undertaken and what the desired end state is.”
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN p. 5

6. The Art of seeing things invisible
1. Who is going to buy the product? Who is the
target customer?
2. Which customer needs will the product
address?
3. Which product attributes are critical to
satisfy the needs selected, and therefore for
the success of the product?
4. How does the product compare against
existing products, both from competitors
and the same company? What are the
product’s unique selling points?
5. What is the target timeframe and budget to
develop and launch the product?
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN p. 6

7. Project Vision (1/3)
1. Mis s ion: What will we do and why ?
 A 2 s e nte nce s u m m ary p roj ct d e s crip tion and wh y
e
you are d oing it.
n Who are the cus tomers ?
 Wh o are le ad ing cu s tom e rs ?
 Wh at are th e m arke t s e gm e nts ?
 Wh o are e nd u s e rs ?
n What are the primary benefits for them ?
 Wh at p rob le m s d o th e y h ave ?
 Wh at is you r s olu tion ?
 H ow can th e ir s olu tion h e lp th e m (m ake m one y) ?

8. Project Vision (2/3)
n What is the value perceived by the cus tomer
?
 C le ar, com p e lling m e s s age s th at s tate wh y you are
d iffe re nt from th e com p e tition and worth b u ying.
 Th is is th e qu ality of th e s ys te m th e u s e r p ays for.
 QUA LITY A TTRUB UTE S
 These qualities should be expressed in a quantified,
measurable and testable way.
 E xam p le s :
 Us ability
 S ec urity

9. Project Vision (3/3)
5. Key Technology & Features .
 P riority fe atu re s to ge t to m arke t e arly (M VP – top 3)
 P rod u ct F u nctionality
 Te ch nology th at will b e u s e d (cons traints )
6. C rucial product factors .
 N on fu nctional re qu ire m e nts (m ore qu ality attrib u te s )
 O p e rational re qu ire m e nts
7. Financials .
 E conom ics : cos t only
 R e le as e d ate s

10. Additional Resources
 QRPD : Quality Rapid Product Development
 Paper on Minerva in the Vision folder
 Template for writing the Vision
 Vision = 2 pages max.
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN p. 10

11. Vision Workshop
 Goal: Create the Vision Statement
 Entire team participates – up to 10 people
 Max duration: 2-3 hrs
 15 minutes intro: process
 10 minutes per topic – brainstorm mode
 Brainstorm = No criticism
 10 minutes review per topic
 Iterative
 Consolidate
 Be prepared:
 Room, flipchart,…
 Read documentation
 Different roles:
 Moderator
 Scribe
 Timekeeper
 OUTPUT:
 2 pages
Vakgroep Informatietechnologie – Onderzoeksgroep IBCN p. 11