Insurence portal
Requirements and questions EXTENDED
Roadmap
Debugging Official Requirements
Mistakes at software developments
Development: Yacht charter
Silo mentality
SW Projects - REQUIREMENTS
Fiskal Condor
Mobile Strategy: 8 Cool Insurance Apps
INSURANCE PORTALS: THE NEXT GENERATION 2003
Famous and Wrong Predictions
Planning
Requirements
Before we start coding
SW Projects
SW project factors
perl lab1
Escape Velocity
Neutralisation by Geoffrey Moore
Lynda Business Courses & Training
Web Projects  
Project Hologram
e-insurence system


Project Hologram
----------------------------------------------
market panoramics / competitive set
----------------------------------------------
Na EU tržištu se poduzetnicima nudi više od ??? različitih insurence portala (2016)
links?

Usporedni prikaz različitih insurence portala u HR i EU
links?
tržište?
broj korisnika?

hierarchy of corporate strategy terminology - powers:
* Category Power - n. of competitors on market – the demand for a category of products in Euro/annum - value of all items/services sold per year
* Company Power - recognized brand, admired organization, best & smartest experts
* Market Power - n. of customers/clients, % market-share
* Offer Power - Wikipedia is an example, most desired * most affordable product on the market
* Execution Power - capability to make superior product, market it and sell it successfully
CaCoMa OfEx
--------------------------------------------------------------
OTVORENA pitanja - project HERMES

project HERMES:



Svako od ovih pitanja zahtijeva nekoliko rečenica razmatranja (mogućih alternativnih) odgovora

1. cloud infrastruktura ?

3. u kojem jeziku će se pisati serverski i klijentski software?

4. tko će napraviti DETALJNU specifikaciju?

4.c backend opis
4.d frontend opis
4.e e-insurence system software - sve komponente i svi featursi



5. tko će pregledati i prekontrolirati specifikaciju u svim aspektima?

6. Posebna lista na koja sva pitanja se trebaju imati odgovori prije nego li se počne programiranje?
6.1 lista bez kojih odgovora se ne može započeti s razvojem
6.2 lista bez kojih odgovora bi se moglo krenuti dalje i odgovori odlučiti/pronaći naknadno, u "letu"

7. da li je pretpostavka od 2 mjeseca razvoja dovoljna s obzirom na točku 6
7.a detaljna roadmapa s 8 milestononova (2 mjeseca razvoja)
7.a gradualnih 8 test-case setova (nakon svakog sprinata)

8. hoćemo li imati code-review?

9. hoćemo li imati pravnog savjetnika?

10. hoćemo li imati fiskalnog savjetnika - knjigovodstveni servis?

11.a koliki bi bio budget ako razvoj traje 12 tjedana ( 4 developera )
ili
11.b koliki bi bio budget ako razvoj traje 24 tjedana ( 2 developera )
ili
11.c koliki bi bio budget ako razvoj traje 48 tjedana ( 2 developera )

12. tko/kakav bi nam bio MERKETINŠKI APARAT

13. koja politika e-insurence system, cijena

14. da li možemo uspijeti sami.. bez pokroviteljsava nekog velikog partnera

15. koja su tri najveća konkurenta u hrvatskoj - e-insurence system

16.a u čemu možemo biti bolji od konkurencije

16.b u čemu moramo biti bolji od konkurencije

16.c u čemu možemo biti jednako dobri kao konkurencija


17.a koliko je zasićeno tržište osiguranja?
17.b brojke?

17.c brojke od konhurencije?

18.a koliko bi mi morali imati prodanih POLICA da bi vratili investiciju?

19. Ne znam koliko se sve to uopće isplati raditi sam bez velikog marketing partnera - da li imaš neki konkretan odgovor primjer?

20. Ne bi želio biti naivan i/ili preoptimističan -- molim te pogledajmo stvarne podatke



21. treba pogledati je li je zakonski moguće (industrijalizirati) e-insurence system servis onima kojima prodajemo usluge i koja je tu problematitka


23. Koji su se novi proizvodi pojavili u 2015 godini na tržištu?

to je za sada to
to su samo MAKRO pitanja kada bi ulazio u detalje stigao bi lako do liste od jedno 200 pitanja vjerujem a ne 20-tak
-------------------------------------
24. B2B partneri mogu biti auto-saloni, rentacar i auto-servisi
******************************

This list consists of a set of issues around which go-to-market plans are built, each of which incorporates a chasm-crossing factor, as follows:
• Target customer/market
• Compelling reason to buy e-insurence police
• Partners and allies
• Distribution
• Pricing
• Competition
• Positioning
• Next target customer

