Managing Complex Project
Managing Complex Project
www.universityexpert.pk
Group Members:
UNIVERSITY OF LAHORE
ACKNOWLEDGEMENT
We would like to thank our instructor/supervisor Syed Abbas Raza for believing in us and
supporting us in whole semester. Without his help, guidance and critique we would not have been
able to successfully complete this project. His greater expectations from us kept us going to achieve
more and his supervision has helped us to be better thinkers.
Our parents have been our constant source of motivation and courage. Their trust in us and their
belief in us has kept us going and helped us in achieving what otherwise would have been quite
difficult. We are glad to have parents who have always encouraged us in following our dreams and
their teachings are what have made us, what we are today.
Our time spent with our classmates has always been really helpful, educating and refreshing. They
have helped us in times when we were totally stuck and could not find a way out.
Finally, we would like to thank the Almighty Allah for his help and grace which allowed us to
move ahead in successfully completing our Masters in Project Management.
Thanking You,
Table of Contents………………………………………………………………………………………Page No.
1. Project Initiation………………………………………………………………..
1.1. Establish the Project Charter……………………………………………………………….
1.2. Appoint the Project Team……………………………………………………………………..
1.3. Stakeholders…………………………………………………………………………….
1.4. Set up the Project Office……………………………………………………………………….
1.5. Perform Phase Review…………………………………………………………………………..
2. Project Planning…………………………………………………………………
2.1. Create a Project Plan………………………………………………………………………………
2.2. Create a Scope Plan
2.3. Create a Resource Plan………………………………………………………………………….
2.4. Create a Cost Plan………………………………………………………………………………….
2.5. Create a Schedule Plan……………………………………………………………
2.6. Create a Quality Plan…………………………………………………………………………….
2.7. Create a Risk Plan………………………………………………………………………………….
2.8. Create a Communications Plan…………………………………………………………
2.9. Create a Procurement Plan…………………………………………………………………
2.10. Perform Phase Review…………………………………………………………………………
3. Project execution and Controlling………………………………………..
3.1. Build Deliverables……………………………………………………………………
3.2. Monitor and Control………………………………………………………………..
3.3. Perform Schedule Management……………………………………………………………
3.4. Perform Cost Management………………………………………………………………...
3.5. Perform Quality Management……………………………………………………………
3.6. Perform Risk Management………………………………………………………………..
3.7. Perform Procurement Management………………………………………….....
3.8. Perform Communications Management………………………………………
4. Project Closing………………………………………………………………..
4.1. Perform Project Closure……………………………………………………………………
4.2. Review Project Completion……………………………………………………………..
5. Conclusion……………………………………………………………………….
INTRODUCTION:
An Automated platform to make admission process smooth and automated i.e., one stop solution
for applying in multiple universities of Pakistan through one single application form along with
guidance system, entry test preparation (Expert book), university comparison, counselling
sessions, aggregate calculator and weekly informative videos about universities. A module of
merit prediction I-e predicating if the student can get admission in a university by comparing it
to current students’ data studying in that institution. Complete guidance for student to choose
and apply in best suitable university by going through an expert system. A website (for user
interface) and automatic form filling module using python scripts so student has to fill just one
form and all the applying process is done through that automation.
OBJECTIVE:
The aim of this project is to discuss the life cycle models implemented. The life cycle process is
to be used to explore the potential for minimizing negative impacts through an increase in the use
of KNOWLEDGE AREAS OF PROJECT MANAGEMENT in IT project implementation.
1-Project Initiation
Initiation began when group members conceived an idea of putting an IT project as a startup.
This idea might be internally generated or may be a consequence of customer’s requirements.
Inauguration of the project was done and all the social media channels which reported initiation
were buried under the inaugural stone in the wall.
Initiation completed when the project charter and preliminary scope statement were completed
through the feasibility study.
The outline of the project charter was prepared keeping in line with the expectations of
stakeholders. In the outline, the constraints like cost, scope, time and quality were accounted.
1.2. Appoint the Project Team
Initiation ended after the appointment of a project manager. The project manager was
delegated with authority and direction necessary to start planning.
Project Team
Project team is also made for this project and these were;
§ Project Manager
Haris
§ Team Leader
Iqra
§ Main Team Members
1.Ujala
2.Hamid
1.3. Stakeholders
Ø Stakeholder Register:
2- Project Planning
In Scope:
This project is focused on making a one stop platform to address all the above issues which
include: Each point here is a user story which needs to be fulfilled.
Out of Scope:
The things that are not in scope are as follows:
• Admissions in MS programs
• Admissions in universities outside Pakistan
• Use of node or react language for any kind of programming
• Any other functionality module which is not mentioned in scope.
Main Deliverables:
Purpose:
FR.01 The system should receive a filled form to apply on behalf of student.
FR.02 The system should receive student’s credentials for calculating merit.
FR.03 The system should compare universities when they are selected from
dropdown.
FR.04 The system should take the online test when selected by the student.
FR.06 The system should give tracking after filled form is received.
FR.07 The system should predict the merit of university when student enter the
credentials.
Non-Functional Requirements
Non-functional requirements are there to define the quality of the attributes and functions
available in the system. These are very useful to check the usability and effectiveness of the
system. Non-functional requirements for this system are as follows:
Software Architecture:
2.3 Create a Resource Plan
1 PROJECT INITIATION 4
1.1 DEFINE PROJECT OBJECTIVES 2
AND SCOPE
1.2 CONDUCT INITIAL RESEARCH 2
AND REQUIREMENTS
2 PLANNING AND DESIGN 10
2.1 DEVELOP A DETAILED PROJECT 1
PLAN, INCLUDING TIMELINES
AND MILESTONES
2.2 CONDUCT USER RESEARCH 1
AND CREATE USER PERSONAS
2.3 DESIGN THE WEBSITE’S 2
INFORMATION ARCHITECTURE
AND WIREFRAMES
2.4 CREATE VISUAL DESIGN AND 2
USER INTERFACE ELEMENTS
2.5 FINALIZE THE TECHNOLOGY 2
STACK
3 DEVELOPMENT 16
3.1 SETUP DEVELOPMENT 2
ENVIRONMENT AND
INFRASTRUCTURE
3.2 DEVELOP THE FRONTEND 10
COMPONENTS AND TEMPLATES
3.3 IMPLEMENT THE BACKEND 10
FUNCTIONALITY AND
DATABASE STRUCTURE
3.4 INTEGRATE CONTENT 4
MANAGEMENT SYSTEM (CMS)
3.5 CONDUCT REGULAR TESTING 12
AND QUALITY ASSURANCE
THROUGHOUT THE
DEVELOPMENT PROCESS
4 CONTENT CREATION AND 8
INTEGRATION
4.1 CREATE AND GEATHER 4
WEBSITE CONTENT (TEXT,
IMAGES, AND VIDEOS ETC.)
4.2 INTEGRATE THE CONTENT INTO 4
WEBSITE STRUCTURE
4.3 OPTIMIZE CONTENT FOR 2
SEARCH ENGINE OPTIMIZATION
(SEO) AND USABILITY
4.4 PERFORM FINAL CONTENT 2
REVIEW AND REVISION
5 TESTING AND LAUNCH 4
5.1 CONDUCT THOROUGH TESTING 3
OF THE WEBSITE’S
FUNCTIONALITY with test cases
5.2 ADDRESS ANY IDENTIFIED 1
BUGS OR ISSUES
5.3 PERFORM USER ACCEPTANCE 1
TESTING
5.5 DEPLOY THE WEBSITE TO 1
PRODUCTION ENVIRONMENT
6 POST LAUNCH SUPPORT AND 6
MAINTENANCE
6.1 PROVIDE ONGOING TECHNICAL 52
SUPPORT AND MAINTENANCE
6.2 MONITOR WEBSITE ONGOING
PERFORMANCE AND ADDRESS
ANY ISSUES
6.4 CONDUCT PERIODIC SECURITY ONGOING
AUDITS AND UPDATES
TOTAL 48
1 PROJECT INITIATION −
2 PLANNING AND DESIGN 20,000
3 DEVELOPMENT 145,000
4 TESTING AND LAUNCH 27,000
POST LAUNCH SUPPORT
5 AND MAINTENANCE 63,000
TOTAL 255,000 PKR
Work Breakdown Structure:
The quality management plan describes how the project management team will
implement the performing organization’s quality policy.
To make sure quality is met not only for reducing cost of project but also for functionality of
website test cases were performed as well.
Quality improvement approach
To improve the quality of the project’s processes many steps were used like:
• Weekly meeting will be called between the project manager and project team so that
difficulties which might affect the project were removed.
• Reports on cost performance were issued weekly to analyze the cost regarding quality.
Control Charts and Scatter plot were made to analyze project, team
members and schedule performance.
2.7 Create a Risk Plan
Risk register
The risk register contained information on threats and opportunities that might impact the project.
Technical risk
Resource risk
Inflation
Natural disaster
Software failure
Communication failure
Power blackout
• Statement: Power backout or load shedding is common in country and it affects every work
• Impact: High
• Probability: 30%
• Response: make sure to have a good power backup.
In these meetings we will inform our stakeholders about the progress of the project
on a weekly and monthly basis. If any change will occur in the project, we will inform
our stakeholders in time.
Procurement Process:
This procurement plan sets the procurement framework for this project. It will serve as the
guideline for managing procurement throughout the life of the project and will be updated when
required.
Total of 10 deliverables were to be achieved base on each user story mentioned in scope and each
sprint was assigned of one user story.
Sprint Goal: User should be able to Sign In/Sign Up and fill the form.
User Stories:
Task Breakdown:
Sprint Backlog:
Effort Estimation:
Developer 3: User profile pages, edit profile and view profile page.
Daily Stand-ups:
Sprint Review:
Sprint Retrospective:
To ensure the tasks compiled with the agreed upon project restrictions, the execution of the
project was closely tracked and supervised by the planning as well as the QA/QC teams.
The project’s operations were all organized in accordance with the needs of the process
and distribution of available resources.
3.4 Perform Cost Management
The required finances were secured well in advance of the cash flow schedule’s
requirement.
There were modifications beyond the originally established scope and procedures
throughout the project’s execution for a variety of causes such as the lack of coordination
between various tasks. These requests of changes were correctly carried out and
documented.
The QA/QC department ensured that all the parameters laid down in the standard
operating procedures are met correctly.
For quality management each user story had gone through a test case to make sure the
functionality works perfectly and there is no flaw in the process.
Following test cases were performed to make sure the quality was met under monitor and
control tab.
Test Case 1:
Comments
Module works as desired
Passed Failed Not Executed
Test Case 2:
2. User clicks on “Sign in” and enters the incorrect A message of “incorrect
Username and password through which he didn’t signed up. username/password” is shown as
response from the system.
Comments
Module works as desired
Passed Failed Not Executed
3.7 Perform Risk Management
A risk evaluation was conducted prior to the project’s launch, and a risk register was kept. All
necessary precautions were taken in order to mitigate potential hazards and increase potential
benefits.
The procurements were listed and resources identified. The vendors sere selected and
orders placed.
The required things were received and checked as per ordered specifications.
4 Project Closing
The endeavor was finished after the assurance tests were completed and an optimized website
integrated with banks payment gateway was handed over to customer.
• Confirm completion of all deliverables according to the project scope and requirements.
• Conduct a final review of the project to ensure that all objectives have been met.
• Conduct all kinds of testing planned for the project.
• Document any outstanding issues or lessons learned during the project.
• Prepare and distribute a final project report summarizing key achievements, deliverables,
and performance metrics.
• Share the final deliverables with stakeholders, ensuring they are accessible and properly
documented.
• Obtain sign-off or acceptance from the project sponsor or client, indicating their
satisfaction with the delivered product or service.
• Conduct a post-implementation review to evaluate the project's overall success, including
the effectiveness of project management processes and methodologies.
• Celebrate the successful completion of the project and acknowledge the contributions of
the project team members.
5 Conclusion
University Expert is an automated platform to make admission process smooth and automated i.e.
one stop solution for applying in multiple universities of Pakistan through one single application
form along with guidance system, entry test preparation (Expert book), university comparison,
counselling sessions, aggregate calculator and weekly informative videos about universities.
Complete guidance for student to choose and apply in best suitable university by going through an
expert system.
References
[1] Muhammad Ahmad Malik. Founder Education Everest (2017). Educational Website.
Retrieved September 10, 2019, from https://www.educationeverest.com/.
[2] Ghulam Ali. Founder Ilm Ki Dunya (2004). Educational Website. Retrieved August 12, 2018,
from https://www.ilmkidunya.com.
[3] Yousuf Almas. Founder EDUVISION (2001). Educational Website. Retrieved August 16,
2019, from https://www.eduvision.edu.pk.
[4] David Coleman. CEO College Board (2012). Educational not for profit Organization. Retrieved
August 16, 2019, from https://www.eduvision.edu.pk.
[5] Riaz Haqq. Haqq’s Musings (2015). Data Driven Blog. Retrieved
October 14, 2019, from http://www.riazhaq.com