There is no need to check your answers to this lab into CVS since I will be able to see your work in Track+.
1. Log into Track+. (If you didn't already get a login, register and let me know so I can process your registration immediately.)
2. Click on Administration -> My Profile. You can change your password here if you like. Click on Home when you are done.
3. Go to Reports. Select the project CS160 and click Execute Query. You should see an important announcement regarding the homework.
4. Click on New Issue. Note the pulldown menus for
Some of the other pulldown menus have dummy entries since we don't worry about things such as subsystems or release numbers.
File an issue of type Risk in the TryItOut project with the synopsis "(Your name) may not be able to learn Track+". Add some bogus text. Assign yourself as responsible and your instructor as manager.
Click on Save.
5. Now view your issues. Go to Reports and execute a query that shows the issue that you just filed. What query parameters did you select?
6. Click on the issue that you just filed. (You need to click on the number.) In the next screen, click on Edit.
At the bottom of the screen, locate the New State pulldown menu. Close this issue, add a bogus comment, and click Save.
7. Run the report again to verify that your issue no longer shows up.
You need to do the following exercises with your teammates. File all these reports in your team, not the generic CS160 project.
8. One of you files an Action Item with synopsis "Select Team Leader". Assign another team member as responsible.
9. Your team agrees on a team leader. The principal duty of the team leader is to communicate with the team members and the instructor, so you want to choose someone who appears to be organized and personable. The person responsible for the item puts the name of the chosen team leader and closes the item. (I will retrieve it later.)
10. Your team leader files an Action Item with the title "Schedule first weekly meeting". In the body of the item, the team leader asks every one to list the preferred and impossible times between now and September 19. This is NOT a test! You need to have your first weekly meeting so you can give a progress report in class on September 20.
11. Each team member responds by adding their scheduling information to the issue.
12. The team leader selects a mutually convenient time.
13. Each team member notes the meeting time.
14. At the meeting, your team will discuss how to organize the following team deliverables:
Feel free to break these up in any way that makes sense to you (e.g. like in the homework, or switch roles from homework).
15. At the team meeting, each of you will be assigned certain deliverables with deadlines. Each of you will enter action items, with deadlines, for each of your deliverables. We will review these in class on Sep. 20
16. After the meeting, the team leader closes the meeting item.
NOTE: In this lab, we have only used Risk and Action Item. Later in the project, you will use Problem Report extensively.
NOTE: It is important that you use Track+ for your project whenever it is reasonable to do so. Projects with more Track+ traffic will get a better grade.
NOTE: Feel free to use the TryItOut project for playing around if you want to experiment with some feature without messing up your project. I will never look at it.
NOTE: I will no longer respond to email questions about the course. File a Track+ item in the CS160 project instead. (If it a personal matter, come to my office hour.)