WikiDeal:Minimum Viable Product: Difference between revisions
| mNo edit summary | |||
| Line 35: | Line 35: | ||
| == Planing == | == Planing == | ||
| # Preparing and submit the MVP proposal to NLnet (done, not to be funded) INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing. | |||
| INTRODUCTION : all key-features for the Wikideal Minimum Viable product being interdependant, they will be developed in paralel, together, following the same planing. | |||
| # '''Users Needs analysis with experts.'''    | # '''Users Needs analysis with experts.'''    | ||
| #: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:   | #: '''a) Design activities:''' developing basic wireframes to visualize the layout and flow of the MVP and defining user stories to outline the expected user interactions. Including meeting to design and adapt:   | ||
| Line 67: | Line 63: | ||
| #:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO] | #:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO] | ||
| #:and perhaps some others. | #:and perhaps some others. | ||
| # '''Ontology planning:''' defining metadata scheme for clauses  | # '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc. | ||
| # '''Development activities:''' implementing the core features identified in the earlier stages. | |||
| # '''Testing''' individual components. | |||
| # '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment. | |||
| # '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements. | |||
| # '''Development activities:''' implementing the core features  | |||
| # '''Testing | |||
| # '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment | |||
| # '''Iterate  | |||
| # '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations. | # '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations. | ||
| == Rough time estimates (for MVP development) == | |||
| Estimated time required for experienced developers proficient in PHP and JavaScript to use MediaWiki and develop MediaWiki extensions. | |||
| ==== Customization of contract templates and clauses (MediaWiki) ==== | |||
| PHP & MediaWiki extension development: approximately 120-140 hours.  | |||
| JavaScript for frontend: estimated 80-100 hours. | |||
| ==== Basic contract creation (MediaWiki) ==== | |||
| PHP & MediaWiki extension development: approximately 120-140 hours.  | |||
| JavaScript for frontend: estimated 80-100 hours. | |||
| ==== Advanced contract creation & Post-Deal support (instance application) ==== | |||
| Development: estimated at 140-160 hours.  | |||
| ==== Negotiation & Signing (instance application) ==== | |||
| Development: approximately 160-180 hours.  | |||
| === Totals === | |||
| ''These estimates are subject to variation based on the familiarity with developing MediaWiki extensions, specific requirements that are to be decided, and other factors.'' | |||
| Total estimated: 700-820 hours (includes hours of coaching, coordination, and documentation) | |||