Introduction
In 2001, the term 'agile' emerged to represent a family of lightweight approaches to software development. Over a decade later, agile has become mainstream, reshaping how organizations deliver benefits to their customers. It is now utilized beyond IT projects, introducing a shift in project management approaches.
Origins of the Hype
Agile's roots lie in IT, primarily applied on a small scale where existing software products were enhanced. Local successes fueled its growth, with methods like Scrum, XP, and DSDM (Dynamic Systems Development Method) gaining traction in the UK. In subsequent years, Agile Project Management methodologies, such as AgilePM, have started gaining broader acceptance.
Where is the Confusion From?
Agile faced challenges in three areas: its application in 'project' environments, its focus on IT, and the scalability of its techniques. These challenges prompted a reassessment of its holistic nature.
Is Agile a Method or a Philosophy?
Agile is a philosophy, a mindset, broad and covering various aspects from collaboration to technical details like writing requirements in the form of 'user stories.'
Towards Agility
The agile philosophy extends beyond IT, reaching organizational levels. However, its versatility brings a challenge: the diverse components of agile are often misunderstood.
Many Techniques are not Agile
An illustration of this phenomenon is the perception that burndown charts, user stories, estimation games, MoSCoW prioritization, pair programming, and various tools and techniques are commonly associated with agile practices. Nevertheless, these areessentially a collection of widely-used techniques applicable to both agile and non-agile projects.
Agile or Waterfall Dichotomy
The misconception that one must choose between agile and traditional project management methods, such as PRINCE2, fuels confusion. This misinterpretation ignores the flexibility of approaches.
Misconceptions about Agile
Two significant misconceptions surround agile: the belief that it is a holistic project management approach (rather than a set of product delivery techniques) and the misconception that traditional project management mandates a waterfall approach.
Is Agile Only of Limited Use?
As agile matures, its applicability expands beyond small-scale IT contexts, making it a potential game-changer.
The Big Agile Irony
An irony emerges as agile matures: incorporating traditional project management basics with agile principles, creating a balanced approach termed 'corporate strength agile.'
Solving the Problem - Where to Start
Understanding that agile primarily operates at the 'solution delivery' level is crucial for success. Changes are required at project management and governance levels, acknowledging agile's deliberate departure from 100% solutions.
Senior Management Be Aware
Senior management must comprehend the reasons for adopting agile and proactively manage its introduction to prevent uncontrolled spread.
What Should a Project Manager Do?
Project managers need to upgrade their skill sets for the transition towards greater agility. Choosing agile training and accreditations wisely, considering the broader agile picture, is essential.
Summary
Agile is not a new project management method but a long-lasting philosophy. Its success depends on adoption, implementation, and practice. In the current economic climate, those embracing agile effectively will reap rewards, while those who do not may face challenges.
Original source: https://agilekrc.com/agile-bas...