Graded Moderated Discussion Board (Graded MDB)
Dear students a Graded Moderated Discussion Board will be opened for "Software Project Management (CS615)" from July 27, 2010 to July 28, 2011, in which you have to post your comments on the topic given below and it will have weight-age of 5% of your total subject marks. Your comments will be graded based on the logic you have used to support your answer.
"MONITORING AND CONTROLLING USING MEETINGS, REVIEWS AND REPORTS FOR COMMUNICATION WITH IN TEAM AND THE OUTSIDE WORLD IS BEst TECHNIQUE IN SOFTWARE PROJECT MANAGEMENT" Either you agree or disagree with given statement , justify your reply with sound arguments".
Note:
1. Books, websites and other reading material may be consulted before posting your comments. (Do not copy the material as it is from internet and other resources.) If any one found copying the answer of other students or from any web site will get zero marks for his/her attempt. 2. Your comments must not exceed more than 7 lines.
3. Try to come up with your own arguments so that you could get maximum benefit from this exercise.
4. Short and to the point comments will be preferred over lengthy comments.
5. You should post your comments on the Graded MDB & not on the Regular MDB. Both will run parallel to each other during the time specified above. Do not post multiple comments.
6. Be careful for you may loose GMDB comments due to electricity load shedding and internet problems. You cannot participate in the discussion after the due date or through e-mail with in specified time.
7. Your answer should contain important points. Also follow the instructions given in announcement.
You can start preparing your comments now. In case of any query mail at[url=mailto:CS615@vu.edu.pk]CS615@vu.edu.pk[/url] ......................
SOLUTION:
Project Management Monitoring and Controlling Tools & Techniques
Monitoring and Controlling a project is the process or activities whereby the project manager tracks, reviews and revises the project activities in order to ensure the project creates the deliverables in accordance with the project objectives. Because of the unique and temporary nature of projects, they require active control. Unlike a process where the same set of activities have been performed repeatedly so that habits and expectations are stable, a project is inherently unstable. The activities are unique to the project or the sequence of activities and resources are only temporarily assigned associated with the project and are redeployed when the project completes. Habits and patterns are not established before everything changes.
The primary results of the Monitoring and Controlling processes are the project performance reports and implementing project changes. The focus for project management is the analysis of project performance to determine whether a change is needed in the plan for the remaining project activities. In my experience, almost every project will require a change to the plan at some point in time. Traditional projects are the most stable projects because the requirements and the activities are clear and well understood. Adaptive and Extreme projects are the least stable. They require very close control and will require numerous changes - if for no other reason the project manager will need to refine the activities of later phases based upon the results of early activities.
Tools and techniques that are used by project managers to conduct the Monitoring and Controlling of a project fall into one of four general categories. The first is the collection of project performance information. Techniques supporting this category are Pulse Meetings, Variance Reports, and Program Reviews. The second category is the analysis of the project performance to determine whether a project change is needed. Techniques that are used in this category are Project Forecasting and Problem Solving. The third category is reporting on project performance. Techniques that support this activity include the use of a Project Management Information System, Management Reviews, and Dashboards. The final category is the management of project change. The technique I commonly use in this category is the maintenance of a Change Management Log. There are two areas of project management tools and techniques that closely support the Monitoring and Controlling process but are also used more broadly throughout the project lifecycle. These are important enough to justify their own page.
The primary results of the Monitoring and Controlling processes are the project performance reports and implementing project changes. The focus for project management is the analysis of project performance to determine whether a change is needed in the plan for the remaining project activities. In my experience, almost every project will require a change to the plan at some point in time. Traditional projects are the most stable projects because the requirements and the activities are clear and well understood. Adaptive and Extreme projects are the least stable. They require very close control and will require numerous changes - if for no other reason the project manager will need to refine the activities of later phases based upon the results of early activities.
Tools and techniques that are used by project managers to conduct the Monitoring and Controlling of a project fall into one of four general categories. The first is the collection of project performance information. Techniques supporting this category are Pulse Meetings, Variance Reports, and Program Reviews. The second category is the analysis of the project performance to determine whether a project change is needed. Techniques that are used in this category are Project Forecasting and Problem Solving. The third category is reporting on project performance. Techniques that support this activity include the use of a Project Management Information System, Management Reviews, and Dashboards. The final category is the management of project change. The technique I commonly use in this category is the maintenance of a Change Management Log. There are two areas of project management tools and techniques that closely support the Monitoring and Controlling process but are also used more broadly throughout the project lifecycle. These are important enough to justify their own page.
...............
Program Reviews
Program Reviews are meetings with the project team members that review the current status of the project as compared to the original project plan. These are most often used on Full-scale and Complex projects. Unlike the Pulse Meetings which focus on day-to-day activities, the Program Reviews focus on the big picture and emphasize the integration between activities and between sub-projects encompassed within the project. The question being asked is whether the project activities and the sub-projects are likely to interfere with each other. In addition, when I have a supplier who is a major contributor on the project and is performing customized work on this project, I will conduct Program Reviews with the supplier for their portion of the project. Program Reviews are sometimes combined with Management Reviews. The danger with this approach is that key stakeholders and managers may intimidate some project team members from providing a frank and honest appraisal of status.
Program Reviews are meetings with the project team members that review the current status of the project as compared to the original project plan. These are most often used on Full-scale and Complex projects. Unlike the Pulse Meetings which focus on day-to-day activities, the Program Reviews focus on the big picture and emphasize the integration between activities and between sub-projects encompassed within the project. The question being asked is whether the project activities and the sub-projects are likely to interfere with each other. In addition, when I have a supplier who is a major contributor on the project and is performing customized work on this project, I will conduct Program Reviews with the supplier for their portion of the project. Program Reviews are sometimes combined with Management Reviews. The danger with this approach is that key stakeholders and managers may intimidate some project team members from providing a frank and honest appraisal of status.
...........
0 comments:
Post a Comment