Ranking the Area of Impact
Online stud farm management system is used for replacement of the current manila systems into Globex.
Rank the area of impact
Area of Impact |
Rank (1 to 5) |
Financial |
2 |
Social |
3 |
Strategy |
1 |
Operational |
3 |
Customer |
4 |
Summarize MOV in table format
Area of impact |
The area of impact which is ranked 1 is strategy. The business strategies of the system is making of ticket bookings throughout the web application and mobile web. There are also storing of breeders records, payment records and generates of breeders reports. |
|
Types of values |
Better: The system manages all the manual tasks better by automatic processes. It also improves the productivity of the company. |
Cheaper: The system automates the ticket booking process which results into reducing the operating cost of the stud farm. |
Appropriate metric to set target and expectations of the project stakeholders: |
||
Project Manager |
It is the expectations of the project manager are to gather of customer requirements and manage them all. It also manages the project activities and team responsibilities. |
|
Software Engineer |
It is the expectations of the software engineer are to share of idea show the system will become more effective. |
|
It is the expectations of the mobile app developer are to ensure that performance of the system is used to measure the team success and responsible for mobile app development activities. |
||
Timeframe |
The entire timeframe to meet MOV is 6 months and project manager is responsible to meet the project targets and objectives. |
Part Two:
- Scope (minimal 10 items)
- The project documents are prepared and recorded as per project requirements.
- The design of the system is done based on organizational requirements.
- There are design and implement of database modelling.
- The team members should have project logs and plan into standard format.
- Design of project architecture
- Develop of website application
- Responsible to development of user interfaces.
- Develop of the mobile app
- Design and implement of database modelling
- Testing of the proposed system
- Complete the project plan within 6 months.
- There is no adding of extra features into the online stud farm management system.
- There are no training programs for the employees.
- The project plan should complete within proposed timeframe and budget.
- There should be proper development of system to meet the organizational requirements.
- There is no possibility of delays and over budget of the project plan.
Constraints
- The system will reduce the cost of the project by its estimated value.
- The system will reduce the time required to complete the plan by around 15 days
The purpose of scope management plan in this report is to deliver the project on scheduled time. There are four processes of the project scope management such as planning, design and implementation, controlling and closure phase. The project plan captures as well as defines the project work which is to be done. After the planning, the project manager goes for design and implementation of proposed system, controlling is focused on documentation tracking, tracking and scope creep, closure phase is included of audit of the deliverables.
- People (and their roles)
Resource list |
Material list |
Project Manager |
Database |
Software Engineer |
|
Mobile app developer |
Testing tools |
Division Manager |
Development of user interface tools |
Financial Officer |
Operating platform |
Resource Manager |
Programming tools |
Application Manager |
|
Database Administrator |
|
Network Architect |
|
Network Engineer |
|
Network Administrator |
|
Programmer |
|
Programmer Analyst |
|
System Designer |
|
System Tester |
|
Risk Officer |
- Technology – any hardware, network and software needs to support the team and the client.
Hardware |
RAM, power supply, hard drive, optical drive, central processing unit, video card |
Software |
Database, Designing tools, Testing tools, operating platform |
Network |
Intranet and Ethernet |
- Facilities –
Most of the people are suited onsite where there are available to work. As the organization has all the IT facilities into the organization, therefore they are supposed to develop the system into the organization only.
- Other –
Travel Requirements |
· Travel allowance for the employee · Visa facilities available for the employees |
Training Requirements |
· Training for unskilled employees in IT · Access to the system perfectly |
- Milestones for each phase and deliverable
Milestone |
Task Name |
Start |
M1 |
Sign off the project planning |
Mon 4/9/18 |
M2 |
Sign of design and implementation documents |
Tue 6/12/18 |
M3 |
Sign off controlling |
Wed 8/22/18 |
M4 |
Sign off closure |
Wed 9/12/18 |
- Activities / Tasks
WBS |
Task Name |
0 |
Online Stud Farm Management System |
1 |
Planning phase |
1.1 |
Requirement specifications |
1.2 |
User interview |
1.3 |
Consolidate of project requirements |
1.4 |
Review the requirements |
1.5 |
Plan schedule and budget |
1.6 |
Identify the resources |
M1 |
Sign off the project planning |
2 |
Design and implementation phase |
2.1 |
Design phase |
2.1.1 |
Review and analyze the system requirements |
2.1.2 |
Identify the vendors |
2.1.3 |
Inform vendors of status |
2.1.4 |
Demonstration of system |
2.1.5 |
Review the findings |
2.2 |
Implementation phase |
2.2.1 |
Details from system demonstration |
2.2.2 |
Revise the system design |
2.2.3 |
Implement of web application and mobile application |
2.2.4 |
Implement of proper network |
2.2.5 |
Implement the system |
M2 |
Sign of design and implementation documents |
3 |
Controlling phase |
3.1 |
Risk management plan |
3.2 |
Testing plan |
3.3 |
Code review |
3.4 |
Run the development tools |
3.5 |
Run user interface tools |
3.6 |
Run database tools |
3.7 |
Programming |
3.8 |
Unit testing |
3.9 |
Build the test plan |
3.10 |
Execute the test plan |
M3 |
Sign off controlling |
4 |
Closure phase |
4.1 |
Training requirements |
4.2 |
Final project review |
4.3 |
Final sign off project deliverables |
M4 |
Sign off closure |
- Resource Assignments
WBS |
Task Name |
Resource Names |
0 |
Online Stud Farm Management System |
|
1 |
Planning phase |
|
1.1 |
Requirement specifications |
Division Manager ,Project Manager |
1.2 |
User interview |
Project Manager ,Resource Manager |
1.3 |
Consolidate of project requirements |
Application Manager ,Division Manager ,Project Manager |
1.4 |
Review the requirements |
Application Manager ,Database Administrator ,Division Manager |
1.5 |
Plan schedule and budget |
Financial Officer ,Project Manager ,Resource Manager |
1.6 |
Identify the resources |
Project Manager ,Resource Manager |
M1 |
Sign off the project planning |
Project Manager |
2 |
Design and implementation phase |
|
2.1 |
Design phase |
|
2.1.1 |
Review and analyze the system requirements |
Network Administrator ,Network Engineer ,System Designer |
2.1.2 |
Identify the vendors |
Network Architect ,Programmer Analyst |
2.1.3 |
Inform vendors of status |
Application Manager ,Database Administrator ,Division Manager |
2.1.4 |
Demonstration of system |
Application Manager ,Software Engineer ,System Designer |
2.1.5 |
Review the findings |
Software Engineer ,System Designer |
2.2 |
Implementation phase |
|
2.2.1 |
Details from system demonstration |
Network Architect ,Network Engineer ,Software Engineer ,System Designer |
2.2.2 |
Revise the system design |
Network Administrator ,Network Architect ,Network Engineer |
2.2.3 |
Implement of web application and mobile application |
Application Manager ,Database Administrator |
2.2.4 |
Implement of proper network |
Network Administrator ,Network Architect ,Network Engineer |
2.2.5 |
Implement the system |
Application Manager ,Database Administrator ,Mobile app developer ,Network Engineer |
M2 |
Sign of design and implementation documents |
Database Administrator ,System Designer |
3 |
Controlling phase |
|
3.1 |
Risk management plan |
Risk Officer |
3.2 |
Testing plan |
System Designer ,System Tester |
3.3 |
Code review |
Programmer ,Programmer Analyst |
3.4 |
Run the development tools |
Programmer ,Programmer Analyst |
3.5 |
Run user interface tools |
Network Engineer ,Programmer ,Programmer Analyst |
3.6 |
Run database tools |
Network Administrator ,Programmer ,Programmer Analyst |
3.7 |
Programming |
Programmer ,Programmer Analyst |
3.8 |
Unit testing |
System Tester |
3.9 |
Build the test plan |
System Tester |
3.10 |
Execute the test plan |
System Designer ,System Tester |
M3 |
Sign off controlling |
Project Manager ,System Tester |
4 |
Closure phase |
|
4.1 |
Training requirements |
Financial Officer ,Project Manager |
4.2 |
Final project review |
Resource Manager |
4.3 |
Final sign off project deliverables |
Financial Officer ,Project Manager ,Resource Manager |
M4 |
Sign off closure |
Project Manager |
Estimates for Each Activity / Task
Ms Project:
- The project plan should complete within proposed timeframe and budget.
- There should be proper development of system to meet the organizational requirements.
- There is no possibility of delays and over budget of the project plan.
- There should be proper design of the web and mobile application.
- There should be proper providing of training to the unskilled workers.
Risk ID |
Description |
Probability |
Impact |
Rate |
Assigned To |
Response Strategy |
Threat or Opportunity |
Risk 1 |
The plan goes over budgeted. |
90% |
5 – for high |
450% |
Financial Officer |
Mitigate- Budget plan |
Threat |
Risk 1 |
There is lack of resource plan. |
80% |
5- for high |
400% |
Resource Manager |
Mitigate- Resource management plan |
Threat |
Risk 3 |
There is possibility of out of scheduled and project delay. |
80% |
3- for medium |
240% |
Project Manager |
Mitigate- Schedule management plan |
Threat |
Risk 4 |
There is lack of project post maintenance plan. |
70% |
3- for medium |
210% |
Software Engineer |
Mitigate- Post maintenance plan |
Threat |
Risk 5 |
There is lack of implementation plan. |
60% |
3- for medium |
180% |
Network Engineer |
Mitigate-Implementation plan |
Threat |
Risk 6 |
There is breakdown of system specifications. |
50% |
1- for low |
50% |
Programmer |
Mitigate-review the system specifications before implementation and design. |
Threat |
- Statement on quality system
- Into this project plan, it is required to deliver of quality software product, web application and mobile application for stud farm. The system should such that it would satisfy the customers. Development of the product performs of needed functionalities but the customers are not satisfied. Therefore, only quality product should e=be delivered to satisfy the customer’s requirements.
- Develop the system quality by:
- A set of verification activities
Verification Activity |
When? |
Requirements based testing |
In testing phase |
Review the test specifications |
In testing phase |
Code review |
In design and implementation phase |
Training related to the verification activities |
In closure phase |
Specification review |
In controlling phase |
Testing and implementation |
In testing phase |
- A set of validation activities
Validation Activity |
When? |
Check final product to meet business needs |
In planning phase |
Determine if software is fit for use |
In testing phase |
Execution of software |
In controlling phase |
Testing techniques |
In testing phase |
Prepare the test cases |
In testing phase |
Test for error messages |
In testing phase |
Closure and Evaluation Researching for the closure checklist and project evaluation
- Annotated bibliography
For project evaluation documentation, please refer to Appendix…
- Develop a closure checklist
Closure activities |
Yes |
No |
Have documents been reviewed and approved? |
ü |
|
Requirements Traceability Matrix been checked? |
ü |
|
Handover completed? |
ü |
|
Training completed? |
ü |
|
All risks and issues closed |
ü |
|
Has testing been completed? |
ü |
- Develop a project evaluation –
Project evaluation activities |
Yes |
No |
Adequate resources |
ü |
|
Strengthen programme design |
ü |
|
Controlling and monitoring of project |
ü |
|
Promote of mechanism for current project |
ü |
|
Lessons learned documents |
ü |
Andersen, E. (2014). Value creation using the mission breakdown structure. International Journal Of Project Management, 32(5), 885-892.
Dalcher, D. (2015). Introduction to Software Project Management. Proj Mgmt Jrnl, 46(4), e2-e2.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management. Project Management Institute.
Harrison, F. and Lock, D., 2017. Advanced project management: a structured approach. Routledge.
Kerzner, H. R. (2013). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Pritchard, C. L., & PMP, P. R. (2014). Risk management: concepts and guidance. CRC Press.
Punt, A. E., Butterworth, D. S., Moor, C. L., De Oliveira, J. A., & Haddon, M. (2016). Management strategy evaluation: best practices. Fish and Fisheries, 17(2), 303-334.
Ramazani, J., & Jergeas, G. (2015). Project managers and the journey from good to great: The benefits of investment in project management training and education. International Journal of Project Management, 33(1), 41-52.
Serra, C. E. M., & Kunc, M. (2015). Benefits realisation management and its influence on project success and on the execution of business strategies. International Journal of Project Management, 33(1), 53-66.
Todorovic, M. L., Petrovic, D. C., Mihic, M. M., Obradovic, V. L., & Bushuyev, S. D. (2015). Project success analysis framework: A knowledge-based approach in project management. International Journal of Project Management, 33(4), 772-783.
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.
Zwikael, O., Chih, Y. Y., & Meredith, J. R. (2018). Project benefit management: Setting effective target benefits. International Journal of Project Management, 36(4), 650-658.