155 items found
The Agile Enterprise: Using Risk Management Standards - A Look at the Role of PMI and ISO Standards in Agile
Most Agile frameworks developed for small software teams (relative to the size of an organisation) believe that adopting Agile is a Risk Mitigation approach and/or that in Agile risk is reduced compared with the traditional planned approach, wrongly limited to "waterfall" software development. Apart from the fact that there is no empirical or scientific evidence of that, most Agile practitioners can't or won't look at the dual aspect of risk (positive and negative), missing one of the significant benefits of Agile – opportunities management, or in other words, positive risks. Considering Risk Management from the Agile perspective, this webinar is a review of how Risk Management practices and standards can be scaled down and adopted by Agile Teams.
Robot Process Automation (RPA) is one of the recent practices that is usually combined with Agile adoption as part of Digital Transformations. This webinar analyzes the benefits of RPA, combined with Agile adoption, using a parallel with the introduction of robotization in manufacturing. It is also an analysis of how/if RPA and Artificial Intelligence can be used in Project Management to improve the project delivery process.
Agile is often 'sold' as a way to improve quality of products and services. One of the fundamental Agile principles is that continuous attention to technical excellence and good design enhances agility.
In an agile world, team members are empowered to make important decisions within the context of the behavioral architecture, without having to ask permission from supervisors or managers. But these supervisors and managers are coming from a lifetime of learning how to succeed in a hierarchical world, so they will need to leave behind those ingrained lessons. In order for agile to be successful at scale, leaders will need to change.
Agile is perceived as a better way of delivering projects, products, and services. Unlike the traditional approach of measuring the value delivered based on the planned deliverables, the budget spent, and meeting the critical milestones, Agile doesn't provide clear metrics that can be used to compare projects and delivery teams. Agile is a new approach, and traditional project benchmarking may not be relevant.
Agile Project Management requires some additional skills to be possessed by an Agile Project Manager. It does not only involve managerial skills but also requires more team-oriented and leadership skills. Agile Development is a value-driven model with focus on outcomes unlike traditional approaches which are plan-driven in nature and based on output.
With the proliferation of cloud-based self-service platforms, it is becoming increasingly commonplace for business to break free from the shackles that bound them to Information Technology (IT) strategy forever. While strategy is never a bad thing, it can be the slow-moving tanker that takes forever to change course, and in the age of agility, most companies have not aligned their strategy with agile principles, even less so IT. Shadow IT, as it is known, has many advantage. But it also creates many challenges.
Agile is a continuous improvement process in itself, but at the enterprise level, most of the Agile frameworks can’t be used for process improvement because the business area has very limited room for agility due to strong governance requirements or because of the culture and strong resistance to change. Process Improvement is a very well defined discipline that has tools and metrics that can easily be used to measure the benefits delivered by transition to Agile. This webinar presents some options for improving processes that have an Agile component but are not entirely Agile.
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.