TRIPLE-R

Organic Waste Management

FIT5057 Project Management S2 2019

Submitted by:
Lakshank Patel (29866855) Neel Shridharani (29882206) Pooja Pancholi (29984939)

Submitted to:

Alind Tiwari
Executive Summary

The report suggests solution of the organic waste by developing an IT system. The idea proposed
consist the combination of hardware software. The system provides Smart Bins for the households
containing sensors to distinguish between the types of waste and alerting to the waste collecting
vendors. The project promotes three R: Reduce, Reuse and Recycle. Reducing the waste
creation, Reusing the waste in different forms and, Recycling where possible. The system also lets
the users hold food donation events in which households or organisations can donate their leftover
food to the poor and reduce the food/organic waste. The project management team has created
schedule baseline for the project in order to complete the project on time. Stakeholder analysis,
Communication plan, Scope management, Schedule baseline, Work breakdown structure,
Network diagram, Cost management plan and Risk management plan are discussed and
developed for a successful project.
 Table of Contents

Executive Summary ..................................................................................................................... 1

1. Introduction .............................................................................................................................. 4
1.1 Introduction ......................................................................................................................... 4
1.2 Purpose of Project .............................................................................................................. 4
1.3 Historical Background ........................................................................................................ 4
2.1 Proof of Concept .................................................................................................................... 5
2.2 STAKEHOLDER ANALYSIS ................................................................................................... 6
2.2.1 Stakeholder Management ................................................................................................ 6
2.2.2 Stakeholder Analysis ....................................................................................................... 7
2.2.3 Communication Plan ....................................................................................................... 9
2.2.4 Summary ........................................................................................................................ 11
2.3 Scope Management Plan ..................................................................................................... 11
2.3.1 Defining scope management......................................................................................... 11
2.3.2 Scope Management Process ......................................................................................... 11
2.3.3 Stakeholder requirements and Impacts ....................................................................... 13
Impacts on different stakeholders ..................................................................................... 13
Functional and non-functional requirements of the system ............................................ 13
2.3.4 The WBS Baseline.......................................................................................................... 14
2.3.5 Work Breakdown Structure........................................................................................ 15
2.4 Schedule Baseline ................................................................................................................ 16
2.4.1 Defining Schedule Management ................................................................................... 16
2.4.2 Gantt Chart ..................................................................................................................... 17
2.4.3 Summary ........................................................................................................................ 19
2.5 Network Diagram .................................................................................................................. 19
2.5.1 Defining Network Diagram ............................................................................................ 19
2.5.2 SDLC activity Network Diagram .................................................................................... 20
2.5.3 Critical Path .................................................................................................................... 21
2.5.5 Summary ........................................................................................................................ 22
2.6 COST MANAGEMENT PLAN ................................................................................................ 22
2.6.1 Introduction .................................................................................................................... 22
2.6.4 Cost tables...................................................................................................................... 22
2.6.3 Summary ........................................................................................................................ 24
2.7 RISK MANAGEMENT ............................................................................................................ 24
 2.7.1 Introduction to risk and risk management ................................................................... 24
2.7.2 Risk register and its importance ................................................................................... 25
2.7.3 Summary ........................................................................................................................ 31
Bibliography ................................................................................................................................. 31
1. Introduction

1.1 Introduction

A Waste Management System offers various solutions for the problems faced due to wastes in
today’s era. Wastes can lead to different pollutions around the globe such as Land Pollution, Air
Pollution, Water Pollution, etc. Avoiding such pollutions and wastes has become vital for the nature
as it is getting worse and leading to global warming. We have, therefore, decided to contribute
towards wellness of the Mother Nature and developed a system for organic waste management.
As there are many types of wastes generated in millions of tons of quantity, i.e. plastic waste,
organic waste, liquid waste, solid rubbish, recyclable rubbish and hazardous waste; we have opted
to focus on organic waste (4waste, 2016). Organic waste is the most lightly taken waste by
humans nowadays as it is not as hazardous as the other forms of wastes (Rinkesh). Hence we
focus on organic waste can be recycled and used.

1.2 Purpose of Project

