Ticketing System Development For RALS Project - MOV, Scope Management Plan, Project Schedule, Risk Analysis, Quality Management Plan, And Essay.

You are to prepare, based on the Case study scenario, and your peer to peer learning.

MOV - Measurable Organisational Value

(This is the goal of the project and is utilised to define the value that your team project will bring to your client)

• Identify the desired area of impact - Rank the following areas in terms of importance: Strategy / Customer / Financial / Operational / Social

• With reference to your project, identify one or two of the following types of value:

• Better - is improving quality important to your client? o Faster - does your client want to increase efficiency?o Cheaper - is cutting costs important?

o  Do more - does your client want to continue its growth?

• Develop an appropriate metric - this sets the target and expectation of all the stakeholders. It is important to determine a quantitative target that needs to be expressed as a metric in terms of an increase or decrease of money.

• Determine the timeframe for achieving the MOV - ask yourselves, when do we want to achieve this target metric?

Define Scope and produce a Scope Management Plan

Define the scope of the project and detail how the scope will be managed.

Identify and detail the resources for the project using MS Project where appropriate, including:

• People (and their roles), plus any extra personnel that is required for the project.

• Technology - any hardware, network and software needs to support the team and your client.

• Facilities - where will most of the teamwork be situated?

• Other - for example, travel, training etc.

Using MS Project, develop a schedule using a high level Work Breakdown Structure (WBS). It should include:

Milestones for each phase and deliverable

• This will tell everyone associated with the project that the phase or deliverable was completed satisfactorily.

Activities / Tasks

• Define a set of activities / tasks that must be completed to produce each deliverable. Resource Assignments

• Assign people and resources to each individual activity.

Estimates for Each Activity / Task

• Develop a time estimate for each task or activity to be completed.

Budget

• Create a time-phased budget using bottom-up estimating. Be sure to include direct costs listed in Part two and add 20% for fringe. State all assumptions and constraints you have used when creating your budget. State how confident you are in your estimates and what would make you more confident.

Project Risk Analysis and Plan

• Document any assumptions you have made about the project

• Using the Risk Identification Framework as a basis, identify five risks to the project – one for each of the five phases of the methodology.

• Analyse these risks, assign a risk to an appropriate member, and describe a strategy for the management of each specific risk.

Quality Management Plan. It should include:

• A short statement that reflects your team’s philosophy or objective for ensuring that you deliver a quality system to your client.

• Develop and describe the following that your project team could implement to ensure quality;

• A set of verification activities o A set of validation activities

Closure and Evaluation Researching for the closure checklist and project evaluation

To prepare for this task, you will be required to provide an annotated bibliography.

Write an Annotated Bibliography for three (3) relevant texts or readings around project evaluation. The Annotated Bibliography is a critical examination of the most relevant, recent and scholarly research on the topic area that is not just a summary of the articles you have read.

You will submit this as an appendix to your project evaluation documentation.

Ensure that the AB submitted by you is your own work and has not been submitted elsewhere and comply with the University's requirements for academic integrity.

1. Develop a closure checklist that the project team will use to ensure that the project has been closed properly.
2. Develop a project evaluation –outline and discuss how your project’s MOV will be evaluated.

Part 1: MOV Values

Ranking: The project of Ticketing System Development for RALS is formed for ensuring that a proper and systematic system for the storing and printing of the tickets for the Riverina Agriculture and Lifestyle Show. The implication of the effective and improved processing methods would imply the formation of the improved processing and the development of the integration management. The project had to comprise the formation for enduring the specific terms of finance, operations, client, strategy, and social issues for the development of the project operations. The analysis of the these factors have been given in the table below,

1. Better- The project of Ticketing System Development for RALS would be helpful for forming an integrated information system that is capable for storing all the information in a single database along with the specific and improved operations for the show.
2. Faster- The ticket generation system for the Riverina Agriculture and Lifestyle Show would be helpful for listing the visitors of the show and easily form the ticket generation system. The system would result in compiling and accessing the information by consuming very less amount of time.
3. Cheaper- The cost of manual ticket generation, salaries of the people managing the operations, and the information management at various places (files or drives) is very high compare to the cost of using the ticketing system. Hence, it would decrease the overall cost of the processes and make the process cheaper in comparison.
4. Do more- The system would also serve as a medium for communication and future operations as the data would be stored permanently. The system would result in easing the process of the effective program development and operations.

Appropriate Metric with timeframe:

