View source for Template:Proposal



= Project structure =

{{:{{{Project_name}}}/Synopsis}}

{(Template:Activity|Person=banana}}

* Project Logic Model: 
{{template:LogicModel|{{{Project_name}}}}}


{{{Project_name}}}

This includes the following:
** Define [[{{{Project_name}}}/Context|context]] with historical factors(if needed e.g. education - What, How, why, etc... of curriculum or programs)
** Introduction and [[{{{Project_name}}}/Goal|Goal]]s of the project
** Quality issues ([[{{{Project_name}}}/Criteria|Success criteria]]) and relevant [[MCatalog/Boundary|boundary condition]]s
** Required [[{{{Project_name}}}/Input|Input]]s and Stakeholders identification
** Proposed [[{{{Project_name}}}/Process|Process]] of Execution
** Budget
** Expected [[{{{Project_name}}}/Output|Output]]s/Outcomes
* References
* Related pages

= Quality documentation =

{{:{{{Project_name}}}/Mandatory}}

=== Quality Protocol ===

[[https://www.pmi.org/disciplined-agile DA]]

'''Planning phase'''
: Portfolio components conception must follow
: Define tolerance specifications and Control limits specification 
: Attend Meeting review for iterations week/component/work launch (sprints or similar), and discuss components on portfolio before develop to make sure everything is understood
'''Development''' 
: by a DevOps approach, apply DDT ([https://en.wikipedia.org/wiki/Data-driven_testing Data Driven Testing], according to [Security Protocol Document|SPD])
:: e.g. Apply unit testings FrontEnd/BackEnd, Linters (ESLint), Prettier and (User-side) Sentry
: Report to Update all [[project-related]] documents and request for changes on plan
: Meeting review to validate products
'''Testing'''
:Quality review on development environment 
::Review at six sigma level, no flaws
::Margins (controls and boundaries) defined on Project Planning 
::apply complementary principles e.g. rule of seven if applicable
:Quality review on stage environment 
::Apply Stress Test Protocol - User side testing 

=== Stress Test Protocol ===
STP is documented [[Stress test Protocol|here]] and it's a document as a [[checklist]] that defines all the steps for a user to run all the functionalities of the software



= Procurements (HR/Materials agreements) =

== Form of Product proposal plan (description&budgeting) ==

===Product description===
* '''(define the state of art, what is the purpose of the product, why is being done and what is solving) 
{{:{{{Project_name}}}/Product description}}

===Product Scope===
* '''(Define the requirements or deliverable of the scope)

{{:{{{Project_name}}}/Infrastructure Requirement}}

* '''(Define for each deliverable the packages of work specifically and the levels of complexity)

===Team and skills===
* '''(Define the Team you require to be able to complete this project)
* '''(Define the hierarchies of the team and the predicted amount of time for each role)

{{:{{{Project_name}}}/Budget}}

{{:{{{Project_name}}}/Phases of Delivery}}

== NDA  [https://en.wikipedia.org/wiki/Non-disclosure_agreement Non-disclosure Agreement] ==

For the fact that PKC is a unique and state-of-the-art, there is no "secrets" making us a 100% OSS organization, therefore, no NDA is necessary. We take for granted that people are self-accountable and should be responsible for what they say, do and create.


== Time & Material agreement ==

(To be updated)
{{Template:International Employment Agreement (Format1)
|PartyA=Del Foundation
|Starting_Day=6th
|Starting_Month=June
|Starting_Year=2022
}}