{"id":15468,"date":"2017-10-19T00:00:00","date_gmt":"2017-10-18T16:00:00","guid":{"rendered":"https:\/\/www2019.dash.org\/2017\/10\/19\/project-portfolio-report-october-2017\/"},"modified":"2021-09-18T11:39:25","modified_gmt":"2021-09-18T11:39:25","slug":"projectupdate","status":"publish","type":"post","link":"https:\/\/wp.dash.org\/news\/projectupdate\/","title":{"rendered":"Project Portfolio Report – October 2017"},"content":{"rendered":"
Dear Masternode Network and Community Members,<\/p>\n
As promised in another thread, I am sharing a Dash project portfolio report from Dash Core Group.
\nThe report contains synthesized information abut delivery status of all our development streams. We are still working on new form of reporting, so please consider it a temporary format.<\/p>\nGeneral comments about the work status<\/strong><\/p>\n
\n
- Majority of developers are being involved in DIPs creation and finalisation. DIPs are technical and functional specification of Dash Evolution.<\/li>\n
- Above causes \u201cON HOLD\u201d status in majority of Evolution development activities<\/li>\n
- After DIPs are being finalised, project plans are going to be updated and roadmap re-defined (with all dependencies included)<\/li>\n
- The team is intensively hiring missing resources<\/li>\n
- Dash Core Group management works on the legal structure finalisation and internal org structure<\/li>\n
- PM team works on delivery model and internal processes<\/li>\n
- Majority of risks are caused by lack of resources and work on DIPs (these risks are being mitigated already by hiring and delivery model preparations)<\/li>\n
- The report contains only status of development projects that are not confidential (e.g. it excludes ongoing integrations and BizDev work)<\/li>\n<\/ul>\n
Please find the report attached.
\nThank you.<\/p><\/blockquote>\nAttached Files:<\/h4>\n