Public:Phased Development of AI projects: Difference between revisions
(Created page with "IT projects fail. To de-risk from failure we projects in phases. AI projects have even more tendency to fail (lost money and time). Because AI and IT projects are different, hence the way phased development is AI projects is different than how you do in IT projects. At Smarter.Codes we build AI in following phases = Ph1: Proof of Concept. For Internal Stakeholders = [https://smartercodes-my.sharepoint.com/:v:/g/personal/tushar_smarter_cod...") |
No edit summary |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
[https://smartercodes-my.sharepoint.com/:v:/g/personal/tushar_smarter_codes/EbbyZL-q2oxIi4EZUcweWZsBp4uFUoYVxC3h3ucvP2WFvw?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZy1MaW5rIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXcifX0%3D&e=Ch9Ndu Video about Proof of Concept phase] | [https://smartercodes-my.sharepoint.com/:v:/g/personal/tushar_smarter_codes/EbbyZL-q2oxIi4EZUcweWZsBp4uFUoYVxC3h3ucvP2WFvw?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZy1MaW5rIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXcifX0%3D&e=Ch9Ndu Video about Proof of Concept phase] | ||
This would be our first working software. Where we would not automate everything. But we would rather cherry pick just a few components that give the highest value to users. | This would be our first working software. Where we would not automate everything. But we would rather cherry pick just a few components that give the highest value to users.<ref>[https://www.prolego.com/blog/blindly-following-the-agile-methodology-will-slowly-and-painfully-kill-your-ai-project Blindly following agile methodology painfully & slowly kills AI projects]</ref> | ||
This is a common practice we conduct to prove the viability of AI to stakeholders. We list down the tasks and cherry pick the select tasks to automate by putting together a Initial Viability Spreadsheet for Course Writing AI. | This is a common practice we conduct to prove the viability of AI to stakeholders. We list down the tasks and cherry pick the select tasks to automate by putting together a Initial Viability Spreadsheet for Course Writing AI. | ||
While this version is largely meant to be demonstrated to internal promoters and investors to prove the viability of AI. However, in certain cases this version has also become useful to actual customers too. | While this version is largely meant to be demonstrated to internal promoters and investors to prove the [https://docs.google.com/spreadsheets/d/1VFsd3g_TKa1the5i0Pa2tlX2ybuSBaUtyhAZhHzIA8g/edit#gid=0 viability of AI].<ref>[https://docs.google.com/spreadsheets/d/1VFsd3g_TKa1the5i0Pa2tlX2ybuSBaUtyhAZhHzIA8g/edit#gid=0 Initial Viability + Prototyping. Of AI Projects at Smarter.Codes]</ref> However, in certain cases this version has also become useful to actual customers too. | ||
Time required : 150 - 200 hours | Time required : 150 - 200 hours | ||
See main article: [[PoC Phase of AI Projects]] | |||
= Ph2 : MVP release. For Innovator Customers = | = Ph2 : MVP release. For Innovator Customers = | ||
This is our first official release for customer use. As per Crossing the Chasm framework, the Innovator Customer segment would be able to start using our AI in production use. Certain kinds of documents are being generated from “end to end” in this version. The type of documents we generate are constrained by either domain, or type. | This is our first official release for customer use. As per [https://thinkinsights.net/strategy/crossing-the-chasm/#Innovators Crossing the Chasm framework], the Innovator Customer segment would be able to start using our AI in production use. Certain kinds of documents are being generated from “end to end” in this version. The type of documents we generate are constrained by either domain, or type. | ||
| Line 25: | Line 26: | ||
Time required 2,500+ hours. On an average it takes 2,500 to 5,000 hrs to build MVP including design, engineering, marketing a product startup<ref>[https://www.quora.com/How-long-will-it-take-to-develop-an-MVP Quora: How long it takes to build MVP]</ref> | Time required 2,500+ hours. On an average it takes 2,500 to 5,000 hrs to build MVP including design, engineering, marketing a product startup<ref>[https://www.quora.com/How-long-will-it-take-to-develop-an-MVP Quora: How long it takes to build MVP]</ref> | ||
= References = | |||
[[Category:Sales Pricing]] | [[Category:Sales Pricing]] | ||
Latest revision as of 08:44, 20 March 2024
IT projects fail. To de-risk from failure we projects in phases. AI projects have even more tendency to fail (lost money and time). Because AI and IT projects are different, hence the way phased development is AI projects is different than how you do in IT projects.
At Smarter.Codes we build AI in following phases
Ph1: Proof of Concept. For Internal Stakeholders
Video about Proof of Concept phase
This would be our first working software. Where we would not automate everything. But we would rather cherry pick just a few components that give the highest value to users.[1]
This is a common practice we conduct to prove the viability of AI to stakeholders. We list down the tasks and cherry pick the select tasks to automate by putting together a Initial Viability Spreadsheet for Course Writing AI.
While this version is largely meant to be demonstrated to internal promoters and investors to prove the viability of AI.[2] However, in certain cases this version has also become useful to actual customers too.
Time required : 150 - 200 hours
See main article: PoC Phase of AI Projects
Ph2 : MVP release. For Innovator Customers
This is our first official release for customer use. As per Crossing the Chasm framework, the Innovator Customer segment would be able to start using our AI in production use. Certain kinds of documents are being generated from “end to end” in this version. The type of documents we generate are constrained by either domain, or type.
Time required : 1000+ hours
Ph3 : MVP release. Early Adopter Customers
Here we increase the domain and type of documents that the AI generates. And as per Crossing the Chasm framework - it enables our AI to be used by wider amount of users as we support more types of documents, more domains, and higher accuracy and automation. Our offering is pretty mature at this time, often Fortune 1,000 companies considering to use our AI in their production
Time required 2,500+ hours. On an average it takes 2,500 to 5,000 hrs to build MVP including design, engineering, marketing a product startup[3]