Developing RALS Roistering System: Budget, Schedule, Challenges And Risks

Project Scope and Requirements

This paper discussed about the show Riverina Agricultural and Lifestyle that mainly arranged to display different types of agricultural events, different lifestyle products. It is mainly identified that different manual techniques are get utilized by organization to manage the large number details that is not in proper manner so the Globex business that mainly aligned with the show which develop the roistering system.

In this paper, information about budget, project schedule, management plan and different resources are discussed. It is also identified that this paper elaborates about different challenges and risks identified in the project to develop the roster system of RALS.

Customer: It mainly identified about a developed system that is helpful to mitigate all related queries that are mainly raised by people.

Strategy:  It is found that the system is more beneficial to track various kinds of volunteer’s details to track them.

Social: the developed system is mainly found to more advantageous for doing the communication with different clients

Operational: the proper utilization of roistering system mainly helps to store significant information of volunteers in the system that leads to make the different organizational operations easier.

Financial: the roistering system that mainly developed by Globex become helpful to provide large quantity of return money that is mainly invested by business.

In the context of RALS Roistering system project, the two types of project value are listed below:

Better: this RALS venture checked the advancement of different framework to expand the work proficiency with the help of data administration.

Cheaper: RALS task mainly helps to deal with various data that mainly diminish all types of general costs related to general cost of data framework administration.

Rank	Impact	Metrics	Timeframe
1	Financial	Revenue and Money Profit era	6 months
2	Customer	All clients returning to association based on different administrative work.	2 months
3	Operational	Reduction of consumption of time to finish different hierarchical techniques.	2 months
4	Strategy	All volunteers need to have the capacity for getting associated with all clients	1 month

Define the scope: The RALS ticketing system advancement techniques helps to build up the project team and different materials to develop all types of project operations.

Requirements: All project requirements are shown in the table format:

Resource Name	Type
Budgeter	Work
Computer Devices	Material
Documenter	Work
IT Engineer	Work
Network Components	Material
Planner	Work
Project Manager	Work
Storage	Material
System Analyst	Work
Tester	Work
Wireless routers	Material

The in-scope of project includes:

• Development of RALS Rostering system of the Globex business
• Incorporating of different volunteers details includes different personal details, qualification details and different additional details
• Proper assistance of documentation of both functional and non-functional project requirements
• Completion of the project within the timeframe of 244 days.

The out-scope of project includes:

• System maintenance is mainly related based on the service quality along with data security that mainly not discussed.
• Training documentation is not provided to all employees of Globex 

Deliverables: The deliverables of this project are listed below:

• To test this system, proper testing plan of the report is created
• Documentation of the development phase
• Documentation of budgetary plan
• Creation of training manual
• Scope verification techniques
• Preparation of system requirements report

The acceptance criteria of this system discuss about the meeting of different requirements along with the demands and needs of clients. Apart from that, it also assists to minimize about response time to have proper solution of different queries. 

Material resources: Different types of technical requirements to complete the project according to pre-determined results discuss about secondary storage, operating system, display adapter etc.

Project Schedule, Management Plan, and Resources

Human resource: The people who are needed to complete the project within the time include system developer, project manager, business analyst, system analyst, project sponsor, investment manager etc. 

Resource Name	Type	Material Label	Initials	Group	Max. Units	Std. Rate	Ovt. Rate	Cost/Use	Accrue At	Base Calendar
Developer	Work		D		100%	$80.00/hr	$0.00/hr	$0.00	Prorated	Standard
System analyst	Work		S		100%	$90.00/hr	$0.00/hr	$0.00	Prorated	Standard
Accountant	Work		A		100%	$85.00/hr	$0.00/hr	$0.00	Prorated	Standard
Project manager	Work		P		100%	$90.00/hr	$0.00/hr	$0.00	Prorated	Standard
Tester	Work		T		100%	$70.00/hr	$0.00/hr	$0.00	Prorated	Standard
Executive sponsor	Work		E		100%	$75.00/hr	$0.00/hr	$0.00	Prorated	Standard
Requirement analyst	Work		R		100%	$65.00/hr	$0.00/hr	$0.00	Prorated	Standard
Risk manager	Work		R		100%	$70.00/hr	$0.00/hr	$0.00	Prorated	Standard

