Page tree
Skip to end of metadata
Go to start of metadata
  • How does the new planning process integrate with other processes already in place?
    • FOLIO Roadmap: TBD (Capacity Planning Team is meeting with representatives of the Roadmap Team on March 15, 2021)
    • Institution Ranking:  Each institution is provided with a custom field in JIRA (i.e. Rank: <institution name>) for storing their rank (i.e. R1, R2, R3, R4, R5) for each UXPROD feature.  This ranking can be viewed as the institution's requirements. How does this rank integrate with the new points process?
      • For the new planning process, the "ballot" will include any feature with at least one institution rank of R1 or R2. 
      • The extra capacity a team may have after planning their highly-pointed features will be spent working on highly-ranked features.
    • PO Rank:  The custom JIRA field PO Rank is a way for product owners to make sure the features that should be worked on in a release are sorted in the correct order.  There may also be mandatory work that needs to be planned, or features from the previous release that were not completed. If a PO has a lot of highly-pointed/highly-ranked features that require back-end development, but has no remaining back-end capacity, they may need to pull in some lower ranked features that require only front-end development.
  • How will the points be used to actually plan the release?
    • Our development teams are not planned at 100% of their capacity.  We must take into account holidays, vacations, meeting time, bad estimates, etc.  To plan accordingly, the teams planned via the Capacity Plan have 60% of their capacity designated as available. 
    • Teams need to reserve part of this 60% for work besides new features.  For example, most of the teams planned via the Capacity Plan have 40% of their capacity allocated to new features, 40% allocated to bugs and 20% allocated to tech debt.  In this example, 40% (of the 60%) would be planned to include the highly-pointed features. 
  • No labels