Conversation
|
|
|
The created documentation from the pull request is available at: docu-html |
anmittag
force-pushed
the
pmp-pm-updates
branch
from
c9a7b60 to
a853a29
Compare
- added diagram - added verification report - added itf to index.rst
Signed-off-by: Philipp Ahmann <philipp.ahmann@de.bosch.com>
update link to release notes add link to maturity levels
anmittag
requested review from
a team,
PandaeDo,
aschemmel-tech,
masc2023 and
pahmann
as code owners
| Org Chart and Main Platform Management Plan Responsibilities | ||
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
|
||
| .. image:: _assets/score_project_management_organization_orgchart.drawio.svg |
There was a problem hiding this comment.
Process activities yellow? Not complete, e,g, Implementation, Architecture, Requirements missing, safety, security analysis, Tool Management should also overlap with Process, Internal and External communication are not process areas, but activities and part of any process, docu->documentation, Steering in my opinion covers also the cross CT/FT Meetings, current process does not define any more Tech Leads, may consider to remove it now also, should be taken over by Project Leads only
| ^^^^^^^^^^^^^^^^^^^ | ||
| Steering of the project is done with the help of *Committees*. | ||
|
|
||
| .. _PLCMBRS: https://github.com/orgs/eclipse-score/teams/automotive-score-PLC-team |
There was a problem hiding this comment.
All Link does not work for me
There was a problem hiding this comment.
Links to Team Structure will be available with: eclipse-score/.eclipsefdn#133
| .. _PLCSLC: https://sdvworkinggroup.slack.com/archives/PLC | ||
| .. _PLCBKL: https://github.com/orgs/eclipse-score/projects/PLC | ||
|
|
||
| .. _TLCMBRS: https://github.com/orgs/eclipse-score/teams/automotive-score-TLC-team |
| .. _pmp_pm_bug: | ||
|
|
||
| Open points from the meetings will be handled by *GitHub Issues* in the *S-CORE* main repository and can be filtered via label *technical_lead_circle*. | ||
| **Bug** |
There was a problem hiding this comment.
What is with improvements or same as Task?
| .. _pmp_pm_task: | ||
|
|
||
| * **Technical Lead Circle meeting** | ||
| **Task** |
There was a problem hiding this comment.
Task/Improvement or separate Improvement?
| - Assignees | ||
| - :ref:`Labels <pmp_pm_gh_labels>` | ||
| - :ref:`Type <pmp_pm_issue_types>` | ||
| - Common Project Attributes |
There was a problem hiding this comment.
The current Project contains also Estimate? How to fill that or is it not in scope?
See below, description should explain, what fields are mandatory and how to fill and which are not used
There was a problem hiding this comment.
I am preparing standard templates and as we have a bunch of different attributes a transformation proposal for each exisiting project e.g. estimation => size
|
|
||
| Releases | ||
| ^^^^^^^^ | ||
| *Releases* are special milestones and used for baselining of the development activities. |
There was a problem hiding this comment.
May link here to the Release Management Plan, in general, may link to the parts of the PMP, where details are described, Release Management, Config Management, etc.
| and one for the complete `S-CORE Roadmap <https://github.com/orgs/eclipse-score/projects/17>`_. Inside a GitHub Project, there is the possibility to generate different views | ||
| for Table, Board and Roadmap supporting Backlogs, Open Point or Task Lists and other useful perspectives. | ||
|
|
||
| .. image:: _assets/score_project_management_planning_overview.drawio.svg |
There was a problem hiding this comment.
As commented above Component Requests?, Feature Modifications, Component Modifications, eclipse-score/module_template#41
20 participants
closes #2401, closes #2379 , closes #2411