Memorandum for Project-Based Management

Running head: MEMORANDUM FOR PROJECT-BASED MANAGEMENT
Memorandum for project-based management
Name of the student:
Name of the university:
Author Note

1MEMORANDUM FOR PROJECT-BASED MANAGEMENT
Key Points:
The following memorandum includes the following structures.
 The organizational context: Here, the present status of the business is demonstrated. This is
related to the matters of considerations.
 Understanding the adoption of waterfall against Agile methodologies.
 Structure of project governance
 The usage of PMO
 The using of framework of Project Management Maturity
 Recommendations: Rational derivation of the matters to be considered.
Organisational context:
 The senior project manager of the current business has recently attended one conference. He
is also accompanied by the senior executive.
 Here, the various differences between the Waterfall Methodologies and Agile approaches are
described. Here, different project related tasks has been mattering. This program
demonstrated various project management maturity models, governance and PMOs.
 Further, the senior manager has asked the advice in the form of this memorandum.
 This written document should be demonstrating the cooperative relationship taking place
between various parties.
 They intends to work together over the project and meet the objectives that are agreed on. It
serves as the legal document and demonstrates the details and terms of the agreement of
partnership. The current memo is useful to denote various complicated matters. Thus it has

2MEMORANDUM FOR PROJECT-BASED MANAGEMENT
turned out to be clear such that the content of the data is passed and never distorted. This
short notice provided from the side of the management addresses specific policies.
 It provides particular announcements and modifications to be on for the organization. The
perquisite of the elements has been deployed for demonstrating the forming to leally bind the
contracts.
 This involves the offers acceptances, considerations, capacity and competency, mutuality of
obligations at particular situations with written tools.
Understanding the matters of considerations:
Adopting Agile versus Waterfall methods:
The Waterfall model is helpful for the customers and developers to get delivered earlier for
the lifecycle of development. It has made the designing and planning to be straightforward. Here, the
developments has been measured easily. This is because there is the total working scope that is
known in advance (Kakabadse and Kakabadse 2017). Across the effort of development, there are
possibilities for different team members to be get included or make continuation of their tasks. This
relies on the project’s active phase. Here, for instance, the business analysts are able to learn about
and then document the necessities to be performed, as the developers are found to work on the other
projects. Moreover, the testers are able to prepare the testing scripts from the documentation
requirements as the coding is underway. At last, the software must be developed totally and with
care. This should be based on the total analysis of every software deliverables (Rothlin and McCann
2016).
However, there are problems to be encountered through pure Waterfall approach. The sector
has been found to be falling short in terms of the requirement effectiveness. Documenting and

3MEMORANDUM FOR PROJECT-BASED MANAGEMENT
gathering of the requirements is meaningful for the clients. It is a complicated part of the
development of software. Further, the clients has been intimidated by the particular details. This is
delivered at the earlier stage of the project. Besides, the clients has been able to make visualizations
of the applications from the document requirement. Here, the effective disadvantage of the Waterfall
development is that the clients are dissatisfied with the software product delivered (Mason 2017).
Since, the deliverables are been based on the documented perquisites, the clients can see what is to
be provided till it gets completed. The changes are complicated and helpful to be implemented.
On the other hand, some of the benefits of the Agile approach includes the customers to be
frequent with early scopes to fetch the task to be provided. This is helpful to make the decisions and
modifications across the project development (Leicester 2016). Again, the clients are able to sense
strong ownerships through working high and directly to the project team across the project. As the
time for the particular applications is higher concern than to release the total feature is set at the
initial launch, the Agile can produce primary version of working, very fast. This is created on
successive iterations. Again, the development is user-focussed and resulting to frequent direction
from the clients (Burk 2016).
Nevertheless, there are various drawbacks of the model also. Here, a greater degree of
customer involvement is present. This presents the issues for consumers who have the interest and
time for this kind of participations. It works best as the team development members are totally
dedicated to the projects. As the Agile has been focussing on the time-boxed delivery and the
reprioritization in frequent manner, it is probable that few time are set for delivery. This can never be
finished under the timeframe allotted. The close working relationships of the Agile project are easy
to control as the team members are situated at the similar physical space. This is not possible always
(Rowe 2016). Besides, there are various ways to control the issue like collaboration tools, webcams