Ask many people what a business analyst does and they’ll tell you it’s about documenting requirements. Is it?
In this presentation, Simon will demonstrate a practical and transparent approach to risk assessment, analysis and management, that allows risk to be usefully described and incorporated in the change process to increase awareness and ensure achievable benefits, costs and timescales. The presentation focuses on the project manager’s role in ensuring that the team collaborate and honestly express their beliefs about the risk to the benefits, costs and time-scales of the change initiative, as well as the project manager’s role in using the risk assessments to set realistic expectations and drive the change efficiently and with an awareness of the risk it faces.
In this interactive and engaging talk you will learn about some of the principles that have led the Technology Innovation and Consumer Experience team at Thomas Jefferson University and Jefferson Health System to analyze, design, develop, release, evaluate, and support innovative enterprise applications with small teams in less than 30-days.
Extreme projects feature high speed, high change, high complexity and high stress. As more projects continue to fall into the extreme zone, successful project and program managers will shift from inhibiting change to proactively creating change and responding to change.
Save Time With Tools And Templates
This presentation looks at a brief history and a definition of agile project management; looks at factors that affect selection of collaboration tool-sets; and looks at key features of project portfolio management tool-sets and at making PPM a business process.
Learn From Others
PMOs are popular and have a lot of potential, but too often fail within organizations. PMOs have unique challenges as an organizational unit—which require them to become more agile. Keeping things simple and adding value in new and different ways are key success factors.
Not every project involves teams with high levels of project execution experience. When low experience levels collide with agile, we need to be aware of the implications.
|A.||Since agile was conceived in 2001 in Snowbird, Utah, it is 100% American in origin. The rest of the world had never tried these practices until the results of this famous meeting were released through a series of speeches, articles and conversations.|
|B.||Agile principles rest on the behaviors Douglas McGregor believed to be basic to most workers, called Theory X. Because it suggests that people dislike work and try to avoid it, the more lax workplace of an agile team tricks them into thinking they are in management.|
|C.||Dr. W. Edwards Deming developed the earliest agile-like philosophy, which he called the Hierarchy of Needs. If a manager can meet all of the needs for the employee, productivity will soar. If even one is left unfulfilled, project outcomes will be subpar.|
|D.||Agile actually is an outgrown of the Japanese motivational theories of Dr. William Ouchi’s “Japanese Management” style from the 1980s. By now, the concepts have been well tested and proven to be effective in the modern-day workplace, first in Japan and then in other locations around the globe.|
It seems as if the larger the agile program, the bigger the planning--but that kind of planning only works for some programs. What can you do? Instead of big discontinuous planning, consider small continuous planning.
If you ask a group of individuals what benefits they expect to achieve by adopting agile methods, you’ll usually hear “faster delivery,” “higher quality,” “cheaper” and “lower risk.” Out of these, “faster” is the most common. Faster delivery can be elusive; the benefit of “cheaper,” however, may be illusory.
The use of traditional empirical project management tools can be used in a simple way to manage and control project deadlines and costs without losing the flexibility of agility. In this article, we are going to mix a traditional technique with agile management using a simple practical example.
The webinar Dude, Where’s My Control?! Transitioning from a Project Manager to a Scrum Master was packed with information, and here the presenter covers some questions and answers that came out of that session.
The words “agile project management” are being used in the industry to describe a new approach to how project management is conducted. The industry and company leaders need to fully understand how project managers can be brought into the agile world to ensure cohesion between these two disciplines.
"Hybrid agile" sounds like a great middle ground between our established ways of doing things and trendy agile methodologies. We keep our current employees happy since they won’t need to abandon their old skills and habits. The only problem? It doesn't exist.
A more nuanced approach to agile and waterfall has started gaining traction. Once referred to as “structured agile,” more practitioners are combining both methodologies. This article provides a framework for how ScrumMasters and project managers can work together using hybrid principles.
Ask a Question