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.
131 items found
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.
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.
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.
Agile is often advertised as the silver bullet in the training class that will deliver "twice the scope in half the time." In principle, the topic of this webinar, agile implementation failures, may be unexpected from someone who used Agile practices long before they were called Agile and who was a champion of adoption of XP and Scrum in the early 2000s when Agile adoption was considered "crazy." One of the fundamental principles of Agile is to fail fast, learn, and recover. But accepting failure is not always as easy as it seems. When a manager “motivates” his team with "failure is not an option" or expects the Project Manager or the Scrum Master to be a "pusher" rather than a servant leader, learning from small mistakes becomes an important process. This webinar presents several situations when Agile failed, analyzing the root cause and what could have been done differently to avoid failure.
Agile transformation is an Organizational Change, it follows the rules of any Business Transformation and needs Executive support in order to succeed. This webinar is a presentation of the Agile transformation that the author was involved in, focusing on the role and the importance of executive support in Agile adoption.
Robot Process Automation (RPA) is one of the recent practices that is usually combined with Agile adoption as part of Digital Transformations. Sometimes implemented as the 'old' workflows, RPA can easily become the famous GIGO (Garbage In - Garbage Out), speeding-up unnecessary processes rather than providing value for the business. 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.
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.
Scaling Agile practices beyond software development teams and IT departments is a growing trend, and the Agile Enterprise is a reality rather than a goal. However, the transition from planned approach to Agile is a painful change, and PMO can provide support for Agile rather than be perceived as an archaic team supporting “waterfall”. Once the organisation decides to adopt Agile, the PMO should be the champion of the transformation process, providing support to the Project Managers with less experience with Agile delivery while ensuring that governance requirements are met. This webinar is a summary of the presenter’s experience in organisations transitioning to Agile.