# What's in a Milestone
Rationale and Reasoning § A project’s goals and priorities are described at its top level by a list of Milestones. The list of these milestones should serve as a guidepost to anyone who is interested in what the project is working on, what the deliverables are of that work, and how that work is going.

- - Nomos Consulting
- Nomos Consulting
- Nomos Consulting
- Nomos Consulting
- - Waku RLN Relay
- ACZ Roadmap Preview
- - - - - - - proxy-re-encryption
        - - Nescience ZK Consulting
      - - init
  - - - Status RLN Usage
  - - Light RLN Verifiers
  - RLN Doc and Outreach
- RLN Light Clients
- - Multi Epoch Constraints
- RLN relay ERC20
- RLN v2 E2E integration
- RLN v2 Waku Relay Integration
- RLNP2P Waku Pruduction Readiness Details
- Waku RLN Membership Management Details
- Waku RLN-RELAY Enhancements 02
- Waku RLN-RELAY Enhancements Details
- - - Secure Channels - fully decentralized design
  - Secure Channels - MLS design
- Secure Channels - MLS PoC
- Secure Channels - PoC of fully decentralized protocol
- - Stealth Address Kit Maintenance
- Stealth Address Kit Research
- - - Productionize Tor Push in Nimbus
- - - maintenance
  - Zerokit v0.4 Release Details
- Zerokit v0.5 Release
- Zerokit v0.6 Release
- - - - Gossipsub Anonymity Layer
- - - Carnot Paper
- - - Reviews
- - - Gossipsub Improvements Paper
  - Gossipsub Simulation
- Unstructured P2P Improvements Survey
- - - Tor Push Paper
  - Tor Push PoC
- Tor Push Related Work
- - - Codex Deep Research ZK consulting
  - Storage Proofs: Open Problems Review
- - - - Blockchain Security in Crypto-economic Models
    - Carnot 2/3 Vote aggregation
  - Carnot Bribary Article
- Carnot Paper 02
- Detecting Reporting Attacks Carnot
- Inter Chain Protocol
- Multi-Leader and Multi-Overlay Carnot
- Network Privacy Stack - Stakeholder Privacy
- - - validator-privacy
- - mix-net-solution
- priv-validator-network
- tor-push-rln
- - - - Testnet
  - - Mixnet
- - Ongoing testing of specific monthly libp2p releases
- - 10k Node Cluster
- Midscale
- - - Bundle Simulation Data
- - - Deployer Tool
  - Visualiser Tool
- - - CI Integration
- - Rlog: Wakurtosis Retrospective
- Wakurtosis Maintenance
- - Techreport
- Techreport_02
- Wakurtosis Features
- - - - Control Messages
  - - Refactoring
- - - Basic Shadow Simulation
  - Shadow Gossipsub Analysis
- - Shadow Waku Relay Analysis
- - - Carnot 2-3rds Vote Aggregation Python Implementation
- - Simulation Analysis
- - - Rlog: Wakurtosis Retrospective
  - Wakurtosis Rlog
- - Gossipsub Topology Analysis
- - 2023-aug
- - - - Benchmarks
    - Research Existing Proofsystems
- - - State Separation Architecture 01
  - State Separation Architecture 02
- - - VM Ecosystem
  - VM Foundations
- - - - chronos-maintainance
- - - compiler
  - editor
- lsp
- nim-suggest
- nimble
- - - - Libchronos Maintenance
- - - Gossipsub DDoS Mitigation
  - Gossipsub Improvements EIP 4844
- Gossipsub Stagger Send
- Libp2p Maintenance
- WebRTC Transport
- - - - Test Automation Codex Discovery
  - - Test Automation cryptarchia
  - Test Automation Data Availability
- - Test Automation nim-libp2p
- Test Automation nim-tooling
- - Interop Testing
- Interop Testing Part 2
- Maintenance go-waku
- Maintenance js-waku
- Maintenance nwaku
- Status-go CLI Testing
- Status-go CLI Testing 2
- Test Automation go-waku
- Test Automation js-waku
- Test Automation nwaku
- Test Automation RLN
- Test Automation Sharding
- Test Plan RLN
- Test Plan Sharding
- Test Plans
- WebSockets Stress Testing
- - - - specs-init
  - - carnot-specification
  - carnot-threat-model-informational
