Exercise 5

Schwalbe P.195 - Chapter 5, Ex 3


Create a WBS for the following project:

• Creating a new information system for your school or company

Decide on all of the level 1 categories for the WBS. Then break down the work at least the third level for one of the level 1 items. Enter the WBS into Project 2003 and print out the Gantt chart. Do not enter any durations or dependencies. Make notes of questions you had while completing this exercise.

Gantt chart

.

Information system for Annie's Company

1 Project Management

2 System Engineering

3 Software

3.1 Software design

3.1.1 Software requirement specification

3.1.2 Software work package definition

3.1.3 Software prototyping

3.1.4 Software unit detailed design

3.2 Software build

3.2.1 Software unit coding

3.2.2 Software unit debugging

3.3 Unit testing

3.3.1 Unit test planning

3.3.2 Unit test case preparation

3.3.3 Unit test conduct

3.3.4 Unit test record
4 Hardware

5 Deliverables Management

6 System Management

7 Support Services

8 Installation

Reference
.
Schwalbe, K. (2006). Information Technology Project Management (4th ed.). Massachusetts: Thomson Course Technology.

Exercise 4

Schwalbe P.160 - Chapter 4, Ex 4

Create a weighted scoring model to determine grades for a course. Final grades are based on three exams worth 15%, 20%, and 25%, respectively; homework is worth 20%; and a group project is worth 20%. Enter scores for three students. Assume Student 1 earns 100% (or 100) on every item. Assume student 2 earns 80% on each of the exams, 90% on the homework, and 95% on the group project. Assume student 3 earns 90% on Exam 1, 75% on Exam 2, 80% on Exam 3, 90% on the homework and 70% on the group project. You can use the weighted scoring model template, create your own spreadsheet, or make the matrix by hand.


Weighted Scoring Model for Course ITC000

Assume that Grades range from A to F, where 50% is the passing mark, A-E means Pass, F is failed below the passing mark.
(The space below is unintended, caused by bugs of this blog site. Please scoll down.)

Assessment	Weight	Student 1	Student 2	Student 3
Exam 1	15%	100 = 15%	80 = 12%	90 = 13.5%
Exam 2	20%	100 = 20%	80 = 16%	75 = 15%
Exam 3	25%	100 = 25%	80 = 20%	80 = 20%
Homework	20%	100 = 20%	90 = 18%	90 = 18%
Group Project	20%	100 = 20%	95 = 19%	70 = 14%
Total	100%	100%	85%	80.5%
Grade	A-F	A	B	B

Reference

Schwalbe, K. (2006). Information Technology Project Management (4th ed.). Massachusetts: Thomson Course Technology.

Exercise 3

Schwalbe P.112 - Chapter 3, Ex 5

Read an article about a recipient of PMI's Project of the Year award, such as the Salt Lake City Organizing committee mentioned on PMI's Web site. Write a one-page paper summarizing the project, focusing on how the project manager and team used good project management practices.


Link to source article:
"PMI® Case Study, Quartier International de Montréal: 2005 PMI Project of the Year" (PMI, 2006),
http://www.pmi.org/PDF/Case_Quartier%20International%20Montreal.pdf


The Quartier International de Montréal (QIM) was a massive urban revitalization project that comprehensively restructured a large portion of Montreal’s city center from the ground up.

The QIM team used standard project management techniques to coordinate the project’s many complex activities, plan for risks, and accommodate last-minute changes to the project plan by the City of Montreal. As a result, the QIM project was completed within budget and schedule, and won the PMI's Project of the Year award.

The project

Montreal city features a large business district and the Old Montreal town center, joined by an expressway that was not only unattractive, but impeded the potentially lucrative flow of pedestrian traffic. The QIM project's goal was to revitalize these two areas by covering the expressway to create 27 additional hectares land for business, cultural and pedestrian use - increasing traffic and revenue for both the quarter and the city. The team was to complete the project within a five-year time frame, US$90 million budget.

