Question:
Indicate whether it would be appropriate for a Senior Supplier to represent the Traditional Owners of land where Central Queensland Campuses are situated.
Give an explanation of your answer.
The Project Executive should choose which of the two opening statements is most appropriate.
Please provide a script with the right wording and an explanation.
This is a good way to gather requirements.
What document is used to track project requirements during the project’s life cycle?
Answer:
Template for Requirements Management Plans
Language is important
Plan the Requirement Activities
Determining the roles of each member of your team:
* The Owner
* Project Manager
* Developer
* Quality assurance analyst
* Trainer
* Database analyst
* End user
* The Stakeholders
Identify the roles and responsibilities for the documents.
Identifying and describing stakeholder.
Strategy for work division definition.
Coordination of the information flow among team members.
Knowledge transfer: Encoded, Embodied, Encultured and Embedded knowledge are the knowledge that should to be transferred (Taskin & Verville, 2013).
1.1 Traditional Owner/S of the Land Where CQUniversity Campuses are Located.
The prince 2 method requires that the project be divided into three roles: Senior user, Executive and Senior supplier.
It is not appropriate for the board or any other supplier to be a single supplier in this situation.
The project board has three roles. First, it uses stage tolerances; secondly, it decides at each stage if the project should continue; and thirdly, it monitors the reports that are provided by the manager (Kortrouba, Alexaki, 2016).
1.2 Wording of ‘Acknowledgement of Country’
The project executive will need to acknowledge the country. An aboriginal person can’t perform a welcome to country.
It may offend the directors or embarrass them to welcome country when the project executive is not part of the traditional owners group (Kowal 2015).
Translation Services: 1.3 Requirements
This is not the right approach for this project.
One change is all that’s needed to gather requirements for translation services (Kaur and Sengupta 2013, 2013).
The following is the recommended list for this case study.
* A high-level description of the project.
* Focusing on specific types of work such as localization, translations, copy edits, revision, updates, proofreading, terminology research.
* Ideal: An editable source file
* The location where the translation will actually be read.
* Information about the target audience
* Please contact us for special requests
* Deadlines for documents
* A person who will provide feedback on the final translation.
Requirements Tracking document
These documents will be used throughout the project’s lifecycle to keep track of requirements.
ConOps (Concept Of Operation): This will describe the characteristics and operation of the system as perceived by the user.
SRD System Requirements Document – A formal statement of the system’s requirements. The following information can be included:
RTM (Requirement Traceability Matrix): A table that links the origin requirements to the traceability of them through the project’s life cycle.
TMP (Test Master Plan), The documents that have the scope methodology, content management, responsibilities, and sequence of test activities (Macaulay 2012).
Requirement Prioritization Process
In software product management, requirements prioritization is used to determine which requirements should be included in a particular release.
This process prioritizes requirements to reduce risk and minimize risk.
This is to ensure that you take care of the highest risk.
This communication is essential because the success or failure of an initiative will depend on the influence and power that stakeholders have (Robertson & Robertson 2012).
The power can be used to support or constrain the initiative.
MoSCoW, a prioritizing method, is used in project management, management, and software development. It is based upon the importance that stakeholders place on the delivery to all requirements.
You may also call it MoSCoW analysis, or MoSCoW priorityitization.
Comprehensive framework for the life cycle of knowledge management systems.
African Journal of Business Management 7(15), 1285.
Project-Based Learning in a Conservative Educational System: Small Steps, Great Leaps
The views of Greek students.
EJSER European Journal of Social Sciences Education and Research Articles. 7.
Welcome to country: Acknowledgement and belonging, white anti-racism and acceptance.
Analysis of the failure of software development projects using software process models.
Springer Science & Business Media.
Understanding the requirements process: How to get requirements right.