Wednesday, July 8, 2015

Adopting an Agile Approach to Project Management - Common Misconceptions About Agile

Full Course: https://www.udemy.com/adopting-an-agile-approach-to-project-management/?couponCode=PROMONOW

Organizations across the world are using agile project management to get superior results. But this doesn't mean that the move from traditional to agile project management will be easy. And, one of the main challenges is overcoming the various myths and misconceptions about what an agile approach involves.
Four misconceptions about agile project management practices are especially common:
Agile project management can't work with other plan-driven or process models
Agile project management requires no documentation
Agile project management is specific to software development, and
Agile projects don't require planning
Can't work with other models
A common misconception about agile project management is that the practices it includes can't work together with other plan-driven or process models.
Many people assume there's no middle ground between traditional project management approaches such as waterfall and full agile project management, but this is incorrect.
Requires no documentation
Agile project management emphasizes the importance of face-to-face meetings and the value of working software over comprehensive documentation.
This has led to the myth that agile project teams don't create or use any documentation, and instead work completely informally. And, this is one of the most widespread myths about agile project management.
Specific to software development
It's a misconception that agile project management is specific to software development. Although  it may have started out as an approach to software development, it has evolved into various well-defined methodologies that can be applied to other types of high-change projects.
Projects don't require planning
A misconception about agile projects is that they don't require planning.
It's true that agile project management is a break from plan-driven development – in which the focus of management is sticking to a project plan – and that, as a member of an agile development team, you're unlikely to use detailed work breakdown structures or Gantt charts.
However, all agile methodologies involve planning at various points. (...)

Full Course: https://www.udemy.com/adopting-an-agile-approach-to-project-management/?couponCode=PROMONOW

No comments:

Post a Comment