IDS end of the process. The disadvantages of the

IDS 507 – Spring 2018

Case Study 1 (Memo)

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

To Jim Barton,

After keenly observing
the meetings and discussions, I am writing this memo to provide recommendations
for a project management approach at IVK Corporation. Based on the documents written
by Davies and the difference of opinions between Rebecca Calder and Jorge
Huerta, I have arrived at the following conclusion about the existing approach:

1.   
The
status of many projects is over budgeted and behind schedule.

2.   
The
existing approach for project management is the traditional approach and it
follows Davies’s approach of introducing slack to meet deadlines in case of unanticipated
requirements or changes in plan.

3.   
I
would recommend the company to use a combination of both the approaches as the
company’s major projects do not involve software development and of those which
involve do with “fitting a purchased package of some kind to existing IVK
systems, creating interfaces between two systems.”

The rest of
this memo explains the basis of my conclusions. I will present my analysis in three
parts. The first part deals with the conversation between Rebecca Calder and Jorge
Huerta on the project status. This is followed by Davies’s approach on existing
system. The last section is on the new approach recommended.

 

Project Status Analysis

From the
conversations between Rebecca Calder and Jorge Huerta, I would agree with
Rebecca Calder as how much ever we plan and anticipate future requirements,
there is always few unanticipated requirements that pop up during or at the end
of the process. The disadvantages of the existing traditional approach are, it
costs more as we near the final stage of the project and also fall behind
schedule to include the unanticipated requirements. The company can overcome these
by following the iterative prototype approach suggested by Rebecca Calder and spend
quality time on gathering requirements and planning so as to reduce the number
of unanticipated requirements.

 

Davies’s Approach

The previous
CIO Davies handled this issue of unanticipated requirements under the existing
system by introducing slack to meet the deadlines. The slack was based on the
estimate confidence. Here the disadvantages are huge reliability on the person
calculating the estimate confidence and at times few projects were finished way
before the mentioned slack which will have its effects on cost and resources. So,
this will not always work out for all the projects carried out using the existing
traditional approach.

 

 

 

New Approach

There are many
factors like Customer Availability, Scope, Feature Prioritization, Team size,
Funding that come into context while choosing an approach for project
management. For Software development projects that have frequent change in
requirements, high customer availability, small team size and non-fixed funding,
Agile approach is the best as it is an iterative, team-based approach to
development. In such scenarios, using traditional approach, leads to the
possibility that the customer will be dissatisfied with the delivered product. As
all deliverables are based upon documented requirements, a customer may not see
what will be delivered until it’s almost finished. By that time, changes can be
difficult (and costly) to implement.

In IVK
Corporation, there are only a few projects that require software development
and majorly the development part of the projects are such that “fitting a
purchased package of some kind to existing IVK systems, creating interfaces
between two systems” which is more of system integration. In such projects it
is difficult to estimate the size and develop prototype models in short
intervals. Hence, I would recommend a combination of both approaches where in there
is more time allocated initially for requirement gathering and planning to
reduce the number of unanticipated requirements. Then as Rebecca Calder said the
company can simulate the prototype on paper for projects that take longer to install
and get configured to overcome those unanticipated requirements.

 

Conclusion

I recommend
the company to use a combination of both approaches (traditional and agile) for
the current projects it has where there is hardly any software development. As
the projects change, the company should adapt other approaches based on the above-mentioned
factors. This would allow the company to deliver high quality projects as per
their schedule and within budget.

 

Sincerely,

Charanya
Subramanian