36119 - 2 - Pages Within 12Hrs

Therefore, the Company is looking to engage a consultant to undertake a scoping study for the requirements of developing a mobile app so as to ensure the company’s:

· Visibility to customers at all times

· Provide value to customers

· Create a direct marketing channel

· Cultivate customer loyalty

· Stand out from competition

· Build brand recognition

As stated above, the purpose of this report is to conduct a scoping study on app development for Company X, utilising effective scoping techniques so as to achieve the study objectives as stated below:

Objective 1: Aim at evaluating mobile app designs and suitability in line with the business goals, this is done by:

· Conducting market analysis

· Utilising interactive model analysis

Objective 2: Aim at reviewing the app design components for the business by:

· Conducting stakeholder mapping

· Adopting the principles of task /technology fit

Objective 3: Strategising for effect app development and launching by:

· Examining mobile app development processes

· Carrying out SWOT analysis

The methodology used is this study is designed to provide the client with high valued service which is aimed at realising the business objective of developing a business app that will facilitate business transactions in a timely manner. Also, the study is conducted using information obtained from industry based studies, case studies and past researches. Furthermore, organisation wide assessment tour will be carried out in order to collect necessary information required for the development and content of the app and also point the usefulness of the study to the client while providing critical analysis that justify the methodology used in the study.

The significance of this section is to conduct a detailed evaluation of academic theories significant to and applied in this study while the theories will help in identifying and evaluating the framework from industrial based practices that are relevant to the study. In order to accurately carry out a scoping study on the requirements for developing a business app for Company X, the section focuses on theories that allows for full analysis of the objectives of this study. The objectives are explained as follows:

Going by the objective which is aimed at evaluating mobile application design for business use, it is therefore vital to carry out market analysis in order to identify the market the business is serving and consider the best app design that fit both the market and the technology being introduced into the business.

Market analysis is an early step in deciding whether there is an audience or a need for an idea (i.e. introducing a mobile app) while an understanding of the market needs and the complexity of what they can cope with provides businesses with relevant information that is important in developing a unique marketing plan (Slater et al; 1995). Market analysis help to describe the stakeholders characteristics, competition, target customers profile and how the company can gain advantage over others in marketing its products and service in order to create a successful business venture (Dalgic and Leeuw, 1994). So for Company X to embark on developing an effective business mobile app, a market analysis needs to be conducted primarily for the following reasons according to Slater et al, (1995):

To determine if the target market is properly understood with regards to their needs, expectation and preferences, also it help to determine if the app need to be integrated into an existing care pathway and how, i.e. does the app need to run on a particular operating system or hardware device and finally consider if the app should be paid for, free or should it come with an existing service.

Mobile app development can be time consuming and expensive endeavour therefore, careful consideration aimed at developing a mobile app can be done through market analysis in order to meet a clearly identified need of the market (University of Bristol, 2016).

Also, market analysis has the potential of helping the company in knowing the make up of the potential users in order to design the features they can cope with and designing these features in the app, how users will have access to the app (i.e. do customers need to register and generate user name and password), the level of transactions that can be carried out via the app, the aspect the of the app that the public will be allowed to access and restricted from etc. (Educause, 2011).

An interactive application is a system in which the user interact with the computer in a conversational mode (Aaker and Weinberg, 1975). This model is an abstraction of a real world system which demonstrates the interactive relationship that exist between supplier’s offer and the buyer’s perceive product (Linn, 2010, Aaker and Weinberg, 1975). This model structure the means available for the business (supplier) to induce meta as well as physical values which are realised in the in the world of the buyers’ perception (Linn, 2010). The idea of businesses using computer terminals in communicating directly with models was proposed, and in an increasing number of organisations the idea is becoming a reality (Aaker and Weinberg, 1975). The motive behind this is that businesses conceive a total product that is perceived as having a value higher than the price asked by a large number of potential buyers (Linn, 2010).

