Meetings:

March 31st, 2 hrs:

All team members present and on time

Agenda:

• High-fi revision touchpoint

• Dev Touchpoint

• Demo discussion (decide preliminarily how we are showing off our MVP)

• Script discussion

• User Story Workflow Discussion

• Initial slide deck discussion

April 3rd, 2 hrs:

All team members present and on time

Agenda:

• Working Session

• Storyboard Discussion

• Final High-fi revision Discussion

• Promotional Website setup

April 7th, 1 hr:

Anuj excused for illness

Agenda:

• Jira touchpoints (design & dev)

• storyboard discussion

• Discuss demo idea tweaks

• First slideshow deck discussion/ideation

Closed Tasks:

Project Logo: Jill, Nikki

Due Date: April 3rd

Description: For this task, we finalized our Juncture logo and configured it to syllabus guidelines.

Takeaways:

• We decided as a team not to make further refinements/adjustments because we have other more pressing tasks on our plate for this final quarter that need to be accomplished before the showcase.

Post High-fi Revisions: Jill, Nikki

Due Date: April 3rd

Description: For this task, we used our high-fi testing feedback in order to make some final critical refinements to our design prototype in order to address issues and discrepancies found during testing.

Takeaways:

• We addressed any user confusion or concern with design tweaks, most notably solidifying our “Choose a time” flow into a smoother process.

• Now that post-hi-fi revisions are completed, our UI screens are completely ready for dev handoff.

Missing App Pages Wrap up: Jill, Nikki

Due Date: April 7th

Description: For this task, our team did an audit of our prototype designs and created all missing pages and states that were needed for our final MVP.

Takeaways:

• Created additional hi-fi wireframes for pages that were needed for the app, including empty state pages, the profile page, and the page for a user to select their own thumbnail.

• This process helped us explore interactions on pages we hadn’t designed for previously.

User Journey Arc Brainstorming: Entire Team

Due Date: April 11th

Description: For this task, our team conducted an initial brainstorming activity in order to develop and crystallize ideas of how we want to tell our user journey story for the following storyboarding task.

Takeaways:

• This task was a great exercise in synchronizing the team’s vision. It was refreshing to realize that we all had very similar impressions of how Juncture should best be demonstrated, as well as which features were the most critical to highlight.

• Once the teams initial visions were established, we refined and condensed the suggested arcs into a tighter narrative.

• We sought to highlight:
  -The chaos of planning without Juncture
  -The ease of which Juncture allows for event creation
  -Finding an available time is simple and quick
  -Memories can be shared afterwards.

• We focused on making the story about a group of friends, and tried to convey a casual, fun feel to align with our intentions for Juncture.

Figma UI Implementation: Anuj, Leah

Due Date: April 7th

Description: For this task, our developers used our completed hI-fi prototype to begin porting over the majority of our Figma assets and designs into our development environment and harmonized our build's appearance with that of the design system.

Takeaways:

• This task wasn’t difficult, per say, but it was time consuming. Thanks designers labeling certain screens and components ready for development, and utilizing “Dev” mode in figma, we were able to complete this task efficiently and effectively.

• We’ve also gained better insights in what is feasible or not from a development perspective with the UI, since certain elements were more difficult to implement than we expected. However, we’ve been able to overcome these challenges and create a number of custom components despite working against our calendar library.

Event Comment Implementation: Anuj, Leah

Due Date: April 3rd

Description: Users should be able to comment within events in order to share information and ask questions about said event.

Takeaways:

• While this task wasn’t the most difficult, it did require some careful adjustment of our database tables. We needed to ensure proper hierarchy of comments, as well as making sure they were synced up between users.

• Luckily, due to previous work syncing and adjusting the tables to match, we were able to accomplish this task without too much issue. Ideally, we’ll be able to take this work and apply it for when we intend to put comments on photos in the future.

Adjusting RSVP Status: Anuj, Leah

Due Date: April 3rd

Description: Users who have not responded to an invitation should be labeled as “Invited,” instead of “Maybe” being the default.

Takeaways:

• This was a long discussion, but we ended up determining that it was worth the update to Juncture. This wasn’t too difficult from a dev perspective; we did have to introduce a new possible state for event attendees, but that wasn’t difficult as we’d done it before.

• Additionally, we just had to be careful to remove the default state from the availability selector.

• We believe this will make who is coming to an event much clearer, because now there is more clarity over who’s accepted an event or not.

Showing RSVP status on Calendar: Anuj, Leah

Due Date: April 3rd

Description: A user’s attendance status should be displayed at the top of the event in a tag.

Takeaways:

