Difference between revisions of "Meeting:2021,07,13/Ben,Kevin,Jared"

From PKC
Jump to navigation Jump to search
(Created page with "{{Logic model events |Start time=2021-07-13T08:00:00.000Z |End time=2021-07-13T09:00:00.000Z |Context=Daily coordination |Goal=Define workflow and boundaries |Criteria=Mutual...")
 
 
(6 intermediate revisions by 2 users not shown)
Line 2: Line 2:
|Start time=2021-07-13T08:00:00.000Z
|Start time=2021-07-13T08:00:00.000Z
|End time=2021-07-13T09:00:00.000Z
|End time=2021-07-13T09:00:00.000Z
|Context=Daily coordination
|Context=Project management
|Goal=Define workflow and boundaries
|Goal=Timeline, Calendar, Workflow
|Criteria=Mutual understanding and participation
|Criteria=Mutual understanding and participation
|Outputs=Clear coordination plan
|Outputs=Project management calendar
|Process=List potential roadblocks and hear everyones opinions
|Process=Define roadblocks, Achieve group concensus
|Inputs=Jared and Kevin present to Ben the proposed plan
|Inputs=Kevin and Jared presentation
|Boundaries=1 hour zoom call
|Boundaries=1 hour zoom call
}}
}}
This is where we can store the meeting notes
 
Agenda:
 
* Discuss the meeting confusion
* Update Ben on our progress
* Get suggestions for next
 
 
Actions:
 
Meeting minutes:
* Agreement on the meeting time.
* The "PKC Workflow#System Implementation" term jettisons our previous work of Backup&Restore, Docker Image workflow, and PKC deployment.
* Ben: We need to relate everything to Logic Model so that users could have limited choice.
** -> Kevin building on this idea : An application express its domain by the cost of complexity. The functionality depends on the expressiveness, and the size of decision space depends on the complexity.
* Kevin: [[Logic Model expressing DevOps|Modeling the iterative process of DevOps using Logic Model]]
 
Process optimization:
[[Process optimization::]]
* For the mutual knowledge which requires to be precise, it is not feasible to talk it verbally.  Instead, we should communicate on a page. Some types of issue required for precise communication:
** Naming or describing some concepts.
** Formalizing the model
** Deliberation of concepts.

Latest revision as of 09:41, 13 July 2021

Start time 2021-07-13T08:00:00.000Z
End time 2021-07-13T09:00:00.000Z
Attendees
Context Project management
Goal Timeline, Calendar, Workflow
Criteria Mutual understanding and participation
Meeting URL


Agenda:

  • Discuss the meeting confusion
  • Update Ben on our progress
  • Get suggestions for next


Actions:

Meeting minutes:

  • Agreement on the meeting time.
  • The "PKC Workflow#System Implementation" term jettisons our previous work of Backup&Restore, Docker Image workflow, and PKC deployment.
  • Ben: We need to relate everything to Logic Model so that users could have limited choice.
    • -> Kevin building on this idea : An application express its domain by the cost of complexity. The functionality depends on the expressiveness, and the size of decision space depends on the complexity.
  • Kevin: Modeling the iterative process of DevOps using Logic Model

Process optimization:

  • For the mutual knowledge which requires to be precise, it is not feasible to talk it verbally. Instead, we should communicate on a page. Some types of issue required for precise communication:
    • Naming or describing some concepts.
    • Formalizing the model
    • Deliberation of concepts.
Retrieved from "https://pkc.pub/index.php?title=Meeting:2021,07,13/Ben,Kevin,Jared&oldid=5264"