Professional Documents
Culture Documents
PPT - 3 - PT101 Implementation Methodology 2019_021603
PPT - 3 - PT101 Implementation Methodology 2019_021603
PPT - 3 - PT101 Implementation Methodology 2019_021603
Implementation Methodology
(PT101)
Click the below image to access the document in the Partner Community
Plan
1. PLAN Confirm Build Validate Deploy
• Customer kick-off • Core Concepts training • Solution configured to • Customer acceptance • Deployment checklist
• Transition from • Workshops to define the approved solution testing (UAT) • “Go-Live” planning
procurement to customer design • Customer training • Support planning
implementation requirements • Unit testing • Customer validation • Stabilization period
• Requirements • Real data imported • Customer sign-off • Transition to Support
• Project teams defined
and staffed
approved (BRD) • Iterative demos • Deployment prep
• Solution design • Train the trainer
• Populate the WBP
created (SDD)
Questionnaire
• Customer review and
• Customer reviews
approval design
Standard Base Product
• Customer begins test
planning
• Assumptions
• Configuration Scope
Discovery Document – high level requirements gathered during the sales cycle
• Scope describes what we will and will not include as part of the project
• Which employee groups in the organization will be addressed as part of the project
Plan
1. PLAN Confirm Build Validate Deploy
• Sales and Delivery Team transition • Review EM Workbook and SOW • Attend kick-off meeting
• Kick-off meeting • Review project plan timeline • Meet the project team
• Training instance set up • Validate Scope • Questionnaire populated based on
• Standard Product Questionnaire • Project plan by project phase SOW
populated • Type and # of resources required • Finalize Project Plan
• Project Plan created • Hours for each resource by week
• Statement of Work (SOW) finalized • Agenda for onsite meeting
• Training documentation
Plan
1. PLAN Confirm Build Validate Deploy
• Test environment deployed • Test environment set up with • Signed Standard Product
• Model requirements gathered data Questionnaire
• Customer-specific requirements • Standard Product Questionnaire • Signed Base Product Usage
gathered signed off Extensions Business
• Solution Design Document • Core Concepts Training delivered Requirements Document
finalized • Base Usage BRD signed off • Signed Solution Design Document
• Solution Design Document • Customer starts test plan
signed off
• Follow-up meetings and questions will occur during the Solution Design Phase
Plan
1. PLAN Confirm Build Validate Deploy
• Environment Built to Specification • Design Team truncate TEST • Finalize the test plan
• Initial load of data takes place • Design team build models and • Supplies data for integrations
• Integrations tested customer-specific requirements
• Terminal configured • Functional consultant QA build at
each stage
• Customer receives testing
preparation testing
• Functional consultant conducts
mid-configuration demo
Plan
1. PLAN Confirm Build Validate Deploy
Week 15 to 18 – Customer
Acceptance/Validation
• Customer has executed test plan and provides
feedback on testing results
Week 19 – Customer
Acceptance/Validation is Completed
• Customer signs off with acceptance of the delivery
configuration and the Stabilization period begins
Plan
1. PLAN Confirm Build Validate Deploy
Employee transfers
Multiple Assignments
Critical defects
Interfaces
Integration Requirements
Custom Report Requirements
• Review each of the integration requirements at a high
level • Custom report requirements will need to be gathered
• Ensure employee base required fields are provided • Custom report requirements are documented in the
• Request payroll files layouts customers Base Product Usage Extension Requirements
• Integration requirements are documented in the spreadsheet
customers Integrations Business Requirements
document
DCT Requirements
• For customer’s using Workforce’s Data Collection
Terminals, requirements for these need to be gathered
• DCT requirements are documented in the customers
DCT Requirements document
• Retrieve sample • Meet with the • This part of the • Review final SDD
data files that are design team as project is heavily and all
needed for the needed dedicated to the requirements
build phase • Design team SDD documents with
• Check with the includes the lead • Remember to the design team
design team what configuration provide
files are needed specialist, traceability to the
interfaces and requirements
reports specialists documents
Determine if
solutions are The FC
outside authors the
Workforce During the SDD
Time Solution
Design
Project
The design
change
team design
requests are
Focus is on system flow
identified
customer-
specific
business
rules
3. Customer Sign-Off!
The brain’s attentional “spotlight” can focus on only one thing at a time.
• No multitasking
• Use proximity
https://www.workforcesoftware.com/services/customer-education/
TMA01 WT&A Employee Functions During build phase Project Team, Testing Team, L&D, Payroll Yes Classroom or WebEx
TMA02 WT&A Manager Functions During build phase Project Team, Testing Team, L&D, Payroll Yes Classroom or WebEx
TMA03 WT&A Administrator Functions During build phase Project Team, Testing Team, L&D, Payroll Yes Classroom or WebEx
TST01 Testing Preparation During build phase Testing Team and Project Team No Classroom or WebEx
TST02 Testing Launch At validate phase kickoff Testing Team and Project Team No Classroom or WebEx
CT101* WT&A Troubleshooting Before deploy phase System Owner / Business Analysts No WebEx
CT102* WT&A Configuration Maintenance Before deploy phase System Owner / Business Analysts No WebEx
CT120 Database Schema Essentials Before Deploy phase Reporting Specialist No WebEx
CT125 Custom Report Development Before deploy phase Reporting Specialist No WebEx
WT&A Advanced Configuration
CT103 After deploy phase System Owner / Business Analysts No WebEx
Maintenance 1
• Level 3 – Adv Configuration Maintenance (CT103) • Requires CT120 completion and Crystal Reports
TA105 WT&A Product Demonstration ACF105 ACT Product Demonstration DFT105 WorkForce 4000 Demonstration
PT104 WT&A Standard Overview ACF120 ACT User Acceptance Testing DCF110 Intro to Terminal Requirements
TA100 WT&A Core Concepts ACF150 ACT Employee Essentials TA171 WorkForce 4000 Time Entry
TA120 WT&A User Acceptance Testing ACF160 ACT Case Manager Essentials TA175 WorkForce 2200 Time Entry
• Full Release
• 3 times per year to introduce enhancements
• Patch
• As-needed basis to address bug fixes
• Ensure the timing is right • Complete a full back up • New features disabled
• Build team applies • Refresh back up to a • Determine if Update is
patches duplicate environment possible
• Consider impact on
• Upgrade environment • Updates post build phase
phased roll-out
(TEST/DEV) should not be done
implementations
• Read release notes • Update PROD • Discuss functionality with the
customer
Pre Update
1 Configuration analysis and SOW
Environment Setup/Kickoff
2 Create internal configuration environment
Customer Testing
4 Customers access to TEST to perform UAT
Production Update
5 Customer sign off and PROD updated
Post Production
6 Non PROD environments updated
Hardware is Ordered
Installation
Conduct Testing
Deployment
Copyright © 2019 WorkForce Software, LLC
Important Questions to Ask on Your Terminal Project
Terminal
Administrator Enroller
WFS LMS
https://www.surveymonkey.com/r/FunctionalImplementation
Or
workforcesoftware.com
info@workforcesoftware.com
+1 877 493 6723
Copyright and trade secret laws protect the information in this manual. Access to this material is provided only
under license or as part of an evaluation of the WorkForce Software, LLC solution specifically authorized by
WorkForce Software, LLC. In no other case are you permitted access to this information. Nor are you permitted to
disclose this information to any third party. If you have been provided this manual under any other circumstances,
you must contact WorkForce Software, LLC at +1 877 493 6723 to arrange to have this material returned
immediately.