From 753485b5ee7f6761a82489f989c6603295638cf0 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Mon, 24 Jun 2024 09:31:47 +0100 Subject: [PATCH] Add daily email for 2024-06-20 Proof of concept --- source/_daily_emails/2024-06-20.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 source/_daily_emails/2024-06-20.md diff --git a/source/_daily_emails/2024-06-20.md b/source/_daily_emails/2024-06-20.md new file mode 100644 index 000000000..cb405e07e --- /dev/null +++ b/source/_daily_emails/2024-06-20.md @@ -0,0 +1,24 @@ +--- +title: Proof of concept +date: 2024-06-20 +permalink: daily/2024/06/20/proof-of-concept +tags: + - software-development +cta: ~ +snippet: | + How can you prove a concept? +--- + +How do you validate an idea from a client or stakeholder? + +Unlike a minimum viable product, which is the smallest amount of functionality for a feature to be released, a proof of concept is an initial investigation into whether the idea is viable. + +What's the least amount of development you can do to prove the concept? + +Can you create something using a smaller data set or with simplified functionality? + +What can you build within a minimal timeframe so, if the idea isn't used, too much time wasn't invested in it, but still verifies it? + +Do you need to write any code or do any development at all? + +All we need to do is find out if the concept could work.