Task Name	Duration	Start	Finish	Resource Names
RAILS Rostering System	244 days	Mon 9/25/17	Thu 8/30/18
Specification determination	23 days	Mon 9/25/17	Wed 10/25/17
Undertaking feasibility study for the different manual system	6 days	Mon 9/25/17	Mon 10/2/17	Project manager, Requirement analyst
Business needs identification	6 days	Tue 10/3/17	Tue 10/10/17	Requirement analyst
Creation of SRS document	7 days	Wed 10/11/17	Thu 10/19/17	Project manager, Requirement analyst
Meeting arrangement	4 days	Fri 10/20/17	Wed 10/25/17	Project manager
Milestone: completion of specification determination	0 days	Wed 10/25/17	Wed 10/25/17
Development team selection	38 days	Thu 10/26/17	Mon 12/18/17
Development of vendor selection	11 days	Thu 10/26/17	Thu 11/9/17	Accountant, Project manager
Checking development history of the vendors	12 days	Fri 11/10/17	Mon 11/27/17	Executive sponsor, Project manager
Development task scheduling	7 days	Tue 11/28/17	Wed 12/6/17	Developer, Project manager
Budget planning for development	8 days	Thu 12/7/17	Mon 12/18/17	Accountant, Executive sponsor, Project manager
Milestone: completion of team selection	0 days	Mon 12/18/17	Mon 12/18/17
Designing phase	69 days	Tue 12/19/17	Fri 3/23/18
Module improvement for volunteer management	21 days	Tue 12/19/17	Tue 1/16/18	Developer, Project manager
First prototype development	17 days	Wed 1/17/18	Thu 2/8/18	Developer
Improvement within new system installation	15 days	Fri 2/9/18	Thu 3/1/18	Developer, Project manager
Determining the needs of the system	16 days	Fri 3/2/18	Fri 3/23/18	Project manager, System analyst
Milestone: Completion of design phase	0 days	Fri 3/23/18	Fri 3/23/18
System implementation system	33 days	Mon 3/26/18	Wed 5/9/18
Different business objectives development	13 days	Mon 3/26/18	Wed 4/11/18	Developer, Requirement analyst
Amendments within the part of the system that is implemented	12 days	Thu 4/12/18	Fri 4/27/18	Developer, Project manager
Using compatible software and hardware	8 days	Mon 4/30/18	Wed 5/9/18	Accountant, Project manager, System analyst
Milestone: Completion of system implementation system	0 days	Wed 5/9/18	Wed 5/9/18
Testing phase	26 days	Thu 5/10/18	Thu 6/14/18
Identifying test cases as well as test plan	7 days	Thu 5/10/18	Fri 5/18/18	Tester
Testing the developed system	8 days	Mon 5/21/18	Wed 5/30/18	Project manager, Tester
Information system analysis from the data	9 days	Thu 5/31/18	Tue 6/12/18	Executive sponsor, Project manager
Results documentation	2 days	Wed 6/13/18	Thu 6/14/18	Project manager
Milestone: acceptance of the test results by client	0 days	Thu 6/14/18	Thu 6/14/18
Risk management phase	30 days	Fri 6/15/18	Thu 7/26/18
Assessment as well as risk identification	11 days	Fri 6/15/18	Fri 6/29/18	Project manager, Risk manager
Presenting risks impact	7 days	Mon 7/2/18	Tue 7/10/18	Risk manager
Risks mitigation	8 days	Wed 7/11/18	Fri 7/20/18	Project manager, System analyst
Impact of the risk registering	4 days	Mon 7/23/18	Thu 7/26/18	Project manager, Risk manager
Milestone: Acceptance of the risk document by the client	0 days	Thu 7/26/18	Thu 7/26/18
Closure of the project	25 days	Fri 7/27/18	Thu 8/30/18
Evaluating roistering system functions	13 days	Fri 7/27/18	Tue 8/14/18	Executive sponsor, Project manager
Final developed product roll out	12 days	Wed 8/15/18	Thu 8/30/18	Project manager
Milestone: Completion of closure phase of the project	0 days	Thu 8/30/18	Thu 8/30/18