• We had to adjust and update our event rendering function for our calendar library. This was a little difficult, as we had to work against the defaults. However, we’d created and updated the calendar renderer in the past, so it wasn’t impossible.

• Getting everything synced up properly was a challenge, but with our previous work we were able to create a cohesive whole that matches with the designers' intentions.

Removing Friends/Declining Requests: Anuj, Leah

Due Date: April 3rd

Description: Users should be able to decline friend requests and remove friends.

Takeaways:

• This was not a difficult task. We’ve done event deletion before, and this was an even more straightforward task.

• While we did have to introduce some new UI elements in order to allow for rejection/deletion, the actual flow itself was straightforward. We accomplished this task with little issue.

Select Juncture Thumbnails: Anuj, Leah

Due Date: April 3rd

Description: When creating an event, users should be able to select from an array of Juncture supplied thumbnails instead of using their own photo if they wish.

Takeaways:

• We’ve handled photo storage and uploading on numerous other tasks, so this one was not a challenge. We’ve implemented this system using similar work as to what we’ve done in the past, such as making links to the photos and then loading them from the database.

• The only major adjustment to the process was that we currently have these images in Cloudinary. At the time of completion, we had not yet gotten more storage on our Supabase. This has changed now that we have our funding. However, we’re keeping the images in Cloudinary for the time being as the links are not changing, and if we have time/need will move them over later.

Open Tasks:

Initial Demo Preparation: Entire Team

Due Date: April 14th

Description: For this task, the team is working on several smaller sub tasks in order to begin the process of constructing what our demoable MVP experience is going to look like. For example these tasks include thoughts on how our users will interact with the application, how we can easily show them our features, and catering a lively experience so that they don't see a barren new profile upon entering the app.

Takeaways:

• For our demo, attendees will be able to create their own Juncture account, and we will have each account prep populated with a "digital past" showing past events uses have "attended" and photo galleries from those events.

• we have decided to have one catered dummy google account that all attendees will have access to sync to their Juncture account, showing their "schedule" for the following couple of weeks. (users may also opt to use their own google account to sync if they so choose (such is the ultimate intent of Juncture).

• We will create event-creation based tasks catered around other dummy accounts so that attendees can have goals to attempt, who's aim is to show off Juncture's core offering.

Round 1 QA testing: Entire Team

Due Date: April 14th

Description: For this task, our team is conducting a comprehensive round of QA testing where we try to discover bugs, design inconsistencies, and others issues to report to our developers in order to polish our MVP build and work out any major kinks.

Takeaways:

• We have discovered lots of bugs so far in our build-polishing process.

• Some bugs are related to functionality issues, while others are reflective of design inconsistencies that need to be tweaked.

Promotional Website: Jill

Due Date: April 24th

Description: For this task, we have begun to lay the groundwork designs for our promotional website for Juncture.

Takeaways:

• Our goal here is to highlight Juncture’s core product offering features (optimized time selection, memories, and event details) and showcases our unique UI.

Promotional Imagery: Jill, Nikki

Due Date: April 24th

Description: For this task, the team has begun to consolidate our imagery assets and design a few key promotional visuals for this deliverable.

Takeaways:

• Currently, we are keeping track of imagery used in promotional website and other materials in order to make sure our deliverable here reflect's Juncture's brand.

Elevator Pitch: Leah

Due Date: April 14th

Description: For this task, we are taking another look at our existing verbiage surrounding Juncture and constructing a comprehensive elevator pitch that outlines our product offering.

Takeaways:

• While Juncture’s initial elevator pitch isn’t the worst, it feels a little lackluster. We want Juncture to be warm and friendly, so infusing more of that tone into the pitch is our intention.

• We’re brainstorming options in order to see which are the best, which will require us to continue discussing which are the best for our purposes.

DIGM Showcase Slide Deck First Draft: Entire Team

Due Date: May 8th

Description: For this task, our team has begun having initial brainstorming discussions about what we want our slideshow deck to include as far as content and how our presentation unfolds.

Takeaways:

• This task is still in its infancy and we have only had one major discussion about our slide deck.

• But we have created a space to brainstorm ideas as our vision crystalizes for how we want to tell our story on Showcase day.

New Tasks:

Expo Poster Draft: Jill, Nikki

Due Date: April 24th

Description: For this task, our team will use the lobby poster assets to construct a new poster for our expo both at the DIGM Showcase.

User Journey Storyboarding: Entire Team

Due Date: April 14th

Description: For this task, our team will next be conducting storyboarding activities where we set up the scenes and angles that reflect our finished story arc outlined earlier.

User Journey Script: Alex, Leah

Due Date: April 21st

Description: For this task, pending the culmination of our storyboarding task, we will then write a script for our user storyboard before heading into full production on the video itself.