Chat with us, powered by LiveChat
Agile vs traditional project management - CITI
32969
post-template-default,single,single-post,postid-32969,single-format-standard,mega-menu-top-navigation,ajax_fade,page_not_loaded,,qode-title-hidden,qode-theme-ver-10.1.1,wpb-js-composer js-comp-ver-5.6,vc_responsive,mob-menu-slideout-over,yellow-block-header

Agile vs traditional project management

Agile vs traditional

Agile vs traditional

This section of learning is aimed at personal development and skills. All of these knowledge and skills based learning titles are to help you communicate, become more confident and support your development in Change and projects delivery. These are the foundation level byte sized learning sessions however, pertinent to all. All sessions will require some reflection, participation and embedding of techniques in the real world to ensure you and your organisation gain value from the learning intervention.

Content

The Agile vs traditional project management session will help participants understand the four key lifecycles (product, product development, project management and investment).  The appropriate application of iterative and predictive approaches.

By the end of this session participants will be able to:

  • identify an appropriate product development lifecycle pertinent to your team and situation
  • explain the purpose of a product development lifecycle
  • understand the difference between iterative and predictive lifecycles.

Your trusted partner

CITI taking you beyond method

Not quite what you were looking for…

  • The Agile vs traditional project management session will help participants understand the four key lifecycles (product, product development, project management and investment).  The appropriate application of iterative and predictive approaches....

  • Definition of critical path.  Introduction and explanation of dependencies; types (SS, FS, SF, FF) and sorts (hard, soft, malleable) and dependency/flow diagrams....

  • Delivering results in project management (outcomes) are dependent on the two factors of product and user reception. Progress can only be reliably measured in terms of results (delivered or enabled) arising from related products....

Tell me more!