If your project is steering towards a tsunami of people who are unaware of upcoming changes – this webinar is for you. If you are leading and/or supporting a large-scale transformation project where people must be informed for change to be successful, you don’t want to miss this! Discover how business leaders are informing thousands of people about upcoming changes who vary in geographic locations and departments – in time for successful change!
1684 items found
Moving to a more agile way of working is not easy. Most infrastructure projects are still delivered via a linear Waterfall approach of design, build, test, and commission through large and often disparate teams. Within these projects, PMOs are indispensable for Project Managers in ensuring they have the right resources, achieve progress towards goals, and deliver expected benefits.
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.
The presentation articulates the needs of the enterprise to transition from “cybersecurity” to “cyberresiliency”. Cyberresilience refers to the ability to constantly deliver intended outcomes despite negative cyber events. It is keeping business intact through the ability to effectively restore normal operations in the areas of information systems, business functions and supply chain management. In simple terms, it is the return to a normal state.
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.
This webinar goes back to the beginning. It explores where project management came from, and why. It examines the essential principles on which it was developed. And it asks whether those principles would still be relevant if we were starting it all again.
We are each given a score and four hours each day - with the exception of frequent fliers who sometimes get more, and sometimes get less, depending on whether they're flying East or West. It's a rare individual who has more time than they need. Most of us would willingly buy more time if such a thing were possible, but we can't... so? How do we use what we have as efficiently as possible? Yes, this session will cover some of the more obvious solutions, but as always, I hope to bring some lesser used strategies and tactics to the discussion. What are some that immediately come to mind? The Virtue of Laziness, Leverage, Drastic measures, Pretend you were to die tomorrow!, a Stoic approach, some simple arithmetic, and of course... some surprises. If you have time to watch this presentation, then the chances are pretty good you don't need to do so. But if you don't have the time to watch, you really should!
This webinar will describe two tools that project managers can use in rescuing distressed projects, team members, and stakeholders. Project managers can use the Breathing-Bleeding-Broken-Consciousness model to stabilize the project emergency and buy time to fix the project problems. The Perception-Appraisal-Motivation-Action model aids the project manager in fixing communication problems with the project team and stakeholders.
I’ve burned a lot of time - and career currency - trying to create that perfect project plan and I can tell you for a fact that those plans did not eat that first punch any better than plans created in much less time. Projectize is a bit of a mouthful but it’s a simple concept at heart: a 4-step method for getting from concept to project blueprint in days (not weeks.) 1. Unpack the work 2. Create a checklist 3, Size the work 4. Plan the work
The four knowledge cornerstones of project risk management are: Project Management(how to run a project); Earned Value Management (how to measure project performance); Risk Management (how to identify and mitigate risks); Subcontract management (how to manage subcontractors). Project risk management is essential today and for future work challenges to manage a successful project. This webinar focuses on earned value management, the second knowledge cornerstone.