Hi, Habrozhiteli!
We have a new book on IT project management.

What are project environments and patterns of project environment formation and management? How to choose the best set of management practices and requirements for information systems? How to make a project manageable and predictable? How to profitably sell yourself as a master of project management? Answers to these and other questions will help you to build management and production processes as efficiently as possible. The publication provides information with links to theoretical materials from different areas of software development management: analysis, architecture, project management, leadership and personnel management - that may be needed in the work on real production projects. Analyzed a variety of cases and situations, are examples of documents and templates required for software development. In addition, a huge array of theoretical information is structured, depending on what has been tested in practice and can be used in the work of professionals in the field of software development.
')
There are many remarkable methodologies and standards of project management and no less remarkable books that describe in detail the practices of PMBOK, CMMI, SOVNET, RUP. This book does not purport to be considered a methodological reference. The authors do not think that it thoroughly covered what has already been described in other sources.
In an effort to develop the approach used in the first book of the
IT Professional Path series, the authors cite only real practitioners and only good practices tested by them on their own experience in real projects, referring to recommended or basic methodological sources. All practices are organized in blocks to help you quickly find the right recommendations and immediately start using them.
The functions of the manager are not limited to the mechanical application of standards and methodologies. The art of a manager is to select from their richest arsenal the ones that best suit the project, its environment and this organization, depending on its level of maturity and staff qualifications. It is on this book that a serious emphasis is placed.
From this point of view, the mission and purpose of the publication is to give impetus to rethinking existing experience, understanding what knowledge may not be enough to develop the underlying principles in managing software development and turn them into patterns with a clear understanding of the criteria for which pattern it makes sense to apply.
This book - the result of more than 15 years of work of authors in the field of software development and information systems. Its main advantage is practical orientation. It analyzes a variety of cases and situations, provides examples of documents and templates required for software development. In addition, the book structures a huge array of theoretical information, depending on what has been tested in practice and can be used in the work of professionals in the field of software development.
Who is this book for?
This book is for professional managers in the project or functional areas of software development, working group leaders, project managers, heads of departments / directors of software development departments.
The book will be useful for both novice managers and managers with experience. The first will be able to find in it new practices for themselves that are almost ready to be used in real industrial life. The latter will be able to generalize and systematize knowledge, look critically from different sides on their own experience and the experience of the authors of the book, perhaps, to revise some patterns or decide to use some of the authors in their own practice.
Of particular note is that the book attempts to fill the gap for the heads of departments / functional departments associated with software development. There is quite a lot of literature describing practices and principles of project management, but similar aspects for functional managers are rather poorly covered. In this book, this array of information is structured in a group of patterns of management of a software development department.
The uniqueness of this book is that you will find practical information gathered in one place with links to theoretical materials from different areas of software development management: analysis, architecture, project management, leadership and personnel management - what you will need in your work on real production projects.
What you will NOT find in this book
In this book you will not find a naked theory. We will provide only the necessary theoretical minimum to illustrate practices and methods. The management, analysis and other disciplines of software development that are affected in the book are quite mature subjects today, and it will not be difficult for you to find materials on them in the Internet and textbooks for sale.
We do not aim to give the reader a theoretical education. The book is focused on the active reader, who has already understood that he must search and absorb the theoretical base independently. You will not find in the book also the authors' confidence that only the described path of the manager and only the methods and techniques offered by the authors are correct. On the contrary, several paths lead to the same goal. We want to show you the path that we ourselves have taken, in which we are sure to give only those patterns that led us to success on this path.
About the authors
Andrei Dmitrievich Pererva
41 years old. Master of Business Administration / Master of Business Information.
Experience in the software development industry - more than 20 years. Experience in leadership positions - 12 years, of which in the top management - eight years. Currently specializes in strategic and tactical planning, operational management and project management of a software development company.
In his career development he passed all possible positions in software development, worked as a programmer, designer and database developer (DB), business analyst, system analyst, architect, project manager, head of business and systems analysis. Took part in the development of information systems such as Workflow, Boeing Reference Engineering Data, Automated Retrieval System, Customer Relationship Management System, Enterprise Management System, corporate portals and integrated business automation systems, and managed such developments.
He has practical experience in creating a quality management system (QMS) of a company, building a software development process (SDLC) in accordance with RUP, Iconix, Agile, PMBOK, CMMI, ISO 9001 methodologies and standards.
Sergey Valerievich Eranov
35 years, experience in software development - about 15 years. During his professional career, Sergey was a programmer, a team leader, an architect, a project manager, a functional department manager.
He has experience in implementing changes to the software development process based on the principles of Agile (Scrum), as well as experience in implementing practices such as Story Mapping, unit testing and continuous integration.
During his professional career he participated in projects on internal automation, custom software development and development of replicable software products. Currently working in the GC "Project Practice" head of IT-direction.
Vera Alekseevna Ivanova
Experience in IT - 14 years. The first seven years she worked as a programmer in public institutions. Gained experience in developing application software using database management systems (DBMS), system administration, and technical user support. She participated in the implementation and maintenance of automated financial accounting systems at the regional level.
In 2003 she began to learn a new specialty - a system analyst - and continued working in companies specializing in software development. Participated in the development of web applications, software for information security. She performed various roles in software development projects: system analyst, database developer, architect, test designer, project manager. Main specialization - systems analyst. The last four years specializes in the methodology of system analysis and software development.
Sergey Nikolaevich Sergeev
36 years. Experience in software development - 15 years. He was engaged in the implementation of various projects and the development of software for public authorities. He worked as a programmer, team leader, now a top manager at Keysystems.
He was involved in the development of replicable software as the main database designer, lead product developer, developer of basic business logic, and graphical interface. By the nature of the tasks being solved, he rather quickly shifted to the management of the full cycle of production of lottery software.
Among the tasks that were solved on the way of professional development were the organization of a quality management system for software production, the creation of a dedicated division of industrial core developers, the introduction of product testing automation systems, the justification of the need and the creation of a marketing management and PR division,
creation of a partner sales channel, organization of IT internships, etc.
More information about the book can be found on
the publisher's website.Table of contentsExcerptFor Habrozhiteley a 25% discount on the coupon -
Project Management