[MUSIC] Thank you so much for doing this, I'm really looking forward to seeing how everything is coming along. >> Okay, well let's get started. So, what we've built is a tablet app that supports audio connection between users. We have two devices here today to demonstrate the connection feature. >> So, as you can see, right now our app displays a book that is laid out to look like the user is reading an actual book. Any pictures that are associated with the material are displayed on the page. You can also adjust the font size so that the user can easily read the text. And, the tablet can be used in portrait or in landscape mode. >> All right, so we're going to show you now our audio connection. So we decided to go with a peer-to-peer audio connection because it allows the children to still talk to each other but it uses less data and it protects the identities of the children better. I believe there's video going to be implemented at some point but, anyways. So, the user can press this button here to connect to other users online. And since these are the only two devices online with the app right now, they're going to connect. And then you can start an audio stream by pressing here. And now the two devices should be able to talk to each other. So I'm going to go outside, and I'm just going to give you guys the full effect. Hello, can you hear me? >> Hi, Josh we can here you loud and clear. >> Great. [LAUGH] Pretty cool, hey? I'm going to come back now. >> So, that's our functionality as of right now. We've gotten our high priority, high risk features developed. So, it should be easier from here on in. Did either of you have any questions? >> Wow guys, great work. Did you end up using the white background like I suggested? The off-white background? >> Yes, we did you were totally right. I actually tried using a bright white background just to see what difference it would make. And it made a huge difference just changing the hue even just a little bit. I played around with various shades of white, but I think that this one still gives a lot of contrast, but doesn't strain the eyes. What do you guys think? >> Yeah, I agree, I think this shade looks just fine. I really like the audio connectivity. It's really exciting to see this all come together. I'm really excited to see how it's going to impact literacy. I'm hopeful. Great work, guys. >> Lisa, did you have any feedback? >> Well, I am just a floored with what you've created so far. I think it looks excellent. The page layout looks so good. I think it's incredible that you can even increase the font size without losing too much the fidelity of the page. Excellent work. So what features are you planning to develop next? >> Well, for the next sprint we're hoping to get the account set up and also create the browsing, selecting, and search features so users will be able to find books. >> Okay, so that sounds good. >> Mm-hm. >> Well, I've been thinking about this project for a long time; and I have a few other ideas for some features. I think it would be really cool if the reader could highlight text on the page. And then their highlights could be saved once they exit the book. I also think we should have a bookmarking feature so that the reader can save their progress in a book. And I think we should feature audio books, so that the reader can listen while a recording reads to them. They can even follow along in the book. >> I took a peak through the database of materials, and I didn't see any audio recordings in there. Did I just miss that, or did that get saved somewhere else? >> You're right, we don't have audiobooks included in that material yet. And we're still in negotiations. So, let's just forget that idea for now. That could be something for the future, for when we have audiobooks included in the database. >> Okay, well thank you so much for your suggestions Lisa. We will definitely take those into account. They sound like fantastic features. So let's now move to the backlog refinement. Daniel, did you have anymore questions before we get to that with Lisa? >> No, everything looks great. Keep up the great work guys. I'll see you next week. >> Okay, thanks, bye. >> See you. >> Okay let's start with adding the new features to the backlog. >> Okay, I can do that. What should we call them? >> As a reader, I want to highlight text from a book, so that I can remember an important aspect of the book. >> You also need to save the highlights when the user exits the book. >> My thinking cap. Okay, so let's make this two different stories. And the second story could be, as a reader I want the things that I highlighted to be available after I exit so that I can look at them. >> I definitely think you're on the right track, but how about we say, as a reader I want the highlights I created to be saved after I exit the book so that I can review them when I return to the book. How does that sound? >> That's much better. [LAUGH] >> [LAUGH] >> Yeah, okay so those two are created. What was the other one again? >> Bookmarks. >> Yeah. Okay, how about, as a reader I want to bookmark my place in the book so that I know where I left off? >> I think we can word it a bit better than that. What do you think about, as a reader I want my place in the book to be saved so that I can return to that place at a later time? >> Yes, okay. Yeah, I'll write that down. >> Okay, great. So next we should assign priorities, story points and risks to all of these. I think these are all pretty low risk. Do we agree? >> I think bookmarks should be one, but saving highlights should be moderate because things can get complicated when we start saving >> Okay, I can see that. And what do we think for story points? >> Ooh, let's do that simultaneous reveal thing that we did before. Where we all hold up what we think the story points should be at the same time, that way there won't be any bias. >> Great idea. On the count of three, hold up the number of story points you think the highlighting feature will be. One, two, three. >> A unanimous decision. One story point it is. So let's move on to saving highlights. One, two, three. >> Very good, I think we're getting good at this. So, two story points for that one. And now for the bookmarking feature. Okay ready? One, two, three. >> Darn. [LAUGH] Odd man out. That's okay, I was debating between two and three story points anyway, so I would be fine with giving that one three story points. >> Okay, fantastic. Let's start prioritizing for the next sprint. So we need to connect the application to the database. We need to save the material locally. Set up browse features with covers of the books. Select reading material and search material. Create the accounts, create login and resetting password features. And sort reading material based on comprehension difficulty of genre. So I think we have our work cut out for us. >> From a development standpoint, getting that database connection set up has gotta be our highest priority. It's going to be a pretty awful app if that doesn't work. I think things like sorting features and saving material locally can be our lowest priority, because even if we get everything else created, we're going to have a pretty functional product. >> Well, I agree with you for the most part. I would say that the database connection is definitely the highest priority, and sorting is probably the lowest priority here. In fact, I would say implementing the bookmarking feature is more important than that. Now that I come to think about it, accounts is pretty low priority. I would order these as bookmarking, sorting, then the accounts. I would rather have the save locally than the accounts. Being able to access the books without a wireless connection is very important to me. >> Okay, I can see that. So if you had to prioritize these for the next sprint, you would say database is most important? Browsing, selecting, and search features medium priority? And then, you would prioritize saving locally above bookmarking, sorting, and accounts? >> Yes, yeah that sounds good. >> Okay, we have to remove some features from the sprint, just because I think we're over our story points. But, we'll work that out when we do the release plan. >> Thank you so much for your input, it was very helpful, Lisa. >> Thank you all so much. Keep up the excellent work. I can't wait to see what you accomplish next week. See you at the next demo. >> Bye, Lisa. >> Bye. >> Bye.