Best Practices: Github Milestones

Github Milestones are used to group sets of issues and help set a due date to them. There is no formal process right now for doing this in the project process, because not all projects are complex enough to require using milestones. However, as a creative director, development lead, or project manager, you may be interested in the progress of a certain group of work over time, in a smaller bucket than just "Design" or "Development", which is what you would see in SmartSheet. This is where milestones come in really handy.

A couple of ways you could use milestones in your project:

• Track the development progress of a major feature within your project in real time, such as a faculty directory that is part of a website redesign
• Track the progress of all work assigned to a particular sprint, and find out if you are running ahead or behind
• Track the progress of issues required for certain upcoming themes in one of our products

Whether or not you choose to use milestones is completely up to you as part of the team leadership. If you're a contributor, you won't need to worry about milestones. They're really for reporting information and staying on track with project schedules.

And remember: The final say for all scheduling and dates is in SmartSheet, regardless of what dates you may see assigned to a milestone. Always check with your project manager for the final answer on when something is due by.