Requirements Management Plan Report - Business Development

This report details a requirements management plan, including the planning of requirement activities, specifically addressing the 'Acknowledgement of Country' protocol and requirements gathering for translation services. It outlines the importance of stakeholder engagement and the use of the Requirement Traceability Matrix for tracking requirements. The report emphasizes the prioritization process, including the application of the MoSCoW technique for prioritizing requirements in an Agile methodology context. References to relevant resources, such as the Department of Education and Training's protocols and the Agile Business Consortium's MoSCoW prioritization, are also included, providing a comprehensive view of the requirements management process within a business development framework.

PPMP20008
REQUIREMENTS MANAMGEMENT PLAN
OUR LANGUAGE MATTERSREQUIREMENTS
MANAGEMENT PLAN
Version Number: 1.0
Version Date: 24/08/2017
Student names and numbers:
Campus:
Tutorial group:
Tutor:
Natalie Ewin

Requirements Management Plan Template
Our Language Matters
1. Planning the requirement activities
1.1 Traditional Owner/s of the land on which
CQUniversity campuses are located.
Senior supplier who can represent the
Traditional Owner of the Land on which Central
Queensland Campuses are located are the
Aboriginal or Torres Strait Islander people, they
can only be any one who this community itself
and a senior person or a recognized person.
(Department of Education and Techniques,
2007)
1.2 Wording of ‘Acknowledgement of Country’ It is because the Project Executive is not from
the origin of Aboriginal or Torres Strait Islander
descent. So he need to use the wording
‘Acknowledgement of Country’’. The wording
should be ‘I am very much thankful to you and
the almighty for giving us the opportunity to
work in Australia and develop its more, but you
are the original owner of the land and will
continue to be’
1.3 Requirements gathering for translation
services
The method obtained was the most easiest
one, but we should not directly jumps in to it,
rather looking for the option feedback from
many local authorities for assembling more
data for the information. For doing as such, we
have to discover the partners, or individuals like
authorities of Department of Roads and
Transport and MRC, with whom we can
presumably talk about for data gathering, at
that point mean to make a social occasion and
have a dialog to acquire their affirmation. At
that point at last in the wake of dissecting the
result, we can distribute data board for the
Local Greek Community Club.
2. Requirements tracking document To handle such a big and complex process, the
requirements are going to come at every stage,
so these must be documented at some central
location. It can be the ‘Requirement
Traceability matrix’ which can be kept centrally
at some common location
3. Requirement Prioritisation Process The requirements are basically arises at the
workshop process itself among the
stakeholders. So after receiving any such
comment the requirement are again shown to
the stakeholders for its finalisation.
3.1 MoSCoW technique It is technique used to priorities the
requirements. It is also useful for the Agile

methodology of system development, as in
Agile the many stages or steps are required to
be prioritise as per comments received from
the users or consultants. This tool is useful to
prioritise by diving the requirements in four
categories like Must, Should, Could and Won’t
an accordingly the items can be prioritise. (Agile
Business Consortium Limited, 2017)
References:
Australia. Department of Education and Training (2017). Protocols for Welcome to Country and
Acknowledgement of Traditional Ownership. [Online]. Available at:
http://generationone.org.au/uploads/assets/WelcomeToCountry.pdf (Accessed 24 August 2017).
Agile Business Consortium Limited. (2017). MoSCoW Prioritisation. [Online]. Available at:
https://www.agilebusiness.org/content/moscow-prioritisation-0 (Accessed 25 August 2017).
Project Board Role Name, Position, Organisation Signature
Project Executive Board of Members,
Department of Transport and
Roads
Senior Supplier Sponsor, Project
Senior User Senior local official,
Queensland