An increasing number of successful applications have been recently launched for downloads on tablets and smartphone with components and functionality more closely mimicking the computer, for example several players in the food industry such as Bwtri in 2014 launched its business app known as ‘Caws Cymru’, McDonalds in 2015 launched it app known as ‘McDonalds mobile’, Domino’s in 2011 launched its ‘Easy order’ mobile app and have used these apps in developing advert programmes for their products (Aaker and Weinberg, 1975). These apps are software applications that can be downloaded onto smart phones, e-readers and tablets to provide solution to marketing hiccups or satisfy a niche requirements, the apps can also be accessories that are attached to a mobile communication devices and smart phones (NHS, 2014). Furthermore, these apps can be programmed to inquire the conversational language the user would like to use depending on the customers the business is serving and the user response will determine the feedback the app display to the user (Aaker and Weinberg, 1975). In order to ensure an effective business app, the end users which are often times the customer needs to use or be involved with the app which implied that stakeholder (including the customers) does not only use the app but be committed to it and this is reflected in their subsequent relationship with it. In developing mobile app lots of decisions needs to be made and each of those decisions can have a dramatic effect on the total cost of the finished app and can affect its chances of being successful (NHS, 2014). Furthermore, in defining an effective business app, Aaker and Weinberg (1975) highlighted the following as important: Stakeholder perception of the app’s usefulness, their willingness to devote effort and time to using it and their dependence on it for carrying out transactions.

However, the following needs to be considered in the application development process as highlighted by Doolittle et al. (2012); NHS (2014):

- A need assessment that ensure detailed understanding of the aim and purpose that the app is set to achieve.

- An understanding that the app design should be simple and easy to use by stakeholders.

- An understanding of the mobile security issues which includes gateways, portals, one time passwords and mobile virtual private networks (VPNs).

- Determining the user base for the mobile app operating system OS.

- Following established regulations on production and deployment models.

Following the increasing functionality linked to mobile device hardware, it implied that mobile apps are more capable of delivering increased functionality and has the capability of responding faster than earlier devices (NHS, 2014).

Based on the foregoing discussions of the objective above and the understanding of the conditions for introducing a business mobile app for Company X which operates in the food industry, two types of apps can be recommended suitable for the business which are: the native app and mobile web app (Jobe, 2013).

The native app work on a mobile device and is developed specially for the device software platform and uses specific coding to using the device features such as the GPS capability and the built in camera (NHS, 2014). A well built native has the tendency of providing rich user experience with enhanced control of the look and feel of the app and can also access device specific features as the GPS, cameras and are likely to work when the device does not have internet connection and can be subject to development standard of the hardware maker (Educause, 2011).

While mobile web apps on the other hand refer to web applications that are designed and developed to imitate the native applications as much as possible but they are executed in a web browser in the host platform (Jobe, 2013). However, mobile web apps can increasingly compete comfortably with native app in terms of functions (NHS, 2013). Furthermore, mobile web app allows a single development and support process irrespective of supported device and typically depend on internet connectivity, often with lesser functionality compared to native app but can work on a wide range of devices and does not need to be downloaded and installed (Educause, 2011). As a result Company X can choose to go for anyone that best suit their purpose using information generated from market analysis as explained above.

This objective is focused on guiding the client Company X in its choice of choosing between apps by reviewing the app fit and design components for the business which will ensure that all stakeholder interest relating to the app are effectively met by carrying out stakeholder mapping as a way of identifying the key players and their interest in the app.

Stakeholder refers to all persons or groups with legitimate interests participating in an enterprise without whose support the organisation will cease to exist (Donaldson and Preston, 1995; Clarke, 1998). On the other hand, it can be said that the company is a system of stakeholders operating within the larger system of the host society that provides the necessary market infrastructure for the firm’s activities (Clarke, 1998). In the execution of the project, a powerful individual stakeholder may have a significant influence on the project decisions and are most influential in shaping the strategy for the project (Newcombe, 2003). However, developing and maintaining a separate version of app for numerous stakeholder devices can be very expensive and may require the developers to share revenues with the vendor’s app store (Educause, 2011).