- carnot-vote-2-3rds-vote-aggregation-specification
- inter-chain-protocol-specification
- multi-leader-and-multi-overlay-carnot-specification
- specs-init
- - Port Status Specs
- - rfc-index
- rfc-process-update
- - core-rfc-updates
- Waku Keystore
- - - - Contracts Formal Verification
    - Review Codex Contracts
- - Access Control Safe Support
- - Community Contracts CollectibleV1 Batch transaction Extension
- Community Contracts Deployer
- Community Contracts ERC20
- Community Contracts ERC721
- Community Contracts Maintenance
- Community Contracts Token Import
- Community Curation dapp Contracts
- Community Vaults - Token Airdrop
- ENS Usernames contracts maintenance
- Governance Contract MVP
- MiniMe Token Enhancements
- MiniMe Token Maintenance
- SNT Optimism Bridge
- Status Staking Contract Maintenance Details
- Status Staking Contract MVP
- Status Staking Contract V1
- Status Swap Aggregator
- - Secureum Upskilling
- Vac RLN Contract Support Details
- - - - Analysis of the Codex Token
    - Codex Bandwidth Incentives
  - Codex Contract Default
- Codex Contract Finalization
- Codex Contract Initiation
- Codex Contract Matching
- Codex Economic Analysis
- Codex Fee Mechanism
- Codex Insurance Mechanism Analysis
- Codex Lender Analysis
- Codex Proof Aggregators
- Codex Recovery Auction
- Codex Slot Repair
- Codex Tax System
- Codex Testnet Incentives
- - Finance Real Option Models
- Financial Growth Models
- - Cryptarchia Wealth Concentration Estimated Stake
- Cryptarchia Wealth Concentration Known Stake
- Nomos Delegation Research
- Nomos Economic Analysis
- Nomos Enshrined Delegation
- Nomos Mixnet Incentives
- Nomos Non Private L2 Consensus
- Nomos Penalizable Actions
- Nomos Rewarded Actions
- Nomos Shared Liquidity
- Nomos Supply Policy
- Nomos TDC Objectives
- Nomos Transaction Fee
- Nomos Validator Rewards
- Nomos Validator Rewards
- Nomos Whitepaper
- - Incentivize Status Communitities
- SNT Governance Proposal
- SNT Litepaper
- SNT Staking
- Status L2 deployment
- Waku Sharding
- - Waku Economic Analysis
- Waku General Incentives
- Waku RLN Attacks Vectors
- Waku RLN Membership
- Waku RLN Risks
- Waku Store Incentives
- - 2023-07-10 Vac Weekly
- 2023-07-17 Vac weekly
- 2023-07-31 Vac weekly
- 2023-08-03 Vac weekly
- 2023-08-07 Vac weekly
- 2023-08-17 Vac weekly
- 2023-08-21 Vac weekly
- 2023-08-28 Vac weekly
- 2023-09-04 Vac weekly
- 2023-09-11 Vac weekly
- 2023-09-18 Vac weekly
- 2023-09-25 Vac weekly
- 2023-10-02 Vac weekly
- 2023-10-09 Vac weekly
- 2023-10-16 Vac weekly
- 2023-10-23 Vac weekly
- 2023-10-30 Vac weekly
- 2023-11-06 Vac weekly
- 2023-11-13 Vac weekly
- 2023-11-20 Vac weekly
- 2023-11-27 Vac weekly
- 2023-12-04 Vac weekly
- 2023-12-11 Vac weekly
- 2023-12-18 Vac weekly
- 2023-12-25 Vac weekly
- 2024-01-01 Vac weekly
- 2024-01-08 Vac weekly
- 2024-01-15 Vac weekly
- 2024-01-22 Vac weekly
- 2024-01-29 Vac weekly
- 2024-02-05 Vac weekly
- 2024-02-12 Vac weekly
- 2024-02-19 Vac weekly
- 2024-02-26 Vac weekly
- 2024-03-04 Vac weekly
- 2024-03-11 Vac weekly
- 2024-03-18 Vac weekly
- 2024-03-25 Vac weekly
- 2024-04-02 Vac weekly
- 2024-04-08 Vac weekly
- 2024-04-15 Vac weekly
- 2024-04-22 Vac weekly
- 2024-04-29 Vac weekly
- 2024-05-06 Vac weekly
- 2024-05-13 Vac weekly
- 2024-05-21 Vac weekly
- 2024-05-27 Vac weekly
- 2024-06-03 Vac weekly
- 2024-06-10 Vac weekly
- 2024-06-17 Vac weekly
- 2024-06-24 Vac weekly
- 2024-07-01 Vac weekly
- 2024-07-08 Vac weekly
- 2024-07-15 Vac weekly
- 2024-07-22 Vac weekly
- 2024-07-29 Vac weekly
- 2024-08-05 Vac weekly
- 2024-08-12 Vac weekly
- 2024-08-19 Vac weekly
- 2024-08-26 Vac weekly
- 2024-09-02 Vac weekly
- 2024-09-09 Vac weekly
- 2024-09-16 Vac weekly
- 2024-09-23 Vac weekly
- - - Finance Wallet monitoring
  - Improve Finance Reporting
