Dash Project Managament Framework Project Control Method 1 Robert Wiecko,

Document Information – Revision History VersionDateAuthorChanges description Robert WieckoFirst draft Robert WieckoPayment schedule definition Robert WieckoAgile and Traditional methods distinction

Table of Contents introduction assumptions and definitions project delivery payment schedule project artifacts

introduction 4

What Do We Expect As A Project Result?

Why Do We Need Dash PMF? 6 Solution: Dash PMF Simple, unified toolbox for Vendor and PM Based on industry standards (PMI, PRINCE2, ITIL) Tailored to Dash needs Requirements: Universal method to control Dash projects Provide information to MN network to make right decisions Control on Dash projects delivery Project status and budget reported on regular basis

Stakeholders Ask Different Questions UserAdminVendorMN Owner What should I develop and how? Where is configuration information? How can I use this tool? PM What needs to be managed? How should I vote? „Yes” or „no”?

Different Information Needed 8 User User Manual Masternode Operator Project Charter Delivery PlanStatus Report Project Dashboard Vendor Functional Specification Technical Specification Test Specification Administrator Operational Handbook Technical Specification Functional Specification Project Manager Project Charter Delivery PlanContract Acceptance Report What should I develop and how? Where is configuration information? How can I use this tool? What needs to be managed? How should I vote? „Yes” or „no”?

What Is Dash PMF? What is Dash PMF?What isn’t Dash PMF? Project control methodBureaucracy Useful information sourceUseless documentation Customizable frameworkCorporate standard

assumptions and definitions how does it work?

Assumptions Project Management Framwork (PMF) is obligatory for all projects funded by Dash Decentralized Governance system. Each Dash PM is trained and understands PMF. Each project funded by DGBB has Dash Project Manager (PM) assigned. Vendor selects delivery method (traditional or agile) and is responsible for delivery process. Dash PM is responsible for control of project and budget execution. Vendors receive guidance and assistance from Dash PM in PMF implementation.

End user of productProject sponsor Vendor Support engineer Project manager Project Roles / Stakeholders UserAdmin Vendor MN OwnerPM

Project Size Clasification 13 Large Medium Small Budget > $50k Budget > $10k and <= $50k Budget <= $10k

Traditional and Agile Three Project Phases 14 PreparationDeliveryOperation

Deliverables For Small Projects 15 Preparation Project Charter Delivery ContractUser Manual Operational Handbook ProductProject Dashboard Operation Closure Report

Deliverables For Medium and Large Projects 16 Preparation Project CharterDelivery Plan Delivery Contract Functional Specification Technical Specification Test SpecificationUser Manual Operational Handbook ProductAcceptance ReportProject DashboardStatus Report Operation Closure Report

project delivery how does it work?

Project Activities 18 Preparation Requirements and Scope Definition Proposal Submission Voting Delivery Development Traditional Agile AcceptanceHandover Operation Deployment / Go-Live Project Closure Support and Maintenance

Reporting Small Project – Traditional Workflow Project Start Proposal Sumbmission Research Project Charter Voting Project accepted? Project Close Contract Development Contract signed? Acceptance Accepted? User Manual Operational Handbook Deployment / Go-Live Handover Yes No Yes No Yes Project Dashboard

Reporting Large And Medium Project – Traditional Workflow Project Start Proposal Sumbmission Research Project Charter Delivery Plan Voting Project accepted? Project Close Contract Functional Specification Technical Specification Test Specification Development Contract signed? Acceptance Acceptance Report Accepted? User Manual Operational Handbook Deployment / Go-Live Handover Closure Report Yes No Yes No Yes Project Dashboard Status Report

Reporting Large And Medium Project – Agile Workflow Project Start Proposal Sumbmission Research Project Charter Delivery Plan Voting Project accepted? Project Close Contract Product Backlog Development Contract signed? Acceptance Acceptance Report Accepted? User Manual Operational Handbook Deployment / Go-Live Handover Closure Report Yes No Yes No Yes Project Dashboard Status Report Technical Specification Test Specification

payment schedule Financials

