Part 1: Develop strategies

Make your proposal by developing strategies and the companyresponse. These must help the client company prepare for the implementation of the recommended emerging technologies and practices.

You must also incorporate the feedback and new information you received during the presentation of the draft proposal (in the first Project Assessment). (The feedback is the implementation timeframe needs to be shorter (18 months instead of two years).

Ensure that your writing is clear andappropriate to your audience.

Address the following headings and content in a copy of your draft proposal document:

Implementation strategies

For each of the three technologies and three practices that you proposed, do the following:

1 Waterfall method for project management 2 Licensed software installed on workstations 3 Multiple servers on the premises 4 Using a spreadsheet for the IT support ticketing system 5 Traditional office space with separated teams 6 Each department/location developing their own systems

1. Define the objectives of the organisation in responding to the technology and practice.
2. Changes required with the related objectives
3. Addressing the impact, opportunities, and threats
4. Develop Plan with ordered and prioritized tasks

Recommendations

1. Outline your recommendations for the company response for each emerging technology and practice. Include your reasons and how the organisation's objectives will be met. (Recommendations)

Version control

1. Include aversion table with a summary of how the received feedback was incorporated (see the Records Management Procedure (GE_Records-Management_procedure.pdf)).

REFER TO:

Three technologies

1. Waterfall method for project management

• Purpose: The waterfall method is a well-established approach to software development that provides a structured, step-by-step process for managing projects.
• Functions: The key functions of the waterfall method include requirements gathering and analysis, design, implementation, testing, and deployment.
• Features/Attributes: The waterfall method is a linear approach to project management that emphasizes clear documentation and planning, with each phase building on the previous one.
• Potential applications: The waterfall method can be applied to any software development project, from small projects to large, complex systems.
• Advantages: The advantages of the waterfall method include a clear structure and roadmap for the project, well-defined deliverables, and a focus on documentation and planning.
• Disadvantages: The disadvantages of the waterfall method include inflexibility, difficulty accommodating changes to requirements or design, and a lack of flexibility in the development process.
• Potential impact: The waterfall method can provide FinBiz Consulting with a structured approach to managing software development projects, which can help ensure that projects are completed on time and within budget. However, the inflexibility of the approach may make it difficult to accommodate changes or unexpected issues, which could slow down development or lead to delays.
• Potential opportunities: The waterfall method may be beneficial in situations where the requirements are well understood and do not change frequently. This approach can also provide a clear understanding of the project timeline and budget, making it easier to manage resources and deliverables. The method may also be suitable for large-scale projects with a fixed budget and timeline.
• Potential threats: The inflexibility of the waterfall method can be a significant threat, especially in situations where requirements may change frequently. This can lead to increased costs and delays, as changes may require significant rework and testing. Additionally, the method may not be suitable for projects that require a high level of collaboration or experimentation.

2. Licensed software installed on workstations

• Purpose: Licensed software installed on workstations provides each computer with a copy of the software, ensuring that it can be used legally and supported by the vendor.
• Functions: The key functions of licensed software installed on workstations include licensing, local installation, and maintenance.
• Features/Attributes: Licensed software requires a license for each installation, which typically involves a fee. It is installed locally on each computer and can be maintained and updated locally.
• Potential applications: Licensed software can be used for any software application that requires a license, from productivity software to specialized business applications.
• Advantages: The advantages of licensed software installed on workstations include legal compliance, local installation that runs independently of the network or internet connection, and the ability to manage maintenance and updates locally.
• Disadvantages: The disadvantages of licensed software installed on workstations include the cost of licenses, which can add up quickly, and the need for IT staff to manage each workstation individually.
• Potential impact: Licensed software installed on workstations can provide FinBiz Consulting with a reliable and legal way to ensure that their software is properly licensed and supported. However, the need to manage licenses and updates on each workstation can be time-consuming and may require additional IT resources.
• Potential opportunities: The use of licensed software can ensure that the software is legitimate and properly supported by the vendor. This can provide greater reliability and security for the software, ensuring that it is less likely to encounter issues or security vulnerabilities. Additionally, licensed software can provide access to support and updates from the vendor, ensuring that the software is up-to-date and functioning properly.
• Potential threats: The use of licensed software can be a significant expense, especially if licenses are required for each installation. This can lead to increased costs and potentially limit the number of installations or updates that can be managed. Additionally, managing updates and maintenance on each workstation individually can be time-consuming and require significant IT staff resources.

3. Multiple servers on the premises

• Purpose: Multiple servers on the premises provide redundancy and scalability for FinBiz Consulting's IT infrastructure.
• Functions: The key functions of multiple servers include redundancy, scalability, and maintenance.
• Features/Attributes: Multiple servers can provide redundancy by ensuring that critical systems remain operational in the event of a hardware failure. They can also be added to the infrastructure to support increased demand or growth.
• Potential applications: Multiple servers can be used for any IT infrastructure that requires redundancy and scalability, from web applications to databases.
• Advantages: The advantages of multiple servers on the premises include redundancy and scalability, which can help ensure that critical systems remain operational and can be expanded to support increased demand.
• Disadvantages: The disadvantages of multiple servers on the premises include the complexity of managing multiple servers and the need for IT staff to ensure that they are properly configured and maintained.
• Potential impact: Multiple servers on the premises can provide FinBiz Consulting with a reliable and scalable IT infrastructure. However, managing multiple servers can be complex and may require additional IT resources and expertise. Additionally, the cost of purchasing and maintaining multiple servers can be significant.
• Potential opportunities: The use of multiple servers can provide redundancy and ensure that critical systems remain operational in the event of a hardware failure. This can provide greater reliability and uptime for critical systems, ensuring that they are less likely to experience downtime or loss of data. Additionally, the use of multiple servers can provide greater scalability, allowing the organization to scale its infrastructure as needed to support increased demand or growth.
• Potential threats: The use of multiple servers can be complex to manage and require significant IT staff resources to ensure that they are properly configured and maintained. This can lead to increased costs and potentially limit the scalability of the infrastructure. Additionally, managing multiple servers can introduce potential security vulnerabilities or errors, especially if they are not properly secured or maintained.

Three practices

1. Using a spreadsheet for the IT support ticketing system

• Purpose: Using a spreadsheet for the IT support ticketing system provides a simple and familiar tool for managing IT support tickets.
• Functions: The functions of using a spreadsheet for the IT support ticketing system include:
• Creating new tickets for IT issues
• Assigning tickets to IT staff members for resolution
• Updating the status of tickets as progress is made
• Closing tickets once the issue is resolved
• Features/Attributes:
• Potential Applications: The use of spreadsheets for IT support ticketing is suitable for small organizations or those with limited IT support needs.
• Easy to use: Spreadsheets are a widely used and familiar tool for many employees, making it easy to make and manage IT support tickets.
• Customizable: Spreadsheets can be customized to meet the specific needs of the organization.
• Limited functionality: Spreadsheets lack the advanced features and automation of dedicated IT support ticketing software, making it more difficult to manage large volumes of tickets.
• Advantages:
• Simple and familiar tool for many employees
• Customizable to meet specific organizational needs
• No additional software or hardware required
• Disadvantages:
• Potential Impact: The potential impact of using a spreadsheet for the IT support ticketing system on FinBiz Consulting's current technology practices includes several opportunities and threats.
• Limited functionality compared to dedicated IT support ticketing software
• Difficult to scale and manage large volumes of tickets
• Can be prone to errors and inaccuracies
• Opportunities:
• Threats:

2. Traditional office space with separated teams

• No additional software or hardware required, reducing costs and complexity.
• Familiar and easy to use for many employees.
• Can be customized to meet specific organizational needs.
• Limited functionality compared to dedicated IT support ticketing software.
• Difficult to scale and manage large volumes of tickets.
• Can be prone to errors and inaccuracies, potentially leading to delays or miscommunications in resolving IT issues.
• Purpose: The purpose of traditional office space with separated teams is to provide individual workspaces for employees and to make a formal organizational structure.
• Functions: The functions of this process include physical separation of teams, hierarchical structures, and formal communication.
• Features/Attributes: This system provides individual workspaces for employees, which can improve focus and productivity. Additionally, the formal communication structure ensures that communication is documented and organized.
• Potential Applications: This system can be applied to any organization that requires individual workspaces for employees and a formal communication structure.
• Advantage: advantages of this system include increased productivity and organized communication.
• Disadvantage: It can also lead to a lack of collaboration and limited creativity among teams.
• Potential impact on the organization's current technology or practice: Implementing a traditional office space with separated teams may not have a significant impact on the organization's current technology or practice. However, it may limit the ability of teams to collaborate and may lead to limited creativity. Additionally, this approach may not be conducive to a more modern and flexible workplace.
• Potential Opportunity: The traditional office space with separated teams can provide a sense of privacy and autonomy for employees, which can help them focus and be more productive. Moreover, it can help establish clear reporting structures and roles, which can improve accountability and decision-making.
• Potential Threat: However, this approach can limit collaboration and creativity, which can be essential for developing innovative solutions and improving business processes. Moreover, physical separation can lead to silos and communication barriers between teams, which can negatively impact productivity and efficiency. Additionally, this approach can be costly, as it requires a dedicated office space for each team.

3. Each department/location developing their own systems

• Purpose: The purpose of allowing each department/location to develop its own systems is to address unique knowledge and requirements.
• Functions: The functions of this process include local knowledge, lack of standardization, and duplication of effort.
• Features/Attributes: This system allows each department/location to develop systems that address its specific needs, which can improve efficiency and productivity. However, the lack of standardization and duplication of effort can lead to inefficiencies and challenges in maintaining and integrating the various systems.
• Potential Applications: This system can be applied to any organization that has multiple departments or locations with unique needs and requirements.
• Advantage: The advantages of this system include the ability to address specific needs and requirements, which can improve productivity and efficiency.
• Disadvantage: The lack of standardization and duplication of effort can lead to inefficiencies and challenges in maintaining and integrating the various systems.
• Potential impact on the organization's current technology or practice: Implementing a system that allows each department/location to develop its own systems could lead to a lack of standardization and duplication of effort. Additionally, integrating and maintaining the various systems could be a challenge. However, the ability to address specific needs and requirements could improve productivity and efficiency. It may be necessary to establish guidelines and standards to ensure that the various systems are integrated and maintained properly.
• Potential Opportunity: Allowing each department or location to develop their own systems can provide flexibility and adaptability to the unique needs of each team. This can improve efficiency and productivity by streamlining processes and reducing duplication of effort. Moreover, this approach can promote innovation and experimentation, as each team can try different approaches and technologies.
• Potential Threat: However, this approach can result in a lack of standardization and interoperability, making it difficult to manage and maintain the various systems. This can lead to data inconsistencies, security vulnerabilities, and higher maintenance costs. Additionally, this approach can lead to a lack of collaboration and communication between teams, which can negatively impact productivity and innovation.