- - Comms Discord Statistics
- IFT Finance Reporting
- IFT Weekly News Website
- Program Overview Dashboard
- Smart Contract Monitoring
- Townhall helper
- Townhall transcript
- VAC Website Contributors
- X Space Analytics
- - Github Monitoring
- Logos Circle Event Dashboard
- Logos Circle Monitoring
- Logos Public RAG
- Logos Winnable Stories extractions
- - RAG Context
- RAG Embedding and Context
- RAG Evaluation mechanism
- RAG MCP Integration
- - Status Social Pipeline
- BI Roadmap Preview
- - - Anoncomms Evaluation
- - Blockchain Evaluation
- - Codex Base Capacity
- Codex Base Capacity
- Codex Comparison
- Codex Comparison
- Codex Evaluation
- - DST Conduit
- DST Conduit
- DST Conduit
- DST Lab
- DST Lab
- DST Research destination
- DST Research destination
- DST Research destination
- DST Research destination
- DST Research destination
- DST Tooling
- DST Tooling
- DST Tooling
- DST Tooling
- Libp2p Evaluation
- Scaling think tank
- Scaling think tank
- VacLab
- VacLab
- VacLab
- Visualiser Tool
- - Logos-core Evaluation
- - Messaging Evaluation
- Messaging Scaling
- - Nomos Scaling
- Nomos Scaling
- Nomos Scaling
- Nomos Scaling
- - Status chat protocol benchmarks
- Status evaluation
- Status evaluation
- Status-go chat protocol benchmarks
- Status-go chat protocol benchmarks
- - Storage Evaluation
- - Libp2p Evaluation
- Libp2p Evaluation
- Libp2p Evaluation
- Libp2p Evaluation
- Libp2p Evaluation
- - Theoretical Analysis
- Waku Evaluation
- Waku Evaluation
- Waku Evaluation
- Waku Evaluation
- Waku Evaluation
- Waku Scaling
- Waku Scaling
- Waku Scaling
- Waku Scaling
- Waku Scaling
- Waku Tooling
- Waku Tooling
- DST Roadmap Preview
- - 2024-10 Vac monthly
- 2024-11 Vac monthly
- 2024-12 Vac monthly
- 2025-01 Vac monthly
- 2025-02 Vac monthly
- 2025-03 Vac monthly
- 2025-04 Vac monthly
- 2025-05 Vac monthly
- 2025-06 Vac monthly
- 2025-07 Vac monthly
- 2025-08 Vac monthly
- 2025-09 Vac monthly
- 2025-10 Vac monthly
- 2025-11 Vac monthly
- 2025-12 Vac monthly
- - - 2024q4 Nimble
  - 2025q1 Nim IDE tooling
