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.
136 items found
Although many practitioners believe that Agile started in software development, Agility started long before the publication of the Manifesto for Agile Software Development (aka Agile Manifesto) at the Enterprise level. Started as an alternative to planned frameworks, in particular as an alternative to the process standardization imposed by Lean Six Sigma, Agile is seen by the Project Management community as 'the future.’ However, none of the Agile frameworks was developed as a generic Project Management approach. Most, if not all, of them originated as software delivery framework with the 'developer' role as the core of an Agile Team.
Nowadays, digital transformation is a hot topic. Every organisation has their own initiative to introduce new tools aimed mainly at enhancing mobility and collaboration. However, the concept of digital transformation is not new; it has been done several times before, most notably with the adoption of the Personal Computer and the .com revolution. Digital or not, transformation means disruptive change and challenges to organisational culture. Agility, rather than being the driver, should support digital transformations by contributing to the mindset changes, adding flexibility to processes, and last but not least supporting empirical learning.
Agile is sometimes introduced as a cheaper 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 and shouldn't track the delivery in the same way. Agile is a new approach, and traditional project finance management may not be relevant or can become an impediment to agility. Agile is or should be based on trust, and in an Agile organization, most of the financial planning and reporting should not be necessary. However, very few organizations have the necessary conditions to abolish tight financial management. This webinar will propose a few financial management approaches for Agile projects, highlighting the necessity as well as the challenges of each of the proposed models.
Agile found its way into project delivery with many certifications attempting to define various agile roles, some of them project-related. Although the Manifesto for Agile Software Development is against specialization in an Agile Team, all the traditional roles have become "Agile" by sticking the "Agile" label to the old job title: for example, Agile Project Manager, Agile Tester, Agile Business Analyst, "Agile" Scrum Master and the "Agile" Coach. Most Agile frameworks, like Scrum, Crystal, and XP, were conceived by developers for a small team of software developers, and the Project Manager role is usually omitted. Unlike 'specialized' Agile Project Manager certifications, PMI's Project Management Professional (PMP)® remains the industry benchmark for the Project Manager role, providing an increased focus on Agile and Hybrid practices without compromising the knowledge required to manage projects that can't or won't use Agile practices. This webinar is a comparative analysis of various roles in a project that uses agile practices and how various project roles should change to adapt to a new way of delivering projects.
The work "project" is often used as a synonym of "waterfall", "command and control," and in general everything that is old and unnecessary. Some even use the term "Scrum project", expanding the role of the Scrum Master to a mini Project Manager. The tag, #noprojects, in combination with other "#no" like "#noestimates" is sometimes used as an excuse for lack of planning, documentation, and discipline. This webinar is an analysis of the "#noprojects" concept, presenting the author's view and experience with projects and a less governed approach to delivery. He explores the relationship between project and product development and the challenges of growing from a small team of "developers" to the real enterprise level.
This webinar is a review of the resurgence of Lean principles describing why and how Lean evolved and why it failed to adapt to the modern market. Practices like Kanban, Kaizen, Theory of Constraints, Servant Leader, to name just a few, are not new. The second part of the webinar is an analysis of Lean vs Agile using DevOps, RPA and AI - three of the 'new' practices seen as Agile evolution.
Since the term, agile, grew popularity in the second decade of the 21st century, Risk Management was one of the strong selling points of various agile frameworks. According to agile surveys, reducing risk is one of the main reasons for agile adoption. However, none of the agile frameworks provide guidance on Risk Management. Most of them are limited to a simplistic view that by delivering in small increments risk is limited to the value of a single sprint. The reality is far more complex, and it is not limited to coding or technical skills. A project is dependent on context, on organizational culture, and last but not least, on people's desire to work as a team and succeed. This webinar is a brief introduction to how important Risk Management is, how it can be done in agile, and why risk, especially in Agile, should not have a negative connotation. Real-life examples will be used to illustrate how the Project Manager, Scrum Master, and the whole project team can take advantage of Risk.
Scaled Agile Framework (SAFe) is considered by some as the most suitable option to scale Agile from a software development team to a large program of work. Although presented as an Agile framework, SAFe includes many practices from Lean and ITIL, and it is considered by some agilists as too formal to be Agile: a re-branded 'waterfall'. This webinar is an analysis of SAFe from a project, program, and portfolio delivery point of view. The webinar looks at the SAFe practices used before the publication of the Manifesto for Agile software development (Agile Manifesto), especially the Lean ones. The presenter will provide recommendations on how SAFe can be used in projects that are not software development related, in combination with the PMBOK® Guide, to provide Agility for 'near perfect' product development processes.
Scaling Agile has been a hot topic in the last 3 to 5 years. Organizations that have successful software deliveries are trying to spread the success of the Scrum Team(s) beyond technology departments. On the other hand, laggards, teams and organizations that didn't embrace Agile when it became clear that it is the future, are cutting corners and launching mammoth programs to "do" Agile. Scrum, the core of the most recent "scaled" frameworks, was designed for teams of less than 10 people developing software products. Even at that size, it is "difficult to master", according to its authors. This webinar takes a look at Agile scaling from both perspectives: agile software development created for small homogenous teams AND agile manufacturing conceived in the last century for large companies as a replacement to Lean. The webinar is based on the author's 30+ years’ of experience as a practitioner. From manufacturing to software development and then to projects, this webinar is an analysis of the famous mindset change and the challenges and lessons learned while doing it and helping others to do it.