As the organic waste is the highly produced waste among all the other wastes, it is very important
to manage and dump it properly. Keeping the perspective of managing organic waste in mind, we
have come to a decision to develop a system that will help managing the organic waste in a better
way. The purpose of the project is to introduce a system that contributes to reduction of the
‘organic waste’ being generated. The project shall help in reduce, recycle and reuse of organic
waste and food; in turn helping us reduce the negative impacts of organic waste over the
environment and other stakeholders. The project consists of Smart Bins fitted with different
sensors that detect the type, quality and quantity of garbage which is managed by a smart app
using IoT. The project also requires collaboration with various transportation and waste
management companies.

1.3 Historical Background

With the increasing rise in overall demand and the increasing population, the amount of waste
being generated also keeps increasing. Over the world, 1/3rd of the food produced is wasted or lost
(i.e. 1.3 billion tons), which results in the loss of global economy of $940 billion every year
(OzHarvest, 2019). This results in to one in every 9 people and a total of 793 million people being
left without food and malnourished (OzHarvest, 2019). Organic food waste also contributes to 8%
of greenhouse gases that contribute to global warming (OzHarvest, 2019). In Australia, the
estimated number of food being wasted is 5 million tonnes which costs over $20 billion per year
(OzHarvest, 2019). Over 35% of waste produced by the household is food waste (organic)
(OzHarvest, 2019). That said nearly 4 million people suffer from food insecurities, quarter of which
are children; of these only 710,000 rely on food relief each month (OzHarvest, 2019). That is why it
is necessary that we reduce, recycle and reuse all the organic wastes produced. It is evident that
organic waste is paid no heed as compared to other forms of waste. It is one of the highest
generated wastes in Australia (OzHarvest, 2019).
 Figure 1: Comparison of Waste Disposed, Recycled and Reused (Pickin & Randell, 2017)

As the above facts suggests, organic waste has to be managed and recycled in huge amounts.
Therefore, we have planned to develop an organic waste management system that will encourage
reducing the amount of organic waste that we create in our day to day lives, encourage to recycle
and reuse the products. The system will semantically allow the users to create an event to donate
food in order to reuse and reduce the organic waste production.

2.1 Proof of Concept

Steps of proof of Concept:

Waste Management Issue and Importance

We plan to manage Organic Waste. Organic waste is biodegradable. Items like food, wood,
garden waste, liquid waste, dairy products, etc. all fall under organic waste. It can be used to
produce compost and generate energy due to the methane gas it releases. That being said the
methane gas it releases is 25 times more dangerous to both environment and people around it
than the greenhouse gases due to anaerobic decomposition. Also increasing number of landfill
and its facilities always leave a bad odour around it. There are multiple ways that organic waste
depending on its type can be recycled or reused, but it is better to reduce creating such kind of
waste (Victoria, 2016).

System Outline

The main idea behind the system is, reducing the amount of organic waste created and managing
the waste that exists. The system will promote is users to create less organic waste by
encouraging them to waste less food, use recyclable materials by telling the benefits and problems
regarding it. Providing smart bins fitted with special sensors to detect when organic waste is ready
to be collected. The bin shall provide the information to the stakeholder for the bins to be collected.
The smart bin also helps separate the organic and inorganic waste with the help of infrared
sensors. The waste is than collected by special truck which is taking to bio gas plants where it
used to produce energy with the help of methane gas released from it in a controlled manner.
Usefulness of the system to the stakeholders

Reducing the amount of waste created will result to saving of stakeholder’s resources and thus his
money. Storing such waste separately to be collected helps the stakeholder dispose of such waste
without the inherent risks from staying around it like methane gas (If the stakeholder is trying to
decompose and compost it at home) and the bad odour. It also helps the surrounding environment
thus helping the stakeholder contribute to slow the already increasing problem that is global
warming.

Software development lifecycle

We will use Iterative Development for the Mobile App to develop. The team has chosen Iterative
development model because the Iterative SDLC model does not attempt to start with a full
specification of requirements. Instead, development begins by specifying and implementing just
part of the software, which is then reviewed to identify further requirements. This process is then
repeated, producing a new version of the software at the end of each iteration of the model. Each
subsequent release of the module adds function to the previous release. The process continues till
the complete system is ready as per the requirement. It makes the process easier as more than
one iterations of the process can be in progress at the same time. This model focuses on rigorous
validation of requirements, and verification & testing of each version of the software against those
requirements within each cycle of the model.
System development by SDLC

Following are the phases of Iterative Development Life Cycle:

o Requirements gathering (Gather requirements from the stakeholders)

