We have identified 3 stakeholders which drive our initiatives. We are building Community Tables products to be easily customized by any local community organizer -- captured by the term localized. Our initial efforts are grounded by Michelle, the Founder of Community Table TN. Michelle is our first customer and viewed as our primary stakeholder during this initial product increment. The other two stakeholders are composites of known neighbors in need and community members, respectively. Persona template adapted from orangebus.

Here are more in-depth profiles of our Stakeholder Personas.

• Name: Community Cloud Tables
• Product Iteration Near Vision: Community Cloud Tables is a software platform to facilitate, support, and encourage neighbors helping neighbors. Through CCT's highly localizable site templates and features, community organizers can easily customize their site to raise awareness, harness membership, and communicate tailored services to those in need.
• Key Architecture:
  • Infrastructure: Amazon AWS Cloud Services
  • Java: Spring MVC / Tomcat
  • Persistence: Mongo DB
  • JavaScript: Bootstrap / jQuery / ReactJS

Community Cloud Tables is a Java 8 Spring MVC web application which leverages HTML5, CSS3 and third party libraries. The primary data store is a MongoDB database. See the architecture diagram for more details:

We have implemented the following CI / CD process:

Community Tables current product backlog is available to our Scrum Team members and management at Trello

Reference our Team Formation Sprint for our Definition of Ready, Definition of Done, User Story Sizing approach, and starting Product Backlog snapshot.

The backlog is ordered by value generated to our stakeholders, namely Community Table TN (the first customer for our open source products). We (as well as our key stakeholder) are starting from scratch (levering other open source software frameworks where feasible). PBIs are groomed to represent excellent users stories within our team's Definition of Ready and have been estimated by the development team.

Our sprint progress is documented at the following link: Sprint 3 (11/28-12/11)

1. Create a rich-text blog within the Admin Portal (established in Sprint-2). Creator can optionally set a featured image when creating (see #5 below).

2. Manage created blogs within the Admin Portal, to include support to delete blogs.

3. Site has a new public section where blogs are initially listed by configurable excerpt.

4. Any blog can be viewed in full by clicking on either the title or the 'Read full entry' button.

5. Share blog url to popular social media platforms such as Facebook, using featured image and exposed via Open Graph meta tags to render previews.

If no featured image is provided, then a site configured default image is provided.

Our sprint progress is documented at the following link: Sprint 2 (11/14-11/25)

1. About Page (backed by highly customizable templates); also supports Google Map API for dynamic location with graceful fallback if missing.

2. Vision Page (also uses templates) to more deeply express the focus and future of the organization.

(continued...)

3. Admin Portal for sensitive site operations, e.g. Member Communication (see below) and Blog Management (estimated sprint3).

4. Allow authorized admins to get a list of emails, ready to copy/paste into email message for ad-hoc communication with registered members. This is the first feature to use the new Admin Portal (see above).

Our sprint progress is documented at the following link: Sprint 1 (10/8-11/11)

1. Compelling site landing page

2. Backed by highly customizable templates ready for your content

3. Customized Welcome Email automatically sent upon registration

4. Unsubscribe link embedded in all site emails

• Scrum Master / Developer (Front End): Melvin Tercan
• Product Owner / Developer (Back End/Front End): Michael Johns
• Developer (Back end) / Meeting Facilitator: Kelly J. Doyle
• Developer (Back end/Front End) / DevOps: Dairai Nyabando
• Developer (Back end): Paul Laskorski
• Developer (Front End/Back End) / DevOps: Vinod Halaharvi
• Developer (Front End) / UX Designer: Shawn Roe

Additional developer info can be found in our Project Setup Notes -- this is a work in progress and most certainly incomplete.

We can also be found in Canvas Project Group 6 and on our Slack channel. Our Kanban board can be found at Trello.