Task 1 - Project Integration Management: Instructions To Learners

Task 1 – Project Integration Management
Instructions to Learners:
 This summative assessment can be completed in class or at any other convenient

location.
 Students are required to complete this task using digital tools and ensure to submit in
an acceptable format, e.g. .docx, .pdf, .pptx, or as advised by your assessor.
 Please use the following formatting guidelines to complete this assessment task:
 Font Size: 12; Line Spacing: Double; Font Style: Times New Roman
 Assessment activities can be completed either in real workplace environment or in a
simulated environment such as your classroom. In both cases, appropriate evidence of
the assessment activities must be provided.
Instruction to Assessors:
 You must assess student’s assessment according to the provided Marking Criteria.
 You must complete and record any evidence related to assessment activities including
role-plays and presentations using appropriate forms which must be attached with
student assessment submission.
 You must provide students with detailed feedback within 10 working days from
submission.
This assessment task requires you to:
 work closely with others to integrate all project management functions across a
project life cycle according to organisational objectives
 negotiate with internal and external stakeholders
 create accurate project management documentation
 make suggestions for improvements to managing project integration in the future.
Assuming your Organisation was awarded the following tender:
ATM ID: NAA RFT 20xx/1058

Agency: National Archives of Australia
Category: 81110000 - Computer services
Close Date & Time: 15-Aug-20xx 2:00 pm (ACT Local Time)
BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF
INTERNATIONAL BUSINESS \UNITS OF COMPETENCY\BSBPMG521: Manage Project Integration\
Revision: 1.0 Revision Date: 22 May 2020 Next Review: 27 May 2021 Approved by:
Nerida McDowall
Publish Date: 15-Jul-20xx
Location: ACT Canberra
ATM Type: Request for Tender
APP Reference: NAA20XX-1
Multi Agency Access: No
Panel Arrangement: No
Description:
A service provider is being sought for the technical upgrade of the Archives’ website
Destination: Australia. In order to ensure the best value for money and optimal
functionality (for the website and related exhibition interactive) going forward, it is
necessary for the website to be transferred from a proprietary CMS to a commonly
available CMS (including, but not limited to, an Open Source CMS).
The website will enable the National Archives of Australia to collect user contributed data
about the photographic collection featured on the site. The interface must be modern,
engaging and user-friendly, designed to meet the needs of people of all ages, and differing
levels of computer and English literacy. The website must interact successfully with an
exhibition interactive via an existing API. There is an option for hosting, maintenance and
support services to be provided from contract execution until 31 December 2019.
Timeframe for Delivery: November/December 20XX with a possible extension of up to 3

years for hosting and maintenance.
The Requirement
The National Archives of Australia (Archives) (the Customer) is responsible under the
Archives Act 1983 (Cth) for the preservation and storage of Commonwealth records,
including the archival resources of the Commonwealth.
This procurement request relates to the website redevelopment and hosting and
maintenance services for website Destination: Australia. The current website is located at
https://www.destinationaustralia.gov.au
The photographs showcased on this website are part of the Immigration Photographic
Archive (Series A12111). This collection comprises more than 22,000 black-and-white and
colour photographs taken by government photographers between 1946 and 1999 to record
the arrival and settlement of migrants in Australia after World War II. The photographs

Nerida McDowall
were used in newspapers, magazines, posters, brochures and displays to promote Australia
as a prosperous welcoming nation to potential migrants and to reassure the Australian
public that new migrants would readily settle into the Australian way of life.
In 2014, Destination: Australia was upgraded to encourage users to upload their own
photographs and stories to share their migrant experience, further adding rich personal
context to the Archives’ collection. These ‘Feature Stories’ are also available (via an API) in
a ‘Globe’ interactive in the Archives’ exhibition A Ticket to Paradise?, which is touring
nationally from April 2016 to September 2019.
Required
 Redevelopment of existing website Destination: Australia
 Software to be either open source or common-use proprietary Content
Management System (CMS)
 One website prototype round, with testing and feedback
 Website testing including content review
 Final revisions
 Final testing and bug fixes
 Website handover
 Final documentation including website style guides, master templates, admin user
guidelines, technical specifications. This must be written in English with clear
instructions for non-technical experts to operate the CMS.
Optional
 External hosting and ongoing support with a service level agreement (3 years).
 Updates and post implementation changes in response to user feedback
Required deliverables
API compatibility
 The website must continue to work with the pre-existing API linking the content