o Planning (Making an outline of the project to be developed)
o Analysis and Design (Analysing different stakeholders their requirements, designing and
establishing any technical requirements)
o Implementation (Implementing and coding the Mobile App)
o Testing (Testing the developed Mobile App for errors and bugs)
o Evaluation (Through evaluation of the project if requirements are met or changes are
require)

Waste Issue Management

o The Smart Bins collect the data with the help of infrared sensors about the waste.
o This data is managed by a smart mobile app.
o It indicates if wrong waste has been added or the bean is required to be collected.
o Special trucks collect the organic waste and take it to a place to be disposed in a closed
and safe environment.
o Special ads and videos regarding the reduction, reuse and recycle of organic waste along
with their benefits to promote its importance to the stakeholders.

2.2 STAKEHOLDER ANALYSIS

2.2.1 Stakeholder Management

There are four processes in Project Stakeholder Management. They are as follows:

 Stakeholder Identification
 Analyze stakeholder expectations and their impact on the project success.
 Engage stakeholders in project decision and execution.
 Develop strategies to manage stakeholder engagement.
Defining Stakeholders

There are various definitions to define the term Stakeholders. According to the paper (Freeman,
1983)stakeholders represents the groups or individuals without whose support the organization
would cease to exist” (Freeman, 1983). The author (Thompson, Wartick, & Smith, 1991) defines
stakeholders as groups in relationship with an organization.

Importance

We can only call a project successful only if we achieve it’s targets and meet the stakeholder
analysis’ requirements as they are effectively associated with the tasks in the project. One of the
important reason to have the involvement of stakeholders in the project because their contribution
will expedite more thoughts and bring different ideas and plans to the table. The importance of the
stakeholder has always been undermined, which leads to most of the fall-outs between the
organization, and the failure of a project. As per Payne & Watt (2018), if a stakeholder is not happy
with the project, then nobody is happy with the project. The success of a project is in the hands of
the stakeholders. Also, their participation will also help project team to gain support from
stakeholders by making them an important part of planning and execution process. This will also
help to strengthen the position of project team which will definitely increase the chances of project
success. Thus, managing the interests of the stakeholders is a necessity for a successful project.

2.2.2 Stakeholder Analysis

The stakeholder analysis table shown below represents all the stakeholders that has impacted or
contributed in the project. We have identified the following stakeholders for the project:

o Board of Directors
o Government and regulators
o Suppliers
o Waste Management Organizations
o Transport provider
o Consumers
o Technical support provider

Stakeholder Analysis Table

Assumption:

 In Table 1, Person name, details and contacts have been assumed.

 The scenario in the Table 1 is formed based on above assumption and the given
strategies.
Table 1: Stakeholder Analysis table
Stakeholder Matrix

Figure 2: Stakeholder Matrix

The figure 2 shows the Stakeholder Matrix for organic waste management. The matrix shows
Importance -> Influence comparison between different stakeholders.

2.2.3 Communication Plan

Defining Communication Plan

Successful projects run on effective communication. A project communication plan is a tool that
enables one particular individual or stakeholder to communicate effectively on a project with the
client, team and other stakeholders within the project (teamgnatt, 2018). It formally defines who
should be given specific information, when that information should be delivered and what
communication channels will be used to deliver the information (Rouse, 2015).

Stakeholder Communication Plan

The table 2 the communications plan between different stakeholders. It describe what, when, why
and how the stakeholders will communicate with each other.
 Table 2: Communication plan for Stakeholders

Project Team Communication Plan

Table 3: Communication plan for Team

2.2.4 Summary

In the project, the Stakeholders were identified based on the system design and on priority using
the matrix. Each stakeholder’s roles and impacts on the project were given along with how they
can contribute to this project and how they can influence the project which could also lead to the
cancellation of the project.

Later in the report the communication plan was developed which includes details about when a
particular stakeholder will be contacted and for what purpose and by what medium. The time
periods are clearly mentioned which can ensure that all the plans are executed successfully. There
are also a few meetings with the Government and regulators so that they can also ensure that the
project is effective and is coherent.

2.3 Scope Management Plan

2.3.1 Defining scope management

The Project Scope Management is the process to ensure that a particular project includes all the
work relevant/appropriate to achieve the project's objectives. Its primary aim is to control what is
and is not involved in the project. The Scope Management techniques enable project managers
and supervisors to allocate just the right amount of work necessary to complete a project (Invensis,
2018).

2.3.2 Scope Management Process

