Technical problems

Progress Report
Introduction
The technical problem faced by the organization is one of limited software use. The organization need to upgrade its systems to increase softwares and to instruct the employees on the utilization of these softwares. The project will involve the buying of the softwares and their integration into the system. The project will also cover the instruction of the employees and all who will be using the computers with the new softwares. This project is anticipated to span three months. This will include the project approval, the acquisition of the merchandise and the implementation phase. The project will have a slight change in that there will be an addition of some hardware which are meant to enhance the use of the new softwares. These hardware however, will be minimal and will be acquired concurrently with the software.
Work completed
In order to organize the project much research has been necessitated. The beginning part of the research was pinpointing the technical needs of the organization. Although the organization has been doing well opportunity for improvements was possible. Next step was identifying one of the problems that could be addressed. The problem had to be solvable and one of the ones which would impact greatly on the organization’s output. Some of the other problems that could be fixed did not offer much expectation for high and lasting changes in the organization so the project identified the one option which should be a priority. Next followed identifying some possible solutions. Research indicated that some funds could be spared for this purpose and that the solution could indeed be implemented. Having been deemed feasible, the proposal could then be made.
Stages of completing the work
Monday 4th July, 2011 Talking with IT department and some employees
This was in order to identify the areas of technological need. The IT department was very helpful and pointed to possible areas which could be improved including the areas which was finally selected. The talk also gave some orientation on the history of the technical needs of the organization and how that has been addressed before. Talking with the employees also clarified some areas of difficulty in using the organization’s computer systems. Decision was reached to invest in software.
Wednesday 6th July, 2011 Research into softwares
Research on the necessary software was conducted. The aim was to identify softwares which would meet the needs of the organization and directly impact the output and efficiency of the employees. The research started online and progressed to the library. The result was that several softwares were identified.
Monday 11th July, 2011 Checking feasibility of acquisition and implementation
This stage comprised of checking how the identified softwares could be acquired and how they would be implemented. The IT department was consulted and their suggestions noted. The manager was also consulted on the procedures of acquiring products and installing the changes. The decision was reached that the softwares could be acquired and implemented to improve the organization.
Sources used
In order to comprehend the scope of the project better certain sources were utilized to which an annotated bibliography is appended. The first one was by Bridges and Bridges “Managing transition: making the most of change”. This book gave an understanding of how to plan for change to maximize its effects. Another book by Fuller “Managing performance improvement projects: Preparing, planning, implementing” highlighted key ways of identifying what needs improvement and how to go about effecting that change.
In choosing the softwares to be acquired two sources were used one being “The next leap in productivity: What top managers really need to know about information technology by Kolawa. The other was a website and the other was “Top 20 applications to increase your productivity”. These sources created awareness of the trends in IT and also important softwares which have been identified as key to increasing output and efficiency.
Work Remaining
The project still needs to identify the actual statistics to be used for the implementation. There is need to figure the costs of the particular softwares and hardwares and other costs related to their implementation. There is additionally a need to identify the time frame of the actual implementation and what procedures need be used. Only after these are established can the following step be started and the organization experiences the envisioned changes.
Stages for work remaining
1st August, 2011 Calculate the costs of the implementation
This stage will include coming up with all the projected costs which will be incurred. This will assist the organization particularly the manager to create a budget for the project. It will also assist him to make a decision about the project’s actual feasibility against the expected benefits.
3rd August, 2011 Submit the final proposal to the managerial
This will be the last stage before a decision is made about the project. The manager having everything necessary to make a decision can proceed with decision-making. This will also determine what the next stage will be. The manager may accept the prepared proposal, he may request modifications on it or he may reject it.
8th August, 2011 Initiate the implementation
If the proposal is approved the it will signal the beginning of implementation and will start with acquisition of the necessary wares will commence and the various stages of the implementation will follow. This will be the last stage.
Problems encountered
Single
The main problem of the project was that the work was a lot for one person. I was alone in the group so I had to do everything. In addition, there was nobody to share ideas with so most of the time thorough research was necessary.
Costs
The cost was also higher as the project was supported by one individual. With a group the costs for the tasks could have been shared.
Time
It was hard to create time as well because of other responsibilities. Most of the tasks were done between other tasks. However, care was taken avoid inadvertently compromising the outcome.
Conclusions
The project has progressed quite well and major difficulties have been overcome. The work done has established an important way of improving the organization with a long time solution. With more time and resources the project could have identified further ways of changing the technological aspect of the organization. It is however hoped that the changes which have been suggested will be adequately implemented and will deliver better use of the hardware that already exists. The project has also been a learning experience for the individual as well as for the organization. With the success of the project, similar improvement initiatives can be taken to bring better performance in the organization.

Annotated bibliography
Bridges, W. and Bridges, S. (2009). Managing transition: Making the most of change.
Philadelphia, PA: Da Capo Press.
This book aids in understanding the impact of change and how to ensure that change is positive. In an organization not all changes deliver what is expected. It is possible, however, to make the transition work for the organization through a proper understanding of what to expect and utilization of channels which will guarantee change is beneficial. The book is a necessary component when initiating change.
Fuller, J. (1997). Managing performance improvement projects: Preparing, planning,
implementing. San Francisco, CA: Jossey-Bass/Pfeiffer.
The author here provides a very well laid out map for a manager who wants to initiate a project aimed at improving performance. The book discusses all the major necessities of such a project and how to navigate the various aspects which would contribute to a successful project. The book makes it easier to understand the task and gives assistance on delivering a feasible project.
Kolawa, A. (2009). The next leap in productivity: What top managers really need to know about information technology. Hoboken, NJ: Wiley.
The author presents information that would be relevant to managers in charge of IT departments. The book explore issues which concern IT utilization and improvement. It also highlights ways in which managers can make changes to ensure their organizations have the best IT departments capable of delivering according to the needs of their organization. Some aspects of management are also discussed.
Lifehack. (2005-11). Top 20 applications to increase your productivity. Retrieved from
http://www.lifehack.org/articles/technology/top-20-free-applications-to-increase-your- productivity.htm
This site is particularly geared towards softwares which have been proven to make great contributions in raising organization’s productivity. It discusses each of the applications and how each of them contributes to increasing productivity and efficiency. The site also offers information on where to get the softwares making it easy to acquire them for those who are interested.

References
Bridges, W. and Bridges, S. (2009). Managing transition: Making the most of change.
Philadelphia, PA: Da Capo Press.
Fuller, J. (1997). Managing performance improvement projects: Preparing, planning,
implementing. San Francisco, CA: Jossey-Bass/Pfeiffer.
Kolawa, A. (2009). The next leap in productivity: What top managers really need to know
About information technology. Hoboken, NJ: Wiley.
Lifehack. (2005-11). Top 20 applications to increase your productivity. Retrieved from
http://www.lifehack.org/articles/technology/top-20-free-applications-to-increase-your- productivity.htm

Latest Assignments