An agile methodology need not be considered the antithesis of a structured project management approach. In fact, agile-run projects can satisfy both the innovators and traditionalists within an organization when certain practical principles are incorporated and communicated. Here are some field-tested examples.
While agile methodologies are becoming a popular choice for managing projects, they are not appropriate for all projects or business environments. General characteristics of agile projects are smaller teams, shorter iterations (or releases) and increased customer interactions, according to the Agile Manifesto. On the technical side, some characteristics are test-driven development and continuous code integration.
That said, it is not always easy to determine if a project is a good candidate for an agile methodology. Ask yourself these questions to help understand whether your project environment truly suits an agile methodology:
·Does your project sponsor have a highly innovative personality style, or change his or her mind frequently?
·Does your client’s market require frequent changes to keep interest levels high?
·Is providing working software early critical to the project’s or relationship’s long-term health?