One of the techniques that I would suggest for the team would be to use documentation that will be based on the stage of the development. The standards that will be followed will describe some aspect of systems that have been developed. This will mean that having systems requirements specification documentation, architecture documentation, technical documentation, and user documentation. With this, it will be simpler and easier to manage the different types of documentation with the development of different systems in the organization. There documentation process of the company will follow a specific format and process. The suggestions imply that there should be documentation for every stage of systems development. The suggestions would be to have an organization-wide standard that will be adopted and used in the various stages of system development. This will categorize the documents based on the systems that they describe in the organization (Roth, Dennis, & Wixom, 2013).
There are many solutions that are available for the documentation of the organization. There is a need to ensure that there is proper documentation in order to have safe documentation process. The solution I would suggest for this is to have a web based document processing system. With this system, it would handle all types of documentation processes. The system would also handle all document formats. The system will be web-based and will mean that it will be reachable to anyone who has access. For standardization purposes, the documentation system will be used by all platforms (Juristo, & Moreno, 2010).
The technique that has been proposed will solve the concern of difficulty to use. This is because web-based applications have simple interfaces. In addition to this, the application that has been proposed will be developed using simple logic that will be simple for everyone. The development process will be managed so that the concerns of all people will be catered in the development process.
There will be steps that will be used to decide on the best process that will be followed in deciding the process that will be developed and followed in the process. The first deciding factor that will be considered is the user requirements. The user needs and requirements will be assessed and evaluated. In this case, the users want a simple system that will run on any platform. Using a web-based system will provide a simple system that will be simple to access by the users. Another point of consideration was the ease of access of the system. With web-based application, it will be accessed from any location within and outside the organization. This will make access of the system simple (Pohl, 2010).
One thing I would do to convince the two about testing advertising data with live data would be to show the past performance of the testing. This will show the impact of testing the advertising module with live data. I would do a comparison of the past tests which have used live data and that which has been done the way they want. I would try to explain to the two the importance of this module to the whole organization. The explanation would entail explaining to the two the role that advertising has on the other modules. The comparison and the explanation would probably serve to show the two how important the modules are and what should be done to ensure there is maximum output for this module (Wohlin et al., 2012).
One thing that systems analysts can do in planning their time is to prioritize on modules which mean a lot to the business. This planning will ensure that there is enough time for most important tasks. Another thing is to start testing as the developers still continue working on the systems. This will enable the analysts have maximum time to test the systems.
One of the problems that might be encountered is that there could be errors with the module which could be transferred to the production stage. This will affect the production and will affect the clientele. It is important to test the module with live data before being transferred to production.
In reality, there are no steps that can be collapsed. This is because any step that will be collapsed will have effect on the stage that will follow. It will affect the productivity of the other modules.
The problem that is happening with the training session is that users of different categories who should be learning different things are being taught the same things. Managers are supposed to be trained on the management side of the systems while junior users should be trained on how to use the system. Mixing the training will not work as users will learn what they are not supposed to learn.
One way in which this can be addressed is to overlap the training of the users. The managers can be trained earlier when the system is still under development. This will ensure that there will be enough time to train the junior users. Another way of solving this is to reduce the time that is spent on training some users.
One basic advice that the team ignored the fact that the system will not be used the same way to all people. The training should be done according to how the users will interact with the system. There should be segmentation of the users according to how they will interact with the system.
Juristo, N., & Moreno, A. M. (2010). Basics of software engineering experimentation. Springer Publishing Company, Incorporated.
Pohl, K. (2010). Requirements engineering: fundamentals, principles, and techniques. Springer Publishing Company, Incorporated.
Roth, R. M., Dennis, A., & Wixom, B. H. (2013). Systems Analysis and Design. John Wiley.
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2012). Experimentation in software engineering. Springer.