The game is not over, of course.
**********************
Offer power
- Retain or innovate model
- Six levers model
- Price/Benefit model
- Core/context model

Recap: The Competitive-Positioning Checklist
To define the battle effectively so that you win the business of a
pragmatist buyer, you must:
Define the Battle

1. Focus the competition within the market segment established by your must-have value proposition—that is, that combination of target customer, product offering, and compelling reason to buy that establishes your primary reason
for being.

2. Create the competition around what, for a pragmatist
buyer, represents a reasonable and reasonably comprehensive set of alternative ways of achieving this value proposition. Do not tamper with this set by artificially excluding a reasonable competitor—nothing is more likely to alienate your pragmatist buyer.

3. Focus your communications by reducing your fundamental competitive claim to a two-sentence formula and then managing every piece of company communication to en
sure that it always stays within the bounds set out by that
formula. In particular, always be sure to reinforce the second sentence of this claim, the one that identifies your primary competition and how you are differentiated from it.

4. Demonstrate the validity of your competitive claim
through the quality of your whole product solution and
the quality of your partners and allies, so that the pragmatist buyer will conclude you are, or must shortly become, the indisputable leader of this competitive set.

Launch the Invasion
In this chapter the final pieces of the D-Day strategy come into
play—distribution and pricing. As we launch our invasion across
the chasm, distribution is the vehicle that will carry us on our
mission, and i pricing is its fuel. These two issues are the only two
points where marketing decisions come into direct contact with
the new mainstream customer. Decisions in both distribution and
pricing, therefore, have enormous strategic impact, and, with distribution in particular, there is typically only one chance to get it
right. For this reason, we have put these two last in our invasion
planning sequence, so that we could have the advantage of nailing everything else down first.

The number-one corporate objective, when crossing the chasm, is to secure a channel into the mainstream market with which the pragmatist customer will be comfortable. This objective comes before revenues,

-----------------------------------------------------------------------------------------
Stage 1:
Starting allocations to begin project/initiative:
- infrastructure (hardware and software) and
- resource (people and money)
For those who lack the resources or would prefer not to staff up for mobile app dev, Constellation suggests engagement with design-shops and system-integrators who have platforms that can scale for the rapid of pace of change in mobile development.

Stage 2:
Updating existing tools and processes to be accessible from mobile devices.

Stage 3:
Updating existing tools and processes to be leverage mobile specific features such as cameras, GPS, accelerometers, etc. and to work across a variety of device types.

Stage 4:
Implementing new tools and/or processes that change the core business (products, services, revenue models, etc.) of the organization.

-------------------------------------------------------------------------
In applying mobile solutions to the solution design point, Constellation recommends:

1. Assess how new generation enterprise mobile apps can change the business.
- seek the most common, cross-functional business problem that cannot be solved with linear thinking.
- Articulate the business problem and benefit.
- Show how the solution orchestrates new experiences.
- Identify how analytics and insights can fuel the business model shift.
- Exploit full native device features. Seek frictionless experiences.

2. Determine whether to build, buy, or modify.
Where solutions have been developed, expect to take these solutions as a platform to expand from.
Where solutions have not been developed, Constellation suggests that organizations who have strong app dev shops standardize on a mobile app platform for development.

3. Plan for a mobile experience workshop.
As part of the design thinking process, clients move beyond the inquiry or exploratory conversation to solidify objectives. The process starts with a proof of concept, road mapping engagement, and then the actual enterprise mobility project. The process often results in quick wins for the business side and cuts cost out of the IT budget.

--------------------------
Planning
--------------------------
Names: isocrat, castor, polux
http://1stmuse.com/web/
http://journeymanpm.com/planning-2/plan-for-a-web-design-project/
https://chrisjmprojmanagement.wordpress.com/2015/07/08/project-timeline-website-design-by-fuel/
http://1stmuse.com/web/questionario.html
http://1stmuse.com/web/competenze.html
http://www.1stmuse.com/articoli/regole.html
----------------
Consulting Services
https://www.designory.com/
http://adaptivepath.org/
http://www.jellyfishcreative.co.uk/approach
https://www.freelancer.com/projects/Java-J-EE/auction-proj/
http://sanfrancisco.metadesign.com/
https://www.ideo.com/about//
http://artandlogic.com/portfolio-grid/
Do you have a vision for your business or need assistance on a project?
---------------
https://www.agriya.com/about/our-expertise
http://www.ids-outsourcing.com/portfolio.html
http://artandlogic.com/
https://www.engenderhealth.org/our-work/index.php
http://www.adobe.com/uk/web/gallery/vivid/
https://www.simplesquare.com/
https://www.interaction-design.org/courses/emotional-design-how-to-make-products-people-will-love