S
S.W CHUNG
Hi everybody
This is my first participation in this group as one of the Microsoft Project
MVP
I’m not sure that I can share my knowledge in this site since here is Q&A
site.
Let me know correct place if I am going wrong way.
I am working in SAMSUNG SDS which is IT service provider in Korea.
we deliver more than 1000 IT project per year and I work in PMO(Project
Management Office) so I can handle all kinds of Project Data.. and I have to
analyze them and find some point of future improvement
I hope I can share my experience in Enterprise Project Managment not only
for system but for pratical management.
Resently, I have done some analysis on WBS in IT Project.
Let me share this result with you..
1. General Information
- sample size : 50 Projects
- average project total duration : 244 day
- longest project total duration : 617 day
- shortes project total duration : 53 day
- average number of work activity(including summary) : 546
- biggest number of work activity(including summary) : 3573
- shortest number of work activity(including summary) : 27
- average number of work package : 313
- biggest number of work package: 1685
- shortest number of work package : 23
2. Actual purpose of using Microsoft Project
- 26.1% : for managing Project
- 73.9% : not just for managing project actually
(43.5% : just for concepting project roughly
17.4% : just for planning project, not managing it
13.0% : just for drawing Gantt chart )
3. Apportionment of phase in IT Project Life cycle
< Duration >
- Initiation : 4.7%
- Analysis : 17.3%
- Design : 22.1%
- Development : 37.0%
- test and deployment : 18.4%
< work load >
- Initiation : 1.9%
- Analysis : 15.2%
- Design : 16.8%
- Development : 52.4%
- test and deployment : 13.7%
< Duration of projects that were actually managed by MS Project >
- Initiation : 2.2%
- Analysis : 14.9%
- Design : 20.3%
- Development : 48.2%
- test and deployment : 14.0%
< work load of projects that were actually managed by MS Project >
- Initiation : 0.7%
- Analysis : 15.8%
- Design : 17.4%
- Development : 50.7%
- test and deployment : 15.4%
4. Average duration of work package
- Projects that were actually managed by MS Project : 7.0 day
- Projects that were not actually managed by MS Project : 14.3 day
5. Depth of WBS (outline level)
- Projects that were actually managed by MS Project : 6.6 level
- Projects that were not actually managed by MS Project : 5.2 level
6. ratio of work package and total project duration (average duration of
work package / average total project duration )
- Projects that were actually managed by MS Project : 3.2 %
- Projects that were not actually managed by MS Project : 7.1 %
Actually, I reported some corrective actions and way of improving maturity
of project management to the management of my company. but it's internal
information of company so I didn't mention it.
If you want to know the detail, feel free to e-mail me doka00â€atâ€naver.com
By the way, I am still not sure that I found right place to share this.
If not, Let me know right place.
Thank you
S.W CHUNG
www.sds.samsung.com
This is my first participation in this group as one of the Microsoft Project
MVP
I’m not sure that I can share my knowledge in this site since here is Q&A
site.
Let me know correct place if I am going wrong way.
I am working in SAMSUNG SDS which is IT service provider in Korea.
we deliver more than 1000 IT project per year and I work in PMO(Project
Management Office) so I can handle all kinds of Project Data.. and I have to
analyze them and find some point of future improvement
I hope I can share my experience in Enterprise Project Managment not only
for system but for pratical management.
Resently, I have done some analysis on WBS in IT Project.
Let me share this result with you..
1. General Information
- sample size : 50 Projects
- average project total duration : 244 day
- longest project total duration : 617 day
- shortes project total duration : 53 day
- average number of work activity(including summary) : 546
- biggest number of work activity(including summary) : 3573
- shortest number of work activity(including summary) : 27
- average number of work package : 313
- biggest number of work package: 1685
- shortest number of work package : 23
2. Actual purpose of using Microsoft Project
- 26.1% : for managing Project
- 73.9% : not just for managing project actually
(43.5% : just for concepting project roughly
17.4% : just for planning project, not managing it
13.0% : just for drawing Gantt chart )
3. Apportionment of phase in IT Project Life cycle
< Duration >
- Initiation : 4.7%
- Analysis : 17.3%
- Design : 22.1%
- Development : 37.0%
- test and deployment : 18.4%
< work load >
- Initiation : 1.9%
- Analysis : 15.2%
- Design : 16.8%
- Development : 52.4%
- test and deployment : 13.7%
< Duration of projects that were actually managed by MS Project >
- Initiation : 2.2%
- Analysis : 14.9%
- Design : 20.3%
- Development : 48.2%
- test and deployment : 14.0%
< work load of projects that were actually managed by MS Project >
- Initiation : 0.7%
- Analysis : 15.8%
- Design : 17.4%
- Development : 50.7%
- test and deployment : 15.4%
4. Average duration of work package
- Projects that were actually managed by MS Project : 7.0 day
- Projects that were not actually managed by MS Project : 14.3 day
5. Depth of WBS (outline level)
- Projects that were actually managed by MS Project : 6.6 level
- Projects that were not actually managed by MS Project : 5.2 level
6. ratio of work package and total project duration (average duration of
work package / average total project duration )
- Projects that were actually managed by MS Project : 3.2 %
- Projects that were not actually managed by MS Project : 7.1 %
Actually, I reported some corrective actions and way of improving maturity
of project management to the management of my company. but it's internal
information of company so I didn't mention it.
If you want to know the detail, feel free to e-mail me doka00â€atâ€naver.com
By the way, I am still not sure that I found right place to share this.
If not, Let me know right place.
Thank you
S.W CHUNG
www.sds.samsung.com