Enterprise Computing - Exploration

A linear, sequential software development approach with distinct phases: Exploration -> Development -> Operations

Software Development Lifecycle involving iterations, each delivering small, functional increments.

An enterprise comes up with a hypothesis about the marketplace and decided what empirical data would validate this hypothesis.

An enterprise tests its hypothesis by collecting the empirical data.

An enterprise creates a Minimal Viable Product if the empirical data looks good.

When it becomes clear that the product could deliver its value more efficiently using different technology.

When a product feature becomes a product.

When a product becomes a product feature.

Changing the target audience while keeping the product roughly the same.

Changing the product to address a different need for your original customer group.

When a person replicates how the product would work, and the customer knows someone is replicating it.

When a person replicates how the product would work, however the customer does not now a person is replicating it.

A page where potential customers can find out about the product idea, and possibly pledge money.

A video that shows how the product might work, and asks customers to sign up for it.

An experiment where you have a hypothesis you are trying to test.

Building things very efficiently that no one wants.

The pivot.

No as with agile, the customer is knows and the specification is not, however with a startup neither the customer or specification is known.

Learning quantitatively how to build a sustainable business.

Only what is necessary to learn whether the plan is correct or not.

Does it minimise total time through the build-measure-learn loop?

Metrics about per customer behaviours that can be measured.

A single program run by a single process formed from a collection of modules that communicate by procedure calls.

Because all the code is in one language in one place.