Course Websites

Continuation of CS 492. Identical to CS 494 except for an additional writing component. See CS 494. Course Information: 3 undergraduate hours. No graduate credit. Credit is not given for both CS 493 and a project course in another engineering department for the same project. Prerequisite: CS 492.

work in teams, coordinate efforts for common goal (1), (2), (3), (4), (5), (6) interview client to define/refine requirements (3), (4), (5) work with client liaison on an ongoing basis and adapt to changing requirements (1), (2), (3), (4) specify limits of project scope (1), (2), (3) identify end-users characteristics (1), (3) construct a feature breakdown structure (1), (2), (3), (4) create a plan based on feature breakdown (1), (2), (3), (4), (5), (6) give a formal technical presentation (f) objectively present the status of a project (b), (c), (d), (f), (i), (k) write a synopsis and progress report with plan for completion at halfway point (3), (4), (5) document completed work (3), (4), (5) evaluate peers performance in team (4), (5) document progress, communicate with stakeholders (3), (4), (5) construct solution to client's problem (1), (2), (3), (4), (5), (6)

Communicating with Your Client and Team
Forms of Communication - Reports, Plans, Memos, Emails, etc
Technical Presentations
Making a Plan
Feature Breakdown
Setting Goals
Managing Your Client’s Expectations
Working in a Team
Professionalism Toward Your Client
Receiving Critique - Making Use of What is Useful, Being Effective at Delivering It
Documenting Your Project

1. Responsibilities as a Team Member
2. Managing Your Project
3. Client Relationship
4. Managing Your Team
5. Choosing Projects and Forming Teams
6. Team Success and the Importance of Inclusivity
7. Respecting and benefiting from working with clients and team members of different genders and backgrounds.
8. Understanding Client Goals
9. Understanding Client Expectations
10. What to do when you do not have specific expertise
11. Managing Expectations
12. Professionalism
13. Defining Outcomes
14. How to Work with Your Client to Make Them Happy
15. Meetings with Clients
16. Team Meetings
17. Taking Responsibility and Ownership
18. Written Communications
19. Planning and Estimating
20. Agile Methods and Tools
21. Useful Status Reports (Are Honest and Accurate)
22. Honesty and Evaluation (Team Evaluations)
23. Measuring Team Productivity (You were probably wrong but that's OK)

Revisions in last 6 years	Approximately when revision was done	Reason for revision	Data or documentation available?
require maintenance of team/project wiki	fall 2011	discussion with industry partners and former students that have graduated
changed formal planning requirement to add focus on agile methods	fall 2010	discussion with industry partners and former students that have graduated
in class presentations include regular status updates for every team rotating between team members	fall 2012	discussion with industry partners and former students that have graduated
changed paper format to wiki, word count replaces page count	fall 2011	discussion with industry partners and former students that have graduated
added requirement to maintain Jira issues-tracking database	fall 2011	discussion with industry partners and former students that have graduated