Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Unassigned
Created By: Cory Warden
Created Date/Time: 12/2/2019 4:31 pm
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 5266
Template/Type: Brandon Time
Title/Caption: Steve, Cory, Brandon-Catch up on projects and updates
Start Date/Time: 12/5/2019 4:00 pm
End Date/Time: 12/5/2019 5:30 pm
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

Cory and Josh were talking about the number of clicks, settings, and being able to show/hide certain fields. The two hot points were the shopping cart and the PO (purchase orders) page. Basically, getting items into the system and then being able to sell out those items quickly. We are leaning towards some shopping cart settings and also breaking down the needs into smaller steps as we know that some of the pieces may end up being really big.

We talked about sketching things out on paper/pencil and then moving things into a graphic mock-up, coding and then wiring things up.

We showed both Josh and Cory some of the new graphic mock-ups that are being done by both Jonathan and Chuck. We looked at some of their ideas and mock-ups to talk about options, layouts, and configuration options. We talked about showing them, meaning our clients, some of the mock-ups and graphics of where we are heading, that would be way better than having them design things from the ground up.

Managing customer expectations. That is always a challenge. As we were getting deeper and deeper, we are seeing more and more needs/wants of being able to configure and customize their own settings and such.

One of the projects that we talked about was dealing with updates and helping to let our clients know about certain updates before they get rolled out, especially if the updates may have consequences and/or possible issues. Some of the high traffic areas are carts, invoices, and state compliance stuff. We talked about delaying some of the updates instead of just pushing up new code.

Josh recommended a update log that could be searched and even have a small blame section - who coded it. Hopefully blame is the wrong word, but we all know what that means.

Maybe a different section, like the developer's notebook, where we could publish some of the updates and make announcements. We also talked about scheduling the code pushes and making sure that we aren't running faster than we are able.

Molly joined us towards the end of the meeting and had some great comments. Good stuff.