Notesale: Turn your study into money

Document Preview

Extracts from the notes are below, to see the PDF you'll receive please use the links above

---

lOMoAR cPSD| 3013804

lOMoAR cPSD| 3013804

Project Management
SOFTWARE DEVELOPEMENT

Project Phasing
To ensure the implementation of large-scale software development projects, they need to
be broken down into more manageable project components
...

Before we begin the project, I must first phase the project and that begins by looking at the
user requirements we have been tasked with by the client
...
They are the end user's requirements
...

However, the reason we are dividing the project into smaller tasks is so that a set task can
correspond to each and every stage of the methodology
...
I already analyzed extensively the project life cycle in learning Aim A but will now
look into in context of my current project
...
I will carry out this phase, through many different means:
Identifying stakeholders
A project scope meeting
Breaking down requirements into smaller non-functional requirements
Acceptance of requirements documentation
Budgetary requirements
Risks and constraints
Project Initiation document
All of these documents/feedback will provide adequate information and scope for
stakeholders and product owner to give the greenlight for the project by highlighting the
requirements and constraints needed
...
It will be a phase of continuation
from the concept initiation including some important documents that will most definitely
be needed to produce in this stage:
Scope and Budget (further developed from the initial documents)
Work breakdown and schedule
Gantt Chart
Communication Plan
Risk Management (in more depth)
Launch and Execution –
Although concept gathering and planning is an important step for every project and its
development it is not the be all and end all of project management and the software
development
...
By setting
realistic and attainable targets with the addition of incentives it boosts output and morale
for workers, other things we will do to accomplish this:
Objectives (making them realistic and attainable to not strain workers)
Quality deliverables
Effort & cost tracking
Performance (vague but an essential tool to look at)
Project Close We must ascertain to keep stakeholders and clients at EBITS happy as I am contracted to
them and the project must serve the purpose, with this in mind producing a solid project
closure
...
However, there were some concerns raised about some user
requirements that were not being given enough importance which is a genuine and rightful
remark to make by the client
...

User Requirements
Functional Requirements: These are the basic features that the system should provide that
the end user specifically requests
...
These are represented or stated as input to be given to the
system, operation to be performed, and expected output
...

Non-functional requirements are the quality constraints that the system must meet to meet
the project contract's requirements
...
Non-behavioral requirements is another
name for them
...


PAGE 3

lOMoAR cPSD| 3013804

integrated nature
Use cases Regulatory Req

Weekly Timetable
Day:
Monday

Tasks:
We will meet and talk to the client at
the beginning of every week and keep
them up to date with how the project is
going and making sure that our aims
are in line, this does not include the
original project scope meeting held
with Stakeholders and the head of the
EBITS company
...
For
example, on Week 1 Where we are
working on Requirements planning
and if we go ahead on schedule then we
can begin to start on User designs
...
Andy the
systems architect, Wahyu will undergo
1 hour of training on this day to
streamline their skills
...
As a collective group we will
then decide what the best course of
action is and work together to solve the
problem so that the project is on
schedule
...
On the Friday we will test
out this prototype first with the
manager and if they give the approval
then we will test it out on the public
...

These two days we will have days off,
but workers may be required to come
back to work in the case of overtime if
behind on the schedule or a problem is
still not solved by Thursday
...

I was able to narrow down my search to two methodologies that I believe would be best
suited for the project that I am managing
...
For example, Agile and RAD have a range of
benefits that subscribe to software development and the philosophy of constant user
feedback centered around development and improvement of the prototypes
...
Obtaining user feedback is very important due to the deconfiguration
management method of keeping computer systems, servers, and software in a consistent,
desired condition
...
The agile methodology is centered
around the need for more agile deliveries to its customers and adapting based on those
needs, it is a methodology that strives for dynamic and flexible solutions to projects which
is exactly what the company needs in the development of the software
...

Another question we must answer is how I as the project manager will integrate the Agile
methodology into the software development and project:
Implement all four phases of the agile methodology
Employing intelligent software with a wide capacity to act and milking agile for its
full potential
Minimum functionalities delivered to customers before closing the project
Avoiding errors by reinventing the prototypes and making the close to perfection
software
Facilitating the intelligent resolution of programs by combining the client needs,
user requirements and improvement from failures resulting from the process
...
Through advanced reporting tools and
techniques, quality is ensured throughout the project's implementation phase, and all
stakeholders are involved in the process with daily progress reports
...
There are more ways to identify and predict risks
within the Agile framework, as well as plan to ensure that the project runs smoothly
...
The project plan is comprehensive and broad for the purpose of organization
and resolution
...
This project plan will aim to limit those factors and be a success, it will help to
curtail overspending and late turnaround by identifying the issues and solving them before
they occur
...

2
...

4
...

6
...

8
...

10
...

12
...

14
...
Test it with wider public
16
...
The software must be viable, reliable, userfriendly, and efficient in its purpose
...
The system is outdated and is prone
for error and therefore EBITS has now identified the need for software that will allow them
to calculate how many hours an employee will spend on a specific project to accurately
charge clients for the time spent, providing more stability, assurance and cash flow for
correct services to their consumers
...

