Difference between revisions of "Template talk:Proposal"
| Line 23: | Line 23: | ||
'''Goals''' - (Product approval requirements) | '''Goals''' - (Product approval requirements) | ||
<br'''Success Criteria''' - (Boundaries definition/quality define tolerance and control limits specification)/> | |||
<br '''Success Criteria''' - (Boundaries definition/quality define tolerance and control limits specification)/> | |||
Revision as of 21:52, 20 June 2022
About shaping planning terminology
This could be inserted in current Logic model
I had a proposal on some changes on the logic model concept to look more as a project-oriented terminology (https://www.pkc.pub/index.php/Template:Proposal#PKC_Project_page_structure)
- The logic model is (somehow) what we call in project management as the “project charter”
Abstract spec
Define: Product and project separately
Define:
- Internal (PKC engine, Apollo implementation, DocAPI, etc…)
or
- External (service or a client e.g. LKPP KeyCloack or CpL)
Goals - (Product approval requirements)
Concrete implementation
Output Process (execution mode) Input
model should also include:
- Stakeholders identification
- Budget
- timing
Create a template with proper UI like this that fills up your logic model: https://trackonperformance.com/charter/62b0e6796f0213005c71606e
Note1: I understand that if we unite later with TOP DB we can update fields like budget and stakeholders Note2: Link timing to the project packages plan (TOP and/or future in Apollo or other) where the ordering defines time and eventually the budget