What is your capability to deliver your project with high levels of trust and accountability?
DLT360 was founded by an ambitious core team coming from many years of leadership experience in business and industry, combined with the fresh perspective of young talents in various disciplines (see team description later in this proposal). The senior founders have also been active members of and contributors to the Catalyst community since early on.
DLT360's core team and extended domain expert team in the knowledge areas of
- Economy
- Technology
- Regulation
- Politics
- ESG
has grown to approximately 25 people (the majority still part-time) during the past 2 years. With Fund 10, we also want to finance the launch of the DLT360 Token as the incentive basis for growing a vibrant global community of content contributors and solution partners.
DLT360 has successfully completed various projects in Funds 6, 7 and 8. Fund 10 is now dedicated to finalizing DLT360's foundational developments. This will get us to scale up our activities in 2024, for which we are aiming for a strategic partnership-based financing round - with the vision to become THE major think-tank and commercial consulting entity in the dynamically growing CARDANO/Web 3.0 space.
What are the main goals for the project and how will you validate if your approach is feasible?
This project is focusing on achieving the following goals and deliverables
-
Creating an open usable material KANBAN solution based on Cardano:
-
Due to the nature of the project, we lower the barrier for the digital adoption of material KANBAN and make it affordable to all sizes of businesses
-
Increase the adoption of Cardano in the industrial space:
-
Currently, there is limited adoption of public permissionless blockchain solutions in the industrial space. This solution will drastically lower the entry barrier for adoption through a practical use case, which has significant cost benefits.
-
Increase the inclusion of small and medium businesses utilizing material KANBAN cycle:
-
Due to the very low cost of adoption due to the pay-per-setup/use approach, this becomes an affordable and therefore inclusive option for specifically small and medium size businesses to adopt industry practice in a digital way.
Please provide a detailed breakdown of your project’s milestones and each of the main tasks or activities to reach the milestone plus the expected timeline for the delivery.
The project will be delivered with an agile methodology broken down into 4-week cadences (2 x two-week sprints) for delivery as follows:
Milestone 1: Project, Processes & Team in place
-
Timeline: End of Week 2 of 52 | Sprint 1
- Method: DLT360 program- and project management
- Activities:
- Setting up project infrastructure & Web-landing page, kickoff meeting
Milestone 2: Architectural vision defined
-
Timeline: End of Week 4 of 52 | Sprint 2
- Method: Research &
- Activities:
- Research in the different methods of KANBAN circles
- Creation of architectural vision
- Definition of requirements & documentation
Milestone 3: Architectural design drafted & finalized
-
Timeline: End of Week 8 of 52 | Sprint 3 & 4
- Method: Architectural evaluation & rapid prototyping
- Activities:
- Definition Business architecture (processes), Information architecture (data), Technology architecture
- Selection of the most promising architectural design
Milestone 4: Development of a PoC draft & finalized
-
Timeline: End of Week 12 of 52 | Sprint 5 & 6
- Method: Rapid prototyping, Interviews
- Activities:
- Initiate rapid prototyping to create a demonstrator
- Feedback from industrial clients
Milestone 5: Refinement
-
Timeline: End of Week 16 of 52 | Sprint 7 & 8
- Method: Architectural design
- Activities:
- Update & refinement of architectural design
Milestone 6: Development partnership / UX Design
-
Timeline: End of Week 20 of 52 | Sprint 9 & 10
- Method: Sourcing - development partnerships
- Activities:
- Select development partners
- UX design (first drafts)
Milestone 7: UX Design & Development (Web 2.0/Smart Contracts)
-
Timeline: End of Week 24 of 52 | Sprint 11 & 12
- Method: UX Design, Programming
- Activities:
- UX design frontend
- Development backend & frontend
Milestone 8: Development (Integration Web 2.0 & backend & smart contract)
-
Timeline: End of Week 28 of 52 | Sprint 13 & 14
- Method: Programming, Testing
- Activities:
- Development frontend, backend, smart contract
- Integration testing
Milestone 9: Testing
-
Timeline: End of Week 32 of 52 | Sprint 15 & 16
- Method: Testing, Programming
- Activities:
- User Acceptance Test (design)
- Bug fixes
Milestone 10: Documentation, Training & Marketing (Phase 1)
-
Timeline: End of Week 36 of 52 | Sprint 17 & 18
- Method: Creation training, writing documentation, PR & marketing
- Activities:
- User documentation
- Marketing & PR (product demos)
- Customer presentations
Milestone 11: Documentation, Training & Marketing (Phase 2)
-
Timeline: End of Week 40 of 52 | Sprint 19 & 20
- Method: Writing, Communication
- Activities:
- Creating training material
- Creating product videos
- Creating explainer videos
- Writing user documentation
- PR & Marketing
Milestone 12: Development wrap up | Sprint 21 & 22
-
Timeline: End of Week 44 of 52
- Method: Documentation
- Activities:
- Finalizing training material
- Scheduling pilot training
- Media communication
Milestone 13: Roadshow & Pilot customer presentations
-
Timeline: End of Week 48 of 51 | Sprint 23 & 24 (one week)
- Method: Presentation
- Activities:
- Pilot training
- Roadshow
- Pilot customer presentation/onboarding
Final Milestone: Project completed
-
Timeline: End of Week 52 of 52 (one week)
- Method: Reporting
- Activities: As a last step, we establish the close-out report and the close-out video as required by the Catalyst guidelines
<u>Project Management:</u>
- Monitoring progress using Github
- Tracking budget usage via Excel
- Submitting a monthly report to Catalyst IOG Team
- Submitting Proof of Milestone reports to Catalyst IOG Team per milestone
Please describe the deliverables, outputs and intended outcomes of each milestone.
Milestone 1: Project, Processes & Team in place
- Deliverable(s):
- [1] Proof of Life
- [2] Statement of Milestones
- [3] Project environment
- Acceptance Criteria:
- [1] & [2] PoC & SoM completed
- [3] Project environment available
- Evidence:
- [1] & [2] Collected by IOG/CT teams
- [3] Short video
Milestone 2: Architectural vision defined
- Deliverable(s):
- [1] Research paper
- [2] Architectural vision document
- Acceptance Criteria:
- [1] Research from about 20 resources collected
- [2] Architectural vision documented & reviewed
- Evidence:
- [1] Paper
- [2] Document
Milestone 3: Architectural design drafted & finalized
- Deliverable(s):
- [1] Architectural documents
- Acceptance Criteria:
- [1] Architectural design(s) documented & reviewed
- Evidence:
- [1] Document(s)
Milestone 4: Development of a PoC draft & finalized
- Deliverable(s):
- [1] Prototype
- [2] Interviews
- Acceptance Criteria:
- [1] Prototype is available
- [2] Interviews have been performed (at least 3)
- Evidence:
- [1] Short video
- [2] Documents (interview notes)
Milestone 5: Refinement
- Deliverable(s):
- [1] Update architectural design
- Acceptance Criteria:
- [1] Update on architectural design documented & reviewed
- Evidence:
- [1] Document(s)
Milestone 6: Development partnership / UX Design
- Deliverable(s):
- [1] Agreements with development partner
- [2] UX design
- Acceptance Criteria:
- [1] Agreements signed (at least 2 partners)
- [2] UX design
- Evidence:
- [1] Agreement (signature page)
- [2] Figma file
Milestone 7: UX Design & Development (Web 2.0/Smart Contracts)
- Deliverable(s):
- [1] Frontend (prototype)
- [2] Backend
- Acceptance Criteria:
- [1] Frontend is developed according to the UX design
- [2] Backend is functional
- Evidence:
- [1] + [2] Short video (demonstration)
Milestone 8: Development (Integration Web 2.0 & backend & smart contract) | Sprint 13 & 14
- Deliverable(s):
- [1] Smart contract(s)
- [2] Integration frontend & backend
- [3] Integration smart contracts
- Acceptance Criteria:
- [1] Smart contracts functional
- [2] Integration functional
- [3] Smart contracts can be executed from Web 2.0 elements
- Evidence:
- [1] - [3] Short video
Milestone 9: Testing
- Deliverable(s):
- [1] User Acceptance Test
- [2] Bug fixes
- Acceptance Criteria:
- [1] User Acceptance Test successful
- [2] Major bugs fixed
- Evidence:
- [1] Document(s) UAT
- [2] Repo submits (Short video)
Milestone 10: Documentation, Training & Marketing
- Deliverable(s):
- [1] User documentation
- [2] Product demos
- [3] Customer presentations
- Acceptance Criteria:
- [1] Documentation available
- [2] Product demos available
- [3] Customer presentations available
- Evidence:
- [1] Online documentation
- [2] Short video
- [3] Presentations
Milestone 11: Documentation, Training & Marketing
- Deliverable(s):
- [1] Training material outline
- [2] Product videos
- [3] Explainer videos
- [4] User documentation
- [5] PR & Marketing plan
- Acceptance Criteria:
- [1] Training material outline available
- [2] Product video available
- [3] Explainer videos available
- [4] User documentation online
- [5] Communications plan available
- Evidence:
- [1] Document(s) (training material)
- [2] Product videos
- [3] Explainer videos
- [4] Online documentation
- [5] A short video (overview comms plan)
Milestone 12: Documentation, Training & Marketing
- Deliverables:
- [1] Training material (finalized)
- [2] Pilot training scheduled (online)
- [3] Media communication started
- Acceptance Criteria:
- [1] Training material available (finalized)
- [2] Pilot training scheduled & invitations sent
- [3] Communication document(s)/video(s) available & comms plan activated
- Evidence:
- [1] Document(s) (Training material)
- [2] A short video (Bookings/confirmations)
- [3] Document(s)/video
Milestone 13: Roadshow & Pilot customer presentations
- Deliverables:
- [1] Pilot training
- [2] Online roadshow (different time zones)
- [3] Pilot customer
- Acceptance Criteria:
- [1] Pilot training delivered
- [2] Roadshow started (at least 2 events)
- [3] Pilot customer acquired
- Evidence:
- [1] Short video
- [2] A short video (impressions)
- [3] Document(s)
Final Milestone:
- Deliverable(s):
- [1] Closeout report
- [2] Closeout video
- Acceptance Criteria:
- [1] Report available & submitted
- [2] Video available & submitted
- Evidence:
- [1] Document (report)
- [2] Short video