1. PRJ566 Project Planning and Management Teamwork 1

2. Software Development  Software Development is needed to turn manual processes into automated processes or to improve/enhance existing automated processes. (http://en.wikipedia.org/wiki/Software_development)http://en.wikipedia.org/wiki/Software_development  Software Development follows a methodology called the SDLC 2

3. Software Development  Systems Development Life Cycle (SDLC) A methodology that organizes the activities of a project Followed by a Systems Analyst to do software development http://en.wikipedia.org/wiki/Software_development_process 3

4. Software Development  A project team (http://en.wikipedia.org/wiki/Project_team) follows a software development life cycle to deliver a software solutionhttp://en.wikipedia.org/wiki/Project_team  The team is made up of members who perform different roles on a project  Each phase in the SDLC can use different team members (business analyst, architect, data base administrator, programmer, etc) 4

5. Teamwork  Henry Ford on teams: Coming together is a beginning. Keeping together is progress. Working together is success.  “Software Development requires students to work together in teams” 5

6. Teamwork  Coming together is a beginning Forming Teams Team Size Team Member Roles 6

7. Forming Teams  Assigned by the Instructor Allows students to:  Learn from one another  Depend on one another  Grow from the interactions with each other  Need strategies for dealing with team conflict 7

8. Forming Teams  Students pick their own teams Students pick their friends Difficult to deal with poor performing team members Friendships disrupted in poor performing teams 8

9. Forming Teams  Mix of students picking team members and instructor assigning team members Need to understand the skill sets that each team member brings to the team 9

10. Team Size  Bigger teams restrict the ability for all team members to participate and contribute to the success of the team  Optimum team size for this course: 3 to 4 students 10

11. Team Roles  Social Loafing A team member will expend less effort when working collectively than when working individually  Free Riding A team member trying to benefit from being a part of the team but not contributing equally 11

12. Team Roles  Perceived Social Loafing Team members perceive that one or more other team members are contributing less than they could to the team  Sucker Effect Team members scale back their efforts to match those of the free riders 12

13. Team Roles  Negative behaviours are sources of conflict that will lead to reduced or poor team performance  Systems stream of courses teach you the skills necessary to work as part of a project team 13

14. Team Roles  Need to define the role of each team member  Always need 1 team member to act in the role of team leader 14

15. Teamwork  Keeping together is progress Managing Teams Tracking Progress 15

16. Managing Teams  Assignment deliverables Ensuring deliverables are on time and done correctly 16

17. Tracking Progress  Regular meetings Track what was discussed:  Tasks done or to be done  Changes made to the system  Issues with team members If not tracked:  Team members don’t know about it  Instructor doesn’t know about it 17

18. Teamwork  Working together is success Project delivered –on time and what the client wants 18

19. Team Motivation Strategies* 1. Foster mutual respect for the expertise of all team members 2. Help weaker team members believe that their effort is vital to team success 3. Support a shared belief in the cooperative capabilities of the team 19

20. Team Motivation Strategies* 4. Hold individual team members accountable for their contributions to the team effort 5. Direct the team’s competitive spirit outside the team *5 Research-tested team motivation strategies, Richard Clark (2005) 20

21. Team Challenges  Projects that fail almost always fail because of team problems  Team communication is the biggest problem  “Not doing work” is the next biggest problem

22. Handling Team Challenges 1  If a team is having problems with a specific member, the team must talk to that person right away. If issue is not resolved   THEN come and see the instructor if the problem is not resolved  cc instructor on any correspondence i.e. emails trying to contact a team member who has not been attending

23. Handling Team Challenges 2  See the instructor immediately if your problem is not resolved quickly  If it’s TOO LATE your instructor cannot help you