Meetings:

Oct 21st, 1:15 hrs:

All team members present and on time

Agenda:

• Status post day reflections

• Go over feature list prioritization plans going forward for minimum MVP

• Competitor analysis touchpoint

• Interview progress touchpoint

• Vision board review

Oct 24th, 2hrs:

All team members present and on time (Alex remote)

Agenda:

• Working Session

• Review interview progress

• Competitor Analysis wrap-up

• Development touchpoint

  
  

Oct 28th, 2:15 hrs:

All team members present and on time

Agenda:

• Interview touchpoint

• Development touchpoint

• Next up with Design/UX

• NUF Analysis/Feature list discussion

Tasks:

Closed Tasks:

Fix Framer site view: Durando
Due Date: Oct 17th
Description: Fixed framer site so that it was responsive for status post review process.

Schedule Team event: All team members
Due Date: Oct 31st
Description: As a team, we scheduled a reoccurring event using Microsoft Teams in order to understand the flow process of coordinating an event between multiple people. While the event did give us some more experience with group scheduling, the team generally felt that this task did not grant us any significant insights into our problem space. It was a specific situation in Teams, and since we'd taken the time to perform some competitor flows, this didn't provide much information that we didn't already know.

Vision Board: All team members
Due Date: Oct 21st
Description: The team came together to create an initial vision board of all our ideas and themes about our app. This was meant to be a creative exploratory exercise and there is no concrete UI/branding as a result of this exercise. With this exercise, we were better able to determine how we planned to approach our app's design in the future. While nothing we established was final, we feel far more confident in regards to future design plans, and have gained a better understanding of what the team is hoping to achieve with Juncture's theming.

Competitor SWOT Analyses: All team Members
Due Date: Oct 21st
Description: We created SWOT analyses for all major competitors to our idea (7 direct, 3 indirect) in order to understand our competitors' strengths, weaknesses, and help to discover opportunities to develop a unique experience within our own app. We got a lot of valuable information from this. One of the major successes with this task was that even our most direct competitors seemed to be lacking features we planned to include. Because of this, we felt more confident in regards to our planned features going forwards.

Competitor flows & Comparison table: All team members
Due Date: Oct 21st
Description: The team came together to catalogue all the major common features of our competitors to understand what functionality/features were covered by each. With this, we also mapped out some sample flows for all of our competitors to understand their UIs a bit better and how they implemented common features. Doing this process allowed us to examine general features common to all calendar apps, that we felt we'd be remiss not to include. There was also the ability here for us to explore features we hadn't initially considered, which provided us good discussion when we began to examine specific features for Juncture.

MVP Architecture Map: Anuj & Leah
Due Date: Oct 21st
Description: Before digging deeper into development, our team created an initial architecture map. We wanted to ensure that all team members understood how all the services we were incorporating to run our app interacted with one another on the front & back end. This also helped us come up with a more solid plan for the future, as well as assisting us in deciding upon a database to use. It helped get the team get on the same page with these plans, as well as giving our developers a good reason to discuss the specifics of our infrastructure.

Initial Calendar Integration: Anuj & Leah
Due Date: Oct 31st
Description: Our developers created an initial connection from our app skeleton to Google Calendar through a third party service called Nylas. By doing this, our developer team created a proof of concept that demonstrated to the team that our idea was feasible in code. It established the groundwork that was necessary for entire foundation of Juncture in the first place. We can now move forward with other core setup deliverables that are roadblocks to all of our features. Through this process, our developers grew more accustomed with the Nylas API, gaining a deeper understanding of what it's able to provide for our application. We were able to determine where more effort would be required in order to fill in the gaps of where Nylas wouldn't be able to help us. This research into Nylas has served us well in discussions of feature planning, as we've been able to highlight specific API calls that will assist in that process.

Open Tasks:

Audience Interviews: Alex & Nikki
Due Date: Oct 28th
Description: Based on our survey feedback, our team created an interview script and has so far conducted 2 interviews. Out intention is to explore our potential user-base and understand how they use their calendars for scheduling. Additionally, we hope to discover any pain points they may have. Currently we have 2 pending scheduling, but we have gathered some interesting insights so far. We have verified that specifically social planning, takes place on mobile devices due to native capabilities such as notifications, default app integrations (photos, other calendars, contacts etc.), further cementing our choice to design and develop a native app. We also have been finding that, other than same day hangouts, which doesn't involve calendars much, planning social events usually happens in stages. So far, participants also say that they find value in sharing photos, and also find themselves reminiscing on memories when past photos are surfaced to them rather than seeking them out themselves.

Database Design map: Anuj & Leah
Due Date: Nov 4th
Description: This is the next major qualitative deliverable before the next stage of development. In order for construction of our database to begin, its important for our team to know the structure of our different database groups and how they will interact with one another.

Database Construction: Anuj & Leah
Due Date: November 11th
Description: We are also initiating initial setup and database construction in this current period. Once this task is completed, our dev team will be able to create profiles that can communicate with one another, and we can begin building out our critical calendar features from this skeleton system.

NUF Analysis & feature list: Everyone
Due Date: Oct 31st
Description: Utilizing our user research and our competitor analyses, our goal was to distill all this information into actual features that we could potentially include in our application. This process also included a High/Low Effort & impact matrix in order to understand what features needed to be implemented first as well as a feature ranking to guide our development process. While we've done some initial discussion in regards to our NUF, as a team we felt that the topic needed to be revisited. There were several features on which we were unsure of, so we intend to continue discussion.

New tasks:

Personas: Jill & Nikki
Due Date: Nov 4th
Description: Once we have gathered of all our initial data from surveys & interviews, our next step is to create comprehensive user personas drawn from this research in order to better understand our users.

Affinity mapping: Everyone
Due Date: Nov 7th
Description: Our team has slated affinity mapping for this next week in order to prioritize our feature clusters and gain key takeaways for next steps in our design process.