Iteration Design Document
Manpower
Recruitment Management System
Iteration Design Document
Table of contents
Address of Document Controller .................................................................................................................................... 4
Approvers ....................................................................................................................................................................... 4
Reviewers....................................................................................................................................................................... 5
Distribution ..................................................................................................................................................................... 5
Copyright ........................................................................................................................................................................ 5
Confidentiality ................................................................................................................................................................. 5
1. Introduction .................................................................................................................................................................. 6
1.1. Configuration Responsibility.................................................................................................................................... 6
1.2. Key Dates ................................................................................................................................................................ 7
2. Iteration Reviews ......................................................................................................................................................... 8
2.1. Iteration 1 & 2 – Recruitment Management System Overview / Job Card & Offer Card ........................................ 8
2.1.1. Job Card Module Overview .......................................................................................................................... 8
2.1.2. Online Requisition Overview ........................................................................................................................ 8
2.1.3. Offer Module Overview ................................................................................................................................ 8
2.1.4. Actions .......................................................................................................................................................... 8
2.1.5. Key Decisions ............................................................................................................................................. 10
2.1.6. Hot Spots .................................................................................................................................................... 10
2.2. Iteration 3 – Recruitment Processes, Sites, Locations, Job Card Approval Processes, Sourcing Channels,
Online Testing .............................................................................................................................................................. 10
2.2.1. Recruitment Processes Overview .............................................................................................................. 11
2.2.2. Previous Actions......................................................................................................................................... 11
2.2.3. Actions ........................................................................................................................................................ 11
2.2.4. Key Decisions ............................................................................................................................................. 11
2.2.5. Hot Spots .................................................................................................................................................... 11
2.3. Iteration 4 –Application Forms, Internal Forms, Job Templates, Job Card Reasons, Contracts, Document
Storage & Categories ................................................................................................................................................... 11
2.3.1. Application Forms / Internal Forms Module Overview ............................................................................... 12
2.3.2. Document Management Overview ............................................................................................................. 12
2.3.3. Previous Actions......................................................................................................................................... 12
2.3.4. Actions ........................................................................................................................................................ 12
2.3.5. Key Decisions ............................................................................................................................................. 12
2.3.6. Hot Spots .................................................................................................................................................... 12
2.4. Iteration 5 –Communication Templates, Talent Search, Booking & Events ......................................................... 12
2.4.1. System Settings – Communications Overview .......................................................................................... 12
2.4.2. Booking & Events Module Overview .......................................................................................................... 12
2.4.3. Talent Search Module Overview ................................................................................................................ 13
2.4.4. Previous Actions......................................................................................................................................... 13
2.4.5. Actions ........................................................................................................................................................ 13
2.4.6. Key Decisions ............................................................................................................................................. 13
2.4.7. Hot Spots .................................................................................................................................................... 13
2.5. Iteration 6 – Reporting, Mandatory Fields, Teams, Permissions .......................................................................... 13
2.5.1. Reporting Module Overview ....................................................................................................................... 13
2.5.2. Previous Actions......................................................................................................................................... 13
2.5.3. Actions ........................................................................................................................................................ 14
2.5.4. Key Decisions ............................................................................................................................................. 14
2.5.5. Hot Spots .................................................................................................................................................... 14
Page 2 of 16 – PageUp People
13 July 2017
Iteration Design Document
3. Final Solution Walkthrough ...................................................................................................................................... 14
3.1.1. Previous Actions......................................................................................................................................... 14
3.1.2. Actions ........................................................................................................................................................ 14
3.1.3. Key Decisions ............................................................................................................................................. 14
3.1.4. Hot Spots .................................................................................................................................................... 15
4. Appendix..................................................................................................................................................................... 16
Page 3 of 16 – PageUp People
13 July 2017
Iteration Design Document
Document Information
Version Control
Version
Date
Nature of Amendment
Author
1.0
29/10/13
Initial Draft
Justin Rundle
Related Documents
Document Name
Version
Document Owner
Document Control & Approval
Responsibilities
Responsibilities for this document have been assigned as follows
Role
Responsibility
Assigned To
Document Approver
Approve the final version.
Kelly Populin
Document Owner
Overall responsibility for document accuracy and
distribution list.
Justin Rundle
Document Author
Prepare the document to the Document Owner’s
specification.
Justin Rundle
Document Controller
Version control and distribution to nominated document
holders.
Justin Rundle
Address of Document Controller
Level 10, 91 William Street
Melbourne VIC 3000 Australia
Approvers
The following table contains the list of this document’s approvers and if this table does not contain the
signatures or email date stamps of the nominated approvers, you have an unapproved copy. Contact the
Document Controller for more information.
Approver
Business Area/Division
Kelly Populin
Program Manager
Justin Rundle
PageUp Project Manager
Rainer Bean
PageUp Implementation Analyst
Page 4 of 16 – PageUp People
Approval
Date
13 July 2017
Iteration Design Document
Reviewers
The following table contains the list of this document’s reviewers.
Reviewer
Business Area/Division
Kelly Populin
Manpower Program Manager
Kristen McKendry
Manpower Program Manager
Rainer Bean
PageUp Implementation Analyst
Justin Rundle
PageUp Project Manager
Reviewed
Date
Distribution
The Document Controller is responsible for ensuring that:

