Skip to content

2020 September Sprint Notes

Paul Ginsberg edited this page Jun 29, 2021 · 1 revision

We're getting started!

We want to build out a modular solution with a simple, adaptable data model.

Functional Areas We Want to Address

Modeling business rules

  • Who is eligible to purchase a membership?
  • Who is eligible to receive a discount on the membership?
  • More generally, what are the business rules surrounding this membership type?
  • Upgrade and downgrade paths?
  • Maintenance of membership dates
    • How do we allow organizations to control when dates are propagated from the Membership level to the Membership Contact Role level?
  • Tracking membership types
    • How do we walk the divide between support small orgs that might use a picklist versus big orgs that might use a Product?
      • Communities - what is the limitation around Products there? Would a Custom Object be better?

Payments and financial reporting

  • How do we connect dollars to memberships?
  • Acknowledge that memberships and Opportunities are not 1:1 in many situations.
  • Forecasting futures.

Membership types and attributes

  • What's the broadest, most flexible way to model membership types?

Benefits

User experience in building memberships

  • Automating connections to households/members

Rollups, Reporting, and Notifications

  • On the Contact and on the Household, we'd want to be able to roll up special types of membership, or criteria about memberships (like that they just expired) from all of the memberships in which they participate.

Use Cases

Individual Lifetime Membership

Note how this pulls in "Who", "Term", and "Benefits"