- 2025q1 Nimble
- 2025q2 Nim IDE tooling
- 2025q2 Nimble
- 2025q3 Nim Core Libraries
- 2025q3 Nim IDE tooling
- 2025q3 Nimble
- 2025q4 Nim Core Libraries
- 2025q4 Nim IDE tooling
- 2025q4 Nimble
- 2026q1 Nim Core Libraries
- 2026q1 Nimble
- Nim IDE Tooling 2024Q4
- - Logos Storage Nimble Integration
- Messaging Nimble Integration
- - Nimbus Nimble Integration
- Nimbus Nimble Integration
- - Waku Nimble Integration
- Nim Roadmap Preview
- - - ACZ Consulting
  - ACZ Consulting
- ACZ Consulting
- - AutoNAT v2
- GossipSub Extensions and Partial Messages
- GossipSub Performance Improvements
- GossipSub Performance Improvements
- GossipSub Performance Improvements
- Kademlia DHT
- Kademlia DHT
- Kademlia DHT
- nim-libp2p Auto TLS
- nim-libp2p c-bindings
- nim-libp2p c-bindings
- nim-libp2p Connection Management
- nim-libp2p IPv6 support
- nim-libp2p logos-core
- Nim-libp2p maintenance
- Nim-libp2p maintenance
- Nim-libp2p maintenance
- Nim-libp2p maintenance
- Nim-libp2p maintenance
- Nim-libp2p Mix
- Nim-libp2p Mix
- nim-libp2p Universal Connectivity App
- nim-libp2p Universal Connectivity App
- nim-libp2p Universal Connectivity App
- nim-libp2p Webtransport
- nim-libp2p Webtransport
- nim-libp2p Webtransport
- nim-libp2p Webtransport
- nim-libp2p Webtransport
- nim-libp2p Wrapping ngtcp2
- Quic Stabilization and removal of runtime dependencies
- - nim-libp2p Test Coverage
- nim-libp2p Test Coverage
- P2P Roadmap Preview
- - - Anoncomms testing
- - Codex Integration Testing
- - Nim Libp2p Testing
- Projects QA Strategy
- Projects QA Strategy
- QA & RFC Synchronization for Js-Waku Project - Core Protocols
- QA & RFC Synchronization for Js-Waku Project - Core Protocols
- QA & RFC Synchronization for Waku Project - Core Protocols
- - Keycard Testing
- Keycard Testing
- Keycard Testing
- - Logos Core QA
- - Messaging Testing
- - Nomos Data Availability Testing
- Nomos Data Availability Testing
- Nomos Data Availability Testing
- Nomos E2E Testing for Nomos Node
- Nomos E2E Testing for Nomos Node
- Nomos E2E Testing for Nomos Node
- - Status Go Functional Testing
- Status Go Functional Testing
- Status Go Functional Testing
- Status Go Functional Testing
- Status QA
- Status QA Desktop
- Status QA Desktop
- Status QA Desktop
- Status QA Documentation
- Status QA Mobile
- Status QA Mobile
- Status QA Mobile
- - Nim Libp2p Testing
- Nim Libp2p Testing
- Nim Libp2p Testing
- Nim Libp2p Testing
- - Chat SDK Testing
- Direct Message Reliability Testing
- Messaging API Testing
- RLN Smart Contract Testing
- RLN Smart Contract Testing
- Status Go Functional Testing
- Waku Interop Testing
- Waku Interop Testing
- Waku Interop Testing
- Waku Interop Testing (extended)
- Waku Testing
- waku-go-bindings Testing
- waku-go-bindings-testing Testing Framework
- Waku-sync Integration Testing
- Waku-sync Testing
- QA Roadmap Preview
- - - RFC Iteration
- - RFC Iteration
- - Marketplace and Client 2024q4
- RFC Iteration
- RFC Iteration
- RFC Iteration
- - Integration with QA
- Integration with QA
- Integration with QA
- RFC Culture Establishment
- RFC Culture Establishment
- RFC Culture Establishment
- RFC Culture Establishment
- RFC Culture Establishment
- rfc-index-maintenance
- rfc-index-maintenance
- rfc-index-maintenance
- rfc-index-maintenance
- rfc-index-maintenance
- rfc-index-maintenance
- - RFC Iteration
- - RFC Iteration
- - RFC Iteration
- RFC Iteration
- - Data Availability Raw RFC
- Data Availability Raw RFCs
- Data Availability Raw RFCs
- RFC Iteration
- RFC Iteration
- RFC Iteration
- RFC Iteration
- - RFC Iteration
- RFC Iteration
- Status Specs to RFC-Index Migration
- - RFC Iteration
- - 2024q4 RFC Iteration
- Migration of PoC Waku RFCs to the rfc-index
- RFC Iteration
- RFC Iteration
- RFC Iteration
- RFC Iteration
- - RFC Iteration
- RFC Roadmap Preview
- - - MLS Smart Contracts Consulting
- - ghost.fun Protocol Review
- - Codex Vault Integration
- Formal Verification (Part 1)
- Formal Verification (Part 2)
- - EIP Discussions
- Formal Verification Tools Research
- Security Audits
- Security Audits
- Security Audits
- Security Audits
- Smart Contracts LearnUp Sessions
- Smart Contracts LearnUp Sessions
- Smart Contracts LearnUp Sessions
- Smart Contracts LearnUp Sessions
- - Risc0 Upskilling
- - Base Chain Integration
- Comunities Contracts on Status Network testnet
- Karma RLN
- Maintainin existing Status smart contracts
- Maintainin existing Status smart contracts
- Staking Protocol (v1)
- Staking Protocol Documentation
- Staking Protocol Refinement
- Status Network Native Bridge Yield Bearing Module
- Status Network Native Dex
- Status Smart Contracts Consulting
- Status Smart Contracts Consulting
- XP NFT (v1)
- XP Token (v1)
- - Maintaining existing Status Network L2 smart contracts
- New Karma Requirements for SN L2
- SN L2 Bridge DAI Yield Management
- SN L2 Bridge ETH Yield Management
- Status Network Karma Enhancements
- Status Network L2 Audit Preparation
- Status Network L2 Pre-Audit Protocol Enhancements
- SC Roadmap Preview
- - - Demos
  - Logos Contributions Portal
