Software Project Management

Software Project Management
Name
Institution
Professor
Course
Date

Table of Contents
Question 1: Software development methodologies....................................................................................................4
Question 2: Memorandum on setting up a project board.........................................................................................8
Question 3 a: Project cost estimates..........................................................................................................................10
Question 3 b: Project cost benefits analysis..............................................................................................................10
Question 4: Project timeline.......................................................................................................................................13
Question 6: PRINCE2 Stages.....................................................................................................................................15
Question 7: Compare and contrast PRINCE2, PM-BOK and ISO 21500............................................................18
Similarities between PRINCE2, PM-BOK and ISO 21500.....................................................................................20
Bibliography................................................................................................................................................................21

Table 1: Comparison of software development methodologies......................................................3
Table 2: projects costs estimates......................................................................................................8
Table 3: cost benefits analysis.......................................................................................................10
Table 4: Project timeline................................................................................................................12
Table 5: Comparison of PRINCE2, PM-BOK and ISO21500......................................................16
Figure 1: Cost benefit analysis......................................................................................................................................12
Figure 2: Project timeline..............................................................................................................................................16

Question 1: Software development methodologies

Table 1: Comparison of software development methodologies
Project Features System development life cycle
(SDLC)
Rapid Application Development
(RAD)
Publicity and
advertisement of the
T&M Stores plc
services
The SDLC is considered to be one of
the most straightforward software
development methodologies to follow.
In this case, it offers the ability to
develop steps literally and give a focus
to the phase that an organization wishes
to deliver first. Since all steps in SDLC
are essential and should be followed,
the software developer can decide to
have a simple implementation of a
given stage keeping in mind it would
be revisited during the next iteration
(Machado & Martes 2015, pp. 32).
Considering T&M Stores plc want
publicity module to be delivered at
earliest, its software development
process can collect required
specifications and related to the
specific urgent need and develop the
module. The development would be
focused on the design phase of
software development. This would help
software developers to come up with
publicity module earlier than expected.
The rationale behind SDLC has been
attributed to its ease of use and several
iterations.
The RAD methodology is believed
to offer faster software
development process compared to
other available methods. Despite
being more rapid, it has proved to
provide the desired quality
products. In this case, it can be
used by software developers to
come with prototypes and
component reusability. Since
T&M Stores plc want to bring on-
board publicity at earlier stages of
software development, RAD
seems more suitable for the
project (Machado & Martes 2015,
pp. 29). Considering RAD is more
applicable to Object-oriented
software development
technologies, it fits the subjected
T&M Stores plc web product. The
website would be developed in
PHP which embraces the use of
OOP concepts. The choice of
RAD has been facilitated by its
ability to focus on a specific part
of the project at any point without
implications.
Reporting tools and With SDLC methodology, it is possible RAD methodology is suitable for

format to the T&M
Stores plc
management
to integrate and implement reporting
tools to the website. It is evident that
management would need to analyse the
rate of traffic on the website. This can
be used to determine the number of the
prospective customer. Through the use
of SDLC methodology, software
developers can implement some
monitoring tools from the earlier
phases of software use (Shaikh &
Ahsan 2015, pp. 126). Once integrated
into the system, it is possible to
improve these reporting tools
continuously and features later during
the next phases of software iterations.
Therefore, the SDLC would be
applicable for reporting tools due to its
capability to offer improved features.
In this case, it would be suitable for
product features that require future
review and improvement as well as
functions that are needed in advance
and are in between different project
phases. The choice of SDLC for the
subjected feature is due to its ability to
offer iterations for improvement.
the development of reporting tools
due to its capability to focus on a
specific instance irrespective of
where it can be found within
project phases (Shaikh & Ahsan
2015, pp. 126). Since RAD does
not have considerable principle
application, it can skip other
phases and focus on what product
developer feels it is more
important. In this case, it can be
used to integrate and implement
reporting tools as required by
T&M Stores plc. It is important to
note that some product features
would be necessary earlier than
others but are in different project
phases. With RAD, it would be
possible to develop them without
considerable implications on
product delivery (Chatzoglou et
al. 2007, pp. 305). The rationale
for RAD at this project feature has
been attributed to the ability to
focus on specific function
irrespective of the project phase.
System integration
with other T&M
Stores plc existing
products
SDLC offers the ability to improve on
the already existing product as well as
new products as envisioned on T&M
Stores plc requirements. T&M Stores
plc requires new web-based product
On the same note, it is possible to
use RAD to link already existing
products with the advanced system
without considering the phase of
the project. Irrespective of the