Adi, Samhitha & Ridhima's Joural
| Name | Github Profile | Tasks | Scrum Board | Commits |
|---|---|---|---|---|
| Samhitha | @dsblack0 | Tickets | Scrum Board | Commits |
| Natasha | @mistylavender | Tickets | Scrum Board | Commits |
| Kira | @4disease | Tickets | Scrum Board | Commits |
| Ridhima | @ridhimainukurti | Tickets | Scrum Board | Commits |
| Adi | @adhithin | Tickets | Scrum Board | Commits |
| Name | Reflection |
|---|---|
| Kira | Reflection |
| Natasha | Reflection |
| Adi | Reflection |
| Ridhima | Reflection |
| Samhitha | Reflection |
| Name | Video | Score | Unit 9 Journals |
|---|---|---|---|
| Kira | Video | /6 | Journal |
| Natasha | Video | /6 | Journal |
| Adi | Video | /6 | Journal |
| Ridhima | Video | /6 | Journal |
| Samhitha | Video | /6 | Journal |
| Name | Unit 8 Journal |
|---|---|
| Kira | Journal |
| Natasha | Journal |
| Adi | Journal |
| Ridhima | Journal |
| Samhitha | Journal |
| Requirement | Evidence |
|---|---|
| Week 7 Review Ticket | Scrum Card |
| View/Frontend improvements | Ticket |
| Control improvements | Ticket |
| Model improvements | Ticket |
| Name | Unit 7 Journal | TT & TPT Notes |
|---|---|---|
| Kira | Journal | Notes |
| Natasha | Journal | Notes |
| Adi | Journal | |
| Ridhima | Journal | Notes |
| Samhitha | Journal | Notes |
| Name | Requirment | Evidence |
|---|---|---|
| Kira | Must create an abstract Class, abstract Interface, polymorphic Behavior in Class that extends and a screen allowing input and showing analysis on HTML frontend | Card |
| Natasha | Must create an abstract Class, abstract Interface, polymorphic Behavior in Class that extends and a screen allowing input and showing analysis on HTML frontend | |
| Ridhima | Must create an abstract Class, abstract Interface, polymorphic Behavior in Class that extends and a screen allowing input and showing analysis on HTML frontend | Scrum Card |
| Samhitha | Must create an abstract Class, abstract Interface, polymorphic Behavior in Class that extends and a screen allowing input and showing analysis on HTML frontend | Scrum Card |
| Adi | Must create an abstract Class, abstract Interface, polymorphic Behavior in Class that extends and a screen allowing input and showing analysis on HTML frontend |
| Name | 30 second Runtime video |
|---|---|
| Kira | |
| Natasha | |
| Ridhima | https://www.youtube.com/watch?v=1GgoGGjDolY&ab_channel=Ridhimainukurti |
| Samhitha | https://drive.google.com/file/d/1zborKLYYGFdFKtF1d3ELHbL8Upn09iXi/view?usp=drivesdk |
| Adi |
| Name | Unit 6 Journal |
|---|---|
| Kira | Journal |
| Natasha | Journal |
| Adi | Journal |
| Ridhima | Journal |
| Samhitha | Journal |
| Name | Unit 5 Journal | TT & TPT Notes | Grade |
|---|---|---|---|
| Kira | Journal | Pair Notes | 5/5 |
| Natasha | Journal | Pair Notes | 5/5 |
| Adi | Journal | Pair Notes | 5/5 |
| Ridhima | Journal | Pair Notes | 5/5 |
| Samhitha | Journal | Pair Notes | 5/5 |
| Requirment | Evidence | Grade |
|---|---|---|
| Team and Scrum Master Planning by Wednesday | Scrum Board | 1/1 |
| Team Technicals 2 points. Evaluation is on how Planning and individual Issues compliment the entire project. | Scrum Board | 2/2 |
| Name | Requirment | Evidence | Grade |
|---|---|---|---|
| Kira | Individual Technicals 2 point. Code commits is required on something Technical. | Ticket | 2/2 |
| Natasha | Individual Technicals 2 point. Code commits is required on something Technical. | Ticket 1 and Ticket 2 | 2/2 |
| Ridhima | Individual Technicals 2 point. Code commits is required on something Technical. | Ticket 1 and Ticket 2 | 2/2 |
| Samhitha | Individual Technicals 2 point. Code commits is required on something Technical. | Ticket1 & Ticket2 | 2/2 |
| Adi | Individual Technicals 2 point. Code commits is required on something Technical. | Tickets & Screenshots | 2/2 |
| Kira | Unit 4 and Journal is 5 points | Individual Journals | 5/5 |
| Natasha | Unit 4 and Journal is 5 points | Individual Journals & TT & TPT Notes | 5/5 |
| Ridhima | Unit 4 and Journal is 5 points | Individual Journals and TT & TPT Notes | 5/5 |
| Samhitha | Unit 4 and Journal is 5 points | Individual Journals and TT & TPT Notes | 5/5 |
| Adi | Unit 4 and Journal is 5 points | Individual Journals | -/5 |
https://www.youtube.com/watch?v=g5CSwQPwKAw&ab_channel=NatashaKapoor
| Requirment | Evidence |
|---|---|
| Pair Design / HTML. Transfer design to layout. Much of this could simply be converting Ideas to HTML. Objective is to get your own STYLE, COLORS, FONTS; NAVIGATION into the site. Establish your VIBE or Groove. Try a couple of prototype experiments and get feedback from similar pair in Crossover. | Layout Ticket and Main Page Ticket & Screenshot |
| Pair Prototyping / Thymeleaf. Try using Class objects in Thymeleaf. Most simple Class would be to use String methods (Links to an external site.) and Number methods, (Links to an external site.) more complex is to use your own defined Class include Images or other Media. Objective is to produce a 3 by 3 grid using Bootstrap Grids, Bootstrap Tables, Bootstrap Cards. Try to incorporate into Project or consider as Mini Lab depending on your design. Try changing 3 x 3 to 4 x 4 or other orientation would be showing ability to manage page dynamically. | Ticket & Screenshot |
| TPT2 MiniLab | Ticket & Screenshot |
| Requirment | Evidence |
|---|---|
| Review Canvas requirements. Additionally, create requirements you want to complement this assignment to ensure your success. | Calendar Page, Chat Bot, and Tasks Page |
| Make Issues and assign to individuals or pairs, place Issues in appropriate Column as you progress. | Scrum Board |
| As you move Issues into review, individuals link Tangible assets to add to the Issue. Those assigned to issue are required to add comments that highlight anything Scrum master should report to Teacher. Videos or previews prior to 1 v 1 event are HIGHLY encoraged. | Scrum Board Review |
| At close of Sprint and each week update README with links to issues completed, it is HIGHLY suggested to use table to display Issues with highlighting descriptions. Time box the week or sprint in README as a section declaring Sprint and dates as section Header. | Done |
| Requirment | Evidence |
|---|---|
| Scrum Master. Define tasks and place assignments to in-progress on the Scrum board. | Scrum Board |
| Designer. Wire Frame (at least three theme pages, team mini-labs, and about) | on our website page |
| Technical Lead. Coordinate brain write session, after preliminary wire frames, make sure you capture technical complexities as an output of this exercise (input, saving data, comments, visual actions, animations, ...) | can be seen in the issues section |
| Navigators. Capture or build highlight of Ideation in README.md, this allows ideas to persist with Project, Make sure that work from Developers works to expectations (testing, suggestions for improvement) | Ideation |
| Developers. Bootstrap drop downs in navbar, start to form Wire Frame menu options. Each menu option should have a Stub code page | Navbar finished Ticket |
| Developers. Integration of Greet, Birds, Unit 1 functionality into a mini-lab page | Ticket |
| Designer/Developer. 1 minute video integrated into About Us on Genesis ideas for project. | Ticket |
Adi, Samhitha & Ridhima's Joural
Evidence of contributions and scrum board
| Name | Score | Evidence | Laptop plans |
|---|---|---|---|
| Samhitha | 7/7 | Individual page, Unit 2 Journal | will use personal laptop at home and school |
| Natasha | 7/7 | Individual page, Unit 2 Journal | will use personal laptop at home and school |
| Kira | 7/7 | Individual page, Unit 2 Journal | will use personal laptop at home and school |
| Ridhima | 7/7 | Individual page, Unit 2 Journal | will use personal laptop at home and school |
| Adi | 7/7 | Individual page, Unit 2 Journal | will use personal laptop at home and school |
Our idea is to create a website that would be a to do list or planner for students in order to organize their tasks and their schedules. We wanted to help them organize their lives and keep them on track. We are planning on having different features such as notifications that would alert them of future tasks that need to be done, also a calendar that would list the tasks, and a login page that would require the user to create a username/password in order to enter the website.