MOV statement: The MOV statement signifies that, “Ticketing System Development for RALS Project” can be implied for the modification of the existing information system so that a new ticketing system for the Riverina Agriculture and Lifestyle Show would be formed for developing the effective and improved processing methods. The system would also help in easing the process of the information transfer and accessing.

Define Scope: The project of Ticketing System Development for RALS would be helpful for forming a ticketing system that would be capable of forming the improved functional analysis and modification of the existing functional development models. The project would involve the development of a project charter document, project scheduling process, cost budget estimation, and risk management plan.

Requirements: The project of Ticketing System Development for RALS would comprise of forming an effective and improved system for ticketing process of Riverina Agriculture and Lifestyle Show. The project would require the use of the IT system development technology, project management principles, and effective leadership style. The project plan would also comprise of using Waterfall Approach for developing the complete project plan. The human resources required for the project are Analyst, Documenter, Project Manager, Planner, Designer, IT Engineer, Database Developer, Programmer, Tester, and Trainer.

In Scope and Out of Scope: The in scope items are the factors or elements of the project that would be included in the deliverables or activities of the project. The project of Ticketing System Development for RALS would involve the formation of the project initiation documentation, charter documentation, project scheduling plan, cost estimation planning, risk management planning, communication planning, scope management planning, complete design development, user interface development, database development, system is developed, user interface testing, black box testing, white box testing, training manual development, staff training, and final documentation. The out of scope items of the project are the elements or components of the system development and implementation that are not a part of the project management plan. The change management plan, transportation requirements, and contractor agreements are not a part of this project and can be said as out of scope items of the project.

Part 2: Scope Management Plan

Deliverables: The deliverables for the project of Ticketing System Development for RALS are listed in the table below,

Acceptance Criteria: The project acceptance criteria for the project of Ticketing System Development for RALS are,

1. Project Team would use the effective project management principles for implementing the advances technology of ticketing system for RALS
2. Overall expense of the project would be limited to an estimated budget of $ 65,000.00 and a provisional budget for $ 5,000.00
3. Project life span would be limited to four months of time duration and the project life cycle would be limited to the 101 working days

Provide a list of resources:

The schedule for the project of Ticketing System Development for RALS is given in the table below,

Development of Verification Activities: Use of specific design methods, simplified database operations, and interface analysis method

Development of Validation Activities: Management of quality, change operations, and risk implementation

Annotated Bibliography: See in appendix

Closure Checklist: The closure checklist is shown in the table below,

Project Evaluation: The evaluation of the project of Ticketing System Development for RALS can be done on the factors of functionality, cost, and performance.

Functionality: The system developed would be helpful for forming an integrated information system that is capable for storing all the information in a single database along with the specific and improved operations for the show. The ticket generation system would be helpful for listing the visitors of the show and easily form the ticket generation system.

Cost: The cost of manual ticket generation, salaries of the people managing the operations, and the information management at various places (files or drives) is very high compare to the cost of using the ticketing system and hence its implementation would decrease the overall cost of the processes and make the process cheaper in comparison.

Other factors: The system would also serve as a medium for communication and future operations as the data would be stored permanently. The system would result in easing the process of the effective program development and operations.

References

Davies, R., & Harty, C. (2013). Implementing ‘Site BIM’: a case study of ICT innovation on a large hospital project. Automation in Construction, 30, 15-24.

Gido, J., Clements, J., & Clements, J. (2014). Successful project management. Nelson Education.

Heagney, J., (2012). Fundamentals of project management. AMACOM Div American Mgmt Assn.

Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring and monitoring project performance. John Wiley & Sons.

Kroczek, A., van Stam, G., & Mweetwa, F. (2013). Stakeholder theory and ICT in rural Macha, Zambia. In International Conference on ICT for Africa.

Kuster, J., Huber, E., Lippmann, R., Schmid, A., Schneider, E., Witschi, U., & Wüst, R. (2015). Project management handbook. Heidelberg: Springer.

Leach, L.P., (2014). Critical chain project management. Artech House.

Marchewka, J.T., (2014). Information technology project management. John Wiley & Sons.

McNeil, A. J., Frey, R., & Embrechts, P. (2015). Quantitative risk management: Concepts, techniques and tools. Princeton university press.

Ruehl, C. H., & Ingenhoff, D. (2015). Communication management on social networking sites: Stakeholder motives and usage types of corporate Facebook, Twitter and YouTube pages. Journal of Communication Management, 19(3), 288-302.