Automated Sales Management Software Implementation For Cosies Insulation

1. Maintain a project journal (a log of YOUR OWN real activities in doing the assignment). Use a table with columns with number, date, activity, explanation and status. This is the diary of your assignment.

2. Produce a 5-6 minute “elevator pitch” video clip explaining to the client what you have done so far and how you did it. Provide a URL link and test it. If your marker cannot watch your video then it won’t be marked; please make sure you can be clearly seen in the video.
 

Stakeholder

Cosies Insulation is an organization that installs insulation in homes and is in existence since past three years. The company has a call centre with 20 members and the sales staff comprises of 8 members. There are certain issues that have emerged for the sales and call centre staff members in terms of business operations and data handling issues. The company has decided to implement automated sales management software that will be utilized by the members of the call centre to record information and make phone calls. The report includes the details of the system in terms of the work breakdown structure, system vision, stakeholder details, product backlog, elicitation, and use cases.

The purpose of the vision statement is to provide the highlight of the system being developed and the justification & benefits associated with it.

Cosies Insulation has decided to implement automated sales management software that will be utilized by the members of the call centre to record information and make phone calls. The users that will be provided with the access to the system will include admin, call centre staff, sales representative, and manager (Kryjak and Komorkiewicz, 2013).  

The product will primarily serve the purpose of tracking and managing the sales data and it will also include the option for the call centre staff members to contact the customers.

There are several issues that are present in the existing system. There are issues of data loss that have been reported and these issues may cause legal obligation to the organization and may also lead to the emergence of trust issues among the customers. There are also data management issues that have emerged in the system. It is necessary that an automated system is developed for the organization so that these issues are resolved and enhanced capabilities are offered to the users (Kuruzovich, 2013).

There are several benefits that the system will offer to the organization and its users.

• The sales data will be automatically handled and there will be no issues of data loss or leakage.
• The sales tracking will become easier and the sales patterns may also be determined.
• The staff members will be able to contact the customers using the system which will ensure that the process is streamlined and is simplified (Matsuo, 2009). 

The following elicitation techniques shall be used to collect the information from the stakeholders:

• Interview: There shall be personal interviews arranged with the employees and the interview questions shall be prepared in advance. The conduction of the interviews shall take place to make sure that the stakeholder expectations and details are obtained.
• Group discussions: There may also be discussions conducted with the stakeholder groups including employees, customers, and Project Sponsor to understand the current issues and expectations from the system (Sood and Arora, 2012).
• Brainstorming Sessions: These sessions shall be organized with the staff there may be new ideas and concepts that may be identified.
• Surveys: The conduction of the surveys shall be done from all the end-users to reach to a wide audience and collect information on the system. 

The requirements assigned under Must (M) category shall be given the priority over the requirement placed under Should (S) category.

References

Bhuiyan, M., Haque, F. and Shabnam, L. (2018). Integration of Organisational Models and UML Use Case. Journal of Computers, 13(1), pp.1-17.

Boesso, G. and Kumar, K. (2016). Examining the association between stakeholder culture, stakeholder salience and stakeholder engagement activities. Management Decision, 54(4), pp.815-831.

Ghai, S. and Kaur, J. (2012). Analysis of User Requirements Gathering Practices in Agile and Non-Agile Software Development Team. International Journal of Computer Applications, 58(8), pp.13-18.

Hudda, S., Mahajan, R. and Chopra, S. (2016). Prioritization of User-Stories in Agile Environment. Indian Journal of Science and Technology, 9(45).

Kryjak, T. and Komorkiewicz, M. (2013). Hardware-software vision system for moving people counting based on 3D information. Image Processing & Communications, 18(2-3), pp.71-81.

Kuruzovich, J. (2013). Sales Technologies, Sales Force Management, and Online Infomediaries. Journal of Personal Selling & Sales Management, 33(2), pp.211-224.

Matsuo, M. (2009). The Influence of Sales Management Control on Innovativeness of Sales Departments. Journal of Personal Selling & Sales Management, 29(4), pp.321-331.

Misbhauddin, M. and Alshayeb, M. (2013). Extending the UML use case metamodel with behavioral information to facilitate model analysis and interchange. Software & Systems Modeling, 14(2), pp.813-838.

Rusconi, G. (2018). Ethical Firm System and Stakeholder Management Theories: A Possible Convergence. European Management Review.

Sobiech, F., Eilermann, B. and Rausch, A. (2016). Using Synergies between User Stories in Scrum. Lecture Notes on Software Engineering, 4(2), pp.91-94.

Sood, V. and Arora, M. (2012). Comparison of Requirements Elicitation Techniques. International Journal of Advances in Computing and Information Technology, 1(4), pp.378-387.