Communication

[TRJFP2019]

anything there

[charlielafosse]

Thanks for that! This will be a great place to talk about meeting times for this week @TRJFP2019

[charlielafosse]

I know you're busy, but if you ever have a moment check out this product owner's guide to Git here @TRJFP2019

[charlielafosse]

Just following on from earlier @TRJFP2019, the upcoming important dates for the next couple weeks:

• (Week 1) Thursday 7th Feb

  • User testing of the prototype.
  • Sprint planning (quick chat with you to get you up to date with what we're planning to do and build over the next two weeks).

• (Week 2) Thursday 14th/Friday 15th

  • Sprint testing, review and planning.

• (Week 3) Friday 22nd

  • Product handover! 🚀
  • Will include a complete presentation on the app.

[Oliversw]

So, we've thought a lot about how to properly implement this verification, and this is what we're thinking of right now. Let us know what you think @TRJFP2019 and @Jbarget! It's a bit complicated to explain in text but I'll do my best.

To begin with, there will be a log in page. For the moment we are thinking of using Airtable.com to host our database, so that Adam can log in and access it from there. For the moment, he will input the list of current drivers and suppliers, including their details, and they will use that information to log in (potentially with email and an id number or password).

Drivers, once logged in, will simply see a screen with today's code (that will originally be hard coded into an Airtable, but will eventually be generated daily) and a reminder of their ID number (or other personally identifiable information).

Suppliers, once logged in, will see two inputs - one for today's code and another for the driver's ID number. They will need to ask the driver for the information for both (they can just show their own page on the app) and then submit it. If all is well they will receive a success page, otherwise they will receive an error page potentially asking them to try again or providing the number to call The Real Junk Food Project. If the verification is successful, we will also record in the database the driver's name, the supplier, and the time, so that there are records for every pick up.

This is quite basic and there is a lot more that we would like to do, but this seems like the most achievable route to do what we need in the shortest amount of time. Ideally we would complete this quickly and then be able to move on to improving it, like using proper databases and creating an admin page for Adam to be able to use. Hopefully this makes some sense, but if you have any questions please let us know!!

[charlielafosse]

Hey @TRJFP2019 we've got a quick question:

How do you organise your drivers each day? It'd be great to know a little bit more about the process: i.e is there one person/admin who knows which drivers are going where, do the drivers all meet somewhere before they head out etc.

Thanks!

[TRJFP2019]

Hi all,

No idea if this is the right place to post this.

Thursday is proving to be a very difficult day for myself and all of the potential users. I don't think I'm going to be available at any point during the day sorry.

I have spoken with Farmfoods HQ, and they mentioned that their staff only use an intranet, and managers do not have Wi-Fi/mobile phone access whilst at work...just to give you some feedback.

I cannot get a hold of Morrisons HQ. We had a call scheduled today, but this didn't happen.

SUMA can be available at 14:00, so maybe I can send them the link?

RE: Question above - Drivers are coordinated via a Whatsapp group. We're fortunate to have consistent drivers, however, we do sometime find ourselves short.
They either come in to collect our company vehicle and are given a route, based on the amount of time they are available for. Or, they collect food on their way in to the HQ from their home, using their own vehicle.

Oliver - love the concept so far, thank you!

[charlielafosse]

@TRJFP2019 this is definitely the right place to post this, thanks so much for getting back to us!

Re: Farmfoods - thanks for that feedback. I think in terms of what we can achieve for the first stage product, the app would only be able to work with Wi-Fi or mobile data. However, exploring ways to get the app functioning offline would be great to work on in the future if the app continues development!

Good news about SUMA - we'll email and text you the link for the prototype beforehand and you can pass it onto them. As we mentioned the other day, it'd be great to know nearly the exact time that they'll be opening the link and testing the prototype, as we'll be able to watch their screen as they interact with it. We'll have it up on our screens for 14:00 anyway though.

[charlielafosse]

@TRJFP2019 here's the link to our prototype! Preferably to be used on mobile, but can also be used on desktop too. I'll send it over to you now over text and email as well.

For both you and the users testing it, there's no right or wrong ways of doing things. We're just looking to learn about how people understand and use the app, and whether the flow is intuitive and makes sense. It's useful if both you and the users can just share anything and everything that comes into your mind as you explore the app, good or bad!

Link here: https://www.figma.com/proto/ViyQ6NenEbc3ezuzFibVHEPT/The-Real-Junk-Food-Project?node-id=0%3A1&scaling=scale-down