Project team for a fictitious technology-intensive company in the year Assignment

Project squad for a fictitious technology-intensive go with in the year 2011 - Assignment compositors case(Solomon, et al., 1993).This managers guide contains a repeatable, institution-wide approach for the management of project teams involve in the development of softw be and hardware deployment projects. The practices contained here in practices are transferable to other types of projects that would benefit from project management. It provide ordered sections presenting the basic steps for formation, management and rating of project teams across the organisation. This guide has been developed specifically for the management of Information Technology projects. The processes with are operational do not need to follow these guidelines. The projects which qualify to use this guide should have the following characteristics it is an main(a) project lasts longer than a few person hours requires a multidisciplinary approach it is not task oriented involves less than five specialists i t is meant to accomplish a interlocking project may require change management process level of risk is high in terms of financial and operational, among others (Ahmed, 2007).All the projects in the company have to be approved by the Chief Executive Officer through a justified Project Document. Depending on the type of project, the project catalogue should clearly indicate the title of the project aims of the project outcomes of the project team composition resource plan methodology of the project workplan project cost and evaluation strategyThis section provides basic guidelines on the formation of IT projects .The following guidelines should be followed in forming project teams for developing software and hardware. The first stage of forming the project team is acquiring the project team. The members can be selected internally or externally as consultants. The members must be selected based on list of required skills and criteria as demanded by