- Logos Core
- Logos Marketing Campaign Narratives & Brand Testing
- Logos Website
- Logos Website
- Newsletter
- Parallel Society Festival Website
- Qaku App
- Web Maintenance & Support
- Web Maintenance & Support
- - Keycard Website
- Keycard Website
- - Contribute Portal
- Logos Forum
- Logos Website
- - Community Curation
- SN Hub
- SN Hub
- SN Hub
- SN Website
- SN Website
- Status App
- Status App
- Status Wallet Extension
- Status Wallet Extension
- Status Website
- Status Website
- Status Website
- Web Roadmap Preview
- - 2023-07-10 Vac Weekly
- 2023-07-17 Vac weekly
- 2023-07-31 Vac weekly
- 2023-08-03 Vac weekly
- 2023-08-07 Vac weekly
- 2023-08-17 Vac weekly
- 2023-08-21 Vac weekly
- 2023-08-28 Vac weekly
- 2023-09-04 Vac weekly
- 2023-09-11 Vac weekly
- 2023-09-18 Vac weekly
- 2023-09-25 Vac weekly
- 2023-10-02 Vac weekly
- 2023-10-09 Vac weekly
- 2023-10-16 Vac weekly
- 2023-10-23 Vac weekly
- 2023-10-30 Vac weekly
- 2023-11-06 Vac weekly
- 2023-11-13 Vac weekly
- 2023-11-20 Vac weekly
- 2023-11-27 Vac weekly
- 2023-12-04 Vac weekly
- 2023-12-11 Vac weekly
- 2023-12-18 Vac weekly
- 2023-12-25 Vac weekly
- 2024-01-01 Vac weekly
- 2024-01-08 Vac weekly
- 2024-01-15 Vac weekly
- 2024-01-22 Vac weekly
- 2024-01-29 Vac weekly
- 2024-02-05 Vac weekly
- 2024-02-12 Vac weekly
- 2024-02-19 Vac weekly
- 2024-02-26 Vac weekly
- 2024-03-04 Vac weekly
- 2024-03-11 Vac weekly
- 2024-03-18 Vac weekly
- 2024-03-25 Vac weekly
- 2024-04-02 Vac weekly
- 2024-04-08 Vac weekly
- 2024-04-15 Vac weekly
- 2024-04-22 Vac weekly
- 2024-04-29 Vac weekly
- 2024-05-06 Vac weekly
- 2024-05-13 Vac weekly
- 2024-05-21 Vac weekly
- 2024-05-27 Vac weekly
- 2024-06-03 Vac weekly
- 2024-06-10 Vac weekly
- 2024-06-17 Vac weekly
- 2024-06-24 Vac weekly
- 2024-07-01 Vac weekly
- 2024-07-08 Vac weekly
- 2024-07-15 Vac weekly
- 2024-07-22 Vac weekly
- 2024-07-29 Vac weekly
- 2024-08-05 Vac weekly
- 2024-08-12 Vac weekly
- 2024-08-19 Vac weekly
- 2024-08-26 Vac weekly
- 2024-09-02 Vac weekly
- 2024-09-09 Vac weekly
- 2024-09-16 Vac weekly
- 2024-09-23 Vac weekly
- 2024-09-30 Vac weekly
- 2024-10-07 Vac weekly
- 2024-10-14 Vac weekly
- 2024-10-21 Vac weekly
- 2024-10-28 Vac weekly
- 2024-11-04 Vac weekly
- 2024-11-11 Vac weekly
- 2024-11-18 Vac weekly
- 2024-11-25 Vac weekly
- 2024-12-02 Vac weekly
- 2024-12-09 Vac weekly
- 2024-12-16 Vac weekly
- 2024-12-23 Vac weekly
- 2024-12-30 Vac weekly
- 2025-01-06 Vac weekly
- 2025-01-13 Vac weekly
- 2025-01-20 Vac weekly
- 2025-01-27 Vac weekly
- 2025-02-03 Vac weekly
- 2025-02-10 Vac weekly
- 2025-02-17 Vac weekly
- 2025-02-24 Vac weekly
- 2025-03-03 Vac weekly
- 2025-03-10 Vac weekly
- 2025-03-17 Vac weekly
- 2025-03-24 Vac weekly
- 2025-03-31 Vac weekly
- 2025-04-07 Vac weekly
- 2025-04-14 Vac weekly
- 2025-04-21 Vac weekly
- 2025-04-28 Vac weekly
- 2025-05-05 Vac weekly
- 2025-05-12 Vac weekly
- 2025-05-19 Vac weekly
- 2025-05-26 Vac weekly
- 2025-06-02 Vac weekly
- 2025-06-09 Vac weekly
- 2025-06-16 Vac weekly
- 2025-06-23 Vac weekly
- 2025-06-30 Vac weekly
- 2025-07-07 Vac weekly
- 2025-07-14 Vac weekly
- 2025-07-21 Vac weekly
- 2025-07-28 Vac weekly
- 2025-08-04 Vac weekly
- 2025-08-11 Vac weekly
- 2025-08-18 Vac weekly
- 2025-08-25 Vac weekly
- 2025-09-01 Vac weekly
- 2025-09-08 Vac weekly
- 2025-09-15 Vac weekly
- 2025-09-22 Vac weekly
- 2025-09-29 Vac weekly
- 2025-10-06 Vac weekly
- 2025-10-13 Vac weekly
- 2025-10-20 Vac weekly
- 2025-10-27 Vac weekly
- 2025-11-03 Vac weekly
- 2025-11-10 Vac weekly
- 2025-11-17 Vac weekly
- 2025-11-24 Vac weekly
- 2025-12-01 Vac weekly
- 2025-12-08 Vac weekly
- 2025-12-15 Vac weekly
- 2025-12-22 Vac weekly
- 2025-12-29 Vac weekly
- 2026-01-05 Vac weekly
- Website Terms of Use
- What's in a Milestone