with an exhibition interactive
 The administrator account to the Destination: Australia CMS must have a check box
function that allows the administrator to select which feature stories will be
published through the API to the exhibition interactive.
 The API must be able to draw all user-added content in the selected feature stories,
including photographs, through to the linked exhibition interactive.

Nerida McDowall
 The website will support sourcing and storing its data from the Archives’ API,
according to API calls provided by the Archives, to ensure valid, up to date data is
displayed on the website.
 The website must successfully GET, POST and PUT and DELETE data using the API
within agreed timeframes.
 Data from the API contains a mix of official records and user generated content
 API compatibility and function must be maintained at all times until December 2019
 The successful supplier will be provided with further documentation on the API.
Accessibility/compatibility
 All elements of the solution must comply with the relevant Australian Government
mandatory criteria including meeting Web Content Accessibility Guidelines (WCAG)
2.0 – to Level AA. Refer to the Australian Government Digital Transformation Office
website for more information – https://www.dto.gov.au/standard/design-guides/
 Any online forms should include identifying mandatory fields, error validation and
error suggestion on input fields (e.g. include @ for email addresses), as per the
WCAG 2.0 Level AA.
 All elements of the solution must display consistently across popular Windows,
Macintosh and Linux browsers including Internet Explorer (V9 up), Firefox, Chrome,
Safari and Opera.
 Code to ensure ease of use and accessibility from desktop, tablet and smart phone
/ mobile platforms using responsive interface design.
Privacy, security and intellectual property

 Data captured in online forms should reflect the Australian Privacy Principles (which
unify the National Privacy Principals and the Information Privacy Principles) and
security obligations of (ASD). Including any updates to how data should be stored
according to the Australian Privacy Principles or security obligations.
 Website security appropriate to support administration module, members’ pages,
API developer key hidden and enables encryption of stored data including indexes
and registered user’s personal details e.g. email address.
Hosting
 The website application must be built to be hosted externally to the Archives’ IT
infrastructure taking into account data sovereignty, data protection controls (see
the Australian Government Protective Security Policy Framework (PSPF) and
Information Security Manual) and compliance with the Privacy Act.

Nerida McDowall
 Please see ‘Optional Deliverables’ for information on the optional hosting
component of this procurement process.
Aesthetic design
 The aesthetic design of the website must be maintained for the upgraded website.
 Style guides and other necessary components will be provided to the successful
Supplier.
Content Management System

 The website must support formats to enable crowd sourced data and display of
collection data including images.
 The solution must provide an easy way for administrators to view and record user-
generated activity across the site from within the administration CMS.
 The website’s supporting CMS or web application must have both a design and
source interface enabling recognition of user contributed data and has the ability to
manage full user administration and content moderation in-house. This must
include tasks such as updating all content (including descriptions on collection
photographs), monitoring and moderating user-generated data and where
necessary, blocking, removing, editing and/or extracting user-generated data.
 Administration module must be secure
 Administration page displays name (as well as screen ID) of contributing users
 The solution must support Google Analytics for website visitor statistics and pre-
scripted database reports for listing and exporting all user generated content.
 The website must comply with records management requirements to enable the
website to be archived with user-generated data extracted (e.g. XML, CSV format
and image formats) with relevant references for future re-purposing.
Email notifications to administrator

 Email notification to be sent to destinationaustralia@naa.gov.au when a user adds
a comment, tag, person, location to a collection photograph, or adds a feature
story. Notifications should include a hyperlink to the new content in the CMS
administrator account.
 Email notification to be sent to destinationaustralia@naa.gov.au when a user
reports comments or other content. Notifications must include a direct hyperlink to
the reported content.
Public user login

Nerida McDowall
 Website users have the option of browsing and searching the website without
registration. Anyone wishing to input data to the website must register and login
with a unique email address and passphrase.
 Existing usernames and passwords must carry over to the redeveloped site
 Profile must include an online form for users to contact Archives to remove or edit
their user-added content
 Optional: ability for the user to ‘link’ together multiple stories that they have
contributed by the user, or to allow sorting by tag with user name. The published
feature story page would display a link to take viewers to the related stories.
Navigation
 Website navigation must align with pre-existing information architecture for
Destination: Australia.
 Breadcrumbs must be added to the top of each page to enhance user navigation
Search function
 Ability to query search and return search results, this will be supported through the
