Project management in software is still a little-known subject, and the software industry is full of examples of project failures due to countless reasons that often have a common denominator. This common denominator, which includes so many failures, is formed by Project Management not supported by effective methods, which leads to: – projects whose cost is much higher than estimated and end much later than expected; – projects that do not end because they know how to manage, manage and reduce complexity. – Projects that, even if they are formally completed, turn out to be field trials and clearly are not able to meet customer expectations. A book is a book in which those who work in the field of software just felt the need: finally, a practical guide based on solid theoretical foundations of a complex, complex and constantly evolving subject.
Much has been written about project management in software, but often written also reflects one or more of the following characteristics: – The author is not from the software industry and does not live due to problems associated with the implementation of software projects with limitations, time, very limited resources those who work in the global and highly competitive sector of the software market; – Important, but partial topics are discussed and discussed, possibly due to the field of research of this particular author or group. In these cases, the work is sometimes excellent as a deepening of individual aspects, but is not very useful for those who are looking for leadership that presents the subject organically and fully, for those who aspire to become a project manager or, already in this area, want to combine their knowledge in subject;
The latter definition focuses on two points; the temporary nature of the effort and the creation of a unique product or service. Temporary nature implies that the project will have a limited duration, this duration can be days or years and can use one or more resources (human and material) to carry out the required work. The uniqueness of a product or service refers to the fact that the project will produce something in a single copy that has never been done or never existed.
When the operational process that needs to be managed is the project, the functions of the leader are what is meant by project management (project management / management).
In practice, a person, in order to overcome his own difficulties, builds on the basis of evidence (reproducible and accessible) and formally correct reasoning a path (system of rules) that must be followed every time he finds that he solves such a problem. The size of the problem (complexity, vastness, timeliness) can contribute to the unification of more people in a group that gets on the road with a higher probability of success: the joint use of all or part of the rule system creates a method in group work that integrates and improves the method in an individual task. Thanks to the Internet, many methodologies are available (and can be acquired) through the network: in Appendix B we briefly described some of the most popular ones, in Appendix I instead we reported the addresses of some sites we visited.
Temporary nature implies that the project will have a limited duration, it can be days or years and can use several resources. Within the framework of the project, a document entitled “Leadership” was prepared (in a preliminary version), in which this body was internally characterized by structuring it in ten areas of knowledge: – software requirements, – software development, – software development, – software testing software, – software maintenance, – software configuration management, – software development management, – software development process lecheniya, – tools and methods for software development – software quality, externally defining relationships with family related disciplines: – cognitive science and human factor – computer engineering – computer science – management and management science – project management.