This session will discuss the use of Agile Techniques in implementing Organizational Change Management. This presentation will be focused exclusively on Organizational Change Management using the Disciplined Agile process-decision toolkit to realize the benefits.
181 items found
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.
VUCA , an acronym that stands for Volatility, Uncertainty, Complexity and Ambiguity, has become a buzzword in management and business circles. It has added a new dimension to management principles and practice this requires a fresh approach to adapt to the new situations that are emerging in business and industry. Over the years project management standards have been adapting to industry practices and through its revisions introducing new topics and areas of knowledge. The objective of the standards has been to present information that is relevant and valid for today's operations. Various project management standards have been studied to assess if the four parameters of VUCA have been included and discussed and if they are adequate for the practising project manager to function effectively.
There is an increasing recognition that embracing Agile (either adopting several Agile practices or going through a complex Agile transformation) becomes mandatory in these times of a rapidly changing market place. An Enterprise Agile Transformation is, however, a deep organizational change for which “copy & paste” does not work. This presentation explains why there is no one single recipe for Agile transformation and illustrates through real life examples the crucial role that culture plays in any such an endeavor.
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.
How Project Management Provides a Foundation to Homebrewing: Project manage your way to better beer!
This webinar will detail how project management skills can be leveraged to learn home brewing, set up a home brewery, and then go on to master the science of beer brewing. In addition, the webinar will detail the vital role project management played in the history and evolution of beer making.
Disciplined Agile Delivery is the 'new' Agile framework adopted by PMI. Although currently not as popular as Scaled Scrum, Disciplined Agile can be seen a competitor to Scaled Agile Framework (SAFe), another framework presenting itself as an evolution of Agile/Scrum to the Enterprise Level. This webinar is an analysis of Disciplined Agile from a Project Manager's point of view - how Disciplined Agile Delivery (DAD) can be used to deliver projects, not necessarily software development projects. The framework is analyzed from the Agile Enterprise perspective looking at how DAD combines 'old' practices, like Lean, with Agile Manifesto values and principles. The webinar also explores how the PMBOK® Guide can augment DAD to become an Enterprise level, industry agnostic Agile delivery option.
Per the Agile Business Consortium, business agility allows businesses to adapt quickly to market changes; respond rapidly and flexibly to customer demands; adapt and lead change in a productive and cost-effective way without compromising quality; and continuously be at a competitive advantage. The primary reason for moving to Agile is to achieve faster business value and keep you ahead of the competition. Agile is built for change - fundamentally, it is about creating Business Agility. It enables the enterprise to deliver projects more efficiently, with relentless focus on business value and providing the highest return on investment. Whether it is a software project, a new service offering or a new product, Agile’s twelve principles and three pillars (transparency, inspection, adaptation) are designed to reduce money spent on undesirable or unusable features which were built based on outdated requirements.
XP, aka Extreme programming, was the first Agile Framework widely used after the publication of the Agile Manifesto. Focused on software development, XP was the beginning of the Agile revolution in software project management. In XP, the Project Manager is not seen as an enemy of the agile development team, and traditional roles are still present. Very popular in the early 2000s, XP basically disappeared from the Agile landscape and 'survives' by some of its practices which are (mis)used by frameworks that adopted them. This webinar relays the author's experience with the success of XP in a 'perfect storm' environment: a software company developing a complex and innovative product when porting a legacy system to C# by a team of analyst programmers working closely with the users under the supervision of a 'command and control' Project Manager. The webinar will also describe the lessons learned in the journey to Scrum and then hybrid 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.