WBS	Task Name	Expected Date
0	RALS Roistering System	Fri 9/23/16
1	Achievement of specific determination	Wed 10/25/17
2	Proper selection of team based on project requirements	Mon 12/18/17
3	Completion of design phase	Fri 3/23/18
4	Closure of system implementation system	Wed 5/9/18
5	Acceptance of t risk document	Thu 7/26/18
6	Completion of closure phase of the project	Thu 8/30/18

Some of project assumptions that are made in this project are mainly listed below:

Budget: the project manager mainly estimates the exact budget that required executing different project activities. Initially, it is set that the estimated budget is $400,000, where as $298.040 will be required to complete all activities and $200, 00 will be required for all other materials including different additional resources.  

Time: the project manager also predicted the entire required time to complete all project activities to develop the roster system. The time estimated by the project manager is near about 244 days.

Resources: the project team also assumes about different project resources that is mainly needed to develop the RALS system. Hence, it is also deduced that proper assumptions of project resources mainly helps to have proper summary that mainly needed to calculate the budget.

No.	Rank	Risk	Description	Category	Root Cause	Triggers	Potential Responses	Risk Owner	Probability	Impact	Status
R44	1	System failure	If system is not get installed in proper manner inside the business that will increase the risks number along with challenges	Technical risk	The lack-age of proper knowledge of system developer, the installation techniques are not maintained properly.	The particular system is not installed properly by taking require time.	This particular system is require to be installed in proper manner.	Project manager	Medium	High	Set up in 1 week
R19	2	inappropriate budget estimation	The estimation of budget by project manager is not occurring in accurate manner.	Financial risk	They also assume the create budget will not be accurate due to in experienced project manager to do analysis of market share.	Different budgetary issues that mainly occurs because of in appropriate market analysis.	Suitable budget estimation are require to be done after the market analysis in effective manner.	Financial manager	Medium	High	Set up in 3 weeks
R8	3	Inappropriate scheduling	The project manger does not gather better understanding about the project goals and objectives due to which the created schedules will not be exact.	Project risk	All types of scheduling related risks occur because of unacceptable amount of information of client’s requirement.	In appropriate understanding about project created differed types of scheduling risks.	The project manager also needed to analyse and also determine all project requirements having the proper understanding.	Project manager	Medium	High	Set up in 2 week
R32	4	Improper management	Inaccurate management of differed project activities created various challenges.	Project risk	It occurs because of lack age of proper experience of related manager.	Improper knowledge of project manager created weak project management.	The project manager also manages the project by maintaining exact strategies including exact methodologies.	Project managers	Medium	High	Set up in 1 week
R28	5	Resources	Unacceptable use of project resources	Resource risk	Improper uses of differed resources because of proper experience.	Correct techniques used for resources management are not mainly used.	The organization must not gathers experience of project managers	Project manager	Medium	Medium	Set up in 1 week

Probability of occurrence	Impact of occurrence
	Very low	Low	Medium	High	Very high
Very low
Low
Medium			Resource risk	Technical risk
High			Schedule risk	Technical risk
Very high

It is mainly recognized that numbers of key elements that are considered become more helpful; to deliver various types of quality based services to all customers including service culture, employee engagement, customer experience etc. Moreover, it is also identified that different types of elements are used to form service culture and different elements are vision, mission, leadership and also various types of organizational norms.

The projected system is identified to be an effective engaging more people with the organization. It is identified that service quality is mainly depends of strategic plan that mainly get utilized by the organization for the proper system installation and maintaining various objectives and goals of the organization.

Project Name:RALS Rostering System	Project manager Name: (<<Name of the Student>>)
Sl.No	Quality related issues that are possible	Mitigation time	Method for mitigation	Owner	Status
1	Various documents are reports are mainly prepared by completing all phases is not having appropriate quality and adequate information.	2 moths	Inspection	Project manager	Open
2	Both the software and hardware materials are mainly get utilized to develop the project that is found to be of low quality.	3 months	Inspection	Project manager	Open
3	The organizational staffs are not very much skilled that results the works done by them have various quality related issues.	2 months	Inspection	project manger	Open

