Project Retrospectives

Currently RMED has various projects of GRAN\WRAN\LRAN being performed. These projects have diverse scopes & activities. A few times we take time to discuss the projects & train the resources in different scopes, but there is a lack of formal process & tracking. Moreover many customers are requesting resources to be well versed in different technologies. So in-order to make all resources aware of different scopes & better ways of working it is suggested that at the end of each project the resources must prepare a project retrospective. It should also be applicable to resources that are working in a long duration project & change their project midway. This should be taken down as goal in knowledge sharing for performance reviews. The retrospective should be in a form of PowerPoint presentation or a document following the guidelines mentioned below for the contents. Project Details: Details should include Customer details No of Nodes/Types List of activities Duration & resources

It can as well include MoP or detailed explanation of commands which have been used to perform the activities. Issues: This part should cover project specific issues. Problem scenario has to be described. It can consist of both technical problems & non-technical challenges which GSC India resources\stakeholders had to face. If any particular problem was solved with managerial intervention, it should also be included with inputs from manager. If any early warning signs if any were noticed.

Best practices\Learnings:

This should include any practice that has resulted in good feedback or appreciation from customer end. It should include explanation of any tools/scripts/WoW that resulted in improvement of efficiency or productivity.

Repository: All project retrospective should be stored on Ericoll or Eridoc. This folder should have read only access to whole team or concerned engineers either working in a particular region at a time or from a CD pool as deemed fit. Write access should be given to respective team leads who will review the retrospective & then it can be delivered within the team. The file for each retrospective should follow clear naming convention i.e. REGION_CUSTOMER_TECH_YEAR_MONTH_PROJECTNAME. Example: RMED_H3G_2013_JAN_DT_PREPARATION.ppt