University of North Florida School of Computing Information Systems Senior Project

Group Contract
Objective: To design, develop and implement an interactive, adequate and manageable webbased information system to meet the requirements and desires set forth by World Arts Education, Inc. Group Business/Agency Name: consuLab.net Names/Contact Information: Student Name: Adam Lankford *Email address: atlankford@gmail.com Phone number: 619-746-3191 Skype: adam.lankford Student Name: Destinijoy Harrington *Email address: djdexter12@gmail.com Phone number: 904-813-3183 Skype: destinijoy.harrington1 Student Name: Marion Collins *Email address: mcollins205@gmail.com Phone number: 904-718-8794 Skype: Student Name: Gabrielle Villanueva *Email address: villanuevaa027@gmail.com Phone number: 904-338-1262 Skype: gabzie1 *Denotes preferred contact method Schedule: The team will utilize the schedule provided on consuLab.net. All team members have the ability to modify the calendar. This calendar will be the single source for team coordination. Meeting Information: The team will utilize an availability based schedule meaning times and dates will fluctuate based the consensus of availability. Additionally, the team will meet via Skype every Wednesday evening. Furthermore, the team will expect to

meet three times a week in the UNF Library, but no fewer than one. The team should expect meetings to last at least one hour. Meetings conducted with World Arts Education will be conducted monthly at a minimum and will likely take place at UNF Library or other coordinated event. Roles and Responsibilities: Although reasonable leniency will be exercised, each member will be required to attend every meeting. Positions: The following positions will be delegated by this contract, however may be changed through out the project if desired by the majority (three) of the team. The responsibilities assigned to the position will not change. Team Leader Adam Lankford Lead and motivate the team Enthusiastic about the project First to arrive and last to leave at team meetings Actively participate in work of the project Serve as primary contact person of the team, for both instructor and community partner Schedule meetings with community partner

Project Manager Gabrielle Villanueva Uses project management tools to plan project tasks Develop sprint iterations and software development plans Works with team to assign tasks to team members Keep track of works completed, work-in-progress, and works to be done Keep track of issues and develop new action items Plan and conduct sprint review meetings

Analyst and Technical Writer Destinijoy Harrington Responsible for reports, user documentation, training documentation. Take notes and summarize meeting discussions. Tracing requirements from user needs through features, use cases, design models, source codes, test cases, and delivery Plan for development and testing use cases to ensure all requirements have been not only meet but verified

Software Quality Analyst Marion Collins Develops a way to ensure that each requirement is addressed, met and tested. Integrates project Sprints to ensure functionality isnt compromised.

Ensure team members work and documents submitted follows provided guidelines. Ensure work submitted by team members is of expected quality Keep track of software development bugs using tools like Bugzilla (http://www.bugzilla.org/)

File Sharing: Primary: Dropbox shared folder Senior Project Secondary: Google Docs Tertiary: Blog consuLab.net

Action Plans: The team will divide tasks based on the members strengths and weaknesses. The Project Manager will delegate tasks and ensure completeness. Deliverables. Each individual in the group would be responsible to type their own part. A day before the deliverable is due, everyone should bring a hardcopy or softcopy on the meeting so everyone could proof read each others work. The Team Leader will be responsible for turning each deliverable in for grading. Disbursement and Delegation. The division of work will be based on the team members strength and weaknesses. However, this does not mean that team members will do the same task the entire project. Each task or work will rotate among the members of the group, so everyone will have an opportunity to learn. The team member who excels on one part should share information with other group members to help strengthen each others skills in the areas they are weak. The Project Manager will ensure tasks are divided equally. Record Keeping. The Technical Writer will also record minutes what transpired at each meeting. In case she is unavailable to do the job, one of the team members will be assigned to take notes. The minutes will be posted to the blog consuLab.net and also a hardcopy will be filed the team binder. Proofreading. All documents will be posted to Dropbox prior to submission. Each member will have an opportunity to individually check-out a document to review and modify prior to final submission. Teamwork. It is preferred that team members work on their section individually, considering the groups guidelines. On the group meeting, each member would be assigned a section to work on, with the standard procedures set by the group. Conflict. In the event of a disagreement, the Team Leader will present the applicable courses of action to the team, and client if necessary. The final decision will be accepted if it is the consensus of the group, or the majority vote.

Procedures: The group members will utilize an evaluation sheet to rate our group members performance throughout the project. An evaluation form will be used every time we turn in a deliverable for our project. This will allow us to rate how we feel a specific team member contributed. Additionally, The group will utilize a three-strike method. In the event that a group member deviates from our group contract, or fails to meet the satisfaction of the other group members, the Team Leader and the member will attempt to resolve the problem. If necessary, the member may receive a strike. On the third strike, if unable to come to any resolve with the Team Leader, the infraction will then be submitted to Dr. Umapathy for review. It will be automatically understood that the offending group member will be graded a dissatisfaction for that meeting or the deliverable.

Signatures and Dates: Destinyijoy Harrington:_____________________________ Date:_____________________ Gabrielle Villanueva:______________________________ Date:_____________________ Marion Collins:___________________________________ Date:____________________ Adam Lankford:___________________________________ Date:____________________

Group evaluation form

Team Name: ___________________________ Date: _________________ Please use the following rating system to rete your group member based on weekly contribution to Sr. Project activities. The following is a list of statements to be answered and each of your group members. 1-Strongly Agree 2-Agree 3-Neutral 4-Disagree 5-Strongly Disagree

Self:

Group member:

Group member:

Group member:

Contributed a fair share of weekly work. Worked well with group members

Attended group meetings Attended group meetings with community partner Overall was a valuable member of the team
Comments: _____________________________________________________________________________________________ _____________________________________________________________________________________________ _____________________________________________________________________________________________ _____________________________________________________________________________________________ _____________________________________________________________________________________________