The verification activities that help to elaborate all the proposed system meet different conditions and regulation of system and organization. It is mainly identified that all criteria are needed to get fulfilled by the system installed by Globex 

The validation testing is needed to be done to elaborate the proposed system quality in this project development phase. The implemented testing method is utilized to meet different needs to businesses as well as clients.

Article 1: In this paper of roles of monitoring and evaluation in projects”,  Boulmetis and Dutwin (2014) discussed that various project numbers that are associated with third work countries fails because of lack understanding of needs evaluation and proper monitoring. The researchers also highlighted the implication of different project monitoring techniques and proper evaluation of successful completion of project. Moreover, in this paper it also discussed about various common constraints that helps to overcome all related problems. Apart from that, evaluation is a technique that mainly helps to determine the sustainability, relevancy and the impacts of activities based on project performance.

Article 2: This paper mainly discussed about the project management roles to achieve success. Heagney (2016) discussed that roles of different types of project management activities to implement the project is mainly established in different areas that also includes cost controlling, planning, quality, time etc. The researchers mainly identified to determine the overlapping that exists between the project management techniques and the project definition. The researchers also identified that people that involves within the project and different project management techniques based on the objectives, expectations as well as their influences. On the other hand, it also helps to demonstrate the appreciation of the distinction between project management and project to bring the advanced possibilities of project success.

Article 3: In this paper, it mainly reflects about the risk identification techniques by project manager (Anca, Cezar & Adrian, 2015). However, it is mainly identified that project risks is mainly defined as an uncertain events that causes either negative or positive impact based on project objectives. Different risks conditions mainly include various characteristics of project that mainly helps to contribute in the project, lack age of integrated systems and dependencies of different external participants. Apart from that, it is also identified that the risk identification is a basic step to manage different project risks.

Task Name	Stakeholder	Signature
Doing the feasibility study for different manual system	Project manager, Requirement analyst
Identification of Business Needs	Requirement analyst
Advancement of vendor selection	Accountant, Project manager
Checking development history of the vendors	Executive sponsor, Project manager
Improvement of the new system installation	Developer, Project manager
Determining the needs of the system	Project manager, System analyst
Using compatible software and hardware	Accountant, Project manager, System analyst
Identifying test cases as well as test plan	Tester
Testing the developed system	Project manager, Tester
Assessment as well as risk identification	Project manager, Risk manager
Risks mitigation	Project manager, System analyst
Evaluating roistering system functions	Executive sponsor, Project manager

Anca, U., Cezar, B., & Adrian, U. (2015, November). Risk Identification in Project Management. In International Conference on Economic Sciences and Business Administration (Vol. 2, No. 1, pp. 259-266). Spiru Haret University.

Boulmetis, J., & Dutwin, P. (2014). The ABCs of evaluation: Timeless techniques for program and project managers (Vol. 56). John Wiley & Sons.

Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management. Cengage Learning.

Heagney, J. (2016). Fundamentals of Project Managementw. AMACOM Div American Mgmt Assn.

Kami, N. (2015). U.S. Patent No. 9,116,916. Washington, DC: U.S. Patent and Trademark Office.

Kendrick, T. (2015). Identifying and managing project risk: essential tools for failure-proofing your project. AMACOM Div American Mgmt Assn.

Pritchard, C. L., & PMP, P. R. (2014). Risk management: concepts and guidance. CRC Press.

Schwalbe, K. (2015). Information technology project management.Cengage Learning.

Tornabene, C., Hussain, M. M., Crowe, T., Cohen, N., & Panzer, J. (2012).U.S. Patent No. 8,103,729. Washington, DC: U.S. Patent and Trademark Office.

Tornabene, C., Hussain, M. M., Crowe, T., Cohen, N., & Panzer, J. (2012).U.S. Patent No. 8,103,729. Washington, DC: U.S. Patent and Trademark Office.