# What's in a Milestone

Jan 06, 2026, 5 min read

## Rationale and Reasoning §

A project’s goals and priorities are described at its top level by a list of Milestones. The list of these milestones should serve as a guidepost to anyone who is interested in what the project is working on, what the deliverables are of that work, and how that work is going.

> If you don't like "Milestone", call it whatever you want as long as it's in line with this description.

This document is an outline of how you should think about creating milestones for your project, and what information should be included in them such that the IFT Grant Process can be completed and everyone stays on the same page.

Projects work to produce things for people, and a milestone describes, plans, and tracks those things. To that end, the deliverables are the key components to reason around what a milestone is for your project. Who are you building for, what are you building for them, and why do they care? A small group of deliverables and the justified impact they have towards their targeted audience should be enough to help someone understand what a project is doing.

In effect, a given milestone is a declaration of:

- Here’s what we want to happen
- This is why this needs to happen
- Here’s how we’re going to make that happen
- This is what we need to do it
- Here’s how you can watch
- This is how confident we are that we can get it done (in time)

The scope of a given milestone is such that the total amount of work you plan for the year equates to ~4-5 individual milestones. For a small project, that’s focused and tight. For a large project, that’s cross-functional and broad. It is expected that larger projects have the appropriate project management resources to sub-divide their milestones in to sub-milestones, epics, and issues as appropriate.