One problem with the software is the accountability for the employees to accurately
report how long they spent on a task each day as employees can lie about how long
they spent on such and such task in order to get more time off or get paid more
which could negatively affect the client and possibly cause complaints and bad rep
for the company
...

Another problem is making the software accessible as was requested by the Client
in our initial scope meetings to meet the demands of disabled and accessible staff
who will be using this software but to also align with the law and follow all
professional guidelines

PAGE 8

lOMoAR cPSD| 3013804

Solving these problems is essential because the audience is at the forefront of our
minds, and this is the staff who will be using the software on a day-to day basis
...


The Solution
The software that we are producing will be an immediate solution to the problem because it
will provide all the functional and non-functional requirements needed
...

Managers must calculate how long each task will take
...

The employee must accurately report how much time they spent on a task each day
...


Highlights
After completing comprehensive market research and analyzing the scale of earnings for a
range of different companies after deploying similar software
...
Examples of this include the famous iMonitorsoft
which records employee activity and productivity to improve output
...
An example
of a company that deployed is Brace who are an investment banking company that saw
profits increase by 75% in Year 1 and 125% in Year 2 with this modelling we have made the
following chart as a projection for EBITS
...
Managers must
estimate, allocate, plan, and distribute resources according to the highest priorities at any given
time to avoid negative consequences such as delays, decreased quality, or increased costs
...
Tools
and equipment, money, and services are all examples of resources
...

In relation to EBITS I as project manager must manage the recourses to an efficient basis as to
not fall into the trap of running out resources, time, money etc
...
]
Budgetary Requirements –

