The Agile Enterprise: The need for new roles and a new organization structure
The Agile Enterprise is a new type of organization. A collaboration-based environment where some of the ‘command and control’ roles are not only obsolete but also can be a roadblock for the Agile transformation. The natural fear of change combined with protecting privileges or the job itself resulted in labelling as ‘Agile’ roles that are not only not defined in any Agile framework but are also the core components of the “waterfall” approach. An “Agile” PM that manages an “Agile” project team where the “Agile” BA writes requirements (called now user stories) and then the “Agile” UX specialist designs the user interface and then the “Agile” Architect analyse the “User Story” and assigns it to the “Agile” Developer who will pass the “increment” to the “Agile” Tester (sometimes wrongly called “Agile” QA engineer) is not an uncommon “Agile” implementation. Agile is a new and better way of building products, a radically new approach with a single role responsible for the design, build (including testing) and deployment called “Developer” and one person responsible for requirements definition and prioritisation called “Product Owner”.
This webinar addresses what a real Agile Team should be with real world examples of Agile teams.
NOTE: You must watch videos in their entirety and all the way through to the end for our system to record your viewing activity accurately. Learn more about PDUs on ProjectManagement.com.