Separate the wheat from the chaff, or Why do we need to classify projects

Question about the project management methodology arises sooner or later in the project office`s team. It`s simple in theory. A lot of methods are available in a special literature or online. There you can find both classical waterfall model and Kanban, but any effort of their implantation without any background can turn out a big failure.

Obviously that it`s important to analyze properly all of the requests of the project before implantation of any model. Why? Project`s scale, ripeness of the client, good attitude to deadlines and budget, team`s experience and many other factors can influence to the efficiency of different methods.

Without claim to flexibility we`d like to present our model of classification of projects. This report will show the evolution of the projects, their classification and management model on the example of one IT department. 




{{ comment.DateCreated | date: 'dd.MM.yyyy' }}
Found a mistake?