Successfully reported this slideshow.

Effective Team Work Model

968 views

Published on

This presentation explains a team work model that can be applied to development projects to facilitate smooth functioning of the project even during sudden non-availability of a developer or in cases where a developer departs from the team.

Published in: Business
  • Be the first to comment

  • Be the first to like this

Effective Team Work Model

  1. 1. ByAngelin R
  2. 2. Effective Team Work Model• This model can be applied to development projects having a minimum of 4 team members working in the same technology.• According to this model, there will be 3 levels of peer support for the actual developer and the peers themselves will be provided the same model of support.• This model will ensure smooth functioning of the project even during sudden non-availability of a developer or in cases where a developer moves out of the team.• This model will lead to improvement in quality, responsiveness and efficiency of deliverables .
  3. 3. Approach• Level 1: Backup peer position where another developer has the same functional knowledge and technical skills as that of the original developer. This is a critical layer enabling smooth execution of the tasks assigned, in the absence of the original developer.• Level 2: Technical support position assigned to another developer who has the technical skills similar to that of the original developer. The person in this position will be responsible for technical review of the deliveries to be made by the original developer.• Level 3: Functional support position assigned to another developer who has the functional knowledge similar to that of the original developer. The person in this position will be responsible for functional review of the deliveries to be made by the original developer.
  4. 4. Developer withfunctional knowledgeand technical skillsrelevant for his/herassigneddevelopmentmodule/componentLevel 1: Backupdeveloper with similarfunctional knowledgeand technical skillsLevel 2: Developerwith similar technicalskills for technicalreviewLevel 3: Developerwith similar functionalknowledge forfunctional review
  5. 5. • In the sudden absence of a team member, his/her backup peer can work on that team member’s tasks.• If that backup peer is already overloaded with development tasks for which he/she is primarily responsible, then his/her backup peer can share the workload of his/her other 2 roles.
  6. 6. Backup Methodology Member temporarily unavailableDeveloper withfunctional knowledgeand technical skillsrelevant for his/herassigneddevelopmentmodule/componentLevel 1: Backupdeveloper with similarfunctional knowledgeand technical skillsLevel 2: Developerwith similar technicalskills for technicalreviewLevel 3: Developerwith similar functionalknowledge forfunctional review
  7. 7. Transition Methodology• Level 1 Transition – Functional transition: When a team member is going to move out of the team, then the person identified as his/her replacement gets functional knowledge transition about all the functionalities being worked and supported by the outgoing member.• Level 2 Transition – Role transition: Then he/she gets knowledge transition from the outgoing member about the roles and responsibilities played by him/her at all levels he/she was involved in.• Once these transitions are completed, the incoming member replaces the outgoing member and the project functions smoothly without any gaps or issues.
  8. 8. Developer withfunctional knowledgeand technical skillsrelevant for his/herassigned developmentmodule/componentLevel 1: Backupdeveloper with similarfunctional knowledgeand technical skillsLevel 2: Developerwith similar technicalskills for technicalreviewLevel 3: Developerwith similar functionalknowledge forfunctional review
  9. 9. Member moving out Member moving inDeveloper with Incomingfunctional knowledgeand technical skills member getsrelevant for his/her functionalassigned developmentmodule/component knowledge transitionLevel 1: Backup about all thedeveloper with similarfunctional knowledge functionalitiesand technical skills being worked and supportedLevel 2: Developer by thewith similar technicalskills for technical outgoingreview memberLevel 3: Developerwith similar functionalknowledge forfunctional review
  10. 10. Member moving out Member moving inDeveloper withfunctional knowledge Incomingand technical skills member getsrelevant for his/herassigned development knowledgemodule/component transition from outgoingLevel 1: Backupdeveloper with similar member aboutfunctional knowledge the rolesand technical skills played by him/her at allLevel 2: Developerwith similar technical levels he/sheskills for technical was involved inreviewLevel 3: Developerwith similar functionalknowledge forfunctional review
  11. 11. Developer withfunctional knowledgeand technical skillsrelevant for his/herassigned developmentmodule/componentLevel 1: Backupdeveloper with similarfunctional knowledgeand technical skillsLevel 2: Developerwith similar technicalskills for technicalreviewLevel 3: Developerwith similar functionalknowledge forfunctional review
  12. 12. • Ensures smooth functioning of the project even during sudden non- availability of a developer or in cases where a developer moves out of the team.• Ensures high code quality through effective technical code reviews by peers.• Ensures customer satisfaction through effective functional code reviews that check if the deliverables are inline with the customer requirements.• Increases customer’s confidence in team members.• Allows job rotation and avoids dependency on individuals for completion of tasks.• Provides opportunity for continual learning and knowledge development of team members – both functionally and technically.• Most developers will know enough portions of the application that they could fill in many roles.• Having a more global view of the application, the team members will have an insight into how best to implement new features while maintaining the overall system architecture.• Ensures effective utilization of skilled resources.

×