CS632 Project Blog - Group 3 Team B

January 31, 2008

Team Contract

Filed under: Uncategorized — oge @ 12:09 pm

Team Contract

This Team Contract (agreed upon by all members) contains guidelines on rules and procedures as to how meetings, communication, assigned works and final project would be managed and completed. Issues addressed are what we feel are vital to the success of this group towards the final project such as member’s roles, project management, etc and by following these we trust that the goals and objectives set as a team would all be achieved. Team Mission: To create a working website that meets and supersedes the client’s requirements within the project timeline. Team Member Roles:

- Aside from the meetings called upon by the PM (Gene) any team member that proposes a meeting would plan and lead the event.

- We would discuss in our meetings: first; where each member team is on the assigned work, order of tasks to be done based on the guidelines and due dates from the Prof and facilitator and PM.

- Every group member will always have a contribution on what part of the assignment or project they can do best.

- Team has decided that certain tasks like the Cost Estimation would be a collective effort, i.e. all group members would participate in this process.

- Meetings would be on a weekly basis (for now) until it is imperative that we meet more frequently, we would adhere and document our progress as various tasks on this projects are completed.

 Project Management:

This is a crucial part of the project in this group and the weekly goals planned and set are thrived to be achieved always.

-          Our timelines would to the best of our abilities adhere to, any team member who cannot achieve this and possibly need help from other team members should not hesitate to let the team know, or send a mail to the PM.

-          Communication is primarily by the use of the blogspot (already in use), others include conference calls (for weekly meetings), WEBCT emailing system.  

-          Do not forget to reply all when replying/sending a mail and cc Prof. Kanabar and Patrick if and when necessary.

 Rules and Guidelines:

-          Strict guidelines only cause tension and stress but we trust that each team member thrives to deliver assigned works on or before due dates.

-           We are hopeful that there would be no team conflict or between team members, but if this so happens, terms and consequences would be discussed at that time.

-          Our plan is that we would be cordial, respectful, and considerate to everyone.

   Project Procedures:

Project procedures have already been discussed (refer to the blog for detailed information).

-          No one team member would be overwhelmed with a task; tasks are equally and evenly distributed.

-          -While we set our tasks, and timelines we do so with the singular purpose of adhering to those set by the Prof, facilitator, communicated as reminders by the PM, and each and every member.

-          Therefore we are responsible to the other team member to make sure we meet deadlines; simply put: It is a team effort in meeting deadlines. Also note that it is a team effort to offer constructive and positive criticism during revision and editing each other’s work.

  Project Tasks:

-          Within this group of highly esteemed members we believe our contributions are equal towards the final project and no one team member (especially the PM) would be overwhelmed.

-          Dividing the work according based on our strengths, skills, drive and interest turning in the efficient and thorough work.

 Team Ethics:

In relation to ethical guidelines, we plan to:

  • Be respectful and listen to other group member’s decisions.
  • Allow group members to constructively criticize documents to be graded.
  • Give feedback in an appropriate manner.
  • Honest with the group’s opinions and reviews.
  • Accepting of thoughts and opinions.
  • Each member being responsible for his or her own part.
  • Most of all submit ethically acceptable work adhering strictly to BU’s ethical code of conduct (on plagiarism)

 Project Goals:

-          Based on our kickoff meeting, we have identified and come to the conclusion that each member of the team is ambitious, meticulous, conscientious, seek to do an excellent work to the best of our abilities, working together as a TEAM.

-          In our group, there are no members who want to contract far less work. Therefore we are determined to receive the highest grade assigned to this project.

  

Name: Oge Ogele

  

Name: ___________________________

  

Name: ___________________________ 

  

Name: ___________________________ 

  

Name: ___________________________

  

Name: ___________________________

