How to be a client

To be a client, we request that not only should you have a software problem/project that would benefit from a systematic application of software engineering principles but also that someone in your organization (preferably yourself) be able to devote roughly 1-2 hours a week to engage with the team assigned to the project. It is essential that such a represerntative be a direct stakeholder in the project success and be empowered to make key decisions regarding the project (or at least be able to reach the concerned person & get decisions from such a person). Further, it is necessary that the client (or the client represerntative) be able to attend 2 project review meetings during the semester during which the project progress, team contribution & client feedback will be used as inputs for instructor feedback & guidance on the best way to continue the project.

Our experience indicates that the best clients (or client represerntatives) are: Collaborative (with the team), Representative (of their organization), Authorized (to make key decisions), Committed (to the project's success) & Knowledgable (of the desired software features, of the technology that could be used to execute the project, of the possible problems etc)

Client activites with respect to course schedule