| Collector App
|
| @Jonathan Bailey (Unlicensed) Alex expressed frustration about showing up to the demo and seeing the same thing he saw the previous week; I understand this frustration, and my own feeling is that this hurts our credibility as a team; our demos should focus on what we have worked on during the previous sprint, and not repeat what has been previously demonstrated Book time with Alex to create better rail maps for Imagine IT Roberto wants to be able to record where the inspector was when they created the inspection record, not just where the inspection is Alex suggests adding a field to indicate how the inspection was conducted (visual, drone, records from operators, Google Maps, etc.); there are a number of additonal ones that could be added, which could be done with Alex / Roberto before ImagineIT
@Josh Hevenor (Unlicensed) Have the name of the app on the screen Have the URL for the portal on the screen Have the credentials on the screen Slide/presentation, not a word doc. Get ready! Announce what the app is, that it’s third party and that we configure the map and what’s collected, but don’t maintain Speak to the fact that we can control who has access to edit what, and that QA/QC processes can be applied to the raw feed Don’t show any config options, just confuses people what they’re looking at, as no one will be able to do this “What’s Oct1”, we didn’t explain what we showing and why we were showing it What happens next, can feed directly to RSID, for example
|