SWOT, Contractors, Project Management and Software Deployment - Assignment Example

Project Management Task SWOT Analysis FTS System has been in the business of designing and creating bespoke software for variouscompanies. The extensive experience in the business of creating and designing bespoke software is an asset because it puts FTS Systems in a proper place to handle a wide range of tasks and deliver quality services. The availability of talented, diverse workforce with a high retention gives FTS System a competitive advantage in the market. FTS Systems has a large base of satisfied clients, which confirms it offers high-quality services. FTS System has highly skilled managers who have experienced in executing large-scale projects. The project managers can organize for the required expertise and collaboration level required to deliver a formidable software security for the government. The weakness is the absence experience in developing software security, which is evidenced by the lack of previous contracts in that sector. Accepting the software security project presents a number of opportunities and threats for FTS Systems. FTS Systems has an opportunity to take up its first software security contract and deliver quality services. It is also an opportunity to collaborate with professional consultants in software security (Cadle, et al., 2010). FTS employees will have a chance to learn from the consultants and gain valuable knowledge for future projects. The threat of failure, which might do so much to tarnish the good reputation created by the company for over 20 years. The lack of experience in software security increased the risk of failure. In addition, FTS System has to compete with firms experienced in software security by developing top-notch software that dwarfs products from competitors in performance and security. SWOT Analysis Summary Strengths Weakness Extensive experience in the business of creating and selling bespoke software. High employee retention level Talented workforce Efficient project management skills. Little experience in developing software security. Opportunity Threats Gain experience in the creation of software security. Collaborate with professionals in software security High level of competition in the industry. High risk of failure. Task 2: Project Management Efficient project management must have a clear timeline scale that does not seem too ambitious or too slow (Gido & Clements, 2009). The aim is to set a time that will be able to push the team under pressure to perform. The project has given a timescale of twelve months, which means time is already limited. The company should with a timescale of eight months so that it can have time to test the developed software and correct all the bugs before being delivered to the client. Eight months is reasonable because with proper management and collaboration the team can manage to create software. The allowance is necessary to test the product and ensure all bugs are corrected. The aim is to deliver high-quality software to the client. The eight months can be broken down for two months of employee training and six months for the actual tasks, which is developing software security. The lack of experience in software security warrants the need to organize training on software security development for employees (Ahlstrom & Bruton, 2010). The training will enhance the ability of FTS Systems to handle the project by providing employees with the essential intellectual tools. In this case, the employees involved in the project will need an extensive course in all the factors that affect software security. Knowledge of the different tricks that hackers use to weaken software security is essential for everyone handling the project. The training should cover the basic techniques used in testing software security. The training should be conducted with professionals who have proved experience in software security development. The training must cover all intrinsic and extrinsic factors that can compromise software security. The company can consider hiring contract workers to help in handling the project (Hamid, 2013). Hiring contract workers is a chance to get professionals with experience in software security, which reduces the risk of project failure. The cost of hiring contract workers is lower than the cost of training employees in the short time remaining. The other advantage of hiring contract workers is that it creates flexibility that allows the company to change any worker who is not performing. Workers are paid strictly on a performance basis (Nicholas & Steyn, 2012). It is imperative to understand that getting contract workers comes with its limitations. First, the management will have less control over contract workers (Hamid, 2013). They are independent contractors who are bound only by the terms of the contract. The company might have limited rights to terminate a contract based on the specifics outlined in the contract. Sometimes contract workers have the right to demand pay for a job that has been poorly done (Hill & Jones, 2013). Contract workers are not long term, which means the company will have to hire contractors for similar projects in future. Hiring contractors robs FTS Systems employees a chance to learn software security and gain experience. The initiation phase of this particular project involves planning activities based on the available timescale, make decisions on whether to seek the services of contract workers or train employees. It also involves accessing all the materials required to complete the project (Kerzner, 2013) (Gido & Clements, 2009, p. 23). The initiation phase is characterized by appointing the project manager, holding meetings with project team members and developing a definite scope for the project. The planning phase is characterized by budget preparation, creation of a detailed schedule, staffing, procurement details and any plans on project control. The aim of the planning phase is to determine what is needed for the project to be executed. The resources needed for the project should be acquired at this phase. Project planning is continuous because of the changes that can affect the initial planning. The execution phases will involve engaging all resources in designing the software according to customer specifications. This phase is when the project team members are busy developing the code for the software. The execution phase will also include the time the team will take to test the software to ensure it is functional. The final phase is the closeout phase, which means ending the project. It entails delivering the product and closing the project. Any documents on the project are archived. The company should consider taking this project because of the opportunities that come with it. FTS Systems has 20 years’ experience and a talented workforce that can take on the challenge. The project is a chance to start a journey in the business of developing software security for many organizations. It is a chance to build a good reputation by delivering quality work. The fact that it is a project from the government is an opportunity to form a long-term relationship by delivering quality work. Task 3: Software Installation Approach The four main approaches to software installation are the pilot, big bang, parallel, and web. Pilot It entails installing the software in one part of the organization to evaluate the performance of the software before committing it to all part of the organization (Kerzner, 2013). For example, the company can start by installing the software in the crime division unit and check its performance. The main advantage of the pilot approach is that it offers an opportunity to test the software and limits losses that might be incurred due to software failure. The limitation is that it might take time to complete the implementation process because the test period might be too long. Parallel It involves running the new software at the same time as the old software. The aim is to assess the performance of the software (Heeks, 2006). The parallel approach is an opportunity to compare the quality of output from both systems. It minimizes the risk of failure because if the new software has a problem the organization can continue with the old software until the problem is fixed. On the downside, the parallel is very expensive because of the time, costs and money that must be spent to make it possible. It demands too many resources, which affects its viability in respect to cost management. Big Bang The big bang approach ensures all the changes are implemented at once (Heeks, 2006). The software will be installed in all parts of the organization at once on a given date. The big bang approach comes with a huge risk because the failure of the software could comprise sensitive information. A failure would mean heavy losses for the government. The only advantage of the Big Bang approach is that it helps save time and money. Web The Web approach deals with software installation from different parts of the organization as it moves. The installation moves in phases as it expands to different phases. It is good because it provides a chance to correct any errors before the software becomes fully functional. The main limitation is that it might take a long time to complete the process of implementation. In addition, it is expensive to handle the different phases. The pilot and parallel approaches are suitable for the government. The Big Bang approach is too risky because of the potential losses that might be incurred if the software malfunctions. The Pilot approach is the best one for implementing the software. The cost of compromising sensitive is much higher than the cost of supporting a pilot approach (Kerzner, 2013) (Dinsmore & Cabanis-Brewin, 2011). The Pilot approach offers information security, which is a priority in the police and justice department. References Ahlstrom, D. & Bruton, G. D., 2010. International Management: Strategy and Culture in the Emerging World. Australia: South-Western Cengage Learning. Cadle, J., Paul, D. & Turner, P., 2010. Business Analysis Techniques: 72 essential tools for success. 1st ed. London: British Computer Society. Dinsmore, P. C. & Cabanis-Brewin, J., 2011. The AMA Handbook of Project Management. 3rd ed. New York: American Management Association. Gido, J. & Clements, J., 2009. Successful Project Management. 5th ed. Mason, OH: South-Western Cengage Learning. Hamid, J., 2013. Strategic Human Resource Management and Performance: The Universalistic Approach--Case of Tunisia. Journal of Business Studies Quarterly, 5(2), pp. 184-201. Heeks, R., 2006. Implementing and managing eGovernment: an international text. 1st ed. London: Sage. Hill, C. & Jones, G., 2013. Strategic Management: Theory. Mason, OH: South-Western Cengage Learning. Kerzner, H., 2013. Project Management: A Systems Approach to Planning, Scheduling, and Controlling. 11th ed. Hoboken, N.J: John Wiley & Sons. Murray-Webster, R. & Williams, G., 2010. Management of Risk: Guidance for Practitioners. 1st ed. Norwich: The Stationary Office. Nicholas, J. M. & Steyn, H., 2012. Project Management for Engineering, Business, and Technology. 4th ed. New York: Routledge. Read More