7 Comments »

  1. Ok, guys, by now you know my weakness ;-) Someone do kindly fix the Team Contract that I just posted.

    Thanks a lot

    Oge

    Comment by oge — January 31, 2008 @ 12:12 pm

  2. Awesome Job! I’ll fix whatever small errors I may find :-)

    Comment by admin — January 31, 2008 @ 10:17 pm

  3. Team Contract
    This Team Contract (agreed upon by all members) contains guidelines on rules and procedures as to how meetings, communication, assigned works and final project would be managed and completed. Issues addressed are what we feel are vital to the success of this group towards the final project such as member’s roles, project management, etc and by following these we trust that the goals and objectives set as a team would all be achieved.
    Team Mission: To create a working website that meets and supersedes the client’s requirements within the project timeline.
    Team Member Roles:
    • Aside from the meetings called upon by the PM (Gene) any team member that proposes a meeting will plan and lead the event.
    • Meeting agenda: first; where each member team is on the assigned work, order of tasks to be completed based on the guidelines and due dates from the Prof, facilitator, and PM.
    • Every group member will comment on what part of the assignment or project they can do best.
    • The team has decided that certain tasks like the Cost Estimation would be a collective effort, i.e. all group members would participate in this process.
    • Meetings will be conducted on a weekly basis (for now) until it is imperative that we meet more frequently.
    • Team members will prepare progress summaries before each meeting and post them on the blog.
    Project Management:
    • Timely completion of goals set by the team PM, lead, and members is imperative for our mutual success.
    • Any team member who needs help or is feeling overwhelmed will seek assistance from other team members without hesitation.
    • Communication will be conducted though our blog (www.boston-recruiting.com), conference calls (for weekly meetings), WEBCT emailing system. All communications must be documented on the blog, especially project deliverables to be discussed by the Team as a whole.
    • Please reply to all when replying/sending a mail and cc Prof. Kananbar and Patrick if and when necessary.
    Rules and Guidelines:
    • Communication is a rule!
    • We trust that each team member thrives to deliver assigned works on or before due dates.
    • In the event of a conflict within the team, the matter should be brought in front of the Project Manager and Facilitator. If the issue is one that can be resolved by the entire group the issue is discussed publicly.
    • The team is working for a common goal thus team mates should be cordial, respectful, and considerate of their peers.
    • There is a 100% open door policy between the PM, Leads, and every team member.
    • Everyone should have fun and learn as much as possible!
    Project Procedures:
    • Project procedures have already been discussed (refer to the blog for detailed information).
    • No one team member should be overwhelmed with a task; tasks are equally and evenly distributed. If you feel this is not the case, please let the PM know!!
    • While we set our tasks and timelines we do so with the singular purpose of adhering to those set by the Prof, facilitator, communicated as reminders by the PM, and each and every member.
    • As a team effort, it is our duty to offer constructive and positive criticism during revision and editing each other’s work. Let your voice be heard!
    Project Tasks:
    • Within this group of highly esteemed members we believe our contributions are equal towards the final project and no one team member (especially the PM) would be overwhelmed.
    • Dividing the work according based on our strengths, skills, drive and interest turning in the efficient and thorough work.
    Team Ethics:
    • Conduct ourselves with the outmost integrity.
    • Be respectful and listen to other group member’s decisions.
    • Allow group members to constructively criticize documents to be graded.
    • Give feedback in an appropriate manner.
    • Be honest with the group’s opinions and reviews.
    • Be accepting of thoughts and opinions.
    • Each member being responsible for his or her own part.
    • Most of all submit ethically acceptable work adhering strictly to BU’s ethical code of conduct (on plagiarism)
    Project Goals:
    • Based on our kickoff meeting, we have identified and come to the conclusion that each member of the team is ambitious, meticulous, conscientious, seek to do an excellent work to the best of our abilities, working together as a TEAM.
    • In our group, there are no members who want to contract far less work. Therefore we are determined to receive the highest grade assigned to this project.
    Name: Oge Ogele

    Name: ___________________________

    Name: ___________________________

    Name: ___________________________

    Name: ___________________________

    Name: ___________________________

    Comment by admin — January 31, 2008 @ 10:55 pm

  4. Now it looks perfect to me, “admin” ;-)

    Gracias

    Comment by oge — February 1, 2008 @ 10:06 am

  5. Excellent!

    Comment by admin — February 1, 2008 @ 11:35 am

  6. I agree!

    Comment by MI — February 12, 2008 @ 11:23 am

  7. The contract is clear and detail, I agree that we all should stick to it.

    -Leong.

    Comment by Leong — February 12, 2008 @ 12:48 pm

RSS feed for comments on this post. TrackBack URL

Leave a comment

You must be logged in to post a comment.

Powered by WordPress