Outstanding project management practices

The QMI team succeed in applying many standard project management techniques:

• Integration management - identifying challenges and resolving methodology during project planning. Developed a detail plan allowing inevitable changes which are highly possible with a project of this scope and complexity. Each phase of the project had built in flexibility to accommodate unforeseen changes, which enabled the project to meet stakeholder needs at the time of request, mitigated the possibility for complaints.
• Quality management - created an outline of the QIM team's principles as initiatives, which provided a point of reference as well as a benchmarking tool throughout the cycle of the project. The team also included quality provisions in the contractors’ and employees’ mandates, and required that all professionals produce prototypes for original deliverables and conduct external testing for all stages of construction.
• Human resource management - established a professional development committee to encourage quality work and support employee morale.
• Communication management - Website, newsletters, mobile exhibit, informational DVD,daylong team meetings are developed to help communications between the team and all stakeholders.
• Risk management - an exploratory dig helped mitigate the risks associate with the project; provisions are included in the risk management budget in anticipation of potential problems.
• Procurement management - mediation and arbitration clauses are included in procurement contracts to create a framework for disputes, helped to avoid making compromises that would not benefit the project.

Outcome

With such good practices of project management, QIM attained a highly remarkable success that both public and private partners almost completely realized their ROI, and 100% satisfaction rate is gained from both users and the city government. The project lauded with international accolades received 17 awards in total.

Reference

PMI, Project Management Institute (2006). PMI® Case Study, Quartier International de Montréal: 2005 PMI Project of the Year. Retrieved August 25, 2007, fromhttp://www.pmi.org/PDF/Case_Quartier%20International%20Montreal.pdf

Exercise 2

Schwalbe P.66 - Chapter 2, Ex 5.

Write a one- to two- pages summary of an article about the importance of top management support for successful information technology projects.


Link to source article:
"The Importance of Executive Buy-In on Your ERP Project" (Kimberling, 2006),
http://blogs.ittoolbox.com/erp/roi/archives/the-importance-of-executive-buyin-on-your-erp-project-8009

This is only a short article but I have found it conclude all important points of the subject issue here. Although it exclusively focused on ERP (Enterprise Resources Planning) project which is big, the same theory literally applies to IT projects of all sizes.

According to a study updated by The Standish Group at 2000, Executive support is listed as top No.1 criteria among "Recipe for success - CHAOS Ten". It leads over User involvement, Experienced project manager, Clear business objectives, and other critical successful factors in project management. It highlights "lack of executive input can jeopardize a project" (Johnson, Boucher, Connors & Robinson, 2001).

And in the above source article, Kimberling stressed that the importance of "executive buy-in" goes beyond approving the budget to pay for the project. I summarised his points as below:

The importance of top management support for successful IT projects

1. Funding the project;
2. Top management or executives need to be engaged in projects to help making key business decisions which will affect the operation model and the organisation itself;
3. Large projects across multiple sectors of an organisation require top management to fight sensitive political battles during implementation, such as changing operation models, business processes, and staff positions;
4. Top management is needed to procure and secure employee resources necessary for the success of projects.

Furthermore, to complete the concept, senior consultant Gary Owen (2007) suggested six techniques to get started in obtaining top management support and but in:

1. Start small, be realistic;
2. Show value;
3. Don’t oversell;
4. Identify costs and resources first;
5. Be available and committed;
6. Build upon business continuity planning (Owen, 2007) visibility.

As the success or failure of IT projects hinges on the level of executive support received, IT professionals need to garner it, and keep it. Otherwise uninterested senior management will often relegate the projects to obscurity.

Reference

Johnson, J., Boucher, K.D., Connors, K., & Robinson, J. (2001). Collaboration: Development & Management, Collaborating on Project Success. Software Magazine and Wiesner Publishing.
Retrieved August 22, 2007, from http://www.softwaremag.com/archive/2001feb/CollaborativeMgt.html.