We ask that the structure of the milestone is somewhat standardized across the IFT, as we have a lot of derivative and automation tasks to perform.

Here’s a list of the sections that need to be included in each milestone:

#### Milestone Title §

A short name of the milestone that succinctly describes its aim and scope.

#### Estimated Delivery Date §

A timeline in which the work is expected to be delivered

#### Description §

More detail as to what you’re aiming to accomplish with this milestone and the justification for its inclusion to the project. This is the human readable encapsulation of the milestone. Someone reading it should be able to understand the general scope of the entire thing, with all other sections adding context and detail.

#### Resources Required §

- roles and % application to it
- external services consumed (Vac/IFT)
- infrastructure

This information here, in combination with the IFT Finance team, should be enough to yield the required budget for the milestone. This allows for private financial information to stay appropriately separated while still allowing us to publish and broadcast the roadmaps (and their progress) to the broader communities.

#### Deliverables §

What are the tangible items that are the result of this milestone’s work, and who is the targeted audience for those items?

It is important to note that we’ve included the intended audience here. Is this a research PoC to be delivered to the Engineering team? Is this a mainnet launch that we need wide community broadcasting on? Is this an SDK being delivered to another IFT project? The appropriate communication of the deliverable should be considered here.

#### Tracking Metrics §

How we track progress on a given milestone is dependent upon what the goal of the milestone is and deliverables it aims to accomplish. As per Jarrad’s Strategy Document and mantra from previous talks, metrics around User Acquisition and Revenue Generation should be included wherever possibly appropriate. If it isn’t directly aimed at these two, its impact on how it facilitates it should be understood.

NOTE: The IFT Insights team will closely monitor all of these and provide dashboards to relevant stakeholders such that progress and status can be monitored and acted upon.

#### Work Breakdown §

Since this is the highest level of “work package” that is considered throughout the org, a description of the way this is going to be broken up and managed should be itemized here. This section is a process of showing “this is explicitly how we plan to deliver this milestone.”

NOTE: It is recommended that the broken down work is structured similarly so it can be understood and tracked, e.g. Milestone -> Epics -> Issues by the IFT Insights team, with each layer more narrowed in scope and explicit in detail. Each project has a significant level of autonomy on how they deliver on the agreed upon milestones and the associated project management and organization that entails it.

#### Perceived Risks §

Each milestone should include a section of what dependencies/assumptions/potential market changes there are that add risk to its completion. What factors come into play that can potentially affect the project delivery date, and how do each of them affect its delivery?