WikiDeal:Minimum Viable Product - Revision history

SpectrumMigou: SpectrumMigou moved page Minimum Viable Product to WikiDeal:Minimum Viable Product

2025-04-01T14:29:18Z

SpectrumMigou moved page Minimum Viable Product to WikiDeal:Minimum Viable Product

← Older revision		Revision as of 16:29, 1 April 2025
(No difference)

Creativesoul4ever: /* Key features */

2023-12-01T10:08:33Z

Key features

← Older revision		Revision as of 12:08, 1 December 2023
Line 27:		Line 27:
	* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.		* '''Contract Creation''': Users select models, input variables, and personalize contracts, saving them in different formats.
	* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).		* '''Negotiation & Signing''': Contracts go through negotiation phases with different statuses (e.g., draft, signed).
	* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms.		* '''Post-Deal Support''': Reminders, automated payments, and service activation/cancellation based on contract terms. With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management. Feature nice to have on the MVP, or will be done in a second phase :
	* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.		* '''Decentralization''': Contracts are stored locally for privacy; proposals for decentralized solutions for organizations and individuals are in place.

	~~With plans for a proof of concept and MVP, WikiDeal envisions a community-driven space fostering innovation in contract management.~~

	Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.		Additional features in the pipeline include personalized contract styling, external contract creation tools, and true peer-to-peer contract creation, aiming for a transformative impact on how contracts are created, managed, and executed.

Creativesoul4ever: /* Key features */

2023-12-01T09:26:17Z

Key features

← Older revision		Revision as of 11:26, 1 December 2023
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.		# Preparing and submit the MVP proposal to NLnet (done, not to be funded) NB : 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:

Creativesoul4ever: /* Rough time estimates (for MVP development) */

2023-12-01T09:02:51Z

Rough time estimates (for MVP development)

← Older revision		Revision as of 11:02, 1 December 2023
Line 69:		Line 69:
	# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.		# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
	# '''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)~~

Creativesoul4ever at 05:53, 1 December 2023

2023-12-01T05:53:23Z

@@ Line 35: / Line 35: @@
 == 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.
 # '''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:
@@ Line 67: / Line 63: @@
 #:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
 #:and perhaps some others.
-# '''Ontology planning:''' defining metadata scheme for clauses and contract models used by the interactive contract builder, data exchange, and the user workflows automation. Our effort will be aimed at providing a detailed breakdown of the yet rough data objects, to make them usable so by humans as by machines:
+# '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc.
-#:; Contract Model
+# '''Development activities:''' implementing the core features identified in the earlier stages.
-#:* Metadata
+# '''Testing''' individual components.
-#::* Options
+# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.
-#::* Variables
+# '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
 # '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

Creativesoul4ever: /* Planing */

2023-12-01T03:46:43Z

Planing

← Older revision		Revision as of 05:46, 1 December 2023
Line 94:		Line 94:
	#:::* Metadata		#:::* Metadata
	#:::* Available Clauses (dynamic) Smaller ontologies will be needed for helper data objects like user manuals, guided tours, etc		#:::* Available Clauses (dynamic) Smaller ontologies will be needed for helper data objects like user manuals, guided tours, etc
	# '''Development activities:''' implementing the core features ~~identified~~ in the earlier stages.		# '''Development activities:''' implementing the core features specified in the earlier stages.
	# '''Testing''' individual components.		# '''Testing''' '''& documenting''' individual components and their integration.
	# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment.		# '''Release the MVP''' to a limited audience or beta testers to collect feedback and monitor its performance in a real-world environment. Including presenting the wikideal beta MVP to an event such as wikimania or FOSS event and inviting beta users to test and give feedbacks.
	# '''Iterate ~~Based~~ on ~~Feedback~~:''' Analyze the feedback received and make necessary improvements.		# '''Iterate based on feedbacks:''' Analyze the feedback received and make necessary improvements.
	# '''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.

Creativesoul4ever: /* Rough time estimates (for MVP development) */ deleted, to avoid fork, since we well reformulate it in a table

2023-12-01T01:16:51Z

Rough time estimates (for MVP development): deleted, to avoid fork, since we well reformulate it in a table

@@ Line 93: / Line 93: @@
 #::* Custom Sections
 #:::* Metadata
-#:::* Available Clauses (dynamic)
+#:::* Available Clauses (dynamic) Smaller ontologies will be needed for helper data objects like user manuals, guided tours, etc
 # '''Development activities:''' implementing the core features identified in the earlier stages.
 # '''Testing''' individual components.
@@ Line 100: / Line 99: @@
 # '''Iterate Based on Feedback:''' Analyze the feedback received and make necessary improvements.
 # '''Track key performance indicators (KPIs)''' to assess the success of the MVP and guide further iterations.

Creativesoul4ever: /* Planing */

2023-11-30T13:50:47Z

Planing

← Older revision		Revision as of 15:50, 30 November 2023
Line 35:		Line 35:

	== Planing ==		== Planing ==
	# 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:

Creativesoul4ever: /* Planing */

2023-11-30T13:50:01Z

Planing

← Older revision		Revision as of 15:50, 30 November 2023
Line 35:		Line 35:

	== Planing ==		== Planing ==
	# 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:

WikiVisor: /* Planing */

2023-11-29T16:11:59Z

Planing

@@ Line 63: / Line 63: @@
 #:* [https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:WikiSEO WikiSEO]
 #:and perhaps some others.
-# '''Ontology planning:''' defining metadata scheme for clauses, contract models, and helper data objects like user manuals, guided tours, etc.
+# '''Ontology planning:''' defining metadata scheme for clauses and contract models used by the interactive contract builder, data exchange, and the user workflows automation. Our effort will be aimed at providing a detailed breakdown of the yet rough data objects, to make them usable so by humans as by machines:
 # '''Development activities:''' implementing the core features identified in the earlier stages.
 # '''Testing''' individual components.