Figure 2: Scope Management Process

Six main processes that are listed under the Project Scope Management are as follows:

1. Plan scope management: The scope management plan describes the project scope and
documents how it will be further defined, validated, and controlled throughout the lifecycle
of the project.

2. Collect requirements: It is the process of defining and documenting stakeholders needs

to meet the project activities. The document for collecting requirements is developed in the
project planning phase.

3. Define scope: This is the process of developing a detailed description of the Project and
product. So, while collecting requirement list, all the different requirements of the Project
and the resulting product or service are defined.

4. Create Work Breakdown Structure: Creating work breakdown structure is done using a
technique called decomposition/breakdown. It is the process of subdividing project
deliverables and project work into smaller and more manageable components for achieving
a better outcome.

5. Validate scope: A part of project monitoring and control process group in which the
process includes reviewing deliverables with the customer or sponsor to ensure that they
are completed satisfactorily and obtaining formal acceptance of deliverables by the
customer or sponsor.

6. Control scope: Control Scope is the last process group in the project scope management.
It is again a part of project monitoring and control process group. Control scope is the
process of monitoring the status of the project and product scope and managing changes
to the scope baseline.

Importance of Scope Management to Project Managers

 Communication is considered as the primary tool to adequately define the importance of

scope management, to both the stakeholders and team members. This process takes
place to ensure and agree as to how the project goals will be met.
 The important features of scope management are that it helps in avoiding the challenges
that a project might face when provided with increasing scope and never-ending
requirement list. As the project is executed, the project scope filters out the essential and
feasible aspects of the project and controls all the aspects mentioned in the project scope.
Additionally, the scope management establishes control mechanism to address factors that
may result in changes during the project lifecycle.
 It is highly impossible to estimate the time and cost required for the project without
adequately defining the project scope. Due to lack of communication, the project scope can
change drastically, which will, in turn, affect the cost and causes variations in the schedule
of the project, causing losses.

The implementation of scope management in a project is considered essential and is never a

difficult task; however, it requires effort, time, and patience. Only with the help of scope
management, a project manager can define, control and ensure that the project deliverables are
met, without any issues/risk occurring during the project lifecycle and that the stakeholders are
satisfied with the investments that they have made.
2.3.3 Stakeholder requirements and Impacts

Impacts on different stakeholders

Impact on government

The waste of a staggering 1.3 billion tonnes of food per year is not only causing major economic losses but
also wreaking significant harm on the natural resources that humanity relies upon to feed itself.

Impact on nature

Impacts on Natural Resources is the first study to analyse the impacts of global food wastage from an
environmental perspective, looking specifically at its consequences for the climate, water and land use, and
biodiversity. Fifty-four percent of the world’s food wastage occurs “upstream” during production, post-harvest
handling and storage, according to FAO’s study. Forty-six percent of it happens “downstream,” at the
processing, distribution and consumption stages. As a general trend, developing countries suffer more food
losses during agricultural production, while food waste at the retail and consumer level tends to be higher in
middle- and high-income regions – where it accounts for 31-39 percent of total wastage – than in low-income
regions (4-16 percent). The later a food product is lost along the chain, the greater the environmental
consequences, FAO’s report notes, since the environmental costs incurred during processing, transport,
storage and cooking must be added to the initial production costs.

Causes

A combination of consumer behaviour and lack of communication in the supply chain underlies the higher
levels of food waste in affluent societies, according to FAO. Consumers fail to plan their shopping, over
purchase, or over-react to “best-before-dates,” while quality and aesthetic standards lead retailers to reject
large amounts of perfectly edible food.

Solution
As above, we can see that organic waste contributes as a major factor of the overall wastes produced by us
humans. To tackle it the following could be done:

 Reducing food wastage: Promoting the importance of reducing waste through audio and video in
system, its benefits and problems.
 Re-use- finding secondary markets or donating extra food: the system shall provide the user a
chance to donate extra food, which when mentioned in the system can be collected by special
transports assigned.
 Recycling and recovery: Special smart bins for organic waste in users’ home, which can be collected
for recycling later by special trucks.

Functional and non-functional requirements of the system

Functional Requirements
 Feature to detect bins garbage via sensors : Priority - High
 Feature to register a donation event : Priority - Medium
 Feature to donate to an event : Priority - Medium
 Feature that manages garbage collection timetable : Priority - High
 Smart bins : Priority – High
 Feature to display promotional videos : Priority – Low