The central task in the process of reviewing app design for deployment to business in Company X is to manage and integrate the relationships and interests of employees, customers, suppliers and other groups in an approach that ensures the long term success of the firm and promoting shared interests (Freeman and McVea, 2001). These groups have expectations which the app is under pressure to fulfil this can pose as a challenge owing to the fact that there may exist conflicting expectations from stakeholders and these conflicts may revolve around short term versus long term objectives, cost efficiency versus effectiveness, control versus independence (Newcombe, 2003). Developing and launching a mobile business app to facilitates business transactions can be likened to what Freeman and McVea (2001) termed “strategy development” this is done in two approaches that involves: prediction and adaptation which is the process of carrying out environmental scanning to identify trends that can help foresee the future business environment and the second approach involves identifying the best way for the firm to adapt to the future environment in order to maximize its position as it has been established that organisations practicing stakeholder management will be successful in conventional performance in terms profit, growth and stability (Donaldson and Preston, 1995).

The consultancy recommends undertaking a stakeholder analysis for the company through a familiarity tour of the company in order to identify the stakeholders in the app who need to be involved in designing and development of the app or kept informed which can include both individuals and organisations (NHS, 2014). However, based on this study and its aim the following are the likely stakeholders that ought to be put into consideration in the app design and development are:

Internal stakeholders: This can include stakeholders at the executives or management, divisional and departmental level and the employees. These stakeholders may want the app designed in a specific way or have some features which may reflect their functions or ease their operational task (NHS, 2014).

External stakeholders: These consist of external individuals, organisations or network of organisations who may have influence in the app development and may be impacted by the development and deployment of the app and these can include; services providers (such as content providers, application providers, payment agents), Communication providers which provides communication service that enable mobile devices to access mobile services (these actors include; mobile network operators and the internet service providers), regulatory authorities (they set the legal and societal framework in which mobile business will evolve) and the end users (the consumers are also important players in these project because they can determine the success or failure of the business app (Camponove and Pigneur, 2003; NHS, 2014). Furthermore, external stakeholder can include providers of complementary products to the company offerings which may proposing a link to their site from the company’s proposed app.

In designing the mobile app components, the stakeholders identified above (both internal and external) are put into consideration by ensuring the platform has the capacity to service substantial number of customers at any time and also ensuring that the content of the app is carefully and professionally chosen in order to accommodate all relevant, effective and easy to use features. Also the app will be developed in a cost effective way and expanded project scope that ensure the technology fit the task to which it is meant to perform (Doolittle et al., 2012).

In designing and developing business app for Company X, the consultancy will consider the impact of information technology and compare it with the task it is expected to perform in order to ensure its fit for purpose. Information technology (IT) innovations such as mobile and wireless technologies can only be successful when developed into applications and later put to use (Gebauer and Shaw, 2002). The essence of task technology fit is to ascertain that for information technology to have a positive effect on individual performance, the technology must be utilized and the technology must be a good fit with the task its supporting (Goodhue and Thompson, 1995). Task-technology fit (TTF) utilisation and user attitudes about the technology result into individual performance impact through its ability to make obvious the importance of TTF in explaining how technology leads to performance and also make more explicit the links between the construct by providing a stronger theoretical basis for thoughts about issues relating to the impact of IT on performance outcome (DeLone and McLean, 1992; Goodhue and Thompson, 1995). The application of TTF in the design and development of business app is to take into consideration the fact that mobile app can cover a wide range of usage than applications with a specific usage such as group support systems (Gabauer and Shaw, 2002). In designing the task the app will perform, the consultancy analyze task on different levels according to different characteristics which include: ambiguity, repetitiveness, structure and complexity of cognitive processes i.e. complex vs simple task (Campbell, 1988; Simon, 1977). However, based on past experience, interdependency may arise in the app design. Three types of interdepedence that may arise are highlighted by Thompson (1967) as sequential, pooled and reciprocal and it is suggested that the application of relevant organisation technologies that enables intensive, mediating and long-linked duties to ensure task coordination. However, the company can measure the TTF of the app after it is launched by those factors highlighted by Goodhue and Thompson (1995) as; ease of use, quality, timeliness, locatability, compatibility, authorisation, relationship with user and system reliability as against these measures TTF can undergo modifications to suit the purpose of the company. The diagram below illustrate the task and performance expectation of the app.

Source: Goodhue and Thompson (1995)

The project need to undertake TTF to ensure effectiveness and foresee all possible failures that may result from the design and development. When the app is fully launched it will serve as an integral part of the day to day operations of the business as the company will rely on it to generate revenues, attract customers and communicate with suppliers therefore the cost of failed online transaction can be huge also an hour of downtime can cost the business huge sum in lost of sales (Pertet and Narasimhan, 2005). Furthermore, downtime can result in: damage to the company’s reputation, dissatisfied customers and lost of employee productivity example of this is what Amazon.com suffered in 2001 as a result of downtime which cost the an estimated amount of £17,000 per minute of downtime (Conrad, 2001). The following are the possible cause of app failure that needed to be guide against as highlighted by Pertet and Narasimhan (2005).

-Softwares failures and human error which is the most significant cause of errors.

-System overload, complex fault recovery routines and resource exhaustion.

-Software failure arising from system complexities, inadequate testing and weak understanding of system dependencies.

-App inaccessibility which can last from minutes to days.

Security violations.

Having taken all these into consideration the main idea is that mobile app can best be applied and successful when there is a good fit between the technology and the underlying tasks (Gebauer and Shaw, 2002) which is the objective the consultancy is seeking to achieve so that the company can derive full economic and other benefits when the app is deployed to business.

This section is aimed at enabling Company X mobile app developers and providers strategies to effectively develop and launch the app into business by summarising the app illustration done above and highlighting a detailed analysis of step by step approach of developing the app.

The following approaches represent a best practice as highlighted by Microsoft (2012) as:

1) Choosing between a native app and a web app: This has been explained earlier with features and capabilities in 2.1.2 above.

