This week in IPPD, we presented a rough draft of our PDR document. By presenting in front of members of other teams, we were able to receive a lot of valuable feedback on our PDR presentation. Additionally, this was a fantastic opportunity to practice our PDR presentation before giving the real presentation this upcoming Tuesday. Beyond this, we also watched other teams present and provided feedback to help improve their final presentation. Overall, everyone did a great job and participating in this event will vastly improve the quality of our final presentations.

Moving forward, we need to modify and fix our PDR Presentation based on the feedback given by fellow IPPD members. This is particularly critical, as the date for our actual PDR Presentation is this upcoming Tuesday. Beyond this, we need to make improvements and changes to our PDR Report Draft. Lastly, we also need to practice presenting as a team to improve our team coordination for the actual presentation

This week in IPPD, we continued learning about our PDR document. Additionally, we learned how to create effective elevator pitches. This skill will be particularly useful during our PDR presentations.

Outside of class, our largest deliverable content was the creation of a system architecture map of the current version of Hacker Jeopardy. This map will be very useful going forward as it will help us determine the flow of the overall program when we begin looking through the python code. Beyond the creation of our system architecture map, we also defined the critical path of our project, began compiling resources to learn Python and the CherryPy library, and started preparing our PDR document.

Moving forward, we need to complete our PDR report draft and have it ready for our peer presentations. Additionally, we need to finalize our user story backlog, select a tool to begin generating concepts with (in the form wireframes), and hold a CTF after the PDR presentations.

This week in IPPD, we continued learning about concept selection strategies and began conceptualizing what we want our changes to look like in the UI. Additionally, we learned more about the PDR document we will be creating and presenting in the coming weeks. 

Outside of class, our biggest accomplishment was the completion of our First Month Report. After spending a considerable amount of time working on the report, we were able to have it checked over by both our coach and liaison. Additionally, we were able to locate the Python source code within the provided virtual machine. Because of this, we can now begin reading through the existing code to gain a deeper understanding of how the app works and how to use the CherryPy library.

Moving forward, we still need to hold a CTF as a means of evaluating the current state of the application. Additionally, we need to complete our Preliminary System/Product Architecture deliverable as well as begin our PDR document.

This week in IPPD, we continued learning about concept selection strategies and began learning about what will be required for our Preliminary Design Review (PDR) event. Additionally, we were fortunate enough to have professional headshots taken during class.

Outside of class, we were able to meet with our liaison, who ran a CTF utilizing the current version of Hacker Jeopardy. As a result, he was able to provide our team with feedback and suggestions of changes he would like to see implemented as we modify the program. Additionally, all members of Team 10 were able to obtain the resources required to run and modify the program, meaning we can now dive into the program’s code and analyze its current implementation. 

Moving forward, one task that needs to be completed is scheduling our own CTF, so that we can continue defining the continuously evolving scope of our project. Additionally, we need to begin analyzing the pre-existing code and understanding how the program works in its current form. Lastly, we must complete our project roadmap and first month report.

This week, we had the opportunity to present our finalized team name and logo in front of all participants in the IPPD program. While a few of our classmates offered constructive criticism, the name and logo were well received.  

Outside of class, our team created the first revision of our Product Design Specifications (PDS) Document and received feedback from our coach. The document currently contains information such as an introduction to the project as well as requirements and specifications that will be adhered to to ensure the development of a successful product. Additionally, we began looking at the pre-existing project and its source code. Lastly, we created a backlog and began populating it with user stories so that we can keep track of our responsibilities both as individuals and as a team. 

Moving forward, we will continue to analyze the pre-existing code to get a better understanding of the project in its current form. Beyond this, we will also begin planning a CTF so that we may test the limitations of the pre-existing project.

This week, our first order of business was finalizing out team name and logo. We ended up naming our team “Double Jeopardy” as it relates to the game of Jeopardy and also because we are the second IPPD that will be working on this project.

Beyond this, we were able to hold our first meeting with both our coach and head liaison in attendance. In doing so, we were able to decide on a weekly meeting time and have a lot of our questions answered regarding the project and its scope of work. Additionally, we were able to obtain virtual machine snapshots containing our project, so we can begin looking at and testing the previous iteration of the project.

Moving forward, our team needs to plan a ctf so that we can begin analyzing the code and assessing the current capabilities of the project. Additionally, we will be putting together a storyboard to divide labor and keep track of tasks and features that need to be implemented.