Okay everybody. Let's take some time to point out some risks that we may face with this project. One thing that immediately came to mind for me were some of the features. I think that some of the features that were suggested are going to actually be a little risky to implement. Things like the voice recognition and the remote connection with users are likely to cause us problems. We just need to make sure that we really evaluate the value of these features before implementing them. I think there are things that we can do, we just need to make sure that they're essential before we risk developing them. >> Yeah, I agree. I've run into technology risks on other projects that I've worked on in the past. >> Mm-hm. >> So we're thinking about developing this for Android and iOS, potentially. That could be risky. I mean, it's a lot of work. And what if we run into compatibility issues with the different operating systems? That's an excellent point, and it's definitely something to keep an eye on. >> I worked with Lisa before, in the past, and she was known to change her mind a lot. It's just something to keep in mind. But don't get me wrong. Her ideas are amazing. And when she has them, it's always for the best. It's just, something that happens often with her. >> What if someone gets sick? We're a small team and everyone is important. >> That's a good point. No one is allowed to get sick. >> What about the database? They've updated it since I've worked with it last, so we don't know what it's going to be like. Hopefully it's something that we can work with easily. But it was really glitchy the last time, so unless that's been fixed, I would say this project is a bust. And I would say that's a very high risk. >> Yeah. That's a good point. That makes me nervous. >> I'm sure it will be fine. It was designed with projects like this in mind, so I'm sure it will be easy to use. We'll just have to wait and see. I'm sure it'll be easy to use. >> So does anyone else have any other risks? >> Not that I can think of. >> Nope. >> Great, then let's make a risk plan. >> Okay.