2) Examining the mobile app experience: This stage defines the important characteristics of modern mobile app of which are born out of best practices and provide a useful framework through which planning and designing of the features are done. As a result, a mobile app ought to be:

Lightweight and responsive: This section suggests that in the design stage of the app, consideration should be given to speed to which content can be accessed on the app. As a result, apps should be lightweight and void of latency by avoiding unimportant heavy markup, use of unnecessary and gratuitous effects and poor data management. A better way of determining the right size is to consider how long it will take users to load a page (Varshney and Vetter, 2002).

Designed to fit each device’s capabilities and constraints: Mobile gadgets come in different sizes, shapes and different CPU power. As a result, instead of developing an app specific to a certain platform browser, device grouping is a better alternative to deliver a flexible app which target the lowest common denominator app, and further layer additional features and enhancements with reference to the capabilities and constraints of each browser and device.

Enhanced, platform-agnostic user interface: This process is strengthened by market analysis explained earlier. i.e. an app can be well designed and has a nice interface but may be hard to use. Users may make mistakes as a result of incomprehensible language used, have difficulty if finding a feature and what a feature is used for. Therefore, an enhanced interface should work well with back end business logic and allow users to complete their task effortlessly.

3) Choosing device and level of support: This section aim at identifying those devices the app will support, and the users achievable user interface experience on their devices by determining the browsers and devices the app will support. Considering the key features and behaviour of the app, experience and context of use, i.e. whether the app will be designed for all purpose use or restricted to shopping activities etc. as explained in (2.2.2) TTF above.

4) Options for building mobile app experience: Making decision on the approach to use in developing a mobile app is always not easy, this is due to the various techniques available on building an app and their various advantages and disadvantages (Microsoft, 2010). Moreover, making this decision depend on the circumstance and consideration of linked factors such as resources, content structures, timeline and design architecture (Educause, 2011).

The above listed steps constitute the minimum process that need to be taken in building a mobile app after which the builder can then proceed to the testing stage of the app in other to identify any area where there may be a malfunctioning in the app while a simple app as illustrated with upto four screens will cost between £1,000 to £7,000, app with multi-features will cost £30,000 upward, also app that can store information on mobile device cost between £5,000 to £30,000 (NHS, 2014). Furthermore, the SWOT analysis will give an inkling of the possible downside that can be experience in the app development processes.

This section explore the literature and provide a summary details of the limitations and challenges that can be encountered in building the app and by extension the threats the app can pose to the business as a result of lapses that may be observed in the app functioning and on the other hand highlight the strength of building the app as the company can decide either to build the app in house or contract it out and how it can be of benefit to the company.

Paliwal (2006) explained that the SWOT is preferred for assessing projects as it yields useful information about the viability of the project due to the predictive capabilities in determining how the app will fare in the light of changes taking place around it. The consultancy emphasise carrying out this analysis based on Milosevic (2010) explanation of SWOT from the company’s point of view that from the moment the company decides to undertake the project (being app development), the company is in suspense regarding the final outcome and the app being met to last over a period of time, large part of the benefits from the investment are realised in the future therefore the study highlight the risk involve so that the company can decide the level of risk its willing to take so as to ensure the project yield expected results. This follows Barney (1995) description of SWOT as a framework that points to the relevance of internal and external forces that help in understanding the source of competitive advantage and also assist to portray organizational situation and identify what information is needed and the decision that are likely to be made at the company level (Balamuralikrishna and Dugger, 1995). The SWOT analysis for this study is used to compare builing the app in-house and contracting it out below:

Strength: Building an app in house has the benefit of connecting the internal stakeholders, their objectives and actively participating in formulating the execution plans and because they formulate the plans they understand it and will assist in producing the desired result and protect the company sensitive data (Apple, 2011). On the other hand, contracting out the app building to specialist has the benefits of using their extensive experience in developing, operating and implementing mobile app, and follow-through checks anytime, anywhere problem arise with the app (T-system, 2012).

Opportunities: Building the app in-house has the capabilities of availing the company the knowledge of app building, ability to work on any area users are finding difficult to use immediately and also has the opportunity of saving cost by bye passing intermediary directly to relevant providers (Microsoft, 2012). On the other hand, the company can push the responsibility to consultant who will do the running around to ensure the app is designed to specification, the company will save more resources by saving the pay it would pay the staff in regular employment in the company and cost of developing it wrongly.

Weakness: The limitations to building an app in house can be due to lack of expertise knowledge needed to securely design and build the app without exposing the app users and the company to unnecessary risk as there will be lots of sensitive info on the device (Denim, 2011). On the other hand, external builders based on their past experience has the understanding of app development, the risk involved and will always put measures in place to guide against those risk (Microsoft, 2012).

Threats: Organisations today are exploring ways of pushing tasks/functionality to the app and this pose as a threat to the company as competitors and hackers are looking for ways of breaking into the network as a result the company need a specialist on ground to monitor and stop any suspicious attempt to break into the system as a successful hacking can paralyse the business activities pending when the problem can be resolved (Denim, 2011).

In conclusion, the SWOT has been used to weigh the pro and con of building a business app in-house as compared with contracting it out to consultants who are expert in the field after a review of literature on SWOT analysis in order to use the strengths to lessen the company’s vulnerability to threats, overcome weaknesses to attain opportunities and prevent weaknesses to avoid the company being more susceptible to threats (Chaermack and Kasshanna, 2007).

Gantt chart is commonly used by project managers in project management due to its useful ways of showing how activities and tasks are displayed against time. As a result, this study use the Gantt chart method to highlight the various activities to be performed, state the starting and ending time for each activities, show how long each activity is planned to last, highlight where an activities overlap with another and the extent to which it overlaps and finally show the start date and end date for the whole project (Gantt.com, 2016). This study also focused on the fundamental activities related to the project over a six month period so as to meet the deadline and avoid knock-on effect on the remaining part of the project. Furthermore, the detailed nature of the Gantt chart ensures the task schedule is workable and also ensure that remedy to potential obstacles are in place before the commencement of the project.

Going by the illustration in the Gantt chart above, the tasks are divided into sections, each of which relate to the objectives set by the client which is the Company X. This method was particularly chosen to illustrate the ways through which each objective is met using appropriate analytical tools. Furthermore, the objectives are divided into subsections whereby each subsection presents the analytical tool used and the corresponding activities required to complete the study. This method is important because of its ability to help work out the practical aspect of the project, i.e. it states the task that needs to be done before another can start and this approach ensures that a detailed sequence for the completion of a task is stated thereby ensuring a timely delivery of the project.

Gantt charts are important in project management due to its ease of use and simplicity to understand by the client and other stakeholders (Wilson, 2003). The main activities of this project as shown in the Gantt chart above emphasize on the successful execution of the set objectives by constantly holding meetings with the client. As a result, if there be a delay in holding the scheduled meeting with the client, there will be a spill-over effect and will have an impact on the entire project. As a result, it is important to schedule tasks along with appropriate timing that will be sufficient for carrying out research that the task might require and also highlight how the different tasks are interconnected and depend on the completion of one before proceeding to the other so as to achieve the set objective and ensure that the needs of stakeholders and client are met.

In completing each objective highlighted in the chart above, the activities needed to complete each objective must be carried out for the consultant to proceed to the next objective. Wilson (2003) illustrates that the activities in a Gantt chart are presented in two dimensions where the horizontal axis shows the placement in time which should be strictly adhered to, the vertical axis represents the activities to be completed for the project to be executed effectively and efficiently. Also, activities on the Gantt chart are separated using different colours and dependency lines signifying important time issues and when all the tasks are to be completed. The relevance of this is that it is helpful in understanding the activities in the chart especially the complex tasks, this will help in carrying along all stakeholders in the project and also facilitate joint agreement on expectations the company will be expecting from the consultancy during the scheduled meeting for feedback and progress report.

Detailed planning and research is required for all activities under each analytical tool as a result the project need both primary and secondary research so as to get detailed information on the requirements for developing a mobile app. As a result, the consultancy allocate time to each objective according to the research requirement of the task to be performed. This is so because of the need to meet the client requirements and maintain a regular interaction and communication with the company throughout the project (Miller et al., 2001).

An important element in the Gantt chart methodology is the allocation of ‘Slack Time’ to tasks. This shows a time where more than one activities can take place simultaneously without affecting the whole schedule. As a result, this project allocates slack time to tasks that does not have direct impact on the chart critical activities. This ensure the allocation of slack time in a way that controls any unexpected circumstance that may affect the overall completion of the project. Istrate et al. (2014) describes this approach as a realistic view that help recover from hindrance and adjust to changes.

In conclusion, Wilson (2003) describes the Gantt chart methodology as a popular tool for project managers to use as an effective means of displaying important information and also provide an interface that enables users to state problems, enhance understanding and proffer solutions. It also enhances coordination between project managers and stakeholders, provide clarity of task and effective time management while ensuring that all the project objectives are met.

The demonstrated frameworks and analytical tools used above are based on high quality research aimed at enlightening the client through the study. The attached Gantt chart above highlight the relevant activities that will be involved in the study to satisfy the models chosen for each objective which is done through analysis of relevant literature and case studies. This section ensures that a detailed assessment of the deliverable outcome for the project is done and a set pattern for meeting client requirements for the study is clear while making sure the client is informed of the reasons for the approaches adopted for the study and how effective they are in meeting their requirements.

In project management research, theory holds that market analysis and testing is often carried out first by project managers before making most decisions (Alketbi and Gardiner, 2014). It is argued that organisations seeking not just increase revenue and profit but transformation in their business use market analysis as a tool for achieving their purpose (Pursche, 1990). For this study, market analysis and the interactive model help transmit information regarding the end users of the app, their level of exposure to modern technology and also determine the level of app (technological) complexities they can cope with as Alketbi and Gardiner (2014) explained that this tool is considered to be the simplest technique used by project managers in solving complicated issues bordering on customers expectations.

In evaluating the suitability of mobile application for business use, the interactive model play an important role because it consider the need for allowing larger number of people have access to organisations software applications for larger number of purposes and in a wider number of contexts (Paterno, 2000). Also, the model ensure this by making the system easy to use why taking into consideration some factors in the design of the interactive application that encourages involvement, active engagement and reaction, two way communication, physical action and feedback (Karimova, 2011). Furthermore, the model help in determining the level of formality adopted, how information is presented, and the level of abstraction that can be use in the app as a tool for creating compelling and easy to understand interaction (Paterno, 2000). This model further ensure that the app is designed and developed in a way that is beneficial in arousing the users and motivate them to stick to the interactions longer, engaging and encouraging the users to return over time, persuasive and increase sales, increase trust and make people feel more secure and comfortable about releasing personal information online, promoting a feeling of personalised experience by making users feel special and also creates feelings of liking, friendliness while supporting generalised positive feelings towards the company (Reeves, 2016).

