WikiDeal:Minimum Viable Product: Difference between revisions

(2 intermediate revisions by one other user not shown)

Line 27:

* '''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).

* '''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.

~~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.

== 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.'''

#: '''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 27: / Line 27: @@
 * '''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).
-* '''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.
-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.
 == 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.'''
 #: '''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: