contextual

Notes on Deliverables (unless otherwise directed by your instructor)

Team Project Deliverables and Homeworks are due PRIOR TO NEXT CLASS (i.e. the week after they appear on the schedule).
Your instructor will clarify the format and manner in which project deliverables are submitted (e.g. via dropbox, Wiki or other)
Unless otherwise specified, all submission should be in .pdf format.

Project Inception@ Week 2

Ideas that Matter to You

Now, think about a problem you wish you could solve, or a cause that you would like to support. Keep it real, make a difference. Here is a list of topics to help get you started:

Climate change
Harambe/Snowflake/Shabani
Organic food
Syrian refugees
Volunteer work
Mental health awareness
World peace
Testing Truthiness/avoid gossip

The project description should state the name of the project, the motivation, the goals, and the intended users. The project description should be 1-2 paragraphs long. An example of a project description can be found here.

Github setup

If you already have a github account you will need to tie-in as primary email your RIT account using userid@rit.edu. If you don't want to do that then create a new "separate" account (not recommended).

Submission (individual):

Your Disc Results
In the comments section of your myCoures submission copy/paste the full URL (website address) of your personal github (e.g. https://github.com/torvalds) repository

Personal challenge (individual setup): If you have completed the above, you are ready to take on this challenge. Note, we will not be holding your hand but want you to familiarize yourself with the installation process and, as we say, setting up your environment. A primary requirement is that your setup matches that of your peers. To that end you need to find out what version of tools that you will be using for this project, are running on the Lab machines and make sure the same ones are what you end up using in your "home" machine(s). For now consider Github desktop, TortoiseGit and one editor of choice (Sublime/Notepad++/Vcode). Here is something that can help you get started.

Homework (individual) before next class:

Complete the Disc assessment and submit a screen grab of results and percentages to myCourses. Also store this results somewhere handy where you can easily retrieve the numbers next class.

Team Building and Project Requirements @ Week 3

Team Building

Every student should complete the DISC assessment. Save the results for your records. Based on the DISC assessment, we will create diverse teams. The instructor will write the 4 types on the board. Once you are done with the DISC assessment, go the board and write your name in the corresponding column. When the whole class is done, the instructor will randomly assign the students to the teams such that:

Teams have nearly equal number of members
Every team has representatives of the 4 personality types

Every team member will introduce himself/herself to the rest of the team. Share your opinion about the DISC assessment with your team. Let them know if you think it truly reflects your personality or not. Share with your team your schedule, more than one way to contact you (e.g. email, phone number). Tell them your favorite means of communication. Do not forget to share one thing that cheers you up, and most importantly your pet peeves. Now one concern, where to keep all this information? Try Trello .

Process @ Week 4

Project Selection

Every team member shall discuss with the group his/her idea. The team shall discuss the pros and cons of each project idea. For each project idea, every team member will rate it on scale from 1 to 10. The project idea that receives the highest accumulative score will be the Team Project. If two project ideas receive the same score, the team should discuss both ideas one more time, and then go for another round of voting.

Project requirements

Identify the users of your product
Identify 10-15 features of the product
Describe each feature in 2-3 sentences

Here is a sample requirements document.

Submission (team):

Your project requirements document

Team Formation

At this point in time, you have had a chance to work with your teammates and are getting familiar with one another. It is time to "formalize" how work is going to be performed. As a team discuss and agree on how to plan your sprint backlog. The sprint backlog is a list of tasks identified by the Scrum team to be completed during the Scrum sprint. During the sprint planning meeting, the team selects some number of product backlog items, usually in the form of user stories, and identifies the tasks necessary to complete each user story. Most teams also estimate how many hours each task will take someone on the team to complete.

Submission (team):

Your project backlog

Modeling and Design @ Week 5

Teams will be allotted time to model their system with use cases, and create a digital mockup of their project using wireframes. Revisit your team sprint backlog. Update the tasks and plan who will be responsible for each task. Estimate the time it will take to finish each task.

Modeling and Design

Take while interacting with the system. Draw a use case diagram that depicts the users and their interactions with the system. Students are encouraged to produce a well thought out design. The design should show the different screens you plan to build, and the elements on every screen e.g. text, buttons, and images. The design should also depict the navigation between the screens. Go to draw.io and start with a blank diagram. You can share your diagram with the rest of your team.
Review the requirements document and the features of your product. Think of who will be using the system, and what actions potential users can take.
Create your mockup on the whiteboard.
After you finish creating the mockup, it is time to think about how you as a team can collaborate on building a project together. Together select one of your team members who successfully completed all tutorials and for the Hello World and uploaded the project to github, s/he can be the technical coordinator. The team and its technical coordinator can begin working on getting real familiar with Github. Complete this simple tutorials: ( Hello World ; Github Pages )

Submission (team):

Updated backlog (Add tasks for every feature e.g. create a use case diagram, assign every task to a team member, estimate the time to be spent on the task and track it.)
Use case diagram (pdf)
A picture of the whiteboard showing the mockup (pdf/png)
Digital mockup (pdf)

Project Construction @ Week 6

Digital Prototype

Teams will be allotted time to create a digital prototype for their project using Google Slides.

Today, we will create a working prototype based on the digital mockups we created last class. This will be accomplished through the use of Google Slides. Please do not be overly concerned with making things too "pretty", but instead focus on the functional flow of the application. The steps for the activity will include:

Team creates digital mock up
Cross team testing
Remediation
Repeat

Submission (team):

Demo of the project in Google Slides. Download it as a pptx file and submit to Mycourses.

Project Presentation @ Week 8

Presentation Planning

Plan, prepare, and rehearse the presentation. Every team should create a shared presentation file, and all members should collaborate on creating the slides. Here is a template to start with. I'd advise that you create a Google Slides version of this document. Explain the steps you took to develop this system from inception to programmed prototype. Discuss your team communications and how you managed the project. Use the demo you created in step 5 in your presentation. Every team has 8 minutes to present, and 2 minutes for Q & A (You don't need to use all 8 minutes).

Project time @ Week 14

Your team will have time to complete the project.

Final Presentation @ Finals Week

Team Project Time

Your team will be given some class time to construct your "application".

Final Class Agenda

Team reflection (before class)
Peer Evaluations
Presentations
Team Reflection

Presentation

Every team will be given 5 minutes to demo their project and describe their process, and 2 minutes for Q & A. The presentation should not be entirely focused on a demonstration of your final product. Your team is still expected to describe some of the whys and hows of what your team did, not just focus on what your team accomplished.

Plan a 5-minute presentation on the project as a whole, led by the team - not your instructor. Each member should participate. A few possible topic items to consider include:

What is the status of your project?
What did you complete?
What process did you use?
What would you have done better?
What did you do well?
Others.....

Some notes for the presentation:

Have something to demonstrate (slides/running implementation).
"Tell a story" in your presentation.
Simple is usually best. Remember Keep It Simple Stupid (KISS)

Team reflection

A beneficial activity in any type of project is to reflect on what your team did well and can improve upon. For this activity, your team will reflect on things you did well so that you can continue those habits, but also recognize areas that you can improve upon.

Submission (team):

Reflection document