Issue

Project-base Learning Requirements

Each sprint there will be hacks and project-based learning requirements. It is up to the individual to develop their own plan for how they will represent work. Here are some links and tips.

  • All work, tangible artifacts, will be captured in personal GitHub Pages
  • Tools and Software Development requirements are foundational requirements for all the CompSci courses. Thus, they are identical, but listed independently under CSSE Projects, CSP Projects, CSA Projects.
  • To obtain clarity on instructions you should start by picking a post in Sprint 1, then ask questions.
  • In Agile Development methodology, which we will learn throughout the course, an iteration (plans, designs, review references, coding) and questions should all be considered as part of your work.
  • Since iteraction and questions are part of your work, you should consider capturing and outlining questions and interations in the blog you create.
  • Be aware, you will get more “Points” if you have “Indicators and ANalytics” that you are progressing on a CompSci journey.
  • There are very few “Correct Answers” in this class! As you code, you will see that there is always more bugs, features, questions, and iterationcs.
  • If you write a plan through a GitHub Issues, Commit Code in GitHub, update your plans, update your code… Analytics will show you are working.

Classroom Guidelines

It will be a very bad day when you say… “I have everything done”. This statement typically comes by students that are lacking understading and do not explore.

This statement shows that the person making the statement knows very little about CompSci and the principles of iteration that are being promoted in this class. In fact, this statement does not agree with Agile Development Methodologies that we will be learning in this class.

The Teacher likes behaviors that are easily viewed and interpreted as productive to CompSci learning.

  • Code, Code, Code. This is the process of making code and involves making plans, designs, reviewing references, asking questions and Code-Code-Coding.
  • No paper. We will be learning to do all work electronically.
  • Work Talk. A very high percentate 75%, 80% or more of your talk during class should be code, code, code talk.
  • Ears that can listen. 100% of time you should be available for discussion. Covered or plugged in ears restricts hearing.
  • Hands that can code. The primary coding device is assumed to be your laptop! Sprint 1 will be focused on laptop importance.

Read Learning Habits Table to understand how behaviors will impact grading.