API calls, and the interface will need to be configured to return merged search
requirements and apply search parameters (e.g. filters) for the Discovering Anzacs
interface.
 Required: free text feature stories and comments contributed by users must be
posted back to the API to become searchable on Destination: Australia.
 User-added tags on stories must be posted back through the API to become
searchable.
 User-added locations on stories must be searchable and clickable to sort stories by
place
 Adding terms to the search parameters should refine the search (it currently
expands the result field)
 The website must include all images within the A12111 series/collection, and search
results must display all relevant images. Check that search picks up all photographs
in collection (or that Destination: Australia captures all images in A12111) – e.g.
searching for “Petrus Mouwmans” does not give a result, although it is listed in
RecordSearch: A12111, 1/1963/14/9.
 Results distinguish between feature stories, collection items and user added
photographs.
 Results able to be sorted by category (feature story, collection item) or by date
range (earliest to latest or vice versa)

Nerida McDowall
 Image title to appear at the top of the results display (currently “view this
photograph”).
 Hit highlighting - the search interface will support search term (eg. keyword, name)
hit highlighting using bold or similar
Updates/fixes to ‘add your story’ form (see Attachment B for images of changes)
 All free text fields must allow users to copy and paste text from other programs.
 The fields ‘Year’, ‘Country of origin’, ‘Theme’ and ‘Photos’ (at least one) must be
compulsory
Adding images
 ‘Add photos’ must be moved to location above ‘Add Your Story’
 When adding an image from the website, the citation and image caption must also
be imported. The citation (e.g. NAA: A12111, 2/1969/4A/18) must be locked in, with
the option for the user to personalise the caption.
 When adding an image from the website, users must be able to search by collection
control symbols and non-consecutive key words.
 When adding an image from the website, user has the ability to refine the search
using date range.
 When adding an image from the website, clicking ‘enter’ after typing keyword must
initiate the search (currently takes user to blank error page).
 ‘Add image from website’ search must return all results available through
Destination: Australia.
 The website must perform checks to ensure the user is uploading an accepted size
and format (e.g. png, jpeg) and provide error messages where limits are exceeded.
 Optional: add a new function to allow users to select from their ‘Favourite’ images
to add to their story.
 Optional: users able to crop images before they upload.
Add your story

 ‘Add your story’ text field must allow simple formatting: paragraph breaks, italics.
 Must display Latin diacritics (accents e.g. acute é, grave è, circonflex ê, caron č; dots
e.g. diaeresis ë; cedilla ç, ogonek ą).
Feature story publishing process

Nerida McDowall
 Selecting ‘Preview’ must save a copy that allows for the user to return and edit
content. This draft copy must not be publicly available at this stage.
 Selecting ‘Save your story’ (on contribution form page) or ‘Save and submit’ (on
preview page) submits the story to the CMS and publishes the feature story on the
live website
 Stories are automatically published on submission.
Feature story display page (front end)

 On published feature stories, viewers must be able to click on categories (year,
country, tags, locations) to bring up a list of any other stories/images with the same
user-added metadata
 Must display Latin diacritics (accents e.g. acute é, grave è, circonflex ê, caron č; dots
e.g. diaeresis ë; cedilla ç, ogonek ą)
 Must display simple formatting: line breaks, italics
 Images must be able to open for larger display in a lightbox, with accompanying
caption
 Optional: where a user has added a photograph from the website, the image on the
published feature story page links back to the image display page for the particular
record (i.e. with metadata, comments, tags etc).
 Optional: if users add data to ‘location’, map with tagged locations should be shown
on published feature story page.
Record display page (front end)

 Required: create ‘order record’ button that takes the user through to PhotoSearch
result for that image and the associated ‘ordering images’ text box.
Home page
 Optional: preview of ‘Feature stories’ displays feature stories at random
Testing
 The Supplier must outline the project plan and team roles and the testing strategy
and plan. It should also include any handover files and documentation to be
provided for implementation.
 Extensive testing will be required prior to the website launch. This includes iterative
testing during development, implementation of changes and subsequent re-testing.
 On implementation and handover the Destination: Australia website should be fully
functional and populated with relevant content and data. As part of the website

Nerida McDowall
handover, training sessions and support documentation for nominated
administrators will also be required.
 Testing must include success of API calls to/from the Destination: Australia website
for creation, deletion, updates and retrieval of data in conjunction A Ticket to
Paradise? ‘globe’ interactive.
 The National Archives will determine when the website is ready to be launched and