Non-Functional Requirements
 24 X 7 Support : Priority - Medium
 Feature to support Advertisements (to generate finance) : Priority - Low
2.3.4 The WBS Baseline

According to (Tausworthe, R. C. (1979)), Work Breakdown Structure (WBS) is referred as a

vehicle for breaking a project down into parts i.e. sub-projects, tasks into sub-tasks and work
packages. It is arbiter as a planning tool which connects the resource and activities with its
resources in a logical framework. The WBS structure designed for our system follows chosen
software development lifecycle i.e. agile method including all the project management deliverables.
Top-down approach is undertaken to build the work breakdown structure in which building starts
from large items and are broken down into small items. Structure followed in work breakdown
structure is explained below:

1. Project Management: This stage includes project initiation tasks and development of
stakeholder analysis, scope management plan, schedule baseline, network diagram, cost
management and risk management plan.

2. Requirement Gathering: As explained before, different requirements were gathered by

above mentioned methods.

3. Procurement: This phase is concentrated on selection of vendor for software

development. It includes the process necessary to acquire products, services and results
from different team and documenting procurement decisions. There are five phases in the
vendor selection process are as follows(The 5 Phases of the Vendor Selection Process,
2018):
 Pre- Solicitation Planning: In this phase, RFP – Request for Proposal is drafted.
 Vendor Selection: Once the responses of RFP are in hand, various evaluation
processes are conducted for selecting a vendor.
 Award Contract: In this phase, the vendor is awarded the contract and clear
expectations are set in the conferences with stakeholders.
 Contract Management: The statement of work is created before the vendor starts
the work. This allows better monitoring on vendor which will verify the status of the
project.

4. Agile Design and Development: This is the development phase reflecting the software
development lifecycle approach followed for this project i.e. agile approach. Agile Method is
said to be the incremental, iterative sequencing of work that are known as “Sprints”. A
sprint is cycle of requirement design and analysis, development, testing and integration.

5. Data Migration: Large organisations do have humongous data. In this stage data is
migrated from cloud and database servers.

6. Testing: This is the imperative process; the development phase is incomplete without
testing of the project. It has got three stages of testing, namely;
 System Integration Testing
 Performance Testing
 User acceptance testing

7. Deployment: This is the final stage including hardware deployment of recharge machines
on trams and buses and software deployment of developed features along with the mobile
and website application.

8. Closing: In this phase the service is closed, the due payments are cleared and lastly, sign-
off from the departments.
2.3.5 Work Breakdown Structure

Figure 3: Work Breakdown Structure

2.3.6 Summary

We have developed a Work Breakdown Structure for the project in order to divide the work
between the project development team for the effective implementation and execution of the task
on time. The work is divided in a way that the tasks can be performed successfully for the better
implementation of the project. We have breakdown the Agile process into different sprints in order
to divide the systems into parts and develop easily.
2.4 Schedule Baseline

Assumptions
 Agile development approach is undertaken and reflected in schedule baseline.
 Resources are assigned using resource designations.
 Tutor is referred as expert.

Constraints
 Milestones are not assigned predecessors as MS Project always changed milestone to
task if a predecessor is added.

2.4.1 Defining Schedule Management

A schedule baseline is original approved project schedule before the project starts. It is the project
schedule that should be followed throughout the process of project implementation and compare it
against the actual project schedule (Baskerville, 2015).
Importance
The project schedule baseline generally includes the project deliverables timeline and estimated
completion timeline of the project (Baskerville, 2015). It is very important to create an accurate
schedule baseline as possible in order to make the project execution successful. Once the
schedule baseline is created, all the stakeholders must agree to the timeline in order to avoid any
future delays about the project development. The schedule baseline can be referred at any point in
the time of developing the project.
Approach
Scheduling involves four main processes: defining activities, sequencing of activities, estimating duration for
all activities and assigning resources to them. According to (PMBOK Guide, 2017), work breakdown
structure (WBS) provides framework for the schedule management plan and it has been used to develop
schedule baseline for Improvised the project. GANTT chart scheduling tool, provided in MS project software,
has been used for this purpose. Following approach is undertaken for developing schedule plan:

 Define activities

Lowest level of work in WBS are the work packages required to be completed to deliver product.
These work packages constitute the list of activities in the schedule baseline (Jeffrey L. Brewer,
2018). Decomposition tool mentioned in (PMBOK Guide, 2017) was used by the team to define all
the activities from WBS and a list of milestones was created.

 Sequence activities
