New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Relates to #12. Project Management Process #13
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
360 changes: 360 additions & 0 deletions
360
projects/eth1.x/project-admin/project-management/MANAGEMENT_PLAN.md
Large diffs are not rendered by default.
Oops, something went wrong.
3 changes: 3 additions & 0 deletions
3
projects/eth1.x/project-admin/project-management/appendices/FILE_STRUCTURE.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# FILE STRUCTURE | ||
|
||
**TODO** |
5 changes: 5 additions & 0 deletions
5
...ects/eth1.x/project-admin/project-management/appendices/ORGANISATIONAL_CHART.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
# ORGANISATIONAL CHART | ||
|
||
### Figure 1 - DECENTRALISED ORGANISATIONAL CHART <a id="appendix-org-chart"></a> | ||
|
||
**TODO** |
75 changes: 75 additions & 0 deletions
75
projects/eth1.x/project-admin/project-management/appendices/POSITION_CHARTER.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,75 @@ | ||
# POSITION CHARTER | ||
|
||
* Project Director - **TBA** | ||
* Responsibilities | ||
* Commitment and provision by entities of require resources and financial capability to ensure successful delivery. | ||
* Monitor level of service to key entities and stakeholders and initiate necessary changes. | ||
* Liaise with key entities and stakeholders. | ||
* Ensure new high level initiatives are incorporated. | ||
* Monitor that key personnel have the appropriate level of experience and authority to fulfil their responsibilities. | ||
* Project Manager - **TBA** | ||
* Responsibilities | ||
* Timeliness and quality of all deliverables | ||
* Reviewing the status and adequacy of the Management Plan to ensure its ongoing suitability and effectiveness. | ||
* Day-to-day Project Management and coordination or delegation to a Displine Team Leader | ||
* Liaise with key entities and stakeholders. | ||
* Liaison with the Project Discipline Leaders on challenging appointments of personnel to responsibilities. | ||
* Project budget control and weekly reporting | ||
* Attending and chairing weekly Project Meetings | ||
* Contract administration (change of scope, variation and extension of time requests) | ||
* Ensuring non-conformances are managed in accordance with the requirements of Management Plan | ||
* Initiating Quality Audits where necessary and instigating any corrective actions. | ||
* Ensuring the Management Plan is updated to address any identified deficiencies or upon significant changes in scope. | ||
* Progress control and reporting; | ||
* Monitoring work elements and processes and the allocation of resources to the Project Team. Initiating changes as required | ||
* Appointment of personnel and subcontractors. | ||
* Approval of invoices. | ||
|
||
* Deputy Project Manager - **TBA** | ||
* Responsibilities | ||
* Preparation of weekly/monthly reports and invoices | ||
* Records and archiving | ||
* Daily assistance to the Project Manager and Interface Manager. | ||
|
||
* Interface Manager - **TBA** | ||
* Responsibilities | ||
* Ensuring the adequacy and completeness of all activities and deliverables | ||
* Interfacing with Project Managers, advisors, stakeholders to provide coordinated and integrated deliverables | ||
* Cross-disciplinary coordination and checking across interfaces verification activities | ||
* Issue of | ||
deliverables and filing in the central filing system; | ||
* Coordinating and controlling subcontractors and ensuring their work is reviewed and verified | ||
* Chairing and participating in weekly meetings | ||
* Day-to-day assistance to the Project Manager and Team Leaders with project activities | ||
|
||
* Project Discipline Leader(s) - **TBA** | ||
* Responsibilities | ||
* Reporting to the Design/Interface Manager | ||
* Authority for the day-to-day management of the relevant technical design team. | ||
* Day-to-day management and coordination of their discipline team; | ||
* Regular liaison with the Design/Interface Manager | ||
* Update the Design/Interface Manager on work progress, resources and issues that may involve changes of scope, variations or extensions of time | ||
* Work area planning, budget control and reporting to the Design/Interface Manager | ||
* Ensuring that all project activities under their control are carried out in accordance with the requirements of the Services Brief and this Management Plan | ||
* Cross-disciplinary coordination and checking across interfaces between work elements (within the work area and between other work areas), verification activities and issue of deliverables | ||
* Coordinating and controlling subcontractors and ensuring their work is reviewed and verified. | ||
|
||
* Project Team - **TBA** | ||
* Responsibilities | ||
* Advise and support the relevant Project Discipline Leader and Interface Manager in identification of resources, programming, response to verification, budget control, and reporting, and ensuring the adequacy and timely and effective delivery of technical outputs in accordance with the project requirements of the Service Brief. | ||
* Overall control of detailed assessment, analysis, design computations, investigations and reporting, implementing, and documenting the project. | ||
|
||
* Engineering Authority Management Approver - **TBA** | ||
* Responsibilities - Approve Management Plan. Shadow Reviewers | ||
|
||
* Engineering Authority Management Reviewer - **TBA** | ||
* Responsibilities - Review Management Plan Management | ||
|
||
* Subcontractors - **TBA** | ||
* Responsibilities | ||
* All subcontractors are to work to a detailed brief designed to incorporate the relevant requirements the [Services Brief](./SERVICES_BRIEF.md). | ||
* Subcontractors will be coordinated on a day-to-day basis by the Project/Interface Manager and/or the relevant Discipline Team Leader to ensure that project services are fully integrated but are responsible for their own internal management and communication. | ||
|
||
* **TODO** | ||
|
||
* Note: Only appropriately qualified and experienced personnel may occupy some roles. **TODO** |
3 changes: 3 additions & 0 deletions
3
...s/eth1.x/project-admin/project-management/appendices/PROJECT_ISSUES_REGISTER.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# PROJECT ISSUES REGISTER | ||
|
||
**TODO** |
3 changes: 3 additions & 0 deletions
3
...x/project-admin/project-management/appendices/PROJECT_OPPORTUNITIES_REGISTER.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# PROJECT OPPORTUNITIES REGISTER | ||
|
||
**TODO** |
3 changes: 3 additions & 0 deletions
3
...cts/eth1.x/project-admin/project-management/appendices/PROJECT_RISK_REGISTER.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# PROJECT RISK REGISTER | ||
|
||
**TODO** |
3 changes: 3 additions & 0 deletions
3
.../eth1.x/project-admin/project-management/appendices/REVIEW_COMMENTS_REGISTER.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# REVIEW COMMENTS REGISTER | ||
|
||
**TODO** |
3 changes: 3 additions & 0 deletions
3
projects/eth1.x/project-admin/project-management/appendices/RFI_REGISTER.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# RFI REGISTER | ||
|
||
**TODO** |
81 changes: 81 additions & 0 deletions
81
projects/eth1.x/project-admin/project-management/appendices/SERVICE_BRIEF_EIP.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,81 @@ | ||
# SERVICE BRIEF - EIP | ||
|
||
The scope demarcations and management of Eth1.x has been split into a services brief containing the following stages: | ||
|
||
* Stage A - Project EIP Options | ||
* Activities | ||
* Review previous EIPs for completeness and compliance with new criteria. | ||
* Divide into manageable EIPs by [EIP Type](http://eips.ethereum.org/). | ||
* Define deliverables for each EIP package, including reports and specification | ||
* Prepare Project EIP Options Report (Review & Assessment) | ||
* Prepare Management Plan | ||
* Review Business, System, and Operational User Requirements | ||
|
||
* Deliverables | ||
* Management Plan, including: | ||
* Work Breakdown Structure (WBS) | ||
* Project Schedule | ||
* Interface Management Plan | ||
* Monthly Reports | ||
* Project EIP Options Report | ||
|
||
* Stage B - Concept EIPs | ||
* Activities | ||
* Submit Project EIP Options Report to Stakeholders | ||
* Obtain Review Comments from Stakeholders and record in Review Comments Register | ||
* Undertake System Planning ahead of Implementation | ||
* Undertake Project Risk Assessment, Project Security Assessment, and Project Sustainability Assessment | ||
* Update Project Issues Register, Project Risk Register, Project Opportunities Register | ||
* Prove the preferred EIP options from Stage A | ||
* Develop each EIP to the level required for submission | ||
* Create a Draft Proposal for each EIP to a standard suitable to submit an EIR. | ||
* Verify suitability of the EIP. | ||
* Prior to a EIP submission by a Proposer they must have demonstrated competency in the subject matter and obtained Ethereum Authority (EA) from an authorised Ethereum Subject Matter Expert (SME). | ||
* EIP should contain sufficient detail to illustrate that the EIP has been fully defined and coordinated across all disciplines including integration of security, and specified to a degree such that its approval does not adversely affect other disciplines or interfaces. | ||
* Proposer of the EIP must obtain relevant consents and approvals from standard authorities and agree and address all stakeholder requirements in the EIP. | ||
* Submit an EIR (Ethereum Improvement Request), which is the submission of an EIP as a Pull Request for review. | ||
* EIPs have been split into the following EIP Types and associated EIP Status: | ||
* Standard Track | ||
* **TODO** | ||
* Core | ||
* Draft | ||
* [EIP 615: Static Jumps and Subroutines](https://eips.ethereum.org/EIPS/eip-615) | ||
* [EIP 1829: Precompile for Elliptic Curve Linear Combinations](https://eips.ethereum.org/EIPS/eip-1829) | ||
* [EIP 1057 ProgPoW, a Programmatic Proof-of-Work](https://eips.ethereum.org/EIPS/eip-1057) | ||
* Networking | ||
* Draft | ||
* [EIP 778 Ethereum Node Records (ENR)](https://eips.ethereum.org/EIPS/eip-778) | ||
* Interface | ||
* **TODO** | ||
* ERC | ||
* **TODO** | ||
* Informational | ||
* **TODO** | ||
* Meta | ||
* Draft | ||
* [EIP 1679 Hardfork Meta: Istanbul](https://eips.ethereum.org/EIPS/eip-1679) | ||
|
||
* Deliverables | ||
* EIP and EIR | ||
* Update Management Plan | ||
* Risk Management Plan **TODO** | ||
* Update Project Issues Register, Project Risk Register, Project Opportunities Register | ||
* Monthly Reports | ||
* **TODO** | ||
|
||
* Stage C - Tender Documentation | ||
|
||
* Activities | ||
* Stakeholder Workshops **TODO** | ||
* Obtain EIR Approval (EIP Status of Approval) | ||
* Prepare and Submit deliverables internally OR | ||
* Create Tender Documents for decentralised tendering EIPs as contracts in accordance with the Procurement Strategy **TODO**. | ||
|
||
* Deliverables | ||
* Tender documents and specificiations | ||
* Information for preparation of Pre-tender Cost Estimates including Work Breakdown Structure (WBS) and contract Schedules (as required) | ||
* Waivers (if any) | ||
* Close-out Review Comments Register for each EIP | ||
* Close-out Project Issues Register, Project Risk Register, and Project Opportunities Register | ||
* Monthly Reports | ||
* **TODO** |
3 changes: 3 additions & 0 deletions
3
projects/eth1.x/project-admin/project-management/appendices/WBS.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# WORK BREAKDOWN STRUCTURE (WBS) | ||
|
||
**TODO** |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These positions would depend on if we can get funding to cover these roles, as far as official positions go.