...pre-post-mortem...
...yesterday i was compiling the pre-post mortem survey forms collected from my colleagues until 1am. i asked them 3 very simple questions : what went well, what went wrong and how can we improve. and here are my findings.
my pm does not know anything about it. in dillema now, shall i talk to my pm about it, or shall i just go direct to the um. arghhh!!!! stress...stress...stress...
lets analyse this situation : pm is goin to transfer all his knowledge of project management to me and he will teach me everything he knows. he will pass me a book to read on project management. he has been promoting me to the um on what i am doing. he has been the nicest person to everyone. he gives me such high ratings for my performance review. haih...stress...stress...stress...
well, i guess what i can do is look at the what went wrong, and see which item we can improve on and initiate some processes that allows us to complete this project with the 10% success rather than 100% failure. i need some inspiration on how can we go on from here. yeap, aaron dude mentioned about attitude. i need to bring along the attitude which i have left it behind and use it to deal with this issue.
Non Technical related:
Project Planning
1.No proper project planning from the beginning.
2.No proper planning from the start of the project.
3.Poor project management.
4.No clear direction and goal to be achieved from the direct management.
5.Staff not able to see the overall picture of the progress of the project.
6.Minimal project progress meeting for daily updates.
Direct Management
7.Direct management seems not concern about the project which causes others to lose motivation to work.
8.Direct management does not monitor progress properly.
9.Staff realizes that the direct management is not doing the job.
Rumors and discouragement
10.Lots of rumors around.
Appreciation and Gratitude
11.Cannot feel the appreciation from IITC – forfeit leave while rushing for project which causes the lost of motivation.
Deadlines
12.Tight timeline and things not well organized causing wastage of time and resources.
Dynamic Allocation of resources
13.Some issues are still pending but still pull resources to other modules causing those pending things to be dragged.
14.Too frequent of shifting of resources caused confusion to the mind.
Contract Programmers
15.Language gap between contract programmers and module lead causing misunderstanding.
16.Low quality of contract programmers.
17.High turnover rate which causes individual workload to increase but there is no replacement by HR.
Working Environment
18.CIAST environment very bad.
19.CIAST is very far and long traveling distance which discourages people to stay back late to work. Tired if stay back late.
20.Wasting time traveling from CIAST to IITC and back to CIAST for events – breakfast session which causes lost of half day.
21.No teamwork due to lost in communication.
Training Programs
22.No proper training for non experienced programmers.
Technical related :
1.No technical document for all programmers to refer to
2.Tables are not designed earlier but many changes along the way.
3.Development method kept on changing – 2-tier to 3-tier SQL to Oracle which causes duplication of effort.
4.No standard coding method. Different people have different method.
5.Requirement capturing not clear for some of the modules.
6.Common user control should share among all project in IITC (similar to EDUGEN) and not developed during project phase as this will cause changes and code modifying on the existing code which is wasting of time and resources.
7.Development time increased causing other task and milestones to be delayed.
8.Students category has a lot of issues that needs to be resolve – ranging from incorrect business rules and requirement that applies and coding skills.
9.Built incorrect database due to misinterpreting the requirements despite so many downloads session provided.
10.Job scope of technical lead is not clear – should only monitor the technical issue only and not the whole project progress. Technical lead should not involve in development.
anyone can help me out, inspire me...
my pm does not know anything about it. in dillema now, shall i talk to my pm about it, or shall i just go direct to the um. arghhh!!!! stress...stress...stress...
lets analyse this situation : pm is goin to transfer all his knowledge of project management to me and he will teach me everything he knows. he will pass me a book to read on project management. he has been promoting me to the um on what i am doing. he has been the nicest person to everyone. he gives me such high ratings for my performance review. haih...stress...stress...stress...
well, i guess what i can do is look at the what went wrong, and see which item we can improve on and initiate some processes that allows us to complete this project with the 10% success rather than 100% failure. i need some inspiration on how can we go on from here. yeap, aaron dude mentioned about attitude. i need to bring along the attitude which i have left it behind and use it to deal with this issue.
Non Technical related:
Project Planning
1.No proper project planning from the beginning.
2.No proper planning from the start of the project.
3.Poor project management.
4.No clear direction and goal to be achieved from the direct management.
5.Staff not able to see the overall picture of the progress of the project.
6.Minimal project progress meeting for daily updates.
Direct Management
7.Direct management seems not concern about the project which causes others to lose motivation to work.
8.Direct management does not monitor progress properly.
9.Staff realizes that the direct management is not doing the job.
Rumors and discouragement
10.Lots of rumors around.
Appreciation and Gratitude
11.Cannot feel the appreciation from IITC – forfeit leave while rushing for project which causes the lost of motivation.
Deadlines
12.Tight timeline and things not well organized causing wastage of time and resources.
Dynamic Allocation of resources
13.Some issues are still pending but still pull resources to other modules causing those pending things to be dragged.
14.Too frequent of shifting of resources caused confusion to the mind.
Contract Programmers
15.Language gap between contract programmers and module lead causing misunderstanding.
16.Low quality of contract programmers.
17.High turnover rate which causes individual workload to increase but there is no replacement by HR.
Working Environment
18.CIAST environment very bad.
19.CIAST is very far and long traveling distance which discourages people to stay back late to work. Tired if stay back late.
20.Wasting time traveling from CIAST to IITC and back to CIAST for events – breakfast session which causes lost of half day.
21.No teamwork due to lost in communication.
Training Programs
22.No proper training for non experienced programmers.
Technical related :
1.No technical document for all programmers to refer to
2.Tables are not designed earlier but many changes along the way.
3.Development method kept on changing – 2-tier to 3-tier SQL to Oracle which causes duplication of effort.
4.No standard coding method. Different people have different method.
5.Requirement capturing not clear for some of the modules.
6.Common user control should share among all project in IITC (similar to EDUGEN) and not developed during project phase as this will cause changes and code modifying on the existing code which is wasting of time and resources.
7.Development time increased causing other task and milestones to be delayed.
8.Students category has a lot of issues that needs to be resolve – ranging from incorrect business rules and requirement that applies and coding skills.
9.Built incorrect database due to misinterpreting the requirements despite so many downloads session provided.
10.Job scope of technical lead is not clear – should only monitor the technical issue only and not the whole project progress. Technical lead should not involve in development.
anyone can help me out, inspire me...
posted by jeeyon at 5:02 AM
0 Comments:
Post a Comment
<< Home