Milestones

It's time to structure up for the upcoming 8-week hack sprint.

Purpose of Milestones

---

Milestones are great in many ways, except giving you solid historic points in your code & versioning it they also bring a lot of other benefits to the table.

Divide development into manageable pieces

Breaking down tasks within milestone to smaller pieces will contribute to keeping your focus where it should be and overall prevent going off road.

Monitor project progress

It is a checkpoint for tracking what has been done and how.

Identify project bottlenecks & Manage risks and assumptions

By breaking it down into Milestones & adding Issues to Milestones it will help to identify bottlenecks.

---

Milestones ABC

• Milestones have a describing name + and versioning https://semver.org/
• A Milestones should contain 3-7 days of work.
• Issues created in Github is added to milestone
• Use git tag 0.1.4 , git tag 0.1.4-rcto match your versioning with milestones
• When milestones are completed, it means that they:
  • met technical and design requirements
  • have tested code
  • is merged in to master branch

Milestone workflow

Initial setup

• Break down and divide your development process down to milestones where each of them have a demonstrable outcome.
• Add Milestones to github.
• Break down each milestone into smaller issues(tasks), tag issues with milestone
• As new issues can occur within milestone make sure to leave space for problems that can block the path.
• If you have own Github, invite Mathias @mindgames to the repo. If you don't have a git repo we will provide you with one.
• Add the milestones to your Roadmap in Notion and check them off.

Reporting

• Add @Mindgames in PR that closes milestone
• Update Roadmap as milestone is achieved

When you develop without specifications