The document provides a project plan for developing a new employer website for ABcorp Global Service Centre. The plan includes an overview of the organization, project objectives, roles and responsibilities, constraints, schedule and budget. It then outlines the work breakdown structure (WBS) with tasks for project initiation, UX design, UI design, development, testing, training and closure. Gantt charts and documents cover the project plan, communication plan, risks and mitigations. The goal is to complete the project within 45 days and on budget with support from stakeholders and mitigations for risks like the coronavirus impact and dependencies.

1. ABcorp Global Service Centre
Employer Website – B2B
Dummy Project Plan (Learning Purpose)
Date: 14-03-2020
Prepared By Rajan Srivastava
Website Name: TechRajan.com
https://www.linkedin.com/in/rajan-srivastava/

2. Index
Section Link Section Linkx`
Overview Of Organization Slide 3 WBS Dictionary- Development Slide 16
Project Objective Slide 4 WBS Dictionary – QA/Testing Slide 17
Project Slide 5 WBS Dictionary – UAT (Testing & Training) Slide 18
Roles And Responsibilities Slide 6 Project Plan Slide 19
Project Constraints Slide 7 Development Plan – Gantt Chart Slide 20
Project Assumptions Slide 8 Communication Plan Slide 21
Project Schedule And Budget Estimate Slide 9 Project Risk And Mitigation Plan Slide 22
Project Scope Statement Slide 10
Project Success Criteria Slide 11
WBS Slide 12
WBS Dictionary – Project Initiation And
Planning
Slide 13
WBS Dictionary- UX Phase Slide 14
WBS Dictionary- UI Phase Slide 15

3. Overview Of Organization
Overview Of Organization: Abcorp connects specialist talent with leading employers across multiple industries and
disciplines. They have different website to get application from candidate for the job posted by consultant. The
proposed project is attempting to revolutionize the service delivery to key stakeholders and foster excellence in
recruitment industry. Getting job application is automated process and handled by different country websites but there
is no platform available for company to get jobs directly from company.
Current Situation and Problem/ Opportunity Statement: Number of job application is directly proportional to no of
jobs available into the platform and it is restricted by number of consultant and their efficiency. If company increase
number of consultant and it will also increase the cost to the company. Therefore they are going to implement a new
Employer website to avoid those limitations. Company don’t want to implement different websites for different
geographical location that is why they need one website for all location.

4. Project Objective
Objectives:
• Transform and advance quality in getting jobs from different companies.
• Enable smooth user journey with less complexity to get requirement form the clients in the form of JD or contacts.
• Provide a robust, flexible, ways of communication between client and the consultant to meet the communications
requirements.
• Upgrade technology infrastructure and support the organization.
Potential Benefits from new Employer Website:
• A modern, state-of-the-art employer website. Integration with other technologies and applications such as bulhorn.
• Modern UX/UI will be used for better user experience.
• Consultant will get more contacts and JD directly from customer without much effort.
• Number of jobs will be increased.
• Number of application will be increased in the same proportional.
• Opportunity to get new client rapidly.

5. Project
Project Information:
Project Start Date: 10-03-2020
Project End Date: 01-05-2020
Project Manager: Rajan Srivastava
Project Sponsor: Alda ( CEO ABcorp)
Project Approach:
Project Approach Phase Descripton
Project Initiation And Planning In this phase all initiation activities such
as resource allocation, planning and
approving project charter will be done.
Project Execution Project execution will be taken care by Agile Approach
Scrum
Final Project Acceptance Project will be uploaded on staging for client to review
Maintenance Maintenance will be taken care using Kanban approach

6. Roles And Responsibilities
Name Role Position Contact Information
Rajan Srivastava Project
Manager/Product Owner
Project Manager resrivastava@ABcorp.com
John Stakeholder Chief Product Officer johna@ABcorp.com
Morgan Project Sponsor Chief Executive Officer morgan@ABcorp.com
Bheem Mohan Customer Chief Consultant bm@ABcorp.com
Amisha Tester Test Engineer amisha@ABcorp.com
Vipul Drupal Developer Senior Software
Engineer
vipul@ABcorp.com
Vinay Ui Developer UI developer vinay@ABcorp.com
Jonathan Team Lead Senior Software
Engineer/Scrum Master
jonathan@ABcorp.com
Sumit SEO/Data entry Seo sumit@ABcorp.com
Sameer UX UX Sameer@ABcorp.com
Niketa Srivastava Drupal Developer Senior Software
Engineer
ns@ABcorp.com

7. Project Constraints
Resource Constraint:
• We don’t have any other free Drupal
• resource available in case of team member absent.
• We have only one tester available and get tester and it may be risk in difficult situation. Sukesh can do manual
testing if required.
Budgetary Constraint:
• Salary scheme for employees will be based on the current market situation and total employee costs will be at
around 30% of the project budget. (comparing resource cost of Ireland and India of same experience)
• Additional cost for broadband, server software/hardware are $1000 for one year.
Schedule Constraints:
• Project requires to be implemented within 2 months or less time frame and the
existing services have to be maintained continuously.
• Project team doesn’t work on weekends.

8. Project Assumptions
Resource Assumption:
• Project staff resources will be available when and as they are needed.
• Required hardware/software resources will be available when and as they are needed.
Delivery Assumption:
• Deliverables will be subject to no more than a specific number of review cycles and limited by sprint review
• There is no change in scope until there is agreement between project team and stakeholder and deadline will be
adjusted.
• The scope of the project is limited to that described in the project scope statement.

9. Project Schedule And Budget Estimate
Phase Estimated Time Duration
Project Initiation And Planning 7 days
UX Phase 7 Days
UI Design 14 Days
Development 27 Days
Testing 8 Days
UAT 2 Days
Final Go Live 1 Day
Testing And Training 2 Day
Cost Areas Cost $
Employee Cost 20000
Server Cost/Year 1000

10. Project Scope Statement
This project is for consultant to help them to get more business from client in terms of their contact or job description
from specific company. This project will serve contents and services for 10 countries. Contact us page will have address
relevant to particular country. Form detail need to be sent to relevant consultant belong to relevant company. People
from different country will see blog posts/content relevant to their country or blog tagged as Global. Employer can get
the salary guide for their country once they submit their information on portal.
This website should also serve to jobseeker. We can enhance this functionality in the future.
With In Scope:
1- Response rate of server should be below 2 second
2- There should not be any vulnerability in the Drupal version or plugin you are going to use.
3- All services must be secure with restricted access rights.
4- A 10 days training period will be given to the client on how to use the system.
5- A user manual for the staff will be available.
Out Of the Scope:
1- All data entering, registration of users etc will be undertaken by consultant.
2- All advertising and marketing required for launch and on an ongoing basis will not be
delivered or paid for by this project .

11. Project Success Criteria
Our goal is to complete the project within 45 days. The initial budget will not be exceeded. In order to meet this goal
each team member must put required work hours per day in Jira System. Deliverables must be completed on time and
within the sponsor’s specifications.
In order to complete the project within time and budget, we need 100% support from customer when required without
delay.
1- Customer has to available in every sprint review without fail.
2- Any changes given by client has to go into product backlog and will be treated as change request.
3- In case of entertaining change request with scope change, deadline has to change and revaluation of project is
required.
4- If suggested changes goes post launch, it will be entertain through Kanban approach.
5- If changes are big in size and require more than a week to complete, we will take it in next phase of project.

12. Employer Website WBS
Project
Initiation And
Planning
UX Phase UI Phase Development Testing UAT Go Live Testing And
Training
Final
Closure
Plan
Budget
Sign-off
Brainstorm
Requirement
Take
Measures
Design
Wireframe
Customer
Approval
Create
Design
Document
Study
Brand
Guideline
Create
PSD
Customer
Approval
On PSD
Create
Linked
Html
Customer
Approval
On Linked
Html
Functional
Developm
ent
Adding
Content
Functional
Testing
Integration
Testing
Performan
ce Testing
QA sign-off
Deplo
yment
on
Stagin
g
Server
QA
Sign-
off
Custo
mer
Sign-
off
Deploy
ment
On Live
Server
Domain
Pointing
Functional
Testing
Integration
Testing
Performan
ce Testing
QA sign-off
Customer
Training
Final
Sign-
off
from
custom
er
All
Resour
ces Has
been
release
d
All documentation will be
forward to customer

13. WbS Dictionary – Project Initiation And Planning
WBS Code WBS-Item Responsible Deliverable Description Days
1.0 Project Initiation
And Planning
Project Manager Approved Project
Charter
7
1.1 Analysis Project Manager Analysis Report Needs analysis as
a formal process
to gather
information
4
1.2 Project Charter Project Manager Project Charter
Document
Objective of the
project acceptable
by stakeholder
2
1.3 Project Approval Project Manager Accepted Project
Document
Project manager
will present the
document and get
the approval from
stakeholder
1

14. WBS Dictionary- UX Phase
WBS Code WBS-Item Responsible Deliverable Days
2.0 UX Phase UX Team Website wireframe 7
2.1 Brainstorm
Requirement
UX Team 1
2.2 Take measures UX team UX requirement doc 1
2.3 Design wireframe UX team Linked wireframe 4
2.3.1 Home Page UX Team Home Page wireframe 0.5
2.3.2 Our Expertise Page UX team Our Expertise
WireFrame
0.5
2.3.3 Job Page flow UX team Job Page wireframe 2
2.3.4 Contact Us Page UX team Contact us wireframe 0.5
2.3.5 Lastest Inside And
advice
UX team Wireframe 0.5
2.4 Customer Approval Stakeholder UX Acceptance
document
1

15. WbS Dictionary- UI Phase
WBS Code WBS-Item Responsible Deliverable Days
3.0 Study Brand Guideline UI Team 14
3.1 Study Brand Guideline UI Team 2
3.2 Create Design
Document
UI Team Design document 2
3.3 Create PSD UI Team PSD 9
3.3.1 Home Page UI Team Home Page PSD 2
3.3.2 Our Expertise Page UI Team Our Expertise PSD 1
3.3.3 Job Page flow UI Team Job Page PSD 2
3.3.4 Contact Us Page UI Team Contact us PSD 2
3.3.5 Lastest Inside And
advice
UI Team PSD 2
Note: We will create remaining element in WBS dictionary using the same way as mentioned above.

16. WBS Dictionary- Development
WBS Code WBS-Item Responsible Deliverable Days
4.0 Development Development Team 27
4.1 Create Linked Html Html Dev Team Html file 12
4.1.1 Home Page Html Dev Team Html file 3
4.1.2 Our Expertise Page Html Dev Team Html file 2
4.1.3 Job Page flow Html Dev Team Html file 3
4.1.4 Contact Us Page Html Dev Team Html file 2
4.1.5 Latest Inside And advice Html Dev Team Html file 2
4.2 Customer approval Stakeholder Approval document 1
4.3 Functional Development Drupal Developer Application 15
4.3.1 Our Expertise Page Drupal Developer Application 1
4.3.2 Job Page flow Drupal Developer Application 7
4.3.3 Contact Us Page Drupal Developer Application 2
4.3.4 Latest Inside And advice Drupal Developer Application 3
4.3.5 Home Page Drupal Developer Application 1
4.4 Adding Content Data Entry Content 1

17. WBS Dictionary – QA/Testing
WBS Code WBS-Item Responsible Deliverable Days
5.0 QA Tester Bug-free product 6
5.1 Functional Testing Project Manager Analysis Report 2
5.2 Integration testing Project Manager Project Charter
Document
2
5.3 Performance
Testing
Project Manager Accepted Project
Document
2

18. WBS Dictionary – UAT
WBS Code WBS-Item Responsible Deliverable Days
6.0 QA/Server Tester/Server/Dev
eloper
Bug-free product
On UAT
2
6.1 Deployment on
UAT
Server
Administrator
Product on
staging Server
1
6.2 Functional+Integr
ation+performace
testing
Tester Bug-free product 1
WbS Dictionary – Testing And Training
WBS Code WBS-Item Responsible Deliverable Days
7.0 Testing And Training Tester Bug-free Live product 2
7.1 Testing On Live Tester Bug-free product On
Live Server
1
7.2 Product Training to
customer
Tester/customer Product
documentaion
1

19. Project Plan
Task Start Date Days To Complete
1.1 10-Mar 4
1.2 17-Mar 2
1.3 18-Mar 1
2.1 19-Mar 1
2.2 20-Mar 1
2.3.1 23-Mar 1
2.3.2 23-Mar 1
2.3.3 24-Mar 2
2.3.4 25-Mar 1
2.3.5 25-Mar 1
2.4 26-Mar 1
3.1 23-Mar 2
3.2 25-Mar 2
3.3.1 26-Mar 2
3.3.2 27-Mar 1
3.3.3 30-Mar 2
3.3.4 31-Mar 2
3.3.5 01-Apr 2
4.1.1 28-Mar 2
4.1.2 31-Mar 2
4.1.3 01-Apr 2
4.1.4 06-Apr 2
4.1.5 08-Apr 2
4.2 09-Apr 1
4.3.1 13-Apr 1
4.3.2 13-Apr 7
4.3.3 13-Apr 2
4.3.4 14-Apr 2
4.3.5 15-Apr 2
4.4 20-Apr 1
5.1 21-Apr 2
5.2 23-Apr 2
5.3 28-Apr 2
6.1 30-Apr 1
6.2 30-Apr 1
7.1 01-May 1
7.2 01-May 1

20. Development Plan – Gantt Chart
10-Mar 20-Mar 30-Mar 9-Apr 19-Apr 29-Apr 9-May
1.1
1.3
2.2
2.3.2
2.3.4
2.4
3.2
3.3.2
3.3.4
4.1.1
4.1.3
4.1.5
4.3.1
4.3.3
4.3.5
5.1
5.3
6.2
7.2

21. Communication Plan
Meeting Frequency Facilitator Attendee
Daily Stand-up Daily Scrum Master Development Team
Sprint Planning Bi-Weekly Scrum Master Scrum Master, Product
Owner/Project Manager,
Development Team
Sprint Review Bi-Weekly Scrum Master Scrum Master, Product
Owner/Project Manager,
Development Team,
Stakeholder
Sprint Retrospective Bi-weekly Scrum Master Scrum Master, Product
Owner/Project Manager,
Development Team
Board Meeting Bi-weekly Project Manager/product
owner
Project Manager,
stakeholder, Board Of
Directors

22. Project Risk And Mitigation Plan
Description Severity
Category
Probability Proposed Actions
Coronavirus can have big impact on team
member’s health can result delay in delivery.
1 2 Proposing to give work from home
option with proper control to reduce
the risk of this threat.
Client presence in sprint review meeting for
frequent feedback is mandatory for delivery
validation.
2 3 We need to put SLA between customer
and Development team to get the
required information on time and
presence in meeting
Only one UI/UX developer. So no backup resource
is available for this project.
3 4 No Leave will be approved when they
are working on the project.
Dependency on external software: Client want to
have one single url for different country page. We
need to use maximind to get ip detail from
customer and serve personalized content. It will
not give correct visitor location every time and it is
big risk
1 2 We will convince customer to get
approval to have different page for
different country
Severity Level: (Catastrophic: 1, Critical: 2, Marginal: 3, Negligible:4)
Frequency Level: (Frequent: 1, Probable: 2, Occasional: 3, Unlikely: 4, Improbable:5, Eliminated:6)

23. Thank You