Agile, the "new" product development approach started in the 1970s as an alternative to Lean Six Sigma, is now “scaling-up” by reverting to traditional practices like Kanban, Theory of Constraints, Voice of Customer, Kaizen, etc. Another area that is often included in scaled Agile is Emotional Intelligence. Unlike other Agile practices, stand-up, and meeting facilitation, Emotional Intelligence is not something that people can necessarily learn in an empiric way. It is a science, a very specialized domain that can't be easily simplified to the level of knowledge and experience of a specific role. This webinar is a Project Manager's view on how Emotional intelligence can be and is used in practice. It contains examples from the real world of how having Emotional Intelligence knowledge and skills can help to deliver a project.
160 items found
This webinar looks at the #noestimate approach, a revolutionary approach seen by some Agile teams as a waste reduction, team morale improvement and of course the elimination of one of the most dreadful activities in "waterfall". The webinar is based on the presenter's practical experience as a Project Manager and Development Manager, including real life examples of the benefits and pitfalls of estimation and lack of estimation.
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 Agile Coach is a relatively new role; it is not very well defined and often overrated. From the first concept of 'coach' introduced in Extreme Programming (XP) which was more of a system architect to the Scrum Master in the service of the Team and the organization, the role morphed in many organizations to a pure consulting role. Most modern Agile frameworks are created as empirical approaches based on a very simple principle: fail fast, learn faster. What is the role of an Agile Coach in an Agile transformation? What skills and experience are required to add value to the process? These questions among others will be addressed in this webinar.
One of the most interesting aspects of Agile adoption at an Enterprise level is Governance. Perceived by many teams as useless red tape and one of the major impediments for Agile adoption, correct governance can have a very positive impact on in the Agile Enterprise. Rather than being a micromanagement tool, governance can provide visibility on the benefits of Agile adoption as well as creating an environment of trust and collaboration. This webinar is an introduction to SMART governance, the type of governance that will support Agile adoption at the enterprise level rather than preserving the command and control culture.
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.
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.