Kimberling, E. (2006). The Importance of Executive Buy-In on Your ERP Project. Information Technology Toolbox, Inc. Retrieved August 22, 2007, from
http://blogs.ittoolbox.com/erp/roi/archives/the-importance-of-executive-buyin-on-your-erp-project-8009.

Owen, G. (2007). Consultants Corner: Getting Executive Support for your BCP. Strohl Systems. Retrieved August 22, 2007, from
http://www.recoverychronicles.com/MediaPR/eNewsletter/November2004/393/Article.asp.

Exercise 1

Schwalbe P.35 - Chapter 1, Ex 4

Find any example of a real project with a real project manager. Feel free to use projects in the media or a project from your work. If applicable. Write a one-page paper describing the project in terms of its scope, time, and cost goals. Discuss what went right and wrong on the project and the role of the project manager and sponsor. Also describe if the project was a success or not and why. Include at least one reference and cite it in the last page.



The Project

Link to source article:
"The project was three years late: but an incredible success!" (Woodward, 2005),
http://www.pmforum.org/library/cases/2005/cases05-0506.htm#02

This article describe a project conducted in USA, a company intended to increase its production by modifying the machines in their manufacturing plants throughout the country.

Here I summarize the project in terms of the Triple Constraint - Scope, Time and Cost (Schwalbe, 2006, p. 7) :

• Scope: To modify 21 paper machines at 4 manufacturing plants in USA, by installing control devices designed to reduce defects and allow workers to speed up the machines.
• Time: 2 years.
• Cost: Not mentioned in the article.

The objective of this project is: To produce additional production at an affordable cost.

As described in the article, inputs of the project includes a scope statement, a diverse team, a list of interested contractors, and the enthusiastic support of management. The project manager oversaw all aspects essential for the project such as communication, change management, risk management, and all the others. To begin with, the project team thought that they had had an excellent plan, even though it was implemented under tight cost and schedule requirements.


What Went Wrong??

The project turned out has the following problems:

1. Over-spending at the earlier stage.
2. New technology did not increase production as anticipated, sales volume was not developing.
3. Further cost constraint induced deference of the project and eventually it could not be completed within the time frame.
4. Downgrade of the project priority from management - from top to none.
5. The project was ordered to put on hold, but permitted to restart at any time.

What Went Right??

Once the project was put on hold, the company left the development team a free hand to restructure it. The project finally accomplished the goal in doing something right:

1. Reduced risk by prototyping each of the technologies included in the original scope, conducted sufficient testings until they found out which one works on the paper machines.
2. Strategic modification of scope - only premium devices were installed, new ideas evolved.
3. Proven methodology recovered sales and provided return on investment.

Role of Project Manager and Sponsor

On the whole, this project does not comply to a rigid plan of management. The project manager was supposed to monitor costing and timing at initial stage, ensure that expected results are shown at intervals. Yet, this is overlooked. The project manager should also investigate a proven or lower-risk methodology of execution during project planning, instead of doing trial and error in a full scale. He did perform a certain degree of change management, such as to redesign the cost and schedule commitments, restructure the project scope and process, etc. Yet the final success only arrived with some luck and flexibility of the sponsor.

Success or Failure?

Obviously this project would not have reached fruition if the management team was out-sourced to an external agent, say, a consultant company. It was possible to take a second chance to restart the whole project with no constraints, only because the project team resided in the company of its sponsor, that its existence was relying on other profit-generating jobs. The desired goals of the project was finally reached, but 3 years after the original completion date. I would consider this project a failure from a traditional project management perspective.

Reference

Schwalbe, K. (2006). Information Technology Project Management (4th ed.). Massachusetts: Thomson CourseTechnology.

Woodward, H. (2005). The project was three years late: but an incredible success! pmforum.org, Inc. Retrieved August 19, 2005, from http://www.pmforum.org/library/cases/2005/cases05-0506.htm#02.