2015 Fall Projects in CS I

This is an archive of our Fall 2015 Projects in CS. You can find the latest class details in our Schoology pages under your course PROJ IN COMP SCI: S1 & S2. Feel free to reference past material here as needed, but there will many changes in the new year. Website links and assignments may vary so some material may be out of date. Check in with Mr. Bergquist if you have any questions.

Date

Goal*, Work Due & Exams

Class Activities

Fall 2015 Semester Class Complete

Hope you had a great 4 Sprints with us and are joining us for 2nd Semester

Initial Stand-up (Sprint 3) Meeting, review release scope and plan with Mentors for approval.
- What Stories (features) will be accomplished? This may lead to rewriting some Stories.
- What's your expectations for release for end of semester (let's plan out now)?
- Do you have a reasonable number of tasks (with time estimates)?

- Get material set for presentation...
+ Sprint 2 work Demo:
+ include plans for Minimum Viable Product Release for Sprint 3!NEW! Sprint Demo Rubric - let's try out this form for scoring. Feedback welcome, we can make adjustments accordingly.

T’was the night before Star Wars, when all through the den
Not a creature was stirring, not even Kylo Ren.
Han Solo was encased at Jabba's in carbonite
And hoped that his friends would soon wage a fight...

Tuesday 12/15

Work on Sprint 3 Tasks

Work on Tasks, assembling material for Thursday's demo. + Please put a copy of your test cases in your team folder on the S drive. Thanks

Work on Tasks, assembling material for Thursday's demo.
+ Please put a copy of your test cases in your team folder on the S drive. Thanks

Congratulations to everyone who went to the Programming contest. I'll let you know when the scores are in. Hope you all had a good time.

Friday 12/11

Task work and Integrate Feedback.

+ Integrate the feedback from the Amazon.com UX Design experts into your projects! - review notes and capture what you have learned.
- Work on Tasks - make sure to document your test cases for review.

Stand up today or Monday? Quick check in on progress.
+ Integrate the feedback from the Amazon.com UX Design experts into your projects! - review notes and capture what you have learned.
- Work on Tasks - make sure to document your test cases for review.

Any volunteers to help with the Hour of Code 3rd period Wednesday (Block)?

Stand Up Meeting with Update on Test cases - Review them.

Let's discuss Code Review Options.

+ Work on Tasks

Tuesday 12/8

Work on tasks, presentations and formalize Test Cases for next release.- Update Presentations for Thursday, you should be Pitch Perfect.- Update Test cases for Grading... Due on Friday.
- Work on Tasks

Any volunteers to help with the Hour of Code after school on Wednesday (Block)?

Task work & insure that you have one to write the test cases for your first Story or two - this will help target your demo's success. Thanks.

Task work & insure that you have one to write the test cases for your first Story or two - this will help target your demo's success. Thanks.

+ Permission slips for Programming Contest DUE!!

Thursday
12/3
Block

Stand-up (Scrum) meeting featuring Test Cases, then work on Tasks.Stand-up (Scrum) Meeting Focus:
* How are your Tasks leading to completing your Stories? Your team needs to have functionality to demonstrate at the end of the Sprint.
* Story Level Test Cases - Please review your test cases with Mentors.

Stand-up (Scrum) Meeting Focus:
* How are your Tasks leading to completing your Stories? Your team needs to have functionality to demonstrate at the end of the Sprint.
* Story Level Test Cases - to insure the team are in agreement as to what defines success of story functionality.

Work on Tasks created for first Sprint, don't forget to create test cases.

Thursday 11/19
(Block)

First Stand-up (Scrum) meeting & Work on Tasks (Android Studio)

Stand Up (Scrum) meeting: 3 Questions:
. - What you worked on yesterday?
. - What are you working on today?
. - Are you blocked on anything??

Remember: Prioritize writing Test cases for stories should be completed by Thursday ideally.

Work on Tasks!

First Stand Up (Scrum) meeting.
- Show all Stories & Tasks created (backlog) with hours
- Highlight what Stories working on and their test cases (should be a task).
- Then have the actual Stand Up (Scrum) meeting: 3 Questions only (see left)

Verify Stories & Tasks, then work on Tasks.
- Finalize & set up your Stories & write Tasks with estimates to accomplish them. Document on a White board.
+ Remember: Prioritize writing Test cases for stories should be completed by Thursday ideally.Work on Tasks: Most Learning Android Studio - suggestion to first work to Build A Simple App: "Bigger Number" game (Week One - at bottom).

Our Class Sprint ScheduleSprint Planning Day!
Finalize & record your Stories & write Tasks with estimates to accomplish them.Work on Tasks: Most Learning Android Studio - suggestion to first work to Build A Simple App: "Bigger Number" game (Week One - at bottom).

Determine the Stories & Tasks going forward for your Project. Tyler, Anthony & I will talk to each team about these steps.

Thursday & Friday
11/5 Block & 11/6