All current documentation is available in Salesforce; and

Personnel who do not have access to Salesforce will be notified of new version via email.
Copyright
This material is copyright. No part of this document may be reproduced in any form, stored in a retrieval system
or transmitted without the prior written permission of PageUp People Pty Ltd.
Confidentiality
This document is classified Commercial in Confidence. It is subject to a confidentiality agreement between the
recipient organisation and PageUp People Pty Ltd. Its contents must not be divulged to third parties
Page 5 of 16 – PageUp People
13 July 2017
Iteration Design Document
1. Introduction
The purpose of this document is to outline and capture the key decisions and iterations completed as part of the
project. This document describes each iteration to be covered as part of the configuration phase detailing the
following components




Module Overview
Key Topics
Key Decisions made
Hot Spots / Actions
The iteration design document includes decisions made during the iteration and configuration review sessions,
however it does not serve as a complete listing of configuration settings within PageUp People.
To contribute to the iteration design document, the Manpower Project Manager will collate documentation
surrounding the processes related to the iteration, including steps and roles within the organisation. Manpower
have opted not to create a data integration point with PageUp People, which may require an initial load of
Manpower HR data to support the PageUp People system.
PageUp People will assist with the definition of this information to enable the Manpower Project Manager to
make these decisions and collect the appropriate documentation.
This document supplements the PageUp People Statement of Work for Manpower.
Each iteration and content will be agreed as part of the Weekly Project Status Update meeting, including
location, duration, and attendees.
1.1. Configuration Responsibility
PageUp People’s implementation approach is to equip the Client to operate and adapt their system in line with
changes to their business and operating environment. During the implementation, PageUp People will train the
Client to configure the Super User accessed elements of the system in order for the Client to become selfsufficient with the functionality. The Client will then be responsible for configuring all elements of the system to
which they have access. Certain components of the configuration must be configured by PageUp People, and
these configuration components will be completed in consultation with the Client.
Owner
Manpower Super User
PageUp People Implementation Analyst
Page 6 of 16 – PageUp People
Configuration Components

Recruitment processes

System settings

Communications

Online requisition processes and communications

Offer approval processes and communications

Reports

Permissions

Job board set up

Create Client Environments

Job card creation

Offer card creation