Different Payment Schedules 23 Large Project Medium Project Small Project Payment Schedule Single Payment OR Payment Schedule Single Payment

24 Preparation Requirements and Scope Definition Proposal Submission Voting Delivery DevelopmentAcceptanceHandover Operation Deployment / Go-Live Project Closure Payment

Sample Payment Schedule (Traditional Delivery) 25 Preparation Requirements and Scope Definition Proposal Submission Voting Delivery – Phase I Functional Specification Technical Specification Test Specification Payment I Delivery – Phase II User Manual Operational Handbook Payment II Delivery – Phase III Product Acceptance Report Handover Payment III Operation Deployment / Go-Live Project Closure Hyer-Care Payment IV

Sample Payment Schedule (Agile Delivery) 26 Preparation Requirements and Scope Definition Proposal Submission Voting Delivery – Release I Product Backlog Sprint 1…Sprint n Payment I Delivery – Release II Sprint 1…Sprint n Payment II Delivery – Release N ProductDocumentation Acceptance Report Handover Payment N Operation Deployment / Go-Live Project ClosureHyper-Care Payment N+1

project artifacts

List of Project Artifacts ArtifactLocation Project Charter Project-Charter-Template-V1.0.docx?api=v2https://dashpay.atlassian.net/wiki/download/attachments/ /01.Dash- Project-Charter-Template-V1.0.docx?api=v2 Delivery Plan sh-Project-Delivery-Plan-Template-V1.0.xls?api=v2https://dashpay.atlassian.net/wiki/download/attachments/ /02.%20Da sh-Project-Delivery-Plan-Template-V1.0.xls?api=v2 Contract sh-Contract-Template-V1.0.docx?api=v2https://dashpay.atlassian.net/wiki/download/attachments/ /03.%20Da sh-Contract-Template-V1.0.docx?api=v2 Functional Specifications sh-Functional-Specification-Template-V1.0.docx?api=v2https://dashpay.atlassian.net/wiki/download/attachments/ /04.%20Da sh-Functional-Specification-Template-V1.0.docx?api=v2 Technical Specification ash-Technical-Specification-Template-V1.0.docx?api=v2https://dashpay.atlassian.net/wiki/download/attachments/ /05.%20D ash-Technical-Specification-Template-V1.0.docx?api=v2 Test Specification ash-Test-Specification-Template-V1.0.docx?api=v2 ash-Test-Specification-Template-V1.0.docx?api=v2 User Manual sh-User%20Manual-Template-V1.0.docx?api=v2 Operational Handbook ash-Operational-Handbook-Template-V1.0.docx?api=v2https://dashpay.atlassian.net/wiki/download/attachments/ /07.%20D ash-Operational-Handbook-Template-V1.0.docx?api=v2 Acceptance Report Acceptance Report is a part of Test Specification Project Dashboard sh-Project-Dashboard-Template-V1.0.xlsx?api=v2https://dashpay.atlassian.net/wiki/download/attachments/ /10.%20Da sh-Project-Dashboard-Template-V1.0.xlsx?api=v2 Status Report sh-Project-Status-Report-Template-V1.0.docx?api=v2https://dashpay.atlassian.net/wiki/download/attachments/ /09.%20Da sh-Project-Status-Report-Template-V1.0.docx?api=v2 Closure Report The same as Status Report

Thank You Dash: Digital Cash

Backup Slides 30

Pros and Cons Advantages of PMF Disadvantages of PMF Projects under control on all project phases Additional effort of Vendor One method to all types of projects and all vendors Additional effort of PM Information for decision makers regularly updated Properly documented products Reusable templates

Responsibility Matrix UserMN OwnerVendorAdminPM Project Charter IR A Delivery Plan IR A Contract A R Functional Specifications RI Technical Specification RI Test Specification RI User Manual I R Operational Handbook RIA Acceptance Report IR A Project Dashboard IC R Status Report IC R Closure Report IC R R: Responsible (a person, who performs the task) A: Accountable (ultimately answerable for the completion of task (may delegate)) C: Consulted (who shares an input) I: Informed (who is kept up-to-date on progress)