This process includes identification of logical relationships between activities and marking
predecessors for all activities (PMBOK Guide, 2017). GANTT chart option to provide predecessor of
the activity was used to allocate different dependencies between all the activities. Finish to start
dependency relationship is used for the project which means that Task “P” is predecessor and Task
“S” is successor. Task “S” can be started only when Task “P” is finished. Sequencing the activities
generate the order of execution of all activities.

S
Figure 4: Finish to Start
  Estimating duration

Estimation of working days required for the activity to be completed is the third important component
of schedule baseline. It depends upon the experience of resources and complexity of task. In real
world, duration estimation and resource allocation are done at the same time (Jeffrey L. Brewer,
2018). Our team discussed with each other to estimate working days and improved the estimation
on basis of feedback received from expert.

 Assigning resources

It is the process of allocating activities to the available resources. Our team assigned resources
using their designation. They are available on the GANTT chart for better presentation.

2.4.2 Gantt Chart

Following are the screen shots for our Gant Chart:

2.4.3 Summary

Creating a schedule baseline for the project is very important in order to make the project
successful and complete on the estimated time. At the beginning of the project, it is always running
according to the baseline, but as the project moves and circumstances change, the schedule
baseline gets differed and the project deliverables timeline gets affected. Sometimes, the project
can be running very well compared to the schedule baseline and can be completed before the
estimated timeline.

2.5 Network Diagram

2.5.1 Defining Network Diagram

A visual representation of all tasks, workflow and responsibilities of a project is called Network
Diagram (Wrike, What is Network Diagram in Project Management?, 2019). It is used to map the
work sequence and schedule of the project.

Importance

The Network Diagram helps to justify the time estimation of the project. It also helps in planning,
organizing and controlling the project. The network diagram helps to monitor the project progress
in order to make the project run smoothly (Chapman, 2019). It helps to identify opportunities to
compress the schedule. Sometimes in the project, you may need to shorten the duration of the
project which is helped performing by the Network Diagram.
2.5.2 SDLC activity Network Diagram

Figure 5: Network Diagram

2.5.3 Critical Path

Network diagram with critical path highlighted by red arrows is shown below:

Figure 6: Network Diagram with Critical Path shown as red arrows

2.5.5 Summary

We have developed the above Network Diagram in order to get the proper visualisation of the
planning of the project. The network diagram provides a quick glance view of the project. I also
demonstrate the summary of task allocated between the development team. The network diagram
developed here will help the project team to keep the schedule baseline being followed and keep
the track of the tasks being executed.

2.6 COST MANAGEMENT PLAN

2.6.1 Introduction

The process of allocating, estimating and controlling cost in a project is called Cost Management.
It is one of the Triple Constraints of a project’s success. It allows the project team to estimate and
predict the overall cost of the project and prevent it to go over budget. (Wrike, What is Cost
Management in Project Management?, 2019) Cost Management is done during the planning
phase of the project and approved before the project starts. Once the project is completed, the
predicted and actual costs of the project are compared and used as a reference for future projects.
Importance
Every project starts with a budget assigned to it. The project’s success is defined on how well the
cost management has done and achieved throughout the project execution (Ganesan, 2018). Cost
management provides the team member a clear outline of the budget that is assigned to a
particular task which helps them to execute the plan in a cost-effective way. It also keeps the
project team aware of any over budget going project phase which need attention to be redefined.
Cost management plays a very important role in a project’s success.

2.6.3 Costing Method and its reasons

The cost estimation tools given in (PMBOK, 2017) are master judgment, practically equivalent to
assessing, parametric evaluating, base up assessing and three-point evaluating. Our group
adopted the bottom-up evaluating strategy for assessing the cost of the improvised project. Cost is
assessed for most minimal degree of work packages and later, moved up or outlined to get the
overall cost estimation for the entire project. Function point analysis is utilized to estimate the cost
of software development by assessing its size. Function points depend on the arrangement of
necessities. It is utilized to express the estimation of usefulness of the framework to be developed.
These functionalities are the necessities of the client and identifies with the outer view for example
information or report (Brewer & Dittman, 2018). This strategy is subject to set of prerequisites and
is as exact as the necessities. It likewise has a standard which is upheld by International Function
Point User Group (IFPUG) (Jeffrey L. Brewer, 2018). Thinking about these reasons, function point
estimation technique was selected to calculate the cost estimation of the ongoing project.

