Respond to below Discussions

Textbook :

James D. McKeen, Heather A. Smith, IT Strategy: Issues and Practices, Third Edition. Pearson, 2015, ISBN-13

978-0-13-354424-4.

Discussion 1 :

This to create the technology roadmap then they should come to know why that road map is needed to him and what to include on a road map all this should get to know that the user. The product roadmap will be making the identification for tracking the product futures improvements and strategy than a part of this that. Technology road maps nothing but they will be studying about the work that supports the products and also the organization so they do not organize each and everything rather they only make organized some of the infrastructure-related technologies and also some of the tools that which there only choose to place had some of the product. So they can be seen and overlap between the products with their wings and also the technology road maps there any by looking at this they need not be mean that every single of the tech-related works and also that related projects belong on the project road map which they are creating. If at all they need to how the infrastructure-related projects then they need to put the product roadmap where you do not get fit then it is a right time to road map which they are creating to implement so it needs some of the plans so that it can demonstrate how one of the individuals Technology initiatives will make some of the support to the product initiatives so here this can be said as the only way to look at the route map which is having go through about the app then it can also take on some of many different forms we can also see the IT system road maps which day data line of the organization on how there it strategy will get tied into their business strategy part of this.

Reference

:

4 Right Steps How to Create a Technology Roadmap: Hygger Blog. (2018, September 12). Retrieved from

https://hygger.io/blog/4-right-steps-create-technology-roadmap/

Discussion 2:

Technology roadmap is a method of planning and executing any project that needs definite resolutions. This method of approach needs a plan for attaining goals both halfway and final goals for more suitable methodological solutions required for a project.

Steps for developing a technology roadmap:

Guiding Principles

                Creating and maintaining principles are very important in the roadmap, combining the entire team, governing the establishments and services in the planned project plan. Sharing guidelines and endorsements within the team or company will be helpful. 

Assess Current Technology

              Before making changes to current technology or making use of new one, accessing the current technology and see how to make use of it most and make changes if needed will be very helpful in the project.  Set highlights on the current technologies which is are made to achieve main goals and try to think about how to make things simpler which seems as complicated keeping in mind about what tools can help the company not only current but also for future work.

Analyze Gap

                Recognize the key, final and most required goals for the company. Make sure that all the goals should be flexible, which needs a room for its development. This can be achieved by analyzing the gap between the current technology and the business plan.

Evaluate Technology Landscape

                Before approving the technology which, will be the foundation of all the projects of company, make sure what will be the technology life and how will it be potential in the next upcoming years besides the current plan of use. It will be helpful to understand and study the subject of technical solutions better before choosing the most maintained and supported by most of the teams in company. So, choosing technologies for any project should have future life and at least a certain provision.

Reference:

Johnson, P., et al. (2004). ―Using Enterprise Architecture for CIO Decision-Making: On the Importance of Theory,‖ Proceedings of the 2nd Annual Conference on Systems Engineering Research.

Discussion 3 :

The Problem with System Development

System development entails the creation of software applications that are customized for an organization. There are too many complex problems that have emerged in contemporary society, which has forced the definition of SD to change to include selection, implementation, and integration of software solutions in different components of a software (Avison & Fitzgerald, 2003). Development projects are seen as costly and time-consuming and which does not deliver much value for a business. The challenge of measuring productivity continues to be a significant problem for system development. Agility, composition, and integration are trends that have been adopted in SD (Avison & Fitzgerald, 2003). Improved governance has also been associated with SD productivity. Changing the strategies of resources to include outsource developers to supplement development that takes place in- house is still on the rise.

SD faces barriers, like business involvement in the process of attempting to enhance productivity. A business leader does not pay much for the services that the developers offer. They require more services with little pay. The other obstacle is assessment, whereby it has become a significant problem to identify changes and gather functional system requirements effectively (Avison & Fitzgerald, 2003). The other obstacles include poor communication between the business trends and IT since SD fails to harmonize the two. SD   productivity can be improved through lessening complexity whereby organizations can develop tools of tailoring that determine the oversight and control level with regard to the risk involved. The other improvement is maximizing on the bigger picture whereby IT and business strategy are aligned, and effective resource management is done. Creating a smarter development environment can also go a long way in enhancing knowledge sharing and collaboration initiatives.

 
Reference

Avison, D., & Fitzgerald, G. (2003). Information systems development: methodologies, techniques and tools. McGraw-Hill.

Discussion 4:

In many of the companies and organizations to do work effectively the employees work by getting together which is called teamwork. In teamwork, each and everyone will be implementing their ideas and the work will get to complete fast and efficiently. Here the work which is done by the company can be calculated with some of the measures but we cannot get any kind of the measurements of the team members strategy India company we can also use advanced technology machines and also some of the equipment to increase the work efficiency but here without using the advanced technology tools and equipment the work should be done effectively and answer quickly for the purpose the team members should dedicate their hard work productivity is a term that which can be measured by measuring the output which comes from the units of input in the completing the measuring the productivity is very easy and also simple but if it all they want to measure the productivity of team then it is too difficult. Here the productivity is not which we open within a short time by keeping a lot of the efforts in the company so here the team members will be working very effectively. Here working hard is not a matter but working smarter is definitely will be a matter of the people were developing the software or any programs will be called as a developer so here they are not the developer to measure the productivity of the workers is not easier as they are not machines as we know some of the employees will work with having very knowledge so that knowledge workers very difficult to measure the outputs which are of the productivity.

Reference:

Samir, & Samir. (n.d.). 10 Ways to Improve Software Development Productivity. Retrieved from 

https://www.linkedin.com/pulse/10-ways-improve-software-development-productivity-samir