Intranet & Website set up
13 July 2017
Iteration Design Document
1.2. Key Dates
Item
Phase
Description
Date
1
Planning
Sign off iteration plan
17 Jan 14
2
Configuration /
Iterations
Iteration 1 & 2 – Recruitment Management System Overview / Job
& Offer Card
16 Jan 14
3
Configuration /
Iterations
Iteration 3 - Recruitment Processes, Sites, Locations, Sourcing
Channels
21 Jan 14
5
Configuration /
Iterations
Iteration 4 - Application Forms, Internal Forms, Job Templates,
Job Card Reasons, Offer Card, Contracts, Document Storage &
Categories
24 Jan 14
6
Configuration /
Iterations
Iteration 5 - Communication Templates, Talent Search, Booking &
Events, LinkedIn
TBC
7
Configuration /
Iterations
Iteration 6 - Reporting, Mandatory Fields, Teams, Permissions
TBC
8
Final Solution
Walkthrough
Completed prior to UAT as a validation check on the solution
TBC
9
UAT Sessions
System UAT, inclusive of 2 Manpower users, and PageUp
Implementation Analyst
3 Feb – 7 Feb
10
Go-LIVE
System Ready for Service
12 Feb
Page 7 of 16 – PageUp People
13 July 2017
Iteration Design Document
2. Iteration Reviews
The following section outlines the iteration reviews that will be completed as part of the implementation for the
RMS modules purchased by Manpower. The iteration reviews will be facilitated by the PageUp Implementation
Analyst, with client attendees including the Project Manager, and any key stakeholders who would provide input
to the final solution. Optional attendance includes the PageUp Project Manager and PageUp Business Owner.
Each iteration will focus on a key component of the system where the key objective is to provide an in depth
analysis of the ‘To Be’ configuration, and to discuss and agree on the configuration to support the Manpower
Recruitment Process.
The iteration schedule will be twice a week at a time to be determined between the PageUp Project Manager
and Manpower Project Manager. The iteration structure will include a combination of GoTo meetings and face
to face engagements, to be determined by the Manpower and PageUp Project Managers.
2.1. Iteration 1 & 2 – Recruitment Management System Overview / Job Card & Offer Card
Date – 16th January
Location – PageUp Offices
Duration – 10:30am – 4:00pm
Attendees – Justin Rundle, Rainer Bean, Kelly Populin, Kristen McKendry
This iteration will focus on providing an end to end demonstration of the pre-configured system that has been
designed by the PageUp Implementation Analyst. The system will incorporate any shared documentation that
has been provided prior to Project Initiation and any information shared between the PageUp People Project
Manager and Manpower Project Manager.
2.1.1. Job Card Module Overview
The Job card, also known as the Position info page or requisition form, is used to store all job related
information. The Job card is configured during your system’s implementation to capture the information
specifically required by your business to approve and recruit against.
2.1.2. Online Requisition Overview
Move your paper-based requisition and approval process online. This module allows your recruitment team to
track the number of requisitions in the system, at what point in the approval process they are, and what jobs
they are for. Knowing this information can help shorten the recruitment cycle by pre-empting workloads and
sending alarms via e-mail if the requisition becomes ‘stuck’ at any step along the way. Tailored approval
processes can be created to support business processes.
2.1.3. Offer Module Overview
The Offer Module allows capture of details relating to the offer process and the new employee. This module
allows management to review and approve all offer details prior to the release to applicant. The offer can be
made electronically, and the applicant can review all offer details, accept the offer and provide required
information directly into the system.
2.1.4. Actions
Item
Module
Description
Resource
Due Date
1(160114)
Job Card
Headcount Management – Is this a mandatory
field, can it be selective depending on the scenario
being completed
RB
170114
2(160114)
Job Card
Provide list of Organisational Hierarchy
information
KP
210114
3(160114)
Job Card
Cost Centre will be linked to organisational
hierarchy, will
Note
Note
4(160114)
Job
Approvals
Keep approval processes functionality on, listing
for approvals will be by Division
Note
Note
Page 8 of 16 – PageUp People
13 July 2017
Iteration Design Document
5(160114)
Recruitment
Process
Provide list of Recruitment Process flow for Project
Roles
KP
210114
6(160114)
Job Card Work Site
locations
Provide list of work site locations
KP
210114
7(160114)
Job Card Advertising
Provide locations for advertising locations for
sourcing purposes
KP
210114
8(160114)
Bulk
Compile &
Send
Test Results – confirm that if multiple tests are
completed they will be sent to the client, will it
include the detail around what type of test it is
RB
210114
9(160114)
Bulk
Compile &
Send
If we are to bulk compile and send, what format is
available to communicate the information, can it
be sent via a report
RB
210114
10(160114)
Reporting
Create report based off the template that KP
sends through including score information /
applicant detail / online test
RB
210114
11(160114)
User File
The users to have access to the system include
KP
210114



Operational Employees (recruiters / HR)
Key Users to be invited to Events
Approvers of Job / Offer Cards
12(160114)
Offer Card
KP to send through contract template to allow
configuration of offer card
KP
170114
13(160114
Online
testing score
- reporting
Multiple tests are required to be displayed in the
‘Order of Merit’ report. Is this information available
through the standard dataview, and if not how do
we source this information
RB
210114
14(160114)
Bulk Export
Report –
Application
Form
Can we incorporate reference check and phone
screen form scoring / assessment centre scoring
into bulk export report
RB
210114
15(160114)
Scoring
How do we best support adding an ‘recruitment
process’ score against a specific applicant for a
recruitment process step
RB
210114
16(160114)
Online
Testing
integration
SHL integration is not currently allocated in this
statement of work. Would this be charged
additionally to complete, or can it be completed
under the current statement of work
JR
210114
17(160114)
Careers
website
KP to organise introduction emails with key
technology resource to complete website build.
RB to share generic website documentation once
scheduled
KP
170114
18(160114)
Super User
Guides
RB to supply generic super user guides to
Manpower Project Team
RB
170114
19(160114)
One Test
Integration
example
Send through screen shots of example integration
online test results that come back from an online
provider
RB
210114
Page 9 of 16 – PageUp People
13 July 2017
Iteration Design Document
20(160114)
Applicant
Portal
Include branding and logos on Applicant portal.
Should be Manpower specific
RB
210114
21(160114)
LinkedIn
Integration
Confirm LinkedIn account details
KP
210114
22(170114)
User profile
Remove Division, Department & Employee
number from the user profile
RB
240114
DONE
23(170114)
Applicant
portal
Applicants need to be able to submit documents
such as medical check documents after they have
submitted their application and after the job
sourcing has closed – RB to see how we can best
support this requirement
RB
240114
24(170114)
Manage
applications
Can phone screen results be visible in Manage
Applications
RB
240114
25(170114)
Manage
applications
Can test results be visible in Manage Applications
RB
240114
26(170114)
Applicant
profile
GPA calculation – see how this works
RB
240114
Description
Resource
Due Date
2.1.5. Key Decisions
Item
Module
2.1.6. Hot Spots
Item
Module
Description
Resource
Due Date
1(160114)
Client
Branding
Manpower support multiple client groups, is there
a way to show specific client branding once the
candidate applies via Seek
RB
210114
2(160114)
Reporting
Once a candidate gets to a recruitment status step
of ‘Order of Merit’ document the number of options
to capture and communicate data to clients. This
can take the forms of report builder reports / bulk
exports / application form exports
RB
210114
3(160114)
Recruitment
Step Scoring
Certain steps in the recruitment process require a
‘score’ to be applied to it. What are the options to
supporting this requirement.
RB
210114
4(160114)
Online
testing score
weightings
Once an online score has been captured by the
online tester, and a score comes back into
PageUp, is there any way a weighting can be
applied (bell curve) to rate the applicants
RB
210114
2.2. Iteration 3 – Recruitment Processes, Sites, Locations, Job Card Approval Processes,
Sourcing Channels, Online Testing
Date – 21st January 2014
Page 10 of 16 – PageUp People
13 July 2017
Iteration Design Document
Location – GoTo Meeting
Duration – 2 hours
Attendees – Justin Rundle, Rainer Bean, Kelly Populin, Kristen McKendry
2.2.1. Recruitment Processes Overview
Recruitment processes manage the progression of an application through the system towards their end point.
You may decide to only have one recruitment process for all applicants or decide to have a different recruitment
process for different level roles (e.g. executive level, graduate level, call centre etc.). A recruitment process is
mapped out by a set of application statuses.
For each application status, you will need to determine the title, the public status (what the applicant will see if
they log-in to the applicant services area), and whether an email template or sms template is required.
Recruitment processes:
 Ensure you are able to move your applicant through the correct application statuses;
 Ensure the correct automated email communications are sent to the applicants;
 The correct data is collected for business reporting; and
 Captures the activity you are performing and allows you to easily track your applicants.
2.2.2. Previous Actions
Item
Module
Description
Resource
Due Date
Module
Description
Resource
Due Date
Description
Resource
Due Date
Description
Resource
Due Date
2.2.3. Actions
Item
2.2.4. Key Decisions
Item
Module
2.2.5. Hot Spots
Item
Module
2.3. Iteration 4 –Application Forms, Internal Forms, Job Templates, Job Card Reasons,
Contracts, Document Storage & Categories
Date – 24th January 2014
Location – TBC
Duration – TBC
Attendees – Rainer Bean, Kelly Populin, Justin Rundle (optional), Kristen McKendry
Page 11 of 16 – PageUp People
13 July 2017
Iteration Design Document
2.3.1. Application Forms / Internal Forms Module Overview
Forms include initial application forms, new employee forms that are triggered when an applicant accepts an
offer as well as other forms such as reference check forms etc that can be customised to suit the customer's
needs.
2.3.2. Document Management Overview
Documents can be setup in the system either as documents to be attached to an applicant or job, or as merge
documents which can be used to pull data from the system into a template document, eg a letter of offer.
Different types of documents will be available for different applications depending on the document type that is
assigned to a particular document.
2.3.3. Previous Actions
Item
Module
Description
Resource
Due Date
Module
Description
Resource
Due Date
Description
Resource
Due Date
Description
Resource
Due Date
2.3.4. Actions
Item
2.3.5. Key Decisions
Item
Module
2.3.6. Hot Spots
Item
Module
2.4. Iteration 5 –Communication Templates, Talent Search, Booking & Events
Date – TBC
Location – TBC
Duration – TBC
Attendees – Rainer Bean, Kelly Populin, Justin Rundle (optional), Kristen McKendry
2.4.1. System Settings – Communications Overview
Communications sit in many places throughout the system. Most of these are predefined by the system and
most can be edited. i.e. Agency release job template. You can also create ‘manual’ communication templates
that send standardized communications from within the system.
2.4.2. Booking & Events Module Overview
The Booking/Events Module allows all interviews, testing and other event bookings to be managed
online. Simply setup timeslots and invite the appropriate applicants to book themselves in at a time convenient
to themselves.
Allows HR users to invite applicants to interviews, phone screening calls, testing and other event bookings
online, significantly reducing the administration time. The user simply set up timeslots and invites the
appropriate applicant to book themselves in at a time convenient to themselves. Approved events are then able
Page 12 of 16 – PageUp People
13 July 2017
Iteration Design Document
to be entered into the recruiters and/or hiring managers Outlook calendar, again acting to streamlining the
process.
Use this module to easily organise events such as interviews, testing, and assessment centres with multiple
applicants.
2.4.3. Talent Search Module Overview
Talent Search gives you the ability to search applicants – as part of building a talent pool or to create a shortlist
of applicants before sourcing externally.
2.4.4. Previous Actions
Item
Module
Description
Resource
Due Date
Module
Description
Resource
Due Date
Description
Resource
Due Date
Description
Resource
Due Date
2.4.5. Actions
Item
2.4.6. Key Decisions
Item
Module
2.4.7. Hot Spots
Item
Module
2.5. Iteration 6 – Reporting, Mandatory Fields, Teams, Permissions
Date – TBC
Location – TBC
Duration – TBC
Attendees – Rainer Bean, Kelly Populin, Justin Rundle (optional), Kristen McKendry
2.5.1. Reporting Module Overview
There are a number of different types of reports available in the system; these include standard reports,
analytics dashboards, and custom reports which can be configured by users to create reports for specific
applications. Custom reports can be setup and saved for use at future dates by any user who has permission to
this area of the system. There are a number of report data views available to base reports on, from these data
views you can select which fields you want to include in the report, you can then add filters and or sorting/
grouping to create the report you want. Reports can also be setup to be sent to a user of the system (by email)
according to a schedule that will be configured in the system.
2.5.2. Previous Actions
Item
Module
Page 13 of 16 – PageUp People
Description
Resource
Due Date
13 July 2017
Iteration Design Document
2.5.3. Actions
Item
Module
Description
Resource
Due Date
Description
Resource
Due Date
Description
Resource
Due Date
2.5.4. Key Decisions
Item
Module
2.5.5. Hot Spots
Item
Module
3. Final Solution Walkthrough
Date – TBC
Location – TBC
Duration – 4 hours
Attendees – Rainer Bean, Kelly Populin, Justin Rundle, Kristen McKendry
This session will cover a detailed end to end walkthrough of the functionality that has been configured by the
PageUp Implementation Analyst and Manpower Project Manager / Super User. The walkthrough will cover the
following topics




Configuration Walkthrough
Super User related tasks
PageUp related tasks
Brief on UAT Phase
3.1.1. Previous Actions
Item
Module
Description
Resource
Due Date
Module
Description
Resource
Due Date
Description
Resource
Due Date
3.1.2. Actions
Item
3.1.3. Key Decisions
Item
Module
Page 14 of 16 – PageUp People
13 July 2017
Iteration Design Document
3.1.4. Hot Spots
Item
Module
Page 15 of 16 – PageUp People
Description
Resource
Due Date
13 July 2017
Iteration Design Document
4. Appendix
To be included
Page 16 of 16 – PageUp People
13 July 2017