Skip to content

Added milestones to process

Eliran Mesika requested to merge acq-hb-3.4 into master

Why is this change being made?

Add clarity in the process of when milestones need to be created and what is our recommended standard protocol for creating those. Creating a standard protocol for integration milestone will further help templatize the process.

Why the specific values used?

  1. 3-4 milestones is a concise set of goals which should cover the bulk of our product interest in the target company being acquired.
  2. 6 months timeframe:
    1. 6 months is the ideal timeframe which isn't too far sighted where possible changes in priorities could consequently lead to us negating our interest in said milestones. This could further lead to complexed legal scenarios where payments are subject to milestone completion but if those were changed then the circumstances are different.
    2. Will help establish focus on both acquired target and our product team
    3. Be able to complete payouts to the entity and shut it down sooner
  3. Ship on first release after joining GitLab:
    1. Critical to adopting our culture and successful future integration of the target's engineering team in GitLab.
    2. Allows us to show early fruits of the acquisitions soon, aligned with our value of iteration.

Does this MR meet the acceptance criteria?

Conformity

Edited by Eliran Mesika

Merge request reports