2.6.4 Cost tables

The following cost table provides an outline of the project’s overall budget and expenses including
the cost of resources.
Table 4: Cost Estimate Table
Cost baseline table:

Table 5: Cost Baseline Table

2.6.3 Summary

Being one of the triple constraints, the cost management plays a very imports role in a
project’s successful execution. If the cost management is done well during the project and
followed throughout the execution of the project, the project goals of profit are said to be
achieved successfully. Having budget of $500,000, we have divided the budget into the best
possible way that the project becomes successful and achieves all its goals.

2.7 RISK MANAGEMENT

2.7.1 Introduction to risk and risk management

Risk is a questionable occasion or condition that, on the off chance that it happens, has a
positive or negative impact on one or more project requirements and objectives. By and
large undertaking risks can either be constructive or destructive for the project. As indicated
by PMBOK Guide 2017, “Project Risk Management includes the processes of conducting
risk management planning, identification, analysis, response planning, response
implementation and monitoring risk on a project”. Risk Management is the phenomenon of
distinguishing potential issues and treating them before they occur. Project risk management
involves the processes of undergoing risk management coming up with identification,
analysis, response implementation and risk monitoring. Risk management is directly
proportional to the success of the project.
Importance

Handling risks in the entire project intends to provide minimum exposure to the risk within a
calculative range by minimizing the negative effects of the risk, promoting awareness
towards positive aspects and increasing the success rate of the project. Risks ought to be
known as a result of it's method to predict the uncertainties in the project and minimize its
impact. Risk identification is meant to be conducted throughout the project life cycle, most
significantly throughout the key milestones of the project.

Approach to manage risks

Following are the steps to manage risk in a project:

 Identify the risk: The task group reveals, perceives and portrays the risks that may
influence the project or its results. A risk register is started to be set up in this stage.
 Analyse the risk: When the risks are distinguished, the project management team
decides the probability and result of each risk. The team at that point builds up a
comprehension of the idea of the risk and its capability to influence the undertaking
objectives and outcomes of the project.
 Evaluate or rank the risk: The risk is assessed by deciding the risk intensity, which
is the mix of probability and result. The team comes up with a decision whether the
risk is acceptable or whether it is not important enough to require attention and
necessary changes.
 Treating the risk: Here, the most noteworthy positioned risks are gotten to, and an
arrangement is embarked to treat or mitigate these risks to accomplish adequately
accepted risk levels. The production of risk mitigation techniques, preventive plans,
and alternate courses of action happen in this progression.
 Monitor and review the risks: Here, the risk register of the project is utilized to
carefully monitor, track and audit the risks involved in the project.

2.7.2 Risk register and its importance

A risk register is a living record that is re-equipped consistently for the duration of the
existence cycle of the project. It turns into an essential part of the project and is incorporated
into the authentic records that are utilized for future undertakings. The risk register
incorporates a rundown of risks, rundown of potential reactions, underlying drivers of risks
and overhauled risk classifications.

A Risk register is a significant report since it tracks every one of the risks and issues
distinguished in a project and tracks it. Risk Register is a streamlined report which is made
during the beginning periods of the project management, records all risks that are normal
and recently rising. It acts as a storage for all dangers and incorporates extra data about the
risks. As an apparatus, the risk register assumes a significant job in the risk management
plan by helping the project management team to monitor and denote risks since it's a live
archive.

Risks are distinguished from wide significant classifications, for example, innovation
changes, project groups, vendors and so forth (Jeffrey L. Brewer, 2018). Meetings to
generate new ideas were directed, and the referenced classes were utilized to recognize
chances to be specific; vendor bankruptcy, innovation chance, key partners leaving the
project (Jeffrey L. Brewer, 2018). Dangers recognized for Improvised task are referenced in
table. Table is the legend utilizing shading coding to show the seriousness and probability of
the dangers.
Risk Score = Likelihood * Impact on the Project

Table 6: Colour Matrix

Table 7: Risk register
2.7.3 Summary

Improvised project is a simple IT project and require investment of $5,00,000. Failure of

project will impact the state with huge monetary loss and will result in bad reputation of the
state government. In such scenario, it becomes essential to identify risks for the project and
perform stringent monitoring and controlling processes. It is imperative to correctly identify
risks related to the project and perform appropriate corrective measures, if any risk occurs,
to mitigate its effect on the project’s success.