the date. However, the supplier must be able to meet the nominal launch date of
25 October 2016.
Acknowledgements
The banner (visible on all pages) must include:
 Destination: Australia web tile

 Multi-agency logo for the National Archives of Australia and the Department of
Immigration and Border Protection (to be provided by the Customer)
 The following tagline:
o ‘The National Archives acknowledges the support of the Department of
Immigration and Border Protection for the Destination: Australia website’,
with the text ‘Department of Immigration and Border Protection’
hyperlinked to the website https://www.border.gov.au/
Progress meetings and reports
The successful Supplier will be required to:

 Attend the project kick-off meeting (face-to-face / teleconference)
 Attend regular updates at an agreed time and day, at least fortnightly.
 Attend scheduled project meetings to report at key milestones or deliverables
throughout the project.
 Communicate any issues which may impact agreed project tolerances as they occur
 Attend project wrap-up meeting with final deliverables and website handover
including report/documentation.
 Work collaboratively with National Archives staff and Suppliers to meet
expectations and resolve issues.
Optional
 Should the option of host services be agreed to by the Customer, the Supplier must
attend ongoing support meetings or maintain regular communication as required,
up until the end of the contract.

Nerida McDowall
Project Management Requirements
 The Archives will nominate a Project Manager who will be responsible for liaison
with the successful supplier in relation to management of the contract and overall
service delivery.
 Potential Suppliers must specify all staff and subcontractors proposed to complete
the work.
 The successful Supplier will be required to nominate a Project Manager as the
primary point of contact for the Archives. This person will be responsible for the
management of the contract as a whole and for liaison with the Archives’ Project
Manager.
After delivery
The Supplier must commit to providing defect resolution in the post-launch period, up to
30 April 20xx, in response to Archives user testing and feedback. In this period the Supplier
must complete full internal testing and bug fixes before any solution release for publishing.
Optional deliverables
Hosting and maintenance

The Potential Supplier should provide a response for an optional service level agreement,
to host the website externally to the Archives’ infrastructure, provide ongoing maintenance
and support until 31 December 2019.
 The website application must be hosted externally to the Archives’ IT infrastructure
taking into account data sovereignty, data protection controls (see the Australian
Government Protective Security Policy Framework (PSPF) and Information Security
Manual) and compliance with the Privacy Act.
 Quality of service requirement in order to maintain its effectiveness; available 99%
of up time annually and has appropriate back-up (with equal features to meet
above-mentioned data security and privacy requirements) scalability options and
recovery processes.
 Response time for issues to be negotiated and confirmed with the successful
Supplier.
Capability to function with future API’s

Potential to link with National Archives’ and external sources’ collections and data, via API’s
that may be developed in the future.

Nerida McDowall
Within your practice environment, complete each of the following parts (Note: Parts of this
assessment task, such as project execution, will be simulated in your practice environment):
Establish the project

1. Provide a Project Charter to initiate the project. Use the template below.
Project Charter:
A. Project Background
<Explain what the project is to achieve and how it was triggered. How does this project satisfy
the organisation’s strategic objectives and goals?>
B. Project Purpose and Justification
<Purpose and why the project is needed>
C. High Level Project Scope Statement

Project Objectives and Success Criteria
<List objectives and success criteria – make then SMART. Make sure you explain how this
project fits in with broader organisation objectives>
High Level Project Scope and Requirements

In scope
 <Broad statements of project and product scope to be included in the

project>
Out of scope
 <Broad statements of project and product scope items not to be included

in the project>
Assumptions
The main assumptions are:
 <assumptions>
Nerida McDowall
Constraints
The main constraints are:
 <constraints>
D. Project Methodology and Approach

<List the project methodology to be used. This must be provided to show you can use a
methodology to help you produce project deliverables.>
The phases are:
<List the main phases with a basic description for each including key requirements or
deliverables for stage completion.>
E. Project Structure
<Provide the project structure chart include a hierarchy diagram for clarity. This also needs to
include project governance>
F. Project Stakeholders and Authority

The major stakeholders and their authority level on this project are shown below.
Name Title Authority Level
G. Project high level risks

Rating scales and categories
Likelihood

Nerida McDowall
Title Ratin Description
g
Very 1 Highly unlikely to occur; however, still needs to be monitored as certain

Low circumstances could result in this risk becoming more likely to occur
during the project
Low 2 Unlikely to occur, based on current information, as the circumstances

