Milestone is a SMART goal, that can be split into individual issues for steps and closed at the end of a sprint. It is not a place to collect thematically similar issues (label is the right option for this). Ideally, every milestone should be:
Specific – Well defined, clear, and unambiguous. A specific goal has a much greater chance of being accomplished than a general goal. Provide enough detail in milestone description so that there is no indecision as to what exactly the participant should be doing. Avoid words like
discussand any other similar lexis. Description should be precise and clear as possible. General discussions and brainstorming should be happening in separate issues and can not be a part of a live milestone
Measurable – The goal must be quantifiable, or at least allow for measurable progress. In this step, you’ll choose what your progress markers are and how you’ll measure them.
Assignable and Agreed – every milestone requires an assignee (officer or general who manages the milestone) and a person who validates the milestone at the creation stage and check with an assigned officer if there is any problem with deadline (general).
Relevant and Realistic – Relevance refers focusing on something that makes sense with the broader business goals (e.g. we prioritize working on a product over one-off client requests). Be diligent about eliminating irrelevant goals and sub-goals to save time.
Time-related – Good goals don’t stretch into infinity – they have a deadline. Make a timeline for your goal, set deadlines for issues and for the entire milestone. Go for short-term rather than long term, as this is more manageable (MVP concept) If it’s a project that’s going to take a few months to complete, then set several milestones by considering specific tasks to accomplish. Complete regular weekly or monthly check-ins to make sure the project is on schedule.
Approved milestones should be prioritized over individual issues. We should use issue trackers for milestones, or milestones in questions. The approval process can go either through a Google Meets, element dialogue, or the issue tracker - as long as both a general and an officer are mentioned in the milestone, it is their responsibility to check it.
Milestone description structure
- Commanding Officer - single person
- Overseeing General - single person
- Brief background:
- Functional/business requirements: As specific as possible. Progress markers (deliverables) and, ideally, MVP should be obvious from this section
Milestone tracker issue
If you want to create a milestone, open an issue with “Get started with a Milestone” template and follow the steps there. This issue template is available in all main repositories. If you don’t find one, ask BI team to help you. When creating a milestone tracker issue, make sure that you specify:
- why this effort is priority A for Inca, considering existing products, available resources, and our strategic goals
- detailed business/functional requirements and an MVP if needed
- an assignee at the officer level
- an overseeing general, who would need to approve your milestone
- a realistic deadline
- everybody involved
Use this issue to complete these steps and ping relevant people. Attach this issue to the milestone and keep it there as a progress tracker and a place to discuss process with everybody involved.