Overall Summary
Concluding the project with outcomes of the project management tasks that we have
performed and learned about. Project management is a continuous project with number of
tasks to be performed simultaneously. The triple constraints: Time, Cost and Scope has
been the most vital part of the project. All the tasks that are assigned and provided within the
scope has been time and cost effective. Given budget of $500,000, we have allocated all the
resources very cost effectively which is the best for the project. As the above facts suggests,
organic waste has to managed and recycled in huge amounts. Therefore, we have planned
to develop an organic waste management system that will encourage to Reduce the amount
of organic waste that we create in our day to day lives, encourage to Recycle the products,
and encourage to Reuse them. The system will semantically allow the users to create an
event to donate food in order to Reuse and Reduce the organic waste production.
Implementing and applying all the important phases of the project management, we have
achieved all goals of the project plan.

Bibliography
4waste. (2016, December 20). There are 5 types of waste, do you know them all? - 4 Waste
Removals. Retrieved October 26, 2019, from 4 Waste Removals:
https://4waste.com.au/rubbish-removal/5-types-waste-know/
Baskerville, P. (2015, July). Schedule Baseline - Skillmaker. Retrieved October 27, 2019,
from skillmaker: https://www.skillmaker.edu.au/schedule-baseline/
(2018). In J. L. Brewer, & K. C. Dittman, Project Time Management (pp. 131-143). Purdue
University Press.
Chapman, T. (2019). 6 Benifits of Network Diagrams. Retrieved October 27, 2019, from
Master of Project Academy: https://blog.masterofproject.com/network-diagrams/
Freeman, R. E. (1983). Stockholders and Stakeholders: A New Perspective on Corporate
Governance. California Management Review, pp. 88-106.
Ganesan, Y. (2018, January 25). Project Cost: Why is it important for Project Managers?
Retrieved October 27, 2019, from greycampus:
https://www.greycampus.com/blog/project-management/project-cost-why-is-it-
important-for-project-managers
Invensis. (2018, 07 10). What is Project Scope Management? Retrieved from Invensis
Learning: https://www.invensislearning.com/resources/pmp/what-is-project-scope-
management
(2018). In a. K. Jeffrey L. Brewer, Project Time Management (pp. 131-143). Purdue
University Press .
OzHarvest. (2019). Food Wase Facts. Retrieved October 26, 2019, from OzHarvest:
https://www.ozharvest.org/what-we-do/environment-facts/
Pickin, D. J., & Randell, P. (2017). Australian National Waste Report 2016. Melbourne: Blue
Environment Pty Ltd.
PMBOK. (2017). A Guide to the Project Management Body of Knowledge ( PMBOK® Guide
)—Sixth Edition. Project Management Instuite.
Rinkesh. (n.d.). What is Waste Management and Methods of Waste Disposal? - Conserve
Energy Future. Retrieved October 27, 2019, from Converse Energy Future:
https://www.conserve-energy-future.com/waste-management-and-waste-disposal-
methods.php
Rouse, M. (2015, May). What is communication plan? Definition from WhaIs.com. Retrieved
October 26, 2019, from WhatIs:
https://whatis.techtarget.com/definition/communication-plan
teamgnatt. (2018, june 26). How to Create a Project Management Communication Plan |
TeamGantt. Retrieved October 26, 2019, from teamgantt:
https://www.teamgantt.com/blog/project-management-communication-plan
Thompson, J. K., Wartick, S. L., & Smith, H. L. (1991). Integrating corporate social
performance and stakeholder management: Implications for a research agenda in
small business. Research in Corporate Social Performance and Policy, 207-230.
Victoria, E. (2016, june 16). Environment Victoria | Organic waste, green waste. Find out
what you can do. Retrieved October 26, 2019, from Environment Victoria:
https://environmentvictoria.org.au/resource/organic-waste/
Wrike. (2019). What is Cost Management in Project Management? Retrieved October 27,
2019, from wrike: https://www.wrike.com/project-management-guide/faq/what-is-
cost-management-in-project-management/
Wrike. (2019). What is Network Diagram in Project Management? Retrieved October 27,
2019, from wrike: https://www.wrike.com/project-management-guide/faq/what-is-a-
network-diagram-in-project-management/
Appendix
Agendas
Minutes of Meetings
Timesheets