likely to trigger the risk are also unlikely to occur©
Medium 3 Likely to occur as it is clear that the risk will probably eventuate
High 4 Very likely to occur, based on the circumstances of the project
Very 5 Highly likely to occur as the circumstances which will cause this risk to
High eventuate are also very likely to be created
Impact
Title Ratin Description

g
Very 1 Insignificant impact on the project. It is not possible to measure the

Low impact on the project as it is minimal
Low 2 Minor impact on the project, e.g. < 5% deviation in scope, scheduled end-
date or project budget
Medium 3 Measurable impact on the project, e.g. 5-10% deviation in scope,

scheduled end-date or project budget
High 4 Significant impact on the project, e.g. 10-25% deviation in scope,

scheduled end-date or project budget
Very 5 Major impact on the project, e.g. >25% deviation in scope, scheduled
High end-date or project budget

Nerida McDowall
Risk Matrix: Likelihood X Impact = Overall Level/Rating
LIKELIHOOD Very Low Low Medium High Very High
IMPACT
1 2 3 4 5
Very Low Low Low Low Medium

Very Low 1
1 2 3 4 5
Low Low Medium Medium High

Low 2
2 4 6 8 10
Low Medium High High Very High

Medium 3
3 6 9 12 15
Low Medium High Very High Very High

High 4
4 8 12 16 20
Medium High Very High Very High Very High

Very High 5
5 10 15 20 25
Overall Level/Rating
0 – 1 = Very Low 2 – 4 = Low 5 – 8 = Medium 9 – 14 = High 15 – 25 = Very

High
Categories
The risk categories are:

Nerida McDowall
 Financial
 Marketing and Sales
 Resourcing
 Technical
 Legal
 <other>
High level risk register

Below are the top 5 risks:
Risk Category Risk Description Likelihood Impact

No.
1 <Category> <A description of the positive or negative risk> <Based on <Based
rating on
scales> rating
scales>
2
3
4
5
H. Summary Schedule
Phase or Milestone Preferred completion Dependencies
date
<Phase/milestone description> <DD/MM/YYYY> <Main dependencies>

Nerida McDowall
Phase or Milestone Preferred completion Dependencies
date
I. Summary Budget
Category of Cost Best Estimate Worst Estimate Most Likely
Note: <any relevant notes to support the budget>
J Document Quality Control

Version Control
Version Date Author Comments
Approvers

Nerida McDowall
Name Title Signature
Reviewers
Name Title Signature
Definitions
TERM/ABBREVIATI FULL NAME DESCRIPTION

ON
--------------------------------------------------------------------------------------------------------------------------
---------
Undertake project planning and design processes
The project management plan describes the necessary work (and the reasons for this work)
that is to be executed to plan, deliver and monitor the scope, time, cost, quality, human
resources, communication and project information, stakeholder management, risk and
procurement management plans assessed in these units in an integrated manner according
to the governance arrangements. This is demonstrated by consistency across these areas
where the information from one area is used as a basis for another. E.g.: timeframes provide
part of the basis of budget estimates.
1. Briefly describe the tools and techniques that you used to develop the project
management plan?

Nerida McDowall
2. Briefly describe how the project work was to be executed to accomplish the project
objectives, including the dependencies and interactions among each knowledge area
of the project?
3. Briefly describe the organisation’s environmental factors you used to plan and deliver
the project?

Nerida McDowall
4. What organisational processes were used to develop the project management plan?
Your answer should include any standardised guidelines, work instructions, proposal
evaluation criteria, performance measurement criteria, change control procedures,
historical information and lessons learned.

Nerida McDowall
5. How was the integrity of your project baselines to be maintained throughout the
project life cycle? Who was responsible for this work?
6. Provide details of how approval would be obtained for the project management plan.

Nerida McDowall
7. Describe how the triple constraint is applied to your project.
Execute project in work environment
What work performance data did you collect about the completion status of
deliverables during this phase of the project? Describe one example of a review of the
impact on late completion of a deliverable and how you managed its impact and
implementation of any agreed changes?

Nerida McDowall
Manage project control
1. Give an example of the tools and techniques that you use to analyse the status of one
deliverable in your project that guided the information and recommendation that you
documented in a status report.
2. Which project plans/logs and registers would you need update to Direct and Manage
Project Work? Why would they change?