[The total budget handed to the project was handed to me by the Stakeholders and
EBITS owner was +/- 100,000$ but as I wanted to stay consistent, I intended to stick
strictly to that figure and the budgetary requirements analysis as shown above in
the chart totaled up to $60,590 by using a range of formulas with the legatee of
time and recourses
...
This will close any loopholes for lawsuits or enemies of
the company retaliating against us
...
However, this is a moving post and we will always keep the
situation updated
...
Most of the project constraints on this project impact
one another, which is why the constraint management is so important
...
As the project
manager for EBITS I have identified 6 constraints that could occur over the course of the
project and have been divided into the table below:
Constraints

Severity

Contingency

1
...
Lack of Recourses

Medium

✔

3
...
Poor quality

High

✘

5
...
Risks

Extreme

✔

7
...
The risk of running out of
money and spending too much is huge so we must actively prepare for that possibility
...
Tracking a project budget, like tracking time, will allow me to see ahead of
time whether a project is expected to go over budget
...
" Tracking the budget monthly is a good place to start if you want to stay on top of
the financial status of your project
...


PAGE 16

lOMoAR cPSD| 3013804

Contingency 2 – Lack of resources
A lack of resources can come from a whole range of issues:
Physical issues – such as a fire or flooding – can cause physical damage to your
property
...

Product failure occurs when your products cause harm or must be recalled
...

Supplier issues – Issues with your major suppliers are likely to have a negative
impact on your business as well
...

However, with the resource management plan in place, we are well prepared in the event of
this happening
...
Extending your project timeline will result in
consequences such as extended deadlines, changes to the team calendar, or less time for
planning
...
In response, I created a range of contingency plans
for me to do in case this happened; one of them is that I have a second Gantt chart in place
that will take precedent if I fall behind on the second one
...
However, now I have a solid method of time management that is prepared in all
scenarios
...
” – Contract on the weekly timetable
...
While project monitoring is regularly overlooked or seen as just another box to
tick off the task list, I view it as a vital part of the project’s success
...


2
...


Divergence of Planned Budget – By monitoring how and who and why the project
budget deviated is important in tracking down waste and inefficiency, as well as for
planning better for the unforeseen challenges inherent to most project
...

Deviation of Planned Hours of Work - Understanding which tasks took the most or
least amount of time can aid in the efficient allocation of consulting and training
time
...

Percentage of Milestones Missed - Identifying when milestones are missed can aid
in the restart of a project and the avoidance of similar problems in the future
...


PAGE 18

lOMoAR cPSD| 3013804

KPI (Key Performance
Indicators)

Software

Installe
d

Divergence of planned budget

Sisense

✔

Deviation of planned hours

Power BI

✔

Percentage of milestones

Klipfolio

✔

Performance of Staf

iMonitorSoft

✔

[The licensing of all the software has been paid for and accounted for in the budgetary
requirements
...

As a collective group we will then decide what the best course of action is and work together
to solve the problem so that the project is on schedule
...
Risk-management
activities may be used at any time during the project's life cycle
...
Unmanaged risks
can easily prevent a project from meeting its objectives or even failing to succeed
...

A successful risk management program helps an organization consider the full range of
risks and plan for them it also examines the relationship between the issues and the
progression of the project allowing a smooth-running operation
...

However, risk managements can mean different things on different types of projects
...
On the other hand, for smaller projects such
as EBITS software development, we are going to list the range of risks that could occur and
prioritize the list of high, medium and low risks
...
In other words, we need to right a detailed project
charter, with the project vision, objectives, scope and deliverables so that the risks can be
identified easily and managed
...
Risk can be either positive or negative, though most people
believe risks are always negative
...

Risk analysis is difficult
...
Of course, much
of that data is complicated, but most industries have best practices that can assist you with
your analysis
...

The vast majority of risk will be damaging, and we must assess probability of occurrence ×
expected impact on the project and how it will affect the delivery of the project; cause any
delays; stop us from reaching the customer requirements
...


1

Risk title
...


Very likely

Potential size of

Major

PAGE 21

lOMoAR cPSD| 3013804

impact
Risk severity
...

not be compatible with the company and/or the technology is not feasible
to be produced
...
The technological aspect of a project poses a significant risk to
data security, organisational services, compliance, and information
security
...
Other technological risks include service
outages, which can cause project delays and failure
...


2

Risk title
...


Unlikely

Potential size of
impact

Moderate

Risk severity
...


Effective and timely communication is a critical work ethic that must be
strictly adhered to when in charge of a project
...
With all the communication channels and
gadgets at our disposal, team members can sometimes overlook the critical
components of effective communication, resulting in data loss or
misinformation and, ultimately, project disruption
...


3

Risk title
...


Unlikely

Potential size of
impact

Major

Risk severity
...


A type of risk that can jeopardise a company's compliance rules is health and
safety
...
The risk can also result in health issues for employees or
customers, putting a company's reputation at risk
...


Risk number
...


Market Risk

Probability
...


High

Explanation of the
risk in context
...

Competitors may seize the opportunity to cripple and eliminate the business
from the market
...
Liquidity, credit, and
interest rate fluctuations are also potential market distractions for the
project's product sales
...


Execution of the Project
Iterations
PAGE 23

lOMoAR cPSD| 3013804

Iteration 1 –

Iteration 2 –

Iteration 3 –

Iteration 4 -

Time –
30/07/2021 – 31/07/2022:

PAGE 24

lOMoAR cPSD| 3013804

Wayhu, Andy have been called to work overtime over the weekend to catch up and finish off
the design phase in order for us to not fall behind on the meetings and stakeholder targets
...
The total number of days we fell behind on the schedule was 15 days
...
In response, I created a range of contingency plans
for me to do in case this happened; one of them is that I have a second Gantt chart in place
that will take precedent if I fall behind on the second one
...
However, now I have a solid method of time management that is prepared in all
scenarios
...
The second Gantt chart is below:

[As can be seen this Gantt chart is more specific to the execution phase and has
been moved back 2 weeks (15 days) to match the pace of the project
...
The extra costs were incurred from our inaccurate estimates we made at the
beginning of the project and during the feasibility analysis, we embarked on a big project
with inaccurate figures in mind
...

Another reason why the budget went over was that some grave project design errors were
made, we rushed the design phase and paid the price during the execution phase, it could
have led to the finished product being designed poorly due to the time constraints placed
on us the project than incurred more and more costs that were not planned for such as
overtime hours etc
...
Scope creep is a major cause of project cost overruns because it can result in a
drastic change in project direction or processes
...
Extra
work, installations, or repairs that were not anticipated or budgeted for were required in the
project
...


Define the quality
...


2
...


3
...
If the team doesn’t know the goal, how can they meet it?

PAGE 26

lOMoAR cPSD| 3013804

4
...
Define relevant testing processes to measure quality targets and assess
effectiveness
...


Act
...


The staff members had these 5 steps painted into their brains and I am pleased to say all
quality targets that were set during the monitoring phase were MET
...


Not Feasible – not Denied –
compatible with
Lack of
data laws
majority for
change

Investor
representative
– Amy Hart

Verbal meeting – Make the software
Icons square to make it look more
attractive and easier on the eye

Feasible

Approved –
Unanimous

Risks and issues- The purpose of the risk and contingency measures was to have a plan in
place in cased a risk happened, however as a team our risk management was superb and
prevented any of the listed risks from occurring
...

We are gathered here to accept the final project
...
; the employee must accurately report how much
time they spent on a task each day
...
So, I have no
objections to the final product”
*Even louder banging on the table and cheers, chants of “Hear, Hear” ring around
the room for a few seconds*

20:10
John Hardy: “If I may, I am pleased with the final software and although I did request
some changes and was overruled by the majority stakeholders” * A few laughter’s* “I want
to congratulate Muscab Ali on this exceptionally well-run project”
*Loudest cheers of the night and chants of “Hear, Hear” for a longer period of
seconds” *
20:15
Muscab Ali: “Thank you all for your brilliant support throughout the project and for the
input you put in on making the software the best it can be, we still have a whole phase left
to complete so it’s time to crack on but as long as all the stakeholders are happy with the
software then I am too

---