Agile project management is useful when teams need short feedback cycles, iterative delivery and the ability to adapt as they learn. It is not automatically superior to predictive project management, and it does not mean working without plans, documentation or governance.<\/p>\n
Project Management Institute research published in 2024 found that project teams can perform similarly using predictive, hybrid and agile approaches. The more useful question is therefore not \u201cWhich methodology wins?\u201d but \u201cWhich way of working best fits this project\u2019s uncertainty, constraints, stakeholders and delivery environment?\u201d<\/p>\n
Source: PMI Pulse of the Profession 2024<\/a><\/p>\n Agile emerged from software development but its underlying ideas have influenced many forms of product and project delivery. Agile approaches generally favour short feedback loops, incremental delivery, close stakeholder collaboration and adaptation as new information becomes available.<\/p>\n Scrum is one specific framework for complex work. Kanban and other approaches use different structures. An organisation can also combine predictive and agile practices in a hybrid model.<\/p>\n The current official Scrum Guide was released in November 2020. It defines Scrum as a lightweight framework founded on empiricism and lean thinking<\/strong>.<\/p>\n Its three empirical pillars are:<\/p>\n Scrum uses an iterative and incremental approach to improve predictability and control risk. The Scrum Team is cross-functional and self-managing, with one Product Owner, one Scrum Master and Developers. The current guide describes the team as typically ten or fewer people.<\/p>\n Source: The 2020 Scrum Guide<\/a><\/p>\n The 2020 Scrum Guide strengthened the connection between each artefact and a commitment:<\/p>\n These commitments matter because Agile without clear goals and quality standards can become a stream of activity rather than disciplined delivery.<\/p>\n Agile teams plan continuously. The difference is that they avoid pretending that every detail can be known accurately at the start of complex work.<\/p>\n Planning can occur at several levels:<\/p>\n As evidence changes, the plan changes. That is adaptation, not absence of discipline.<\/p>\n Predictive approaches can work well when requirements and delivery steps are relatively stable, dependencies are understood and a detailed sequence can be planned with reasonable confidence.<\/p>\n Examples may include work with:<\/p>\n This does not mean predictive projects cannot adapt. It means more of the delivery logic is established upfront.<\/p>\n Agile approaches are often useful when:<\/p>\n PMI\u2019s 2024 research found increased use of hybrid approaches, which combine elements of predictive and agile delivery. It also found significant differences by industry.<\/p>\n Construction respondents reported much greater use of predictive approaches than agile ones, while financial services and information technology showed higher use of agile and hybrid approaches. That supports a fit-for-purpose view rather than a universal methodology rule.<\/p>\n Hybrid delivery can be appropriate when, for example, a programme has fixed governance, procurement or infrastructure milestones but contains digital components that benefit from iterative development and user feedback.<\/p>\n A team can hold daily stand-ups and two-week Sprints without being meaningfully agile.<\/p>\n Warning signs include:<\/p>\n In Scrum, the Product Owner is accountable for maximising product value and for effective Product Backlog management. If the person called \u201cProduct Owner\u201d has no authority to order priorities or clarify the Product Goal, the organisation has created a title without the corresponding accountability.<\/p>\n The solution is not unlimited authority. Governance still matters. The organisation needs to define which decisions belong to the team, which belong to the Product Owner and which require higher-level approval.<\/p>\n Scrum Teams decide internally who does what, when and how. That does not remove organisational objectives, budgets, regulatory obligations, risk controls or leadership accountability.<\/p>\n Good governance defines boundaries and outcomes while allowing the team enough autonomy to solve the work inside those boundaries.<\/p>\n A Sprint is not successful merely because many backlog items moved across a board. Work should meet an agreed Definition of Done before it is treated as a completed Increment.<\/p>\n The Definition of Done can include relevant quality, testing, documentation, security or compliance expectations. This is particularly important in regulated or high-risk environments where \u201cmove fast\u201d cannot mean bypassing required controls.<\/p>\n The Agile Manifesto values working outcomes over comprehensive documentation, but explicitly recognises value in documentation. The practical question is how much documentation is needed to support delivery, maintenance, compliance, knowledge transfer and decision-making.<\/p>\n Highly regulated sectors may need substantial documentation. Agile delivery changes when and how that documentation is created; it does not make legal or regulatory obligations disappear.<\/p>\n Useful project and product measures depend on the work, but can include:<\/p>\n Velocity can help one team forecast its own future work. It should not be used as a productivity league table across teams because estimation practices differ.<\/p>\n Adopting agile delivery changes decision rights, planning rhythms, management behaviour, team boundaries, funding and stakeholder involvement. Treating it as a software-tool rollout is therefore unlikely to be enough.<\/p>\n Leaders may need to change how they:<\/p>\n Project environments across the GCC and Africa vary enormously. A Dubai fintech, Saudi government programme, Kenyan technology company and Nigerian infrastructure project should not be expected to use the same delivery model merely because they are grouped into broad regions.<\/p>\n Relevant contextual questions include:<\/p>\n The methodology should follow the work rather than a regional stereotype.<\/p>\n Before choosing predictive, agile or hybrid delivery, ask:<\/p>\n The answers may point to a single approach or to a deliberate hybrid.<\/p>\n MATSH\u2019s Agile Project Management Foundation Training<\/a> can help professionals understand iterative delivery and Agile ways of working. Organisations should still choose methods based on project characteristics rather than adopting Agile as a universal policy.<\/p>\n Not universally. PMI\u2019s 2024 research found similar overall project performance across predictive, hybrid and agile approaches. Fit between the approach and the project environment matters more than methodology branding.<\/p>\n No. Agile is a broader family of values and approaches. Scrum is a specific framework for complex work with defined accountabilities, events, artefacts and commitments.<\/p>\n The official 2020 Scrum Guide says a Scrum Team is typically ten or fewer people. It should be small enough to remain nimble but large enough to create useful value within a Sprint.<\/p>\n No. Agile encourages teams to avoid unnecessary documentation, not to ignore useful, contractual, operational or regulatory documentation.<\/p>\n Hybrid delivery is useful when different parts of a project have different levels of uncertainty or governance. For example, fixed contractual milestones may coexist with iterative product development inside the same programme.<\/p>\n Agile project management is useful when teams need short feedback cycles, iterative delivery and the ability to adapt as they learn. It is not automatically superior to predictive project management, and it does not mean working without plans, documentation or governance. Project Management Institute research published in 2024 found that project teams can perform similarly…<\/p>\n","protected":false},"author":1,"featured_media":9133,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[404],"tags":[],"class_list":["post-9132","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-professional-development"],"_links":{"self":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts\/9132","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/comments?post=9132"}],"version-history":[{"count":1,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts\/9132\/revisions"}],"predecessor-version":[{"id":9886,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/posts\/9132\/revisions\/9886"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/media\/9133"}],"wp:attachment":[{"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/media?parent=9132"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/categories?post=9132"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/matsh.co\/en\/wp-json\/wp\/v2\/tags?post=9132"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Agile is an approach, not a synonym for Scrum<\/h2>\n
What Scrum actually says<\/h2>\n
\n
Scrum\u2019s key commitments<\/h2>\n
\n
Agile does not mean no planning<\/h2>\n
\n
When predictive approaches can be the better fit<\/h2>\n
\n
When agile approaches are useful<\/h2>\n
\n
Hybrid approaches are increasingly normal<\/h2>\n
Common failure mode: adopting ceremonies without the operating model<\/h2>\n
\n
Product Owner authority matters<\/h2>\n
Self-managing does not mean unmanaged<\/h2>\n
Definition of Done protects quality<\/h2>\n
Agile is not anti-documentation<\/h2>\n
Measure outcomes, not ceremony compliance<\/h2>\n
\n
Agile transformation is an organisational change problem<\/h2>\n
\n
GCC and African organisations should adapt to organisational context, not stereotypes<\/h2>\n
\n
A simple method-selection checklist<\/h2>\n
\n
Develop project capability with MATSH<\/h2>\n
Frequently asked questions<\/h2>\n
Is Agile better than Waterfall or predictive project management?<\/h3>\n
Is Scrum the same as Agile?<\/h3>\n
How large should a Scrum Team be?<\/h3>\n
Does Agile mean no documentation?<\/h3>\n
When is hybrid project management useful?<\/h3>\n
Sources<\/h2>\n
\n