Plotting out Scenario Maps & creating Wireframes.

1) As a team build finish up your Scenario Maps for your primary App & Review it with another team for feedback.
2) Have Mr. Bergquist set up a new Balsamiq project for your team - an invite will go to an email address, then you can log to the site at:k12app.mybalsamiq.com/projects (for our Apps Class use only, requires log in)
3) Complete your Project Document Details for your Team's presentations next week!

First: Building Scenario Maps:
Finish your Scenario Maps using your User Personas
+ Share your Maps with another team for added comments & questions. Second: Start Wire-frames in Balsamiq:The Balsamiq Site (Arrange a login with Mr. Bergquist)
NOTE: Divide & Conquer - have a couple team members work on the Balsamiq Wireframes and others assemble your Project Document Details.

Monday & Tuesday
10/2 & 3rd

Creating Personas & Scenario Maps - starting the flow of your App.

- Review the Mentor Feedback for your Project. Archive our additional projects for future consideration.
- Finalize your User Personas (3-5) with user details and their key needs/goals for your project
- Build a Scenario Map on Poster board, making sure ALL your users needs are met.- When done, find a team who is also done and share your Map with them, see if they have any steps, questions or ideas to add.
- Start planning out how your "steps" will map to screens for your WireFrame design (on Thursday or earlier)

+ NCWIT Aspirations in Technology competition extended to Wednesday, Nov 4th 2015 - all women in CS should consider applying.
+ EasyCTF a High School Hacking Competition started Saturday Oct 31st! are you on a team? (not associated with SPS or Garfield HS, include your parents in the details)

Pay close attention to the Projects presented, we will be choosing from these to go forward. Identify two or three you would like to work on!

Monday
10/26

Integrating User Surveys and assembling your Scoping Research

+ Integrate your User and Market online research and out of class surveys & interviews. Create a written summary of the research conclusions to integrate into your product.
+ Add this to your team's written summary of the research conclusions to integrate into your product for both ideas. Due Tuesday, 10/27 (this includes any projects you have decided to scratch.)
You can use the Scoping Checklist Worksheet or similar, but put it into a Word document or PowerPoint for easier presenting.

+ User and Market research outside of class - surveys, interviews & online research.
+ Create a written summary of the research conclusions to integrate into your product. Due Tuesday, 10/27.
You can use the Scoping Checklist Worksheet or similar, but put it into a Word document or PowerPoint for easier presenting.

Continue: For next week, please create your team's written summary of the research conclusions to integrate into your product for both ideas. Due Tuesday, 10/27 (this includes any projects you have decided to scratch.)
Let's use the Scoping Checklist Worksheet, but put it into a Word document or PowerPoint for easier sharing.

TO CONSIDER (Next): Technology/Data investigation:(1-2 students)
Does your idea have key data or technology that is essential to its success? Investigate feasibility of solving this - you are not looking for the final solution, more of a basic test if this will be available & viable for your project.

How goes Scoping?
Let's Share from each Group:
- One Marketing Key Insight (has this changed your priorities?)
- Most significant User Key Goal or still looking...
+ Let's talk time line to have a UX external project review, so we can arrange those volunteers.

With a Mentors, Let's review your plan for User Research (surveying) outside of class - let's check out your User Sequence Map and set questions (User Interview Instructions). Talk to potential users over the weekend!

For next week, please create your team's written summary of the research conclusions to integrate into your product for both ideas. Due Tuesday, 10/27 (this includes any projects you have decided to scratch.)
Let's use the Scoping Checklist Worksheet, but put it into a Word document for easier sharing.

Planning out some HOMEWORK, Later this week:
Each Group interviews at least 10 Users (preferably more) outside of class and summarize in writing what you have learnt:
a) changes to the problem sequence (Map)
b) key outcomes/ needs
c) issues with current solutions
d) surprising answersKeep a paper copy of your resulting interview notes to share with your team and our Mentors.

Understanding the User (1-2 students)User Insights
Goal is to identify who your key users are and what information you need to know about them? i.e. What would you ask in a Survey??User Interview Instructions to create:
. - Each App’s Problem Sequence Map
. - Each App's Interview Guide questions

Later... Technology/Data investigation:(1-2 students)
Does your idea have key data or technology that is essential to its success? Investigate feasibility of solving this - you are not looking for the final solution, more of a basic test if this will be available & viable for your project.

1) Scoping Checklist Worksheet - fill in the initial pitch, then after the Competitor Analysis, update the "Understand the Market" section.
2) Understanding the Marketplace: (2-3 students) Complete the Competitor Analysis Worksheets for your two App ideas, using the Instructions
3) Understanding the User (1-2 students)
Preparation for your user homework assignment, using the User Interview Instructions to create:
. - Each App’s Problem Sequence Map
. - Each App's Interview Guide questions
. - Print out these to share with your team members

Warm Up: Name all the Users exercise!

Scoping Kick Off
- fill out the first page today...Key: Divide and investigate: Review and we will decide how to proceed

Later... Technology/Data investigation:(1-2 students)
Does your idea have key data or technology that is essential to its success? Investigate feasibility of solving this - you are not looking for the final solution, more of a basic test if this will be available & viable for your project.

Two more weeks left in SOCKTOBER! Bring in new socks, we are up to 24 pairs.

When all is done, check in with your team to see if you have narrowed down to your top 2 ideas.

Chick Tech Event Sat & Sun, Nov 7 & 8th - let Mr. B know today if you are interested, and talk to your folks. This is not an SPS or Garfield HS event and you need to talk to your parents/guardians before registering or attending.

+ Further detail you ideas and try the "what would your Grandmother do?" exercise, how would the problem/task be solved without technology in earlier years (not necessarily by the elderly).
+ Start highlighting your top 4 or 5 ideas to continue on...

Team Activity:
1) Any initial ideas team members already have, jot them down.
2) Expanding a Big Issue by team Brainwriting. Pull out the new ideas
3) Adjust them, more specific or more general - how can you adjust them to be a more complete project idea.

Goal: identify about a dozen problem/ideas for our projects for each team.
Document your ideas (problems) on Post Notes and keep them in your Notebook.
+ Develop them a bit further exploring them
+ Then vote on them to identify the most popular five or so. We may

Ideation - Brainstorming Project Ideas
- Class Activity: Life Highlight Game
- Finish dividing our class into two groups of 4 and two group of 5
- Brainwriting - pass on your list...
- Key: write down all your ideas - post-its or paper, keep them all; you may expand on them later. (see instructions at left)

First, Divide class into two groups of 4 and two group of 5:
Getting Started - Review Slide 3 of From Ideas to Applications
Key: write down all your ideas - post-its or paper, keep them all; you may expand on them later. (see instructions at left)

Last day for Elevens!
Most teams are in the finishing steps of getting Eleven's board working. If you are done, help another team please. Demo your working program to Anthony or Mr. B.
Not done? Please make a copy and work on it out side of class (i.e. Homework to finish up).

Thursday 10/1
Block

Create the board for the Eleven's Lab in your paired group.

Complete through Activity 9, the Elevens Board Game.
Done? You have two options:
1) Go back to Activity 5: Testing with Assertions. We will likely do this in InteliJ later. OR
2) See how easy it is now to set up the Thirteen's Game (Activity 10, let me know if I need to install it)

Finishing Up Elevens!
Most teams are in the finishing steps of getting Eleven's board working, let's work to get this finished up. You can always make a copy and work on it out side of class too (i.e. Homework to finish up).

NOTE: The Read-Only folders were all refreshed, so any accidental changes to that code is fixed. This should *not* have caused any loss of code, right?

+ Still a couple teams' Activity 7: Elevens Board Class Design Sign off's on Question 4. a. through e. about the three helper methods. Have it reviewed

+ EasyCTD a Hight School Hacking Competition, starts Saturday, create a team (not associated with SPS or Garfield HS, include your parents in the details)

Friday 9/25
Homecoming!

Determine how to create the board for the Eleven's Lab in your paired group.
- Progress Check in - demonstrate your working Deck to one of our Mentors, including the Shuffle method, by running your thorough DeckTester class.
- Activity 7: Elevens Board Class Design - write out your answers to all parts of Question 4. a. through e. about the three helper methods. Have it reviewed before going on...
- Activity 8: Using an Abstract Board Class

Check in
- How is it going? Where are we at
- Moving on to the Board Class Design, we are going to use a solid Abstract Board Class allowing additional games to be built.

Thursday 9/24
Block

Review Class Guidelines & Resources, and continue on pair Eleven's Lab:
- Activity 3: Shuffling the Cards in a Deck (Optional) - you can just use the shuffle algorithm we did in AP CS Arrays as Parameters Exercise)
- Activity 4: Ingrate Shuffle method for an ArrayList in your Deck.
(Skip 5 if you like)
- Activity 6: See how Elevens are played.
(Let Mr. Bergquist know when you are done with these Activities - we add more)

Eleven's Check-In - How is it going? Getting the hang of usgin Objects again? Getting the logic in the right place?

Meet your fellow students, a couple new to Garfield CS!
- "Water Cooler Conversations"
and Introductory Details...2015 Projects in CS Syllabus (pdf format) - review and give me your feedback - We are adding two major deliverables (to be detailed later):
1) Code Sample, at least 100 lines of code for a formal peer and mentor Code Review.
2) Resource/Skills presentation - independently learn how to use a new resource and present it in class showing how to use it (cheat sheets & links), how you applied it, & how you learned it.

Let's talk about Project Ideas? What do you want to do??

* Goal should be preceded by: “Student will be able to…” (SWBAT).

** Starred Events are not SPS nor Garfield HS events and you need to talk to your parents/guardians before registering or participating in them