ini rupa bilik helpdesk kat PJC tu. Depan tu monitor untuk nengok status network kat Putrajaya.
Tempat technician. Tu budak kita, Firdaus.
Azalea dan Azmuni
Bus station is where the bus stops... guess what happen at workstation?
Showing posts with label Projects. Show all posts
Showing posts with label Projects. Show all posts
10 October 2008
Bebudak Helpdek PJC
ini rupa bilik helpdesk kat PJC tu. Depan tu monitor untuk nengok status network kat Putrajaya.Tempat technician. Tu budak kita, Firdaus.Azalea dan Azmuni
09 October 2008
Prasarana Site Visit
Hari ni aku dan Dakmon pegi site visit kat Prasarana. Meratalah kami jalan. ntah apa apa dah.... sorry gambo senget, lupa nak tukau awal awal....
Itu jerlah yang dia dok buat, check sms jer sepanjang site visit nih....
Boring gila. Nasib baik ada awek ni. Nama dia Zainura. Boleh tahan. Dia peramah. Yerlah, dia Sales Manager.
Ni gambar skodeng.. Irwan yang suruh ambik. Dia dari mula asyik dok usha awek.
18 August 2008
Hayat in Action
Bla, bla, bla...
Hayat dengan coolnya menceritakan bagaimana sistem ini boleh berjalan dengan lancar....
23 July 2008
07 May 2008
Installation thin client at library uia
today we got installation of thin client at uia. this is the first installation for thin client. alhamdulillah everything went well despite hiccups from the end user. they did not really prepare for the installation and because of that it took longer than it should. and we didn't finished the installation in total because of the delay. hope to finish by next week.
Posted from moBlog – mobile blogging tool for Windows Mobile
Posted from moBlog – mobile blogging tool for Windows Mobile
24 April 2008
UAT Thin client
hari ni uat utk server citrix thin client. aku mmg tak faham sgt apa dorang citer. like what Gom said "wa jual jer dude!" wakakaka
Posted from moBlog – mobile blogging tool for Windows Mobile
Posted from moBlog – mobile blogging tool for Windows Mobile
03 April 2008
01 April 2008
Delivery of Wyse Thin Client
This is the same Thin Client that we delivered to our customer yesterday. 300 units of them.
96 units has been allocated to the customer's library, unfortunately the library haven't decided what to do with the units. The setup and installation works have been postponed. No date is confirmed yet.
Yesterday, we tried to install Adobe Reader on the unit, but it can't. But as per my conversation with the supplier this morning, he said the software can be installed. And it shouldn't be any problem with it. He will email me the details on this soon.
If his solution is failed, I was thinking of installing Foxit Reader. They claimed it to be "an exclusive small and fast PDF Reader of the same!"
Hah!
29 March 2008
Mind in progress
Typical look in my office. contengan merata-rata. banyak sangat benda nak kena tengokkan. kalau tak tulih atas whiteboard, mahu pecah kepala, jadi gila. nanti jadi sorang mamat india yang selalu jalan-jalan kat area office ... mana la plak mamat tu sekarang, kan?
27 March 2008
Presentation
Ini gambo Hayat tengah present kat UTM Skudai. semua orang terpegun dengan presentation hayat sebab dia terrer sungguh goreng part IT ni. ntah betul ntah idak, itu tak tau.Pelakon tambahan: Faizal - tukang tekan butang 'next' kat dalam presentation slide tuh
Aku masa ni tengah ngantuk giler, after driving the whole way to Johor.
22 March 2008
How To Manage A Project
By F. John Reh
1. Define the Scope
The first, and most important, step in any project is defining the scope of the project. What is it you are supposed to accomplish by managing this project? What is the project objective? Equally important is defining what is not included in the scope of your project. If you don't get enough definition from your boss, clarify the scope yourself and send it back upstairs for confirmation.
2. Determine Available Resources
What people, equipment, and money will you have available to you to achieve the project objectives? As a project manager, you usually will not have direct control of these resources, but will have to manage them through matrix management. Find out how easy or difficult that will be to do.
3. Check the Timeline
When does the project have to be completed? As you develop your project plan you may have some flexibility in how you use time during the project, but deadlines usually are fixed. If you decide to use overtime hours to meet the schedule, you must weigh that against the limitations of your budget.
4. Assemble Your Project Team
Get the people on your team together and start a dialog. They are the technical experts. That's why their functional supervisor assigned them to the project. Your job is to manage the team.
5. List the Big Steps
What are the major pieces of the project? If you don't know, start by asking your team. It is a good idea to list the steps in chronological order but don't obsess about it; you can always change the order later.
6. List the Smaller Steps
List the smaller steps in each of the larger steps. Again, it usually helps you remember all the steps if you list them in chronological order. How many levels deep you go of more and more detailed steps depends on the size and complexity of your project.
7. Develop a Preliminary Plan
Assemble all your steps into a plan. What happens first? What is the next step? Which steps can go on at the same time with different resources? Who is going to do each step? How long will it take? There are many excellent software packages available that can automate a lot of this detail for you. Ask others in similar positions what they use.
8. Create Your Baseline Plan
Get feedback on your preliminary plan from your team and from any other stakeholders. Adjust your timelines and work schedules to fit the project into the available time. Make any necessary adjustments to the preliminary plan to produce a baseline plan.
9. Request Project Adjustments
There is almost never enough time, money or talent assigned to a project. Your job is to do more with the limited resources than people expect. However, there are often limits placed on a project that are simply unrealistic. You need to make your case and present it to your boss and request these unrealistic limits be changed. Ask for the changes at the beginning of the project. Don't wait until it's in trouble to ask for the changes you need.
10. Work Your Plan, But Don't Die For It
Making the plan is important, but the plan can be changed. You have a plan for driving to work every morning. If one intersection is blocked by an accident, you change your plan and go a different way. Do the same with your project plans. Change them as needed, but always keep the scope and resources in mind.
11. Monitor Your Team's Progress
You will make little progress at the beginning of the project, but start then to monitor what everyone is doing anyway. That will make it easier to catch issues before they become problems.
12. Document Everything
Keep records. Every time you change from your baseline plan, write down what the change was and why it was necessary. Every time a new requirement is added to the project write down where the requirement came from and how the timeline or budget was adjusted because of it. You can't remember everything, so write them down so you'll be able to look them up at the end-of-project review and learn from them.
13. Keep Everyone Informed
Keep all the project stakeholders informed of progress all along. Let them know of your success as you complete each milestone, but also inform them of problems as soon as they come up. Also keep you team informed. If changes are being considered, tell the team about them as far ahead as you can. Make sure everyone on the team is aware of what everyone else is doing.
*Taken from here
1. Define the Scope
The first, and most important, step in any project is defining the scope of the project. What is it you are supposed to accomplish by managing this project? What is the project objective? Equally important is defining what is not included in the scope of your project. If you don't get enough definition from your boss, clarify the scope yourself and send it back upstairs for confirmation.
2. Determine Available Resources
What people, equipment, and money will you have available to you to achieve the project objectives? As a project manager, you usually will not have direct control of these resources, but will have to manage them through matrix management. Find out how easy or difficult that will be to do.
3. Check the Timeline
When does the project have to be completed? As you develop your project plan you may have some flexibility in how you use time during the project, but deadlines usually are fixed. If you decide to use overtime hours to meet the schedule, you must weigh that against the limitations of your budget.
4. Assemble Your Project Team
Get the people on your team together and start a dialog. They are the technical experts. That's why their functional supervisor assigned them to the project. Your job is to manage the team.
5. List the Big Steps
What are the major pieces of the project? If you don't know, start by asking your team. It is a good idea to list the steps in chronological order but don't obsess about it; you can always change the order later.
6. List the Smaller Steps
List the smaller steps in each of the larger steps. Again, it usually helps you remember all the steps if you list them in chronological order. How many levels deep you go of more and more detailed steps depends on the size and complexity of your project.
7. Develop a Preliminary Plan
Assemble all your steps into a plan. What happens first? What is the next step? Which steps can go on at the same time with different resources? Who is going to do each step? How long will it take? There are many excellent software packages available that can automate a lot of this detail for you. Ask others in similar positions what they use.
8. Create Your Baseline Plan
Get feedback on your preliminary plan from your team and from any other stakeholders. Adjust your timelines and work schedules to fit the project into the available time. Make any necessary adjustments to the preliminary plan to produce a baseline plan.
9. Request Project Adjustments
There is almost never enough time, money or talent assigned to a project. Your job is to do more with the limited resources than people expect. However, there are often limits placed on a project that are simply unrealistic. You need to make your case and present it to your boss and request these unrealistic limits be changed. Ask for the changes at the beginning of the project. Don't wait until it's in trouble to ask for the changes you need.
10. Work Your Plan, But Don't Die For It
Making the plan is important, but the plan can be changed. You have a plan for driving to work every morning. If one intersection is blocked by an accident, you change your plan and go a different way. Do the same with your project plans. Change them as needed, but always keep the scope and resources in mind.
11. Monitor Your Team's Progress
You will make little progress at the beginning of the project, but start then to monitor what everyone is doing anyway. That will make it easier to catch issues before they become problems.
12. Document Everything
Keep records. Every time you change from your baseline plan, write down what the change was and why it was necessary. Every time a new requirement is added to the project write down where the requirement came from and how the timeline or budget was adjusted because of it. You can't remember everything, so write them down so you'll be able to look them up at the end-of-project review and learn from them.
13. Keep Everyone Informed
Keep all the project stakeholders informed of progress all along. Let them know of your success as you complete each milestone, but also inform them of problems as soon as they come up. Also keep you team informed. If changes are being considered, tell the team about them as far ahead as you can. Make sure everyone on the team is aware of what everyone else is doing.
*Taken from here
21 March 2008
Garmin GPS
This is the model of Garmin that we are going to supply to our customer: Garmin 60CSx. I have tested it and it is cool. It comes with map of Malaysia. but I haven't really take a look at the map. So I'm not sure whether it is as extensive as my Malsingmaps. But from the look of it, it is not that extensive.
Now, we have to look for the rechargeable batteries and start to deliver all the rest of the items.
19 March 2008
Subscribe to:
Posts (Atom)
