Timeline

Week # Activities
Week 1 Get your tools ready. See GitHube remote repo. Meet with your faculty advisor. See Faculty Advisor Meeting. Get started on the Project Outline.
Week 2 Meet with your advisor. Master’s Thesis only: select (or re-connect) with thesis committee members. Class meeting #1. Go to Class Meeting 1.
Week 3 Work on the Project Outline. Meet with your advisor.
Week 4 Meet with your advisor. Do project work. Project Outline is due Feb 17. Class meeting #2. Go to Class Meeting 2
Week 5 Do project work. Meet/communicagte with your faculty advisor
Week 6 Do project work. Meet/communicagte with your faculty advisor
Week 7 Do project work. Meet/communicagte with your faculty advisor
Week 8 Do project work. Meet/communicagte with your faculty advisor. Class meeting #3.
Week 9 Get started on the First Draft. Meet/communicate with your advisor. Do project work
Week 10 Meet/communicate with your advisor. Do project work.
Week 11 Meet/communicate with your advisor. Do project work. First Draft is due Apr 14. Class meeting #4
Week 12 Meet/communicate with your advisor. Do project work. Work on the Almost Final drat. Monday, April 18 is the last day to have your thesis reviewed for formatting by the Graduate School for December graduation. Intent-to-graduate* for May 2022 is also due Monday, April 18
Week 13 Do project work. Meet/communicate with your faculty advisor. Review feedback and revise almost final draft.
Week 14 Meet/communicate with your advisor. Do project work. Class meeting #5.
Week 15 Meet/communicate with your advisor. Do project work. Thesis manuscript is due to Graduate School May 9. Almost Final is due May 12. Project presentations are scheduled Friday, May 13.
Week 16 Meet/communicate with your advisor. More Project presentations are scheduled Monday, May 16. All computing artifacts are due May 16. Complete your project paper.
Week 17 Final project paper are due May 23.

Note Each week starts Saturday and ends Friday noon. For weeks when we have class meetings scheduled, you must have the assigned work completed Thursday midnight.

Weekly Activities

Week 1

Jan 24 - 28

GitHub remote repo

  • Verify that you have access to the GitHub remote repo.
  • Use Discord # github channel for more information.
  • The name of your GitHub remote repo is lastname-firstname
  • Review documentation on how to use GitHub project board, issues, and pullrequests to manage all your project development activities
    • Make sure you’ve created a project board for your remote repo
    • Set the GitHub project template to automated Kanban. See Configuring automation for project boards
    • Practice the use of GitHub project board by creating a note card in the To-Do column, named advisor meeting mm-dd-yyyy.
      • You will move it to In Progress when you have the meeting and then to Done after the meeting with your faculty advisor.

Faculty Advisor Meeting

  • Connect with your advisor and schedule an advising meeting no later than Feb 3
  • Meeting preparation
    • Document in the GitHub Kanban project board the meeting by moving the meeting card from To Do to In Progress and then Done
      • The card must have a reference to where the meeting notes are.
    • Have the meeting notes ready with the meeting agenda items
  • Meeting agenda
    • Discuss potential project goals and domain area for your project
    • Narrow down the scope of your project to a very specific domain
    • Get advice on relevant resources and references
    • If this is continuing research, review progress and plan project development milestones
    • Take notes on discussion points and action items
    • Discuss means of communication to inform about progress and get feedback on your work
    • Schedule weekly meetings and touh points for the rest of the semester
    • Determine the ACM Computing Classification codes that best characterize the computing area of your project.
  • Outputs
    • Meeting notes in OneDrive or GitHub Wiki
    • Mark your Outlook calendar to block off time for your weekly meetings/touch points
    • Review and select the ACM Computing Classification System (CCS) codes that best represent the domain area of your project; save the informaiton in your notes
      • Masetr’s Project: See video in Canvas to learn how to generate the TeX encoding of the CCS codes, and insert it in the driver.tex file in Overleaf

Go to the top of Timeline

Week 2

Jan 21 - Feb 4

  • Have all your tools and platforms set up
  • Get started on drafting the project outline
  • Meet with your faculty advisor
    • Finalize the topic of your project
    • Discuss project goal, sub-goals, expected result(s), and how you’ll evaluate the results
    • Get feedback on the project outline
    • Master’s Thesis: Select (or re-establish connection) with thesis committee members

Overleaf platform project

  • Verify that your access to an Overleaf project is set up to contain your project paper or thesis manuscript materials.
  • Use Discord # overleaf channel for more information.
  • The name of your Overleaf project is 2022-spring Lastname, Firstname.
  • Become familiar with Overleaf and LaTeX

Class Meeting 1

  • Who we are
  • Syllabus tour
  • Learning in this course
    • How, with whom, what
    • Desirable professional competencies
  • Overview of computing areas of research and development (R&D) in the IT field
  • R&D strategies for project work
  • Next steps

Go to the top of Timeline

Week 3

Feb 7 - Feb 11

  • Continue drafting your project outline
    • Read first feedback to outline draft and revise
  • Meet/communicate with your faculty advisor
    • Get feedback on project outline draft
  • Review feedback and revise outline draft
    • Read second feedback to outline draft and revise
  • Document projet work using
    • GitHub Kanban board and cards
    • GitHub Wiki
    • Other materials (e.g., OneDrive shared with your faculty advisor and course instructor)

Go to the top of Timeline

Week 4

Feb 14 - Feb 18

  • Meet/communicate with faculty advisor
  • Review feedback, revise, finalize, and submit project outline
    • Project outline is due Thursday, Feb 17
  • Do and document project work

Class Meeting 2

  • Reflective practitioners
  • Goal of project work study
  • Outline of project work
  • Plagiarism, attribution, citations, references
  • Project development process
  • Project directory structure
  • Next steps

Go to the top of Timeline

Week 5

Feb 21 - Feb 25

  • Meet/communicate with faculty advisor
  • Do and document project work

Go to the top of Timeline

Week 6

Feb 28 - Mar 4

  • Meet/communicate with faculty advisor
  • Do and document projet work

Go to the top of Timeline

Week 7

Mar 7 - Mar 11

  • Meet/communicate with faculty advisor
  • Do and document project work

Go to the top of Timeline

Week 8

Mar 21 - Mar 25

  • Meet/communicate with faculty advisor
  • Do and document project work

Class Meeting 3

Go to the top of Timeline

Week 9

Mar 28 - Apr 1

  • Do and document project work
  • Get started on the first draft of your project paper/thesis manuscript
  • Meet/communicate with faculty advisor
    • Get feedback on your project work and first draft
  • Review feedback and revise first draft

Go to the top of Timeline

Week 10

Apr 4 - Apr 8

  • Do and document project work
  • Meet/communicate with faculty advisor
    • Get feedback on your project work and your revisions of the first draft

Go to the top of Timeline

Week 11

Apr 11 - Apr 15

  • Do and document work on the project
  • Meet/communicate with faculty advisor
  • Finalize your first draft
    • First draft is due Thursday, Apr 14

Class Meeting 4

Go to the top of Timeline

Week 12

Apr 18 - Apr 22

  • Do and document project work
  • Get started on the almost final draft of your project paper/thesis manuscript
  • Meet/communicate with faculty advisor
    • Get feedback on project work and the almost final draft
  • Review feedback and revise almost final draft
  • Monday, April 18 is the last day to have your thesis reviewed for formatting by the Graduate School for December graduation.
  • Intent-to-graduate for May 2022 is also due Monday, April 18

Go to the top of Timeline

Week 13

Apr 25 - Apr 29

  • Do and document work on the project
  • Meet/communicate with faculty advisor
    • Get feedback on project wrok and the almost final draft
  • Review feedback and revise almost final draft

Go to the top of Timeline

Week 14

May 2 - May 6

  • Do and document project wrok
  • Meet/communicate with faculty advisor
  • Finalize your almost final project paper/thesis manuscript

Go to the top of Timeline

Class Meeting 5

Week 15

May 9 - May 13

  • Complete project work
  • Freeze Work progress reflected in
    • GitHut Kanban project board
    • GitHub Wiki
    • Other ther materials (e.g., OneDrive files shared with faculty advisor and course instrutor)
  • Master’s Thesis
    • Thesis manuscript is due to Graduate Schoole Monday, May 9
  • Almost final draft is due Thursday, May 12
  • Meet/communicate with faculty advisor
  • Prepare, rehearse, get feedback, and give your presentation
  • Presenatations are scheduled Friday, May 13

Go to the top of Timeline

Week 16

May 16 - May 20

  • Meet/communicate with faculty advisor
  • Presenatations are scheduled Monday, May 16
  • Complete all the computing artifacts
    • Computing artiacts are due Monday, May 16
  • Master’s Project
    • Revise and finalize your project paper

Go to the top of Timeline

Week 17

May 23

  • Final project paper due Monday, May 23

Go to the top of Timeline