V2MOM

V2MOM for the Summit Events app

What's a V2MOM you may ask. That's a good question and there is a Trailhead for that.

Vision

To introduce a sustainable open source community events app that serves a broad variety of needs for EDUs and NGOs. The event solution has the flexibility needed to offer events of different types: paid, free, group, guests, and individual. The solution will include the full life cycle of the event: registration, receipting, confirmation, reporting and web faced exposure. This solution facilitates a Salesforce connected campus and will be compatible with Salesforce.org’s Data Architectures.

Note: This application is being built with a focus on Higher Education. That being said, the project understands the application has value for both K-12 and nonprofit audiences. This project encourages other uses and welcomes any support around increasing the flexibility of its architecture.

Values

• Trust - We value solutions built upon the continuous feedback and engagement of its community. Everything that goes into this solution is considered to have merit by its core community of users. When installing such solutions, an org should assured knowing they have access to a dedicated project team ready to support them should they encounter any issues, speed-bumps, or have questions.
• Community Sourced Innovation - We value the belief that a rising tide lifts all boats and by working together we can support and sustain the life of this application to the benefit of all involved.
• Continuous Delivery - We value innovating quickly by removing development obstacles to support feature enhancements, issue resolution, and release management.
• Ease of adoption - We value the fact that lowering the cost of implementation and ongoing support increases the potential for adoption and we’ve uphold this value through the introduction of an engaged open source community of collaborators and contributors, a dedicated project team, and an architecture that is compatible with EDA and/or NPSP.
• Ease of use - We value the need for end users (non admins and developers) to find this solution intuitive to use in the creation, reporting, and management of events..
• Flexibility - We value maintaining an architecture that is versatile enough to match the event needs of a variety business process and/or department needs.

Methods & Measures

• Method: Work to establish and sustain a dedicated project team of community sponsored organizations.
  • Measure(s):
    • Committed project team with organizational diversity of at least 3 and project roles of manager, developer, QA testers, technical writer, support and marketing being claimed by those on the team using Open Source Common Definitions as a guide for these roles.
• Method: Utilize continuous integration development and collaboration framework starting with CumulusCI, Salesforce DX, and GitHub.
  • Measure(s):
    • 10 GitHub users star the project repository
    • 4 GitHub users outside of the University of St. Thomas make pull request of code or documentation into the master branch of the project.
• Method: Introduce a process that supports ease of distribution and upgrades for the Summit Events App.
  • Measure(s):
    • Managed package
    • TDTM triggers for on/off optional functionality
• Method: Build community enablement around the Summit Events App with a focus on visibility, feedback, and adoption.
  • Measure(s):
    • Dedicated group in the Power of US Hub to drive visibility, feedback, and engagement
    • Repository of ate documentation inside Github that focuses on the users ability to install, configure, troubleshoot, escalate and contribute
    • Host 1 live walk-through of the Summit Events app
• Method: Establish the project through early adopter engagement.
  • Measure(s):
    • 1 high education institution identified for pilot use in a production org.
    • 1 nonprofit organization identified for pilot use in a production org.
• Method: Seek out community engagement opportunities to solicit additional support for documentation, development, and use cases.
  • Measure(s):
    • Project Team attendance at all Open Source Community Sprints in 2020
    • Visible Project Roadmap defined and shared before each Sprint in 2020
    • Encourage early adopters to attend at least 1 Sprint in 2020
• Method: Couple EDA and/or NPSP data as much as possible to not reinvent already in use best data architecture practices.
  • Measure(s):
    • School lookup and program linkages re-established in event definition (currently commented out because of previous non-Salesforce.org data architectures).
    • Keep core Summit Events package free of dependencies on other packages to maximize who can use it, but create "extension" packages to work with EDA and NPSP to provide needed functionality to work tightly with those tools (similar approach of how Outbound Funds has both a core package and an extension package for NPSP)

Obstacles

• Solution is currently in an unmanaged state
• Solution requires a heavy lift to get it to a managed state
• Lack of community visibility and engagement around solution as it stands today.
• Lack of invested community resources (i.e. developers, admins, business analysts, documenters, testers, and engagers).
• Lack of community experience collaborating in an Open Source environment.
• Lack of community experience using Salesforce.org continuous development and delivery toolsets.