Nerida McDowall
Manage project finalisation
1. Provide a post implementation report you completed for your project showing
performance measured against objectives and success criteria.
For this project, provide a project checklist of relevant project finalisation activities including
who will be responsible for these. These activities may include: handover, financial, legal,
contractual, documentation, issue, reports finalisation and organisation knowledge
management. Write your answers on a piece of paper, clearly writing the contributors and
describing the project.

Nerida McDowall
TASK 1 – MARKING CRITERIA
BSBPMG521 Manage project integration S NYS

Learner’s name:
Assessor’s name:
Observation Criteria S NS

Nerida McDowall
Identified, clarified and prepared project initiation documentation
Identified relationship between the project and broader
organisational strategies and goals
Negotiated and documented project objectives, outcomes and
benefits
Negotiated project governance structure with relevant authorities
and stakeholders
Prepared and submitted project charter for approval by relevant
authorities
Established and implemented a methodology to disaggregate
project objectives into achievable project deliverables
Identified project stages and key requirements for stage completion
against client requirements and project objectives
Analysed project management functions to identify
interdependencies and impacts of constraints
Developed a project management plan that integrates all project-
management functions with associated plans and baselines
Established designated mechanisms to monitor and control
planned activity
Negotiated approval of project plan with relevant stakeholders and
project authority
Managed the project in an established internal work environment
to ensure work is conducted effectively throughout the project
Maintained established links to align project objectives with
organisational objectives throughout the project
Within authority levels, resolved conflicts negatively affecting
attainment of project objectives
Ensured project records are updated against project deliverables
and plans at required intervals
Analysed and submitted status reports on project progress and
identified issues with stakeholders and relevant authorities
Analysed and submitted impact analysis of change requests for
approval, where required
Maintained relevant project logs and registers accurately and
regularly to assist with project audit
Ensured associated plans are updated to reflect project progress
against baselines and approved changes
Identified and allocated project finalisation activities
Nerida McDowall
Ensured project products and associated documentation are
prepared for handover to client in a timely manner
Finalised financial, legal and contractual obligations
Undertook project review assessments as input to future projects
Feedback to Learner:
Assessor’s Signature: Date:

Nerida McDowall

Task 1 - Project Integration Management: Instructions To Learners

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Task 1 - Project Integration Management: Instructions To Learners

Uploaded by

Copyright:

Available Formats

Task 1 – Project Integration Management

 This summative assessment can be completed in class or at any other convenient

This assessment task requires you to:

Assuming your Organisation was awarded the following tender:

ATM ID: NAA RFT 20xx/1058

Timeframe for Delivery: November/December 20XX with a possible extension of up to 3

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

Privacy, security and intellectual property

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

Content Management System

Email notifications to administrator

Public user login

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

Add your story

Feature story publishing process

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

Feature story display page (front end)

Record display page (front end)

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

 Destination: Australia web tile

Progress meetings and reports

The successful Supplier will be required to:

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

Hosting and maintenance

Capability to function with future API’s

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

Establish the project

C. High Level Project Scope Statement

High Level Project Scope and Requirements

 <Broad statements of project and product scope to be included in the

 <Broad statements of project and product scope items not to be included

D. Project Methodology and Approach

F. Project Stakeholders and Authority

Name Title Authority Level

G. Project high level risks

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

Very 1 Highly unlikely to occur; however, still needs to be monitored as certain

Low 2 Unlikely to occur, based on current information, as the circumstances

High 4 Very likely to occur, based on the circumstances of the project

Title Ratin Description

Very 1 Insignificant impact on the project. It is not possible to measure the

Medium 3 Measurable impact on the project, e.g. 5-10% deviation in scope,

High 4 Significant impact on the project, e.g. 10-25% deviation in scope,

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

LIKELIHOOD Very Low Low Medium High Very High

Very Low Low Low Low Medium

Low Low Medium Medium High

Low Medium High High Very High

Low Medium High Very High Very High

Medium High Very High Very High Very High

0 – 1 = Very Low 2 – 4 = Low 5 – 8 = Medium 9 – 14 = High 15 – 25 = Very

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

High level risk register

Risk Category Risk Description Likelihood Impact

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

Category of Cost Best Estimate Worst Estimate Most Likely

Note: <any relevant notes to support the budget>

J Document Quality Control

Version Date Author Comments

BSBPMG521 Task 1 NovaCore\DMS\TRAINING LIBRARY\BUSINESS\BSB50815 DIPLOMA OF

Name Title Signature