![]() | High Impact Teams in Technical Environments |
Syllabus/Announcements Team Topic Chapter Outline Resources Colors Teams Observation Teams of 3- Sign Up Here Reading assignments ITPM - Team FORCE eXtreme Management Diversity Team Leading High Performing Teams Virtual Teams Six Sigma Summary Feedback - Class Feedback for Teams |
Six SigmaTeam MembersNikhil Almeida Suchithra Devulapalli Hiral Shah Kaushal Kantawala Swetha Patnaikuni Mohammed Nasir Ground rules for our team. 1) Meet deadlines 2) Deliver modules in totality 3) Listen attentively to other team members 4) Respecting other's opinions 5) Aligning personal goals with team goals 6) Helping each other complete individual tasks 7) Roles and framework should be clearly laid out 8) No ambiguity on goals and their interpretation 9) Immediate resolution of conflicts 10) Speaking out openly 11) Presenting a complete break-down of work put into parts of the project 12) Discuss all ideas, even ones resulting in personal benefit 13) Team members should specify clearly where they are trying to reach or headed 14) Regular discussion to enunciate where each team member sees the team in future 15) Individual progress should be made transparent to other team members 16) Meet once a week Minutes of Meetings 2/5/08 Team Meeting for Teamwork Survey Questions were discussed one by one in order. Team members gave out individual preferences, and the majority vote was considered to be the final score for all questions. Final Scores were calculated. We scored 21 on Forming, 22 on Storming, 25 on Norming, and 35 on Performing. We made changes to the team swiki, discussed meeting schedule, and finalized a team logo to be added to the swiki. 2/7/7/08 Weekly Team Meeting We decided on what our project should like, and what it should contain. We decided to start working on the Introduction part of our Project. Everybody decided to contribute their part, and suggest changes if required to the doc. Tuckman Survey Results: Our team was on consensus for most questions about how the team is bonding and acceptance of each other as team members etc so the team has formed well and bonded well. Everyone said they have accepted each others strengths and weaknesses and we were proud of the team. A point where there was confusion was the question related to the team leader since we have decided to have rotating roles (ie a person will be in a role for a particular week or two depending on the task ) Also this was too early for the test(read survey) as we are still coming up with the objective.Not only the team leader but also all the members are working towards establishing that goal. Through this exercise (of taking the test) we moved from storming stage to norming stage. This is what stage our team feels in right now. The results of the test are :- Scores Forming 21 Storming 22 Norming 25 Performing 35 Max score = 35 for Performing stage That is, we are in the performing stage. But according to the scoring guidelines if we have three scores really close (Forming 21, Storming 22, Norming 25) we are in the storming stage and that this stage is highly volatile and results can have very high or low points because the operation of the team is not quite clear. We as a team felt we were still in the storming stage before we took the test. In the process of doing this group task we had to set norms and define a clear communication procedure, set meeting agendas etc. All this activity help in 'norming'. And with the help of the discussions in the meeting we were able to take the team from storming to norming. Team Logo ![]() Last modified 2 April 2008 at 1:04 pm by dorn |
| Georgia Tech Disclaimer :: ©2009 |