Our site uses
cookies.
If you are using the site, you give you consent to use cookies, according to current browser settings.
Got it
IT Managers
See what work of IT managers looks like. Check what are the
average salaries of IT managers.
Find out what are the most
popular project management methodologies.
Scrum has become key in the project world, taking the lead among frameworks/methodologies. The advantage is significant - regardless of the company's size, agile methods surpass waterfall methods.
Proper implementation of agility can reflect the growing maturity of companies engaging in project activities. So when do we support ourselves with waterfall methodologies? When we have to. For example, in situations requiring longer decision paths or predefined procedures.
The Prince2 is dead, long live Waterfall! Only 7% of respondents from large companies and 2% from very large ones choose the very popular Prince2 methodology in the public sector. With other variations of Waterfall, it is more stable, as they remain on the podium, albeit in the last place. Increasingly, hybrid solutions are being used, combining the formal requirements of organizations with agile elements of project teams.
Scrum, while fashionable, is not the answer to all project needs. The initial excitement has somewhat faded, and projects that are not suitable for adaptation to this methodology's realities may often trap us in "patho-scrum" and cause more harm than benefit.
Approach everything with common sense. Experiences from Totalizator Sportowy show that it is worth building the project structure according to internal regulations, thereby ensuring proper reporting. At the same time, let's leave it to Project Managers to freely choose the methodology that, according to their knowledge and experience, best meets the needs and specifics of the project.
Agility makes sense and brings real value, but only when it is implemented thoughtfully and tailored to the actual needs of teams and organizations.
Scrum has become key in the project world, taking the lead among frameworks/methodologies. The advantage is significant - regardless of the company's size, agile methods surpass waterfall methods.
Proper implementation of agility can reflect the growing maturity of companies engaging in project activities. So when do we support ourselves with waterfall methodologies? When we have to. For example, in situations requiring longer decision paths or predefined procedures.
The Prince2 is dead, long live Waterfall! Only 7% of respondents from large companies and 2% from very large ones choose the very popular Prince2 methodology in the public sector. With other variations of Waterfall, it is more stable, as they remain on the podium, albeit in the last place. Increasingly, hybrid solutions are being used, combining the formal requirements of organizations with agile elements of project teams.
Scrum, while fashionable, is not the answer to all project needs. The initial excitement has somewhat faded, and projects that are not suitable for adaptation to this methodology's realities may often trap us in "patho-scrum" and cause more harm than benefit.
Approach everything with common sense. Experiences from Totalizator Sportowy show that it is worth building the project structure according to internal regulations, thereby ensuring proper reporting. At the same time, let's leave it to Project Managers to freely choose the methodology that, according to their knowledge and experience, best meets the needs and specifics of the project.
Agility makes sense and brings real value, but only when it is implemented thoughtfully and tailored to the actual needs of teams and organizations.