As a way of satisfying the first objective, the study made use of market analysis and interactive model to evaluate the suitability of business app to the company, which the consultancy consider effective and beneficial tools. The interactive model consider the relevance of customers having direct access to the company and market analysis analysed the customers with regard to the level of complexity in technology they can cope with.

In reviewing the app building and design for the company, it becomes necessary to conduct stakeholder mapping as a way of identifying key stakeholders and featuring their interest in the app design. This tool is important for the company in identifying these stakeholders who can affect the project and then managing their differing demand through communication and fashioning out ways of realising the proposed project objectives (Olander and Landin, 2005). For the company to acquire relevant data on the app design, there is the need to carry out extensive primary research in the form of interview inquiring on their interest, designs, interactions and other features in the app in a way that ensure the project objectives correspond with the stakeholders’ (Freeman, 1984).

Stakeholder theory has been regarded to be important in identifying stakeholders in any project and allows everyone to understand the importance and influence of the project, allow for continuous improvement while it can be effectively used to determine stakeholder requirements by project managers (Kennon et al., 2009; Scholl, 2011; Olander and Landin, 2005). As it is believed that the views and initiative of stakeholders in the project can be useful for strategic planning and design process (Clarke, 1998). This justifies the relevance of implementing stakeholder mapping in the review and design stage of the project.

Having known the technology at hand, this tool helps in determining the task the company will like to be performed using the app and then build the app to perform the task identified to be done through the app i.e determining whether the task will be best perfomed by native app or mobile web app. Goodhue and Thompson (1995) explain that tasks are actions to be carried out to turn input to output why task characteristics in this case are those that make the company to rely heavily on certain aspects of information technology. While technology on the other hand, are tools used in carrying out tasks. As a result, in building the app TTF will be used in helping to get a reasonable balance between task to be formed and the technology which is the app. The tool relied on Tornatzky and Klein (1982) postulation that successful innovation happens when the task and the technology are compatible. As TTF is the correspondence between functionality of the technology, individual/organisational abilities and the task requirement (Goodhue and Thompson, 1995).

The app development process is undertaken in order to give a clear understanding on the task the app need to perform (TTF), for whom it is meant (market analysis), and the environment it needs to operate in (NHS, 2014). This aspect made clear app design and development processes and the key steps that need to be taken using an agile development process, while the process offers a responsive and rapid approach to the building of the app and its functionality using a range of development tools with tried and tested processes. The section also serves as a document to support internal development of the app and also provide a clear and unambiguous requirements external developer can seek if the company decides to outsource the app development. This section strengthens Abrahamsson et al. (2014) postulation that anyone with the needed skills can build a mobile app while a good knowledge of the specific characteristics and challenges of developing software for mobile devices is required which this study has provided.

SWOT is used as an important support tool for making decision and systematic analysis of of the company external and internal capabilities and also provide a strong basis for decision making (Yuksel and Deviren, 2007). In choice of developing the app, the section uses the SWOT as a tool to highlight the benefits and privileges the company stand to gain while on the other hand it explained the short comings and possible consequence of developing the app in-house. As a result, SWOT is used as a tool to help the company in selecting amongst strategic alternatives in the light of the strength, weakness, opportunities and threats involved in building the app (Hanley and Spash, 1993).

5.0 References

Abrahamsson, P., Hanhineva, A., Huikko, H., Ihme, T., Jaalinnoja, J., Korkela, M., Koskela, J., Kyllonen, P. and Salo, O. (2014) ‘Mobile-D: an agile approach for mobile application development’, 19th annual ACM SIGPLAN